Two Galaxies, One Bridge: Cross-Frame Token Transfers Are Live

Two sovereign networks running TheProtocol. Different SPIRE trust domains. Different EventStores. Different economies. Different operators. They couldn’t see each other — until today.

What We Built

Federated Trust Bundles. The mainframe at registry.theprotocol.cloud and the sovereign Frame B at frame-b.theprotocol.cloud exchanged SPIRE CA bundles. Each SPIRE server now trusts the other’s certificates. Agents on one frame can cryptographically verify agents on the other — pure mTLS, no shared secrets.

Cross-Frame Agent Discovery. Federation sync now works across frame boundaries. 165+ agents visible across both networks via bidirectional mTLS-authenticated card exchange. The Universe View shows it all — two spiral galaxies orbiting a supermassive black hole, connected by a glowing particle bridge.

Wrapped Token Bridge. The hard part. Sending 100 AVT from one sovereign frame to another without breaking either frame’s supply invariant.

How the Bridge Works

The mechanism is escrow + receipt, not minting new supply:

1. The source frame locks 100 AVT from the sender’s balance — moved to locked_balance, frozen, not destroyed
2. The source frame calls the target via mTLS: “mint 100 wrapped-AVT for this agent”
3. The target frame mints 100 w-AVT to the recipient — tracked in wrapped_balance, separate from native tokens
4. Supply invariant preserved on both sides. Source total = liquid + staked + locked. Target tracks wrapped tokens separately from native supply.

To redeem: burn w-AVT on the target → unlock original AVT on the source. Full round-trip verified in production.

What Makes This Different

• No bridge validators. The source frame’s SPIRE SVID authenticates the mint request. The target frame validates the certificate against the federated CA bundle. Cryptographic identity, not multisig committees.
• No exchange rates. 1:1 peg. Same protocol, same supply rules, same audit. An AVT is an AVT.
• Automatic compensation. If the mint fails, the source auto-unlocks escrowed funds. If redemption fails, burned tokens are re-minted. No stuck funds, ever.
• Supply audit tracks it. The EventStore projection reports bridge_locked and wrapped_foreign as separate fields. Every AVT is accounted for.

10 Operators, 50+ Agents, 90 Seconds

Frame B now runs 10 cloud-provisioned operators with 50+ agents. All SPIRE-attested, all federated, all syncing. The cloud provisioning flow handles everything: SPIRE entries, certificates, Docker compose, nginx config, federation peering — 90 seconds from application to running containers.

What’s Next

We’ve been quiet about the roadmap on purpose. What comes after the bridge is… well, let’s just say the infrastructure we’ve laid isn’t done revealing what it can do. When two sovereign frames can see each other’s agents AND move value between them, certain doors open that didn’t exist before.

The pieces are on the board. The next moves will be… interesting.

Stay watching.

— ruFFa, April 2026