Conversation
…n node Extracted from the PubSub SWIP (PR #93) Milestone 3 and generalised: any push-sync+retrieval-capable, potentially non-reachable node can carry out a private mutually authenticated exchange with a previously unknown full node in the neighbourhood of a pre-agreed anchor. Includes a leakless known-responder PSS variant. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a new SWIP (SWIP-58) specifying MEX (Message EXchange): a two-phase anchored rendezvous and mutually authenticated request/response exchange built from existing Swarm primitives (MIC/MOC, SOC/GSOC, push-sync receipts, retrieval). This extracts and generalizes the “Milestone 3” discovery/exchange pattern from the the outdated original PubSub SWIP #93 so other protocols can reference it as a standalone dependency.
Changes:
- Introduces the full SWIP-58 specification (terminology, phases, variant for known responder via PSS trojan, encryption/key derivation, rationale, security considerations).
- Adds explicit operational/security requirements (notably at-least-once delivery implications and mandatory per-chunk-address session dedup).
- Documents implementation links and test case scenarios.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
This was referenced Aug 3, 2026
Open
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
zelig
changed the title
zelig
changed the title
SWIP-0 specifies `type: Standards Track` with the subcategory in a separate `category:` header (one of Core / Networking / Interface), as swip-19 and swip-20 do. This file carried the category inside `type:`, the only form in the repo, which may break tooling that parses the front matter. Copilot's other findings on PR #103 were already fixed by the 58 -> 59 renumbering pass: the "poQ stage stamp" and "Re dd" editing artifacts are gone, the double space is gone, and the nonce derivation names `req_key` / `res_key` explicitly rather than a bare `key`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The Phase-2 note read "decrypt → Q, id_B; store SOC(...) locally". A semicolon is a statement separator in mermaid, so it terminated the note and the rest parsed as garbage: GitHub silently fell back to rendering the raw source, and the diagram has never displayed. Replaced with an em dash; verified to parse under mermaid 11. Same defect as the one found in SWIP-60's diagram. Every mermaid block across SWIP-59, 60, 61, 65 and 66 has now been scanned for it, and all of them parse. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
MEX (Message EXchange): a two-phase rendezvous-and-exchange pattern by which any node capable of push-sync and retrieval — including light, potentially non-reachable nodes — carries out a private, mutually authenticated message exchange with a previously unknown full node in the neighbourhood of a pre-agreed anchor. Built entirely from existing primitives: MIC/MOC (SWIP-42, #80), single-owner chunks, push-sync receipts, retrieval.
Extracted from the PubSub SWIP (#93), where it was worked out as Milestone 3, and generalised so it can be referenced independently — by PubSub as a dependency and by MIC/MOC as a use case — keeping the cryptographic detail out of the PubSub spec.
Also specifies:
Follow-ups
🤖 Generated with Claude Code