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
However, how will STAMP prevent such things? Would it be part of StampNet:
Preventing two accounts having duplicates of some credentials (like email address)
Pruning a stamp sybill cluster periodically
etc.
If you are just sharing your identity file, someone would need a tool to verify the stamps are not a sybill attack. BrightID does this by putting everything on a blockchain that everyone has, and running their sybill algorithm on the chain periodically. That's a good approach. In a federated way though, you could set up StampNet federated nodes (maybe with activitypub) which share (or blacklist) other nodes of themselves, and identity's they've seen could be shared among them (anyone could upload anyones identity), and then you could go to such a website for "verification" of an identity.
Just some ideas.
The text was updated successfully, but these errors were encountered:
Found a great repo on sybill algorithms on a DAG
https://github.com/BrightID/BrightID-AntiSybil
However, how will STAMP prevent such things? Would it be part of StampNet:
etc.
If you are just sharing your identity file, someone would need a tool to verify the stamps are not a sybill attack. BrightID does this by putting everything on a blockchain that everyone has, and running their sybill algorithm on the chain periodically. That's a good approach. In a federated way though, you could set up StampNet federated nodes (maybe with activitypub) which share (or blacklist) other nodes of themselves, and identity's they've seen could be shared among them (anyone could upload anyones identity), and then you could go to such a website for "verification" of an identity.
Just some ideas.
The text was updated successfully, but these errors were encountered: