UPDATE: Once again, pinching myself to see if I am dreaming or not. I am making excellent progress on #nostr #safebox. Since the beginning of the project I have been building the component to work within the context of a command line interface (cli) app, I am now getting it to work as part of a web app. The last couple of weeks was sorting out a whole bunch of async issues - the cli app is synchronous, but the web app is asynchronous. I got everything sorted out so the component now works in both contexts. I am also ensuring NIP-60 compatibility and working on Lightning Multi-Path Payment working. The core concept of #safebox is that it exists ‘out there’ in the network, under the sole control of a private key. I am now bolting it into the backend of my openbalance.app so I no longer need to be a custodian for a Lightning wallet service. Everything is stored in the safebox. The most exciting part is that this approach makes custody suck less, because the user can use the command line interface independently and without involvement from the service provider to move funds and burn the wallet if necessary. True sovereignty. I am also exploring how to store private data - verifiable credentials and health data. I have the NIP-44 encryption working for storing funds and it works fine for any arbitrary data. The idea is that I can securely store, along with my funds, my critical private and health data independently of any data provider, replicated across relays to ensure availability. Anyway, still lots of work to do, but I am beyond excited with the possibilities and wanted to share. I want to thank @npub10pen...n34f for the support! Not yet ready for testing (aiming late Feb) but the repo is at the link below. https://github.com/trbouma/safebox