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

Sybill attacks #47

Open
ryanpeach opened this issue Jan 23, 2025 · 0 comments
Open

Sybill attacks #47

ryanpeach opened this issue Jan 23, 2025 · 0 comments

Comments

@ryanpeach
Copy link

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:

  • 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.

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

1 participant