We’re replacing IPFS with a layer 2 off-chain storage system that stores files with our optimized merkle trees, like IPFS does, but we ditch their bootstrapping system for a trust-minimized relay discovery system.

The node running this storage system also runs a git server, as you suggested. I have to say, I explained the basics of our storage system with merkle root on-chain — but I haven’t gone in-depth on how we’re doing the GitHub itself in context to the storage system.

Happy to share, just was trying to finish it before someone else did — it was a competition afterall.

1. Centralized bootstrapping: you must rely on a centralized set of nodes to connect into the network.

2. No user-server model: users are forced to spin up a server to browse their decentralized web. You can’t even turn a file into a merkle tree without being forced to spin up an IPFS blockstore server.

3. Their Merkle Trees/DAGs are not optimized for downloading one branch at a time, because you must download a list of all children hashes when downloading any parent hashes — creating excessively bloated merkle branches.

We’ve invented a new type of Merkle Tree/DAG that has the ability to map file directories like IPFS Merkle DAGs, and maintains the small branches of Merkle Trees for quick user validation.

This achievement may help projects independently of Nostr.

IPFS is a nightmare, though merkle trees are indeed vital to storing large repos. That’s how IPFS handles storage.

I’m growing more and more concerned about the reliance on GitHub.

And starting to think a bounty isn’t the right way to fund this work.