Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Epic] Design of Dispersal Algorithm #27

Open
Cofson opened this issue Jul 16, 2024 · 0 comments
Open

[Epic] Design of Dispersal Algorithm #27

Cofson opened this issue Jul 16, 2024 · 0 comments

Comments

@Cofson
Copy link
Collaborator

Cofson commented Jul 16, 2024

Requirements

  • Nodes have to provide a Proof-of-Validator to the networking layer
  • The networking layer needs to check this PoV in order to allow or reject nodes
  • One of the most important aspects is to limit bandwidth requirements
  • Another one of the main goals is to reduce the number of connections.
  • The easiest thing to do always is to connect each node to each other and fan out data to each. This approach does not scale. Therefore the protocol needs to optimize the number of connections without sacrificing the availability of data.
  • Spam upload should be prevented
  • A Data Availability Sampling node can be operated on low resource devices.
  • A Data Availability Sampling node can be operated behind a NAT (ISP-provided internet access)
  • A Data Availability Dispersal Client does not need to know any details of the network topology (e.g. number of nodes) to be able to successfully upload data to the network.
  • The logical 4096 column data receivers need to be able to be mapped transparently to small networks (development, testnet) as well as big networks (mainnet).

https://www.notion.so/Dispersal-Sampling-ed112d55cdf4466f993b6228d9db43d7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant