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.