1. Purpose
The Neutral Bridge exists to provide transport only, not authority.
Its sole purpose is to deliver a sealed request from one blockchain environment to another, without:
• Inspecting contents
• Enforcing policy
• Granting permission
• Extracting value
The bridge does not decide who may enter.
It only ensures the request reaches the destination intact.
2. Core Principle: Separation of Responsibilities
The system is intentionally divided into three independent layers:
Origin Chain – where the request is created
Neutral Bridge – where the request is transported
Destination Chain – where the request is accepted or rejected
The bridge never participates in identity verification, asset validation, or execution logic.
3. The “Sealed Envelope” Model
All cross-chain interaction is represented as a sealed envelope:
• The bridge cannot read it
• The bridge cannot modify it
• The bridge cannot approve or deny it
The envelope contains:
• Proofs generated by the origin chain
• Claims asserted by the user or application
• Optional payloads (assets, messages, references)
The envelope is delivered unopened.
4. No Shared State, No Asset Custody
The Neutral Bridge:
• Holds no assets
• Maintains no mirrored balances
• Keeps no shared global state across chains
All state remains sovereign to each chain.
5. Destination Sovereignty
Every destination chain is fully sovereign.
Upon receiving an envelope, the destination chain may:
• Accept it entirely
• Reject it entirely
• Partially process it
• Ignore it completely
Acceptance rules are defined exclusively by the destination chain.
6. Identity and Authorization Are External
The bridge does not define identity.
Identity verification may rely on:
• Wallet signatures
• Hardware wallets
• Native chain authentication
• External identity systems
If identity is invalid, rejection happens at the destination, not on the bridge.
7. “Stupid by Design”
The bridge is intentionally minimal.
It is:
• Not upgradeable by governance
• Not parameter-tunable for preference
• Not expressive enough to encode policy
This “stupidity” is a feature, not a limitation.
8. Neutrality Guarantee
The bridge:
• Does not prioritize chains
• Does not charge mandatory fees
• Does not extract rent
• Does not favor volume or influence
Any economic layer must exist outside the bridge.
9. Permissionless Integration
Any chain may integrate by:
• Implementing an adapter on its own side
• Accepting or rejecting envelopes by its own logic
No approval from the bridge is required.
10. Security Model
Security emerges from:
• Cryptographic proofs at the origin
• Verification logic at the destination
• Public auditability of the bridge’s minimal code
The bridge itself is not a trust anchor.
11. Governance Absence
There is no central governance over:
•Who may use the bridge
• Which chains are supported
• What payloads are allowed
The system survives precisely because no one can control it.
12. Public Infrastructure Ethos
The Neutral Bridge is comparable to:
• A road
• A port
• A network cable
It exists for use, not ownership.
13. Failure Tolerance
If:
• A destination refuses all envelopes → bridge still functions
• A chain attacks the bridge → other chains unaffected
• No one maintains adapters → bridge remains neutral and intact
14. What the Bridge Is NOT
The Neutral Bridge is NOT:
• A wrapped-asset mint
• A liquidity protocol
• A cross-chain DEX
• A revenue-generating platform
Those are optional layers others may build.
15. Final Assertion
Interoperability does not require control.
It requires delivery without judgment.
The Neutral Bridge exists so that systems may communicate
without trusting the messenger.
Takeshi Sato