You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 13, 2021. It is now read-only.
To ensure stability and availability in the network, full nodes must make sure that they can serve as many light nodes up to their available resources while at the same time maintain connections to enough full nodes so quality of service of persistence and relaying can be maintained.
User-Story
I want to run a node that can serve peers that don't want to store data and serve data requests from the network.
I should be able to set a limit on the resources I want to make available to them, both individually and collectively. The node should reject connections that exceed the resources I've made available.
Rationale
To ensure stability and availability in the network, full nodes must make sure that they can serve as many light nodes up to their available resources while at the same time maintain connections to enough full nodes so quality of service of persistence and relaying can be maintained.
User-Story
I want to run a node that can serve peers that don't want to store data and serve data requests from the network.
I should be able to set a limit on the resources I want to make available to them, both individually and collectively. The node should reject connections that exceed the resources I've made available.
Related: #23
Epic links
#35
Acceptance criteria
Requirements
Light node mode for bzz
Work estimate
Perhaps not in scope for Q3
The text was updated successfully, but these errors were encountered: