• Outline plan for next steps in research. Target dates.
• Outline plan for next steps in development. Target dates.
• Risks. Backup plan.
• Need to hire?

Data availability

• Deterministic assignation of nodes to DA subnetworks needs to be studied. Redundancy factor.
• We can use PoV for the deterministically positive network.
• Many subnetworks with low subscription is bad for performance. In the future we need to implement proper subnetwork propagation.
• We can use incentives for “online and delivered". These incentives can 1 small for everyone, or 1 large randomly provided (executor needs to be enforced in the choice by using verifiable randomness).

Plan

• Risks
  • 4096 is too high. Low risk.
  • Too low performance.
  • Rely on PoV
• Research:
  1. Eventually consistent membership distribution algorithm specification and executable specification.
  2. Create a network analysis of the design:
     1. Estimate bandwidth usage for each of the networks layers
     2. Estimate number of connections per node and network layer (total and relative to the layer)
     3. Simulate and validate above model (either python or simulation app)
• Dev:
  1. Implement a python runnable POC (logical concept working)
  2. Implement a rust runnable POC (logical concept working, not performant)
  3. Implement a rust custom (in-house probably) networking stack that fits every requirement in the best possible way.
     • Investigate how the stable network can be implemented. Is it a libp2p DHT?
     • How to include the POV (proof of validator) eventually consistent membership protocol? INCLUDE POV DOCUMENT HERE
• Hire a networking engineer if possible

Mixnet

• New design highly decentralized and mitigates performance.

Plan

• Risks:
  • Incentives not considered
  • Rely on PoV
• How to implement this?
  • Option 1: Gossipsub
  • Option 2: Direct connection (improvement in the future)
• Next steps
  • SEE REPORT