Signed Services, Media and Paid Work

Evaluate Nostr signing, event retention, supporting files and explicit payment states.

Updated Read as Markdown ↗

Evaluate one useful outcome

Start with one permission boundary: who may request a signature, retrieve a file or spend from a wallet? Demonstrate an allowed request and a refused one, then restart the relevant service and inspect what survived.

Keep signing, search, retention and wallet authority separate. The historical nsecbunker acceptance run does not certify a Nosternity search dashboard, NWC spending integration or every relay. For payment work, deliver separate payment, execution and evidence records with a recovery test.

Implementation basis: nsecbunker, Nosternity, Blossom and payment flows.

Check the capability matrix and return to all solutions.

Search documentation

Search titles, summaries and document paths.