How clients can be assigned to subnets while upholding anonymity guarantees

Aperta
#4 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
rust

Direzione di ricerca

Start with participation_subnet in crates/anymone-core/src/runtime.rs, which picks a subnet from a hash of the private seed and the round index. Read how eligible_subnets is built and how subnet add/remove governance feeds into it. The issue is a design question, not a code change, so done means a written proposal that keeps a minimum client count per subnet per round and keeps clients on a stable subnet across linkable messages, agreed with maintainers before any code.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Anymone uses 'subnets', which are used to scale the network in response to the size of the client or server set changing.

Subnets can be added or removed via the governance protocol in order to achieve a balance between having enough clients to give strong anonymity, and not having so many that servers get overloaded.

How clients are assigned to subnets

Each round, clients call participation_subnet which deterministically selects a subnet based on the round index and a private seed.

pseudocode:
selected_subnet = hash(private_seed, round) % eligible_subnets.len();

Including the round index means that users constantly switch subnets even when the number of subnets has not changed.

The issues for anonymity
  1. Subnets may on some rounds have only a very small number of clients, reducing anonymity.
  2. Having clients move between subnets is problematic if their messages are linkable by their content or application metadata. If message 1 is sent to subnet A, and a similar message 2 to subnet B the following round, the intersection of the client sets on those subnet-rounds will contain the user.
What would be needed to fix this

Ideally we want a method of picking a subnet which guarantees a minimum number of clients on any round, and that clients stick to a stable subnet between linkable application messages.

The things which make this hard to do well:

  • Clients may come and go between rounds as they please - so we have no way to know how many will participate in the upcoming round
  • Without sybil protection, the minimum number of clients per subnet must be big enough to make de-anonymising a subnet impractical
Lingua principale
Rust
Stelle
0
Fork
0
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di flashbots/anymone

Tutte le issue di flashbots/anymone

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.