What’s cool about this approach, is that with your nsec the ‘wallet is the network’, or vice-versa the ‘network is the wallet’. This obviates any requirement to build a specialized ‘wallet app’ (still need a client/nsec app) or any special custodial wallet capability - it can be all done with events and relays! nostr:note14kvyjyhza7k074j8kyl953u7rswuyyzddaqmy2lkwn2ncnnjsawsy8emzt
Has anybody grokked TBD Decentralized Web Nodes? IMHO, this is the closest ‘competitor’ to #nostr
It works. I tested accessing the wallet across three different devices and two different OSs. This is truly nuts!!!
“When acquired, the money symbol expresses a certain uncertainty in the available possibilities of gain, and makes possible reduction of this complexity according to individual wishes. The decision about how this complexity will be reduced, how, when, and with whom, and for what purpose the individual spends his money has, in principle, no consequences for the social system – and that is one of the prerequisites for the institutionalization of general, individual freedom.”
ibid.
“Money is transferable freedom against a limited choice of goods. It guarantees this freedom abstractly, by means of an opportunity for exchange, on a quantitatively limited basis, leaving open questions of when, with whom, for which object and under what conditions the person possessing the money will carry out the exchange.”
~ Niklas Luhmann, Trust and Power
We could generalize this as a set of linked recovery events, each having their own recovery proof method.
Agree. It’s all about a verifiable chain of events. I am also wondering if you could put in the event a nip05 name that could serve as a recovery service?
Then just traverse the events for the latest and greatest key. It means that you need to be super-careful about your recovery key because then you are really screwed.
Could it be as simple as a key recovery event where the current nsec signs a recovery npub and the recovery nsec countersigns the current npub. The general idea is to show that the user had control of both keys. If the current nsec is compromised a recovery event is published by the recovery nsec which then makes it the current npub.
I watched until he started to hit the command line. I agree that the ‘verifiable key history’ is an important piece. Right now, if my nsec is compromised, there is no what for anyone to figuring what the next npub should be. Is this something we could replicate with events?
#usenostr 
Huge milestone: First demo of Nostr Web Services (NWS) bringing TCP to Nostr. With NWS, you can host any existing web application on Nostr without having to use DNS or even announce your public IP to the world, simply by sharing your service's npub (or nprofile).
Try it out the demo yourself. Here is a Cashu test mint running with NWS. Let's use curl to retrieve the mint's information. The request travels from your computer to the public NWS entry relay, then through nostr to the service's NWS exit relay. At the other end is a Cashu mint with HTTPS encryption.
```
curl -s -x socks5h://relay.8333.space:8882 https://nprofile1qqs8a8nk09fhrxylcd42haz8ev4cprhnk5egntvs0whafvaaxpk8plgpzemhxue69uhhyetvv9ujuwpnxvejuumsv93k2g6k9kr/v1/info --insecure | jq
```
I can't stress this enough: THE MINT RUNS BEHIND HTTPS!
The NWS entry relay can't read your traffic. It's encrypted. We can host public entry relays that can be used by anyone.
This means we can plug the entire internet to it 🌐.
Let's plug it into Cashu for now. Nutshell wallet supports socks5 proxies (that's how it uses Tor). By setting the public entry relay as the proxy, the wallet can now connect to a mint's npub/nprofile and communicate with it via NWS.
This is going to be so freaking cool. And it's going to be a lot more useful than just for Cashu. There are still bugs and issues that need to be ironed out but the code is coming out soon. Watch this space.
Super! Just tried it. It works!
A lot of people are going out on a personal or professional limb to foster #nostr. nostr:note18wvuccfduzh2jlcnnfnlve8g0k62qymx8qg45addp3adwezz3arqa55yqx
“The internet protocol treats each internet datagram as an independent
entity unrelated to any other internet datagram. There are no
connections or logical circuits (virtual or otherwise).”
After the invention of TCP, the internet never looked back.
That’s worth a follow!
Remember, you can’t unsay things.
#Nostr makes that even harder.