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
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
The text was updated successfully, but these errors were encountered:
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
specification
The text was updated successfully, but these errors were encountered: