1. Lightning for off-chain transactions.⚡️
2. Taro for off-chain NFTs & digital assets.💰
3. DIDs for off-chain domains & monikers.👥
4. Nostr 2.0 for off-chain websites & apps.📲
⚓️ All anchored to bitcoin with small proofs attached to normal transactions. Verifying collections of off-chain data with a hash on-chain.
#[0]
Would’ve loved to give a presentation on Nostr 2.0 at Nostrica but in-person is maxed out..
Zion isn’t open-source either, what a shame. Everyone is LARPing.
Nostr 2.0 solves each problem. 🙄
Content addressing solves the content duplication problem: https://proto.school/content-addressing/
While on-chain merkle roots let users verify huge collections of posts all at once, without needing to examine the signature of every single post. Both will be explained in our documentation with the Nostr GitHub code.
Imagine the compute burden for a relay too… verifying all those posts requires a lot of processing power. In this context — Nostr 2.0 will save computational resources for both the user and the relay.
Nostr 2.0 solves each problem. 🙄
Content addressing solves the content duplication problem: https://proto.school/content-addressing/
While on-chain merkle roots let users verify huge collections of posts all at once, without needing to examine the signature of every single post. Both will be explained in our documentation with the Nostr GitHub code.
a.k.a The Bitcoin Web… 🕸️🌩️
It’s like Web5 on the frontend and Nostr on the backend. Users download merkle trees from nostr nodes and load them up as normal files into a browser or mobile app.
The on-chain merkle roots provide tamper-resistance for entire websites rather than just for profiles. Updating an entire website with an on-chain merkle root and tree hash is smaller than inscribing a single NFT. 🖼️
Essentially, it’s Web3 compressed on layer 2.
A few hashes in the taproot section underneath a normal bitcoin transaction can decentralize your entire website with user-verifiable tamper-resistance that doesn’t require verifying the signatures of every individual action. ❤️
With this method, you don’t need to verify the signatures of every post. It verifies the content of all the profile’s posts in one swoop with a hash that matches a tiny on-chain merkle root.
Posts are arranged in a merkle tree. You can validate the contents of someone’s profile one merkle branch at a time, or you can verify the contents of the entire profile/tree at once if you’re not missing any of its posts.
It’s like batched verification but even more compact.
#[7]
Let’s face it, we’re LARPing if we aren’t verifying signatures. This method will provide verifiable security for mobile without the costly burden of verifying one post at a time.
Our team will release this general purpose tool with the code for the Nostr GitHub. 💜
In Nostr 2.0, users will be able to tell when a profile has been tampered with since hashing all the posts together matches the on-chain merkle root of that profile.
Instead of verifying the signature of each post, users can take a hash of the entire profile and make sure it matches the on-chain merkle root.
Computational Requirements: users become lightwallets, nostr relays becomes full-nodes.
A forest of merkle trees with node pools. 🌌
An option to turn on signature verification for the people a user follows may be a good way to do it. That way mobile phones don’t need to verify every signature on the global feed…
