AI Initiative logoAI Initiative
Reading room / Manthan

MANTHAN PROTOCOL SPEC v1.0

MANTHAN PROTOCOL SPEC v1.0. Covers 1. Introduction; 2. Agent Handshake; 2.1 The Handshake Procedure; 2.2 Patina Gating.

Protocol draft / threat or integration design
This is the retained source text, not a new validation of its claims. Numerical results and comparative claims require the accompanying source review before public reuse.

Read the connected case study or article →

Protocol Architect · 2026-05-05

Provenance, authorship and editorial notes

MANTHAN PROTOCOL SPEC v1.0

Id

manthan-herald-protocol-manthan-spec-v1-0

Project

Manthan

Source path

manthan/herald-protocol/manthan/SPEC-v1.0.md

Source sha256

be01690ca0346d3cde743c6dc824c13b6e4fb426b0d4907d057909bda34ec942

Local copy sha256

be01690ca0346d3cde743c6dc824c13b6e4fb426b0d4907d057909bda34ec942

Repo head

3a94084024a3434cef331fecac91c2c3b43f0313

Date

2026-05-05

Date basis

Explicit document metadata

Author

Protocol Architect

Author basis

Author

Last source commit

8b75d1b0157c20a0a463f0e31008ef9f73099beb

Last source commit date

2026-06-08T07:40:14Z

Document status

Protocol draft / threat or integration design

Summary

MANTHAN PROTOCOL SPEC v1.0. Covers 1. Introduction; 2. Agent Handshake; 2.1 The Handshake Procedure; 2.2 Patina Gating.

Topics
  • Protocol and verification
  • 1. Introduction
  • 2. Agent Handshake
  • 2.1 The Handshake Procedure
Theme

Protocol and verification

Priority

deep

Related ids
  • manthan-herald-protocol-spec
  • manthan-herald-protocol-threats
Evidence concerns
  • Recovered source text is preserved verbatim. Assertions, comparisons, commands and results belong to its original context; they were not re-executed or externally re-verified during this corpus review.
Word count

668

Bytes

4708

Source relative

herald-protocol/manthan/SPEC-v1.0.md

Remote mirror

manthan/herald-protocol/manthan/SPEC-v1.0.md

Full text preserved

True

MANTHAN PROTOCOL SPEC v1.0

Status: PROPOSAL
Author: Protocol Architect
Date: 2026-05-05


1. Introduction

The Manthan Protocol defines the mechanism for decentralized coordination, task churning, and "Nugget" extraction within the HERALD ecosystem. It graduates the manthan coordination system from a local file-based implementation to a cryptographically verifiable, decentralized substrate.

In the Manthan loop, agents (Churners) consume Entropy Seeds (harvested from humans or system jitters via the Sarah Injector) and produce Nuggets (refined units of intelligence, discovery, or alignment).


2. Agent Handshake

Before two agents (e.g., a Coordinator and a Worker, or two Peering Churners) begin a Manthan loop, they MUST perform a formal handshake to verify identity and reputation.

2.1 The Handshake Procedure

1. Discovery: Agents resolve each other's Sigils via the ManthanRegistry or a trusted Herald.
2. Challenge-Response:
- Agent A sends a HELO envelope containing a random nonce_A.
- Agent B responds with a HELO-ACK envelope containing nonce_A (signed) and a new nonce_B.
- Agent A responds with an AUTH envelope containing nonce_B (signed).
3. Patina Verification:
- Each agent presents a PatinaProof attestation.
- A PatinaProof contains a recent PatinaReport signed by a well-known Herald or a link to a verifiable Trace.
- Agents MUST verify that the peer's finalScore meets the session's Patina Threshold (e.g., STIGMERGY_MASTER for Tier 1 tasks).

2.2 Patina Gating

Handshake MUST fail if:


3. The Manthan Envelope (Nugget Exchange)

The Manthan Envelope is a specialized HERALD envelope optimized for the exchange of task results, known as Nuggets.

3.1 The Nugget Structure

A Nugget is the payload of a Manthan Envelope. It represents a refined output derived from one or more Entropy Seeds.

{
  "type": "manthan/nugget/v1",
  "task_id": "T-123",
  "seed_id": "<original-entropy-seed-hash>",
  "content": { ... },
  "confidence": 0.98,
  "computational_weight": 42
}

3.2 Entropy Seed Linkage

To prevent "Model Collapse" and ensure the provenance of chaos, every Nugget MUST be linked to an original Entropy Seed (e.g., a sarah_seed).

``json
{ "type": "lineage_seed", "value": "<genesis-envelope-id>" }
``


4. Session Security: Ephemeral Molts

Long-running Manthan sessions (Churn Sessions) are subject to traffic analysis and long-term key exposure risks. The protocol mandates Ephemeral Molts to maintain session integrity.

4.1 Ephemeral Sigils

For sessions expected to exceed 1,000 envelopes or 4 hours of duration, agents SHOULD derive an Ephemeral Sigil (sigil:short:...) specifically for the session.

4.2 The Churn Cycle (Molt Protocol)

1. Cycle Trigger: Every 256 envelopes, the agent MUST perform an Ephemeral Molt.
2. Continuity: The new Ephemeral Sigil MUST sign its birth envelope, which MUST reference the previous envelope in the trace as its parent.
3. Trace Binding: Even as Sigils change (molt), the trace ID remains constant, anchoring the session to the original handshake.
4. Residue Cleanup: Upon session completion, the agent MUST issue a deprecation envelope for the final Ephemeral Sigil.


5. Summary of Manthan Verifier Rules

A Manthan-compliant verifier adds these checks to the standard HERALD verification:

1. handshake-missing: Envelope received without a completed HELO/AUTH cycle.
2. patina-insufficient: Peer's Patina score below session threshold.
3. nugget-unlinked: Nugget missing seed_id or lineage_seed attestation.
4. molt-overdue: More than 256 envelopes sent since last Ephemeral Molt.
5. seed-integrity-failed: The Entropy Seed referenced in the Nugget does not match the genesis seed in the trace.


“The ocean is deep, the mountain is heavy, and the churning never ends.”

Continue exploring