OTL Network is a coordination layer in the crypto infrastructure stack. It sits above transport rails like CCTP and Hyperlane and beside orchestration layers like Across, LI.FI, Relay, and Eco Routes. The Open Transaction Layer launched on May 28, 2026 with 30+ institutional founders led by Fireblocks, and its own launch site frames OTL as an "open protocol stack for coordinating onchain transactions."
​

This article maps the 2026 stack in four rows (rails, orchestration layers, coordination layers, apps), shows where OTL fits, and explains how the rows compose with each other. The framing is mechanism-only. Each row solves a different problem; an institutional builder usually integrates pieces from more than one row.
​

The 2026 crypto infrastructure stack has four functional rows. Rails move value between chains. Orchestration layers pick which rail to use for a given transfer. Coordination layers standardize the workflow around a transfer (identity, compliance, messaging). Apps expose all of this to an end user or a treasury operator as a single product surface.
​

This four-row picture extends the older three-tier mental model that Multicoin Capital and others popularized for DeFi composability. Multicoin's 2020 DeFi stack essay framed DeFi primitives as layered protocols where each piece is independently useful and composable. The same idea applies to stablecoin movement in 2026, with the addition of a new row (coordination) that emerged as institutions started settling onchain at scale.
​

The stack rows in current shape:
​

The rows are functional, not strict. Some products span two rows. Fireblocks, for example, runs custody software (an app-row service) while also founding OTL (a coordination-row protocol). The point of the model is mapping where a specific capability lives, not boxing companies.
​

Transport rails are the lowest row in the stack. They move tokens or messages from chain A to chain B and they expose primitive APIs that higher rows compose against. They do not pick themselves, they do not check counterparty identity, and they do not present a UI. A builder integrating a rail directly is taking on the orchestration job upstairs.
​

Named rails currently in production:
​

Rails are infrastructure for infrastructure. Most apps do not call a rail directly. They call an orchestration layer that calls the rail.
​

Orchestration layers sit one row above rails. They accept a builder's intent and decide which rail to use, in which sequence, at which cost. This is where most cross-chain stablecoin volume gets shaped today. A treasury moving USDC from Arbitrum to Solana hits an orchestration layer, which picks among CCTP, a fast-bridge solver network, or a multi-hop route through an intermediate chain.
​

Named orchestration layers and their public mechanism descriptions:
​

These services do not compete for the same workload as coordination layers. An orchestration layer answers "which rail and how." A coordination layer answers "how do two counterparties agree on identity, compliance, and settlement before either side touches a rail." Both questions exist for a single institutional flow; the answers come from different services.
​

Coordination layers are the row OTL Network occupies. They standardize the workflow around a transaction so two institutions can move value to each other without writing a custom integration. The row covers identity, messaging, session, transport, and compliance handoff. It does not move value itself.
​

OTL describes its scope in five layers per the Fireblocks launch post: identity, session, transport, messaging, and application. The first four are technical primitives; the fifth is where business logic combines them into end-to-end flows. Per the same post and the OTL announcement on PR Newswire, OTL is built on existing standards including W3C DIDs, IVMS101 (the FATF Travel Rule data standard), ISO 20022, and CAIP-19. Fireblocks states that OTL is "not replacing what moves value, but standardizing everything that has to happen around it," positioning it above settlement, blockchain rails, and bridges rather than competing with them.
​

OTL's launch on otl.network lists 30+ institutional founders, including B2C2, Checkout.com, Coins.ph, Cross River Bank, eToro, FalconX, MetaMask, Moonpay, Privy (Stripe-owned), Bridge (Stripe-owned), Robinhood, Securitize, SoFi, Taptap Send, Tazapay, Triple-A, WalletConnect, Wintermute, Xendit, Zengo, Zerocap, and zerohash. Ledger Insights coverage confirms Fireblocks initiated the effort, which builds on the Blockchain Payments Consortium it convened in December 2025.
​

What sits in the coordination row alongside OTL is still forming. The category boundaries are early. Private vendor stacks (Fireblocks Network, exchange-to-exchange settlement hubs) have done bilateral versions of this work for years. The Blockchain Payments Consortium operates in adjacent territory. OTL is the first open-protocol entrant with a published spec. Whether other open coordination layers emerge or OTL becomes the standard the way ISO 20022 did for traditional payments messaging is not yet visible.
​

Apps are the top row. They turn the layers below into a product a human or a program uses. Named app categories in 2026 stablecoin flows include corporate treasuries, merchant processors, exchanges, neobanks, remittance platforms, and AI-agent wallets that initiate transactions autonomously. Examples include MetaMask, Robinhood, Phantom, Opera MiniPay, and Caldera-built chain platforms.
​

App-row services compose the rows below into a usable surface. A merchant processor paying out USDC to vendors will typically call an orchestration layer to move funds, call a coordination protocol to handle Travel Rule and identity for institutional counterparties, and manage custody through a wallet provider. Four rows touched in one logical flow. Several app-row companies also appear in OTL's founder list, which is expected. They are the firms that need the coordination row to standardize so their integrations stop being bespoke.
​

OTL composes with rails and orchestration layers by sitting above both and standardizing the agreement step that precedes any onchain move. Two institutions settling a $5M USDC transfer can use OTL to exchange identity claims, satisfy Travel Rule, and confirm terms. The actual movement still goes through an orchestration layer, which still selects a rail. OTL does not replace either; it removes the bilateral integration that used to wrap them.
​

This matches OTL's own framing on the launch post: "It's not replacing what moves value, but standardizing everything that has to happen around it." The launch material draws an analogy to internet standards, with OTL playing roles closer to TCP/IP, DNS, SSL/TLS, and HTTP than to the physical fiber that carries the bits. The architectural intent is clear from public material; whether the analogy holds in practice depends on adoption, which is too early to evaluate.
​

A plausible institutional flow in 2026: a treasury submits an instruction to its custody platform; the platform handles OTL handshakes with the destination institution (identity, compliance, terms); the platform calls an orchestration layer to execute; the orchestration layer selects a rail (CCTP, Hyperlane, an intent-bridge solver) and confirms settlement. Each row does the job it is built for. OTL and orchestration layers are not substitutes. A builder routing retail USDC volume across 60 chains is solving a different problem than two banks settling a structured product onchain. The first is well-served by orchestration alone. The second needs coordination on top.
​

The table below summarizes the four rows with named examples and the kind of problem each solves.
​

The framing softens at the edges. OTL's coordination row is the newest and the least populated; the boundary between "coordination," "compliance vendor," and "messaging standard" is being drawn in real time. The May 28, 2026 launch is the first datapoint for an open coordination protocol. The fuller picture of who else lives in the row will come over the next several quarters.
​

A builder evaluating "where do I integrate" should map their product's job to a row and pick services from rows below that compose with that pick. A consumer swap app picks an orchestration layer and consumes rails through it. A treasury platform serving regulated counterparties picks a coordination protocol, picks an orchestration layer, and consumes rails through both. For builders moving stablecoins for treasuries or apps without an institutional-counterparty constraint, orchestration is the row to integrate. Eco Routes is one example of an intent-routing layer in that row, alongside Across, LI.FI, and Relay. For builders coordinating multi-party institutional transactions where identity and compliance handshakes drive cost, the coordination row matters too, and OTL is the first open-protocol entrant. The two rows are complementary; many product roadmaps will integrate both.
​

Sources and methodology. OTL Network's mission statement, partner list, and architectural framing pulled from otl.network and the Fireblocks launch post on May 28, 2026. Partner roster cross-referenced with Ledger Insights and Crypto Briefing. Rail and orchestration descriptions reference each protocol's own documentation. The four-row stack model extends the DeFi-stack thinking in Multicoin Capital's 2020 essay with a coordination row added to reflect the institutional-onchain shape of 2026.
​