[protocol/transport] Proposal: Integrating zero-metadata transport architecture inspired by Montana Messenger
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- haskell
- 领域
- networking, security
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- Haskell
- 星标
- 19.7k
- 派生
- 1.3k
- 平均合并
- 1 天 10 小时
- 30 天内合并 PR
- 236
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
simplex-chat/simplex-chat 的其他 Issue
-
bug desktop
难度 2/5 1-3 小时 新手友好度 85/100
simplex-chat/simplex-chat#8291 ·
维护者通常 1 天内回复
-
enhancement triage
难度 1/5 1-3 小时 新手友好度 66/100
simplex-chat/simplex-chat#8043 ·
维护者通常 1 天内回复
-
enhancement triage
难度 1/5 1 小时以内 新手友好度 77/100
simplex-chat/simplex-chat#7781 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 85/100
simplex-chat/simplex-chat#7714 · 1 个 reaction ·
维护者通常 1 天内回复
-
bug triage
难度 2/5 1-3 小时 新手友好度 68/100
simplex-chat/simplex-chat#7649 ·
维护者通常 1 天内回复
查看 simplex-chat/simplex-chat 的全部 Issue
相似的 Issue
-
[BUG]: C# programs with top-level statements fail to compile可能已有人在做 @AsyncNigam 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 76/100
compiler-explorer/compiler-explorer#9625 · 1 条评论 ·
维护者通常 1 天内回复
-
needs triage type: enhancement
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 3 天内回复
-
reflex-0.10未关闭
难度 1/5 1 小时以内 新手友好度 62/100
commercialhaskell/stackage#8180 ·
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 78/100
OpenZeppelin/canton-contracts#140 ·
维护者通常 1 天内回复
-
takeInterval yields nothing, dropInterval drops nothing可能已有人在做 @GuillaumedeVolpiano 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
composewell/streamly#3271 ·