Nobody else seems to care but I think nostr finally needs a Hash Chain event kind or tag that is enforced server-side: - To add a new event to the chain, you MUST reference a previous event. If the referenced event does not exist, you get an error. - Only one event can reference another event. If an event has already been referenced before, you get an error. IMO (almost) solves the biggest issue with nostr which is the fact that you never know if the data you have is complete and it allows atomic updates of data. Suggestions for improvements of this idea welcome.

Masterclass of how to make sure you never get user adoption 🤘 View quoted note →

gm. people will withdraw their onchain zaps onto their hardware wallet. and people will also use their hardware wallets to top up their zap wallets. please don't do stupid shit like onchain zaps. we've been tirelessly to improve bitcoin privacy. don't fuck it all up now and link people's life savings with their public nostr profiles. please. 🙏

Imagine BlueSky but with Nutzaps

Running mints in enclaves is funny and hard. It's like setting up the mint blindfolded. All key generation, storage, and setup happens inside. Keeping it running is a whole other challenge: database can't grow infinitely because you have no access to it, Lightning pure is basically impossible because of channel management, and Ecash keyset rotations etc must all happen fully automatic. It's like doing it all in full self driving mode while also being blind at the same time. View quoted note →

Wish there was more going on in Bitcoin.

Can Nostr VPN also do NAT punching?

gm

good one

i can’t express enough gratitude to my supporters, collaborators, thought provokers, teachers, and preachers. it’s an immense honor to fight with you for the future of the internet, open source, communication, money, and ultimately our civilization. this is our time.