The significance of the #nostr #safebox architecture I am building toward is that the operators of 'networked resources' used by #safebox have no clue about the data that they are storing nor do they know about the transactions they are facilitating.
Further, these operators have no clue whether they are a singular resource, or part of a broader 'pool' or resources, that if they fail or withdraw service, it doesn't make any difference to the end user because someone else in the pool makes up the gap.
#Safebox has been designed from the ground up to use multiple: mints, relays and blossom servers riding on top of lightning and bitcoin for value transfer. If someone objects to bitcoin/lightning, eventually they will be able to bolt in their own anchoring and settlement layer for value transfer (stablecoins, fiat, whatever).
While there are still many REST/APIs in the mix, once I have the architecture and functionality stabilized, I will be replacing those APIs; the web app will become a hypermedia app and eventually, #safebox mobile OS apps will interact solely with nAuth/NWC protocols using JSON-RPC messaging.
In the end, the value proposition to the end user is still clear - having exclusing control over their funds along records with the freedom to transact and share with their choice of client.
Onward!
#nostr #safebox
