GATEWAY
I4Gateway Platform · Interoperability

Interoperability,
with privacy on top.

Move assets, messages, proofs and liquidity between sovereign ledgers, public chains and existing rails over Agglayer, CLIP, CCIP or IBC. Gateway runs Open Privacy Suite alongside the route, so each party sees only what its role allows.

Sender Bank A sees its own trade in full.

Illustrative trade, not live data.
P7The problem

Interop moves value.
It moves information too.

Every crossing carries positions, counterparties and client data. On a standard EVM ledger, anyone with access to a node can read all of it. Connecting ledgers shouldn’t mean opening your books.

What a crossing gives away without an access layer

  • LiquidityWhere your cash and collateral sit, and when they move. A desk’s position, open to anyone who can read the ledger.
  • AssetsHoldings, trade sizes and counterparties, on both sides of every crossing.
  • MessagesPayment instructions carry originator and beneficiary data. The rules say it must travel; data protection says to minimise who sees it.

Where privacy has to hold

  1. The routeIn transitEach route has its own security model. Some can encrypt what they carry; relayers and operators see the rest.Your route’s own controls
  2. Each ledger’s access layerWhere it landsWho can read the trade once it settles: the counterparty, an approved regulator, nobody else.Open Privacy Suite
  3. Decision evidenceOn the recordWho saw what, under which policy, approved by whom. Ready for the auditor.Open Privacy Suite
L4The answer: interoperability with privacy

Choose any route.
Privacy comes with it.

Pick the route for each flow: Agglayer, CLIP, CCIP or IBC. Gateway runs Open Privacy Suite alongside it, at each ledger’s access layer, so every party sees only what its role allows and every decision is on the record.

Choose a route
Bank A sends to Institution B over Agglayer, secured by pessimistic proofs. Open Privacy Suite runs alongside it: it checks identity and policy on every call, scopes what each party may see, and records every decision.
Counterparty
The trade it shares, nothing else
Regulator or auditor
A scoped, approved, expiring view
Other participants
Nothing they are not party to
Public chain
Proofs; state stays with your operators
  1. 01IdentityEvery caller is a verified person, institution or agent.
  2. 02PolicyRules set which contracts, methods and parameters each caller may use. Anything else fails closed.
  3. 03RouteYour chosen path carries the transaction: Agglayer, CLIP, CCIP or IBC.
  4. 04DisclosureEach party sees its own view; disclosure is scoped, approved and expiring, and every decision leaves evidence.
  • Per-trade visibility

    Name who may see a transaction when it is submitted: the counterparty, an auditor, a regulator. Recorded, auditable, and no contract redeploy.

  • Piloted

    A bank settlement consortium: each participant saw its own flows, while the operator kept an auditable view of the whole. Read the case study

Open Privacy Suite governs access, disclosure and evidence. The ledger and the route keep their own security, finality and custody, and source node operators keep access to underlying state. Route support is confirmed per deployment.

Explore Open Privacy Suite
A8The shape of the network

Private and public networks.
One privacy layer.

Your estate mixes sovereign ledgers, public chains and existing rails. Two kinds of interop join them. One privacy layer sits on top of the networks you run, on the standard EVM ledgers you already use.

A heterogeneous network estate with privacy on topSovereign ledgers (Bank A, Institution B and a market infrastructure) connect to each other, and Bank A reaches core banking and RTGS over ISO 20022. Public networks (two rollups and Ethereum) connect to each other. Two paths cross from the private side to the public side. Open Privacy Suite spans the top and runs alongside every route, governing access, disclosure and evidence.OPEN PRIVACY SUITEAccess · disclosure · evidence on the networks you runSOVEREIGN LEDGERSPUBLIC NETWORKSEXISTING RAILSCore banking · RTGS · ISO 20022PATHSBank ASovereign ledgerInstitution BSovereign ledgerMarket infraShared FMI ledgerYour rollupPrivacy zoneRollupPublic L2EthereumSettlement layer
M3What crosses

Bank to institution.
Only the agreed legs cross.

Assets, messages, proofs and liquidity move between two books. Everything else stays home.

Your sovereign networkBank A
  • AssetsTokenised bond ⇄ tokenised deposits
  • MessagesDelivery-versus-payment instruction
  • Proofs & dataProof each leg is final
  • LiquidityCollateral posted where it is needed
Another institution’s networkInstitution B

Stays home: Client positions, other trades, each side’s books

R5The paths

The right path
for every flow.

Agglayer, CCIP, CLIP, IBC and more each trade security, speed and reach differently. We match a path to each flow and keep it replaceable.

Gateway operatesPolygon

Unified bridge for rollups.

A unified bridge with shared liquidity across connected chains. Since v0.3 it accepts chains beyond Polygon CDK.

Reach
Public: rollups to Ethereum
Moves
Assets and messages, through one bridge shared by every connected chain.
Security model
Pessimistic proofs: zero-knowledge proofs that no connected chain can withdraw more than was deposited into it.
With Gateway
Gateway builds and operates rollups connected to Agglayer and contributed to its development.
Many chains share one bridge and settle to EthereumRollupChain 1RollupChain 2RollupChain 3RollupChain 4AgglayerOne shared bridgeSettlementEthereum
Many chains share one bridge and settle to Ethereum

Status shows Gateway’s position, not the protocol’s maturity. Facts checked against public sources on 18 November 2026; network, version and feature support are confirmed per deployment.

D6How Gateway delivers it

From first route
to full network.

Start with one corridor and prove it. Gateway designs, deploys and operates every route after it with the same discipline, including rollups connected to Agglayer.

  1. 01MapYour connection map

    Which counterparties, assets and systems each flow must reach.

    Candidate pathsTrust assumptionsLimits and allowlists
  2. 02PilotOne route, end to end

    A single corridor, live with privacy and reconciliation in place.

    Path infrastructureOpen Privacy Suite policyISO 20022 and core banking
  3. 03ProductionOperated by Gateway

    The route runs under agreed service levels, with Gateway on call.

    MonitoringPause and recoveryIncident response
  4. 04ScaleMore routes, same discipline

    Add counterparties, paths and public reach without redesigning.

    New counterpartiesFurther pathsPublic liquidity

Every path stays replaceable. Trust assumptions, limits and failure modes are written down per flow; responsibilities are agreed in the contract.

Plan your first route
Q8Common questions

Before you connect.

Do we have to choose one protocol?

No. Different flows can use different paths, for example Agglayer for rollup assets and CCIP for a counterparty already on it. Each path adds its own trust assumptions, so we keep the number deliberate.

Does connecting to a public chain expose our data?

Not by itself. Only what you approve crosses: approved tokens, messages and proofs. In a privacy-zone deployment, state stays with your network’s approved operators, and Open Privacy Suite governs the views returned to users and counterparties.

Does Open Privacy Suite hide data from bridges and relayers?

No, and we don’t claim it does. Open Privacy Suite governs who can read each ledger and records every decision; the route keeps its own security, and some routes can encrypt what they carry. Where node operators must not see state, Inlay (in pilot) delivers each node only its authorised state; for the block producer, add a confidentiality layer.

Who carries the risk of a cross-chain path?

Each path has its own security model, and that model stays in place. The design records its trust assumptions, limits and failure modes; operating responsibilities are agreed in the contract.

Can the network connect to our payment systems?

Yes, through Gateway Orchestration: ISO 20022 messaging, core banking and reconciliation. A connection to a specific external network depends on that network’s access rules.

Is Gateway a bridge provider?

We don’t ask you to adopt a proprietary bridge. We design, deploy and operate established, open protocols for your network, and keep them replaceable.

C3Map your connections

Bring your network. Leave with a path for every flow.

Tell us which counterparties, assets and systems your network must reach. We’ll set out the candidate paths, their trust assumptions and the controls each one needs.