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

Sub-nets #264

Closed
sandreae opened this issue Dec 23, 2022 · 0 comments
Closed

Sub-nets #264

sandreae opened this issue Dec 23, 2022 · 0 comments

Comments

@sandreae
Copy link
Member

sandreae commented Dec 23, 2022

In p2panda all data has a schema and a peer wishing to replicate data registers which schema it is interested in. This is one way we a peer can limit it's interactions with the main net.

Another layer below this could be introducing sub-nets / network IDs. A peer would only replicate data from peers on its own net, and by data following schemas it is interested in. This gives nice control of a peers interaction in, potentially many, sub-nets.

example

  • many festivals organised around the world use the same schemas, there are festivals each year. Each festival could have it's own sub-net ID so the events from one festival/year don't polite others. You could have a "mega" festival peer who is interested in all sub-nets. In this example all festivals are public, but you could imagine a sub-net being private for not-public festivals.

specification

  • tbc 🤣
  • tor / onion services could be interesting
@sandreae sandreae changed the title Sub-net ids Sub-nets Dec 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants