Colby Serpaš” on Nostr: Decentralized GitHub Progress Status: 1. We've designed a new type of Merkle ...
Decentralized GitHub Progress Status:
1. We've designed a new type of Merkle Tree/DAG. It's able to organize file directories just like IPFS Merkle DAGs, while maintaining the small branches of classic Merkle Trees for inexpensive and quick user validation of data (repos, notes, etc). Currently, we are transforming this into a standalone library that any project can use. It is the foundation of the project.
2. As for storing data, we're keeping it off-chain as Merkle Trees on relays, with the Merkle root stored on-chain. Weāve already chosen the cache/database system and have developed a method to traverse each leaf throughout our database. We will complete this storage infrastructure once we finish the optimized Merkle Tree library.
3. We've also built a GitHub-like UI from scratch. It doesn't rely on any elements of the centralized web or components that depend on centralized URLs, and it works with any browser.
After these three core pieces are completed, it will just be a matter of assembling the piecesā¦ the decentralized GitHub will be born. The toughest computer science problems, such as creating Merkle DAGs with small branches and managing low-overhead leaf syncing, will be resolved. This storage system also enables people to build decentralized apps atop of it, including a synchronized nostr relay and client that is backwards compatible.
åæčćÆē¾å¾³
1. We've designed a new type of Merkle Tree/DAG. It's able to organize file directories just like IPFS Merkle DAGs, while maintaining the small branches of classic Merkle Trees for inexpensive and quick user validation of data (repos, notes, etc). Currently, we are transforming this into a standalone library that any project can use. It is the foundation of the project.
2. As for storing data, we're keeping it off-chain as Merkle Trees on relays, with the Merkle root stored on-chain. Weāve already chosen the cache/database system and have developed a method to traverse each leaf throughout our database. We will complete this storage infrastructure once we finish the optimized Merkle Tree library.
3. We've also built a GitHub-like UI from scratch. It doesn't rely on any elements of the centralized web or components that depend on centralized URLs, and it works with any browser.
After these three core pieces are completed, it will just be a matter of assembling the piecesā¦ the decentralized GitHub will be born. The toughest computer science problems, such as creating Merkle DAGs with small branches and managing low-overhead leaf syncing, will be resolved. This storage system also enables people to build decentralized apps atop of it, including a synchronized nostr relay and client that is backwards compatible.
åæčćÆē¾å¾³