[protocol/transport] Proposal: Integrating zero-metadata transport architecture inspired by Montana Messenger
Los mantenedores suelen responder en 1 día
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
- haskell
- Área
- networking, security
Línea de trabajo
The proposal names the SimpleX relay queue subsystem but does not identify files, tests, or a specific change to make. Start by reviewing the linked Montana Messenger repository and the relay queue architecture; ask maintainers to define a testable scope. Done would require an agreed feasibility evaluation for the proposed transport layer.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Architectural Problem Statement
While the SimpleX Chat protocol successfully achieves identifier-free routing and eliminates long-term user IDs, it remains fundamentally vulnerable to passive traffic timing analysis and global statistical correlation attacks. If an adversary compromises or logs data from independent entry and exit relays, the end-to-end communication graph can be mathematically deduced via packet-emission timestamps. For high-risk user profiles (such as media administrators and whistleblowers migrating from centralized platforms like Telegram), this metadata leakage is an unacceptable threat vector.
Proposed Solution: Integrating Montana Transport Layer
We propose evaluating the architectural transport specifications implemented in the Montana Messenger core protocol. Montana is engineered specifically to withstand a Global Passive Adversary (GPA) performing correlation attacks.
The integration addresses the core protocol layer through two main primitives:
- Mathematical Metadata Decoupling: Routing relies entirely on single-use cryptographic tokens per hop. Relays possess zero contextual awareness regarding the status of the target queue, making traffic indistinguishable from idle synchronization.
- Pluggable High-Risk Transport Mode: We do not suggest refactoring the primary Haskell stack of SimpleX. Instead, Montana’s transport layer can be deployed as an isolated, dedicated routing bridge (experimental pluggable transport) that introduces strict fixed-rate padding and noise injection.
Reference & Implementation Guidelines
The complete threat model, architecture constraints, and core zero-knowledge transport requirements are already structurally formalized and available in our repository guidelines:
https://github.com/efir369999/montana_messenger
We welcome precise engineering feedback from the maintainers regarding the feasibility of testing this zero-metadata padding layer within the SimpleX relay queue subsystem.
For the maintainers' context regarding protocol viability:
The core cryptographic architecture of Montana—specifically our hybrid ML-KEM-768 Noise-style ephemeral key handling specification—has been submitted for peer review to key figures in the cryptographic community, including Bruce Schneier.
While core developers of legacy P2P engines resort to administrative closure, global experts are validating the technical language of our threat model. Montana’s zero-metadata transport layer design stands as a rigorous academic project. We continue peer-review evaluations with independent researchers who prioritize mathematical security over repository gatekeeping.
- Lenguaje dominante
- Haskell
- Estrellas
- 19.7k
- Forks
- 1.3k
- Merge medio
- 1 d 10 h
- PR fusionados (30 d)
- 236
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
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 simplex-chat/simplex-chat
-
bug desktop
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
simplex-chat/simplex-chat#8291 ·
Los mantenedores suelen responder en 1 día
-
enhancement triage
Dificultad 1/5 1-3 horas Aptitud para principiantes 66/100
simplex-chat/simplex-chat#8043 ·
Los mantenedores suelen responder en 1 día
-
enhancement triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 77/100
simplex-chat/simplex-chat#7781 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
simplex-chat/simplex-chat#7714 · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
bug triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
simplex-chat/simplex-chat#7649 ·
Los mantenedores suelen responder en 1 día
Todos los issues de simplex-chat/simplex-chat
Issues similares
-
[BUG]: C# programs with top-level statements fail to compilePosiblemente ocupada @AsyncNigam la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
compiler-explorer/compiler-explorer#9625 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
needs triage type: enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 3 días
-
reflex-0.10Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
commercialhaskell/stackage#8180 ·
Los mantenedores suelen responder en 1 día
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
OpenZeppelin/canton-contracts#140 ·
Los mantenedores suelen responder en 1 día
-
takeInterval yields nothing, dropInterval drops nothingPosiblemente ocupada @GuillaumedeVolpiano la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
composewell/streamly#3271 ·