# Signed Services, Media and Paid Work

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

Canonical HTML: <https://damagebdd.com/solutions/signed_services.html>



<a id="evaluate-one-useful-outcome"></a>

## 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.

-   [Remote signing policy](../articles/nostr_signing_governance.md)
-   [Nostr search evaluation](../articles/nostr_search_for_products.md)
-   [Supporting media evidence](../articles/verifiable_media_evidence.md)
-   [A paid verification job](../articles/lightning_api_economics.md)

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](../articles/damage_nsecbunker.md),
[Nosternity](../articles/nosternity.md), [Blossom](../articles/blossom_media.md)
and [payment flows](../payments.md).

Check the [capability matrix](../articles/features_current.md) and return to
[all solutions](index.md).