Nostr Web Client

Nostr is eating up bandwidth which is a huge problem over cellular networks. I suspect a lot of content is downloaded simultaneously from many relays over and over again instead of having clever caching and optimization. Are devs working on solutions to this?

Akis 2y ago

in a situation where someone new joins the network/relay, won't they have to verify a lot of signatures of past events?

shouldnt this make it very computationally intensive to trustlessly join a relay when the network scales up?

Reply to this note

Please Login to reply.

Discussion

Colby Serpa 2y ago

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.

Colby Serpa 2y ago

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.