Minimize transport and resource binding.
Proof of *hood
Sharing some more of my design and architectural thinking for #nostr #safebox. The first diagram shows the main elements of the substrate capabilities, namely #Blossom, #Cashu, #Nostr, #Lightning, and #Bitcoin. Eventually all of this will be abstracted away from the users who only care about the safekeeping of their #Funds and #Record. The primary coordinating protocol I am building for #safebox is called #nAuth (you can see the interaction diagram on the next image). #nAuth is built on NIP-17, NIP-44, NIP-59 and extends NIP-47 (Nostr Wallet Connect). I have extended NWC to offer and accept records between safeboxes, and to send and receive payments between safeboxes, so that they don't have to drop down #Lightning to settle payments - they are all cleared using the #Cashu mints. In the end, my vision is very clear for #safebox (even though the engineering is hella complicated) - to give users the ability to safekeep and use their funds and records, to directly and privately transact with one another, and without necessary reliance on their app, device, or platform provider. It will take some time - I am rooting out the single points of failure, roots of capture, and invisible gatekeepers, but I see a path to create a global, generic capability that anyone (including agents) can use without permission. Onward!
First step of integrating imaging data into #nostr #safebox. Data is stored in Blossom servers.
Using emails as evidence is about as safe as using dynamite for kindling.
My first programmitic upload of a pdf to blossom. Seamless! https://blossom.getsafebox.app/df190ca609d76e5cc20619dfe49a986b506f17678ab8f3020afa2eb518c9594e
Starting my blob integration into #nostr #safebox Blossom is f***ing amazing!
Here is an updated block diagram of #nostr #safebox showing the networked resources used behind the scenes so that users can manage their funds and records. The QR code illustrates that a direct connection can be initated via a QR code. image