SondreB
SondreB
Consider removing the :// part from the protocol handler. It is not a required element. Not sure if the Bitcoin specification it's derived from, used ://?
Consider using this JSON to display a list of relays that users can choose from: https://nostr.watch/relays.json We should also pick a few default ones. The relay management should support url,...
When multiple requests is active, it should not return immediately. The queued up requests does popup when first window is closed, but the handler logic has already processed.
We want to play along with the existing ecosystem around SSI and part of that is the CHAPI, Credential Handler API: https://chapi.io/
Aggregation of ongoing translation tasks to remember: ## REMOVE ~~Account.FeeRateTooLow~~
When the sign message action is triggered, the controller's constructor is called twice, meaning the controller is created twice for the action being triggered. This might be some routing etc....


 When this validation occurs, the "Continue" button should be disabled. If user continues, missing input error will be shown (since the logic did not select inputs for the tx).