How clients can be assigned to subnets while upholding anonymity guarantees
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 15/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- rust
- Área
- distributed-systems, security
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Subnets may on some rounds have only a very small number of clients, reducing anonymity.
- 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
- Lenguaje dominante
- Rust
- Estrellas
- 0
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de flashbots/anymone
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
-
Queued pipe payloads can be silently dropped at stage time after passing the send-time size checkAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 54/100
-
Documentation of Anymone's governance committeeQuizá libre de nuevo @ameba23 la tomó hace 43 días y no hay ningún pull request abierto. Abiertodocumentation
Todos los issues de flashbots/anymone
Issues similares
-
priority middle
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
KATO-Hiro/AtCoderClans#13029 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
RustCrypto/formats#2544 ·
Los mantenedores suelen responder en 1 día
-
bug ui
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
userFRM/egui-charts#3363 ·
Los mantenedores suelen responder en 1 día
-
ada documentation mobile report
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
physicsdolphin/nv-uefi-unlocker#254 · 2 reacciones ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
kindraywind/rustnarok-client#1382 ·
Los mantenedores suelen responder en 1 día