Replying to Avatar frphank

Blockchain ledgers are centralized in so far as that "there is only one" ledger but stored decentralized on many redundant nodes. I don't need to explain that to you Mr. Bitcoin.

So a team having to have "the one fork" they work on together doesn't imply centralized single point of failure storage. Of course blockchain ledgers achieve this at absurdly high bandwidth costs and simplistic consensus algorithms.

Can you take it from there and reduce bandwidth, increase consensus sophistication so that the team's one fork can live on 2 dozen servers like nostr relays and yet be synced well enough to appear as one.

Not an easy task I know but it's the only way forward.
Avatar
DanConwayDev 1y ago

The architecture I propose for achieving this is treating git servers like relays. The nostr repository event includes a list of git servers and the commit-ids for the tips of each branch. a git remote-helper enables maintainers to push to all git server mirrors and update the repo event with the new branch tip with a simple 'git push' command. I wrote a bit more about the proposed repo event format for this here: https://github.com/nostr-protocol/nips/pull/997#discussion_r1464484832

Reply to this note

Please Login to reply.

Discussion

Avatar
Cyber Seagull 1y ago

I hope you guys get the bounty ! Perhaps after some more refinement to meet the terms ?