Stablecoins as the Settlement Layer
The Settlement Layer Has No Flight Recorder
NEARWEEK Research. The Verifiable Stack, Settlement Layer.
The Verifiable Stack is a NEARWEEK research initiative. This series maps the infrastructure required for verifiable AI at institutional scale. It presents a framework, not a product. The goal is industry-wide adoption of verifiable AI infrastructure.
TL;DR: The GENIUS Act (July 2025) triggered stablecoin issuer proliferation. McKinsey projects $3.7T in stablecoin supply by 2030. Current DEX infrastructure cannot support institutional-grade swaps across dozens of stablecoin pairs. The Stablecoin Transport Protocol (STP) by Yonder Labs introduces uncollateralized lending to TEE-attested Shade Agent solvers for cross-chain swaps at $1M-$10M+ with 1–3bp fees and zero slippage. StableFlow (@0xStableFlow) is the live frontend, processing USDT across 9 chains at 0.01% fees. STP is the first production protocol where the verification layer is built into the settlement mechanism rather than bolted on afterward. The unsolved problem: the off-chain execution leg remains a black box, and no unified Verifiable Commerce Receipt connects solver attestation to settlement proof to agent decision provenance.
The GENIUS Act Broke the Stablecoin Duopoly
The GENIUS Act passed in July 2025. It created the first comprehensive US regulatory framework for stablecoin issuers, standardizing reserve requirements, reporting obligations, and compliance thresholds. The policy intent was stability. The market effect was fragmentation.
Within months of passage, banks, fintechs, payment companies, and technology platforms began announcing stablecoin products. USDC and USDT continue to dominate aggregate supply, but their share of the issuer landscape is declining as new entrants enter with regulatory cover that did not exist before the Act. PayPal’s PYUSD, Ripple’s RLUSD, World Liberty Financial’s USD1, and Hashnote’s USYC represent only the first wave. Every major US bank with a stablecoin strategy now has a regulatory pathway [1].
McKinsey’s “The Stable Door Opens” report projects stablecoin supply reaching $3.7T by 2030 [2]. That projection assumes dozens of issuers, each with meaningful supply, operating across multiple chains. The infrastructure question is not whether stablecoins will proliferate. The question is whether the rails that move them between chains can handle the resulting fragmentation.
A $1M swap of PYUSD for USD1 on a centralized exchange today moves the market by several basis points. On decentralized venues, the slippage is worse. Current daily stablecoin-to-stablecoin volume sits at roughly $3–5B on DEXs and $6–10B on CEXs [3]. Conservative projections place this at $100B daily by 2030. The infrastructure that handles the current load cannot scale to the projected load, particularly at the long tail of the stablecoin distribution where liquidity is thin and pair depth is shallow.
The Capital Efficiency Problem
Existing DEX protocols use automated market maker (AMM) designs where liquidity providers deposit paired assets into pools. Capital is distributed across a price range. A $10M liquidity pool on Curve or Uniswap might support a $500K swap without significant slippage, but the remaining $9.5M sits idle across price points that may never be touched. This is acceptable for high-volume pairs like USDC/USDT. It breaks for long-tail pairs where total liquidity is measured in hundreds of thousands, not millions.
Concentrated liquidity (Uniswap V3, Fluid) improves capital efficiency by letting providers target specific price ranges. But it introduces active management requirements that most liquidity providers cannot sustain, and it still fragments capital across range positions rather than deploying it to fill individual swaps.
Centralized exchanges offer better depth for major pairs but collapse on long-tail stablecoin pairs. They also introduce counterparty risk, custody risk, and jurisdictional fragmentation. An institutional desk executing a $5M PYUSD-to-RLUSD swap has no single venue with reliable depth.
The structural problem is clear. AMM designs spread capital. Concentrated liquidity fragments capital. Centralized exchanges centralize risk. None of these architectures are designed for a world with 30+ stablecoin issuers, each requiring deep cross-pair liquidity at institutional scale.
STP: Lending to Verified Solvers
The Stablecoin Transport Protocol (STP), developed by Yonder Labs within the Proximity Labs ecosystem, is built on a different architecture. STP is not an AMM. It is not an order book. It is a short-term uncollateralized lending protocol that lends stablecoins to cryptographically verified solvers for the explicit purpose of filling cross-chain swaps [3].
The capital efficiency gain is structural. An AMM pool of $10M supports a fraction of that in single-swap capacity because capital is distributed across a price curve. An STP lending pool of $10M supports a $10M swap because the entire pool is lent to a single solver for a single transaction. The pool is borrowed, the swap is executed, the pool is repaid. Utilization approaches 100% per transaction.
The solvers are not arbitrary counterparties. They are Shade Agents: cryptographically verified software instances running inside Trusted Execution Environments (TEEs) using NEAR AI’s Shade Agent framework and dStack infrastructure [4][5].
Three security primitives enforce the trust model.
TEE attestation is the first. Before a loan is issued, the solver submits a cryptographically signed remote attestation to the STP smart contract. The attestation proves the solver is running a specified, audited codebase inside a TEE. The contract verifies the attestation before releasing any funds. If the solver is running modified code, or code outside a TEE, the loan is rejected [3].
Escrow-first is the second. Solvers cannot borrow speculatively. To initiate a loan, the solver must present a signed NEAR Intents quote proving that a user has already deposited source funds into NEAR Intents. The repayment capital is secured onchain before the loan is ever issued. There is no window where the lender’s capital is exposed without a corresponding user deposit backing it [3].
Atomic settlement sequencing is the third. The TEE code enforces a strict, linear execution path. Borrowed funds route to an off-chain venue (Binance, Coinbase, Circle), execute the swap, withdraw the target stablecoin to the destination chain, finalize delivery through NEAR Intents, then reverse the process to repay the lending pool. The solver cannot deviate from this sequence. The code running inside the TEE is the enforcement mechanism [3].
A concrete example from the STP litepaper: a user wants to swap 1M USD1 on Base for 1M PYUSD on Solana. The user signs an intent and deposits USD1 into NEAR Intents. A Shade Agent solver presents the signed intent to the STP contract. STP verifies the solver’s TEE attestation, confirms the escrow deposit, and lends 999,900 USDC. The solver routes to a CEX, purchases PYUSD, withdraws to NEAR Intents on Solana, and finalizes the swap. The user receives 999,900 PYUSD. The solver converts the received USD1 to USDC and repays the pool. Lenders earn approximately $100 on the transaction [3].
Fees range from 1 to 3 basis points. Slippage is zero at the protocol level because the full pool backs each swap. The solver absorbs CEX-side slippage, which for major pairs at institutional size is typically sub-basis-point.
StableFlow: Live in Production
@0xStableFlow: (app(dot)stableflow(dot)ai), built by @DapDapMeUp, is the production frontend for the STP protocol. It is live and processing transactions. Current coverage: USDT across 9 chains (Ethereum, Arbitrum, Polygon, BNB Chain, Optimism, Avalanche, Solana, Tron). Transaction fees: 0.01%. Minimal slippage up to $1M [6].
The roadmap includes USDC, USD1, and USDH support, expanding the pair matrix as new stablecoin issuers achieve sufficient CEX depth for the solver execution leg [6].
StableFlow launched in October 2025, covered by Phemex and Coinspeaker [6]. The significance is not the frontend itself but what it proves: the STP mechanism works in production. TEE-attested solvers are borrowing, executing, and repaying in live market conditions. The architecture is not a whitepaper. It is shipping.
The Verifiable Stack Connection
STP is architecturally significant for the Verifiable Stack because the verification layer is not an add-on. It is the protocol.
TEE attestation maps directly to the Models/Computation pillar. The solver’s execution is cryptographically attested before any capital moves. The STP contract can verify that the solver is running the correct code in a genuine TEE before issuing a loan. This is verifiable computation applied to financial execution rather than LLM inference, but the primitive is identical: prove that a specific computation ran in a trusted environment.
The escrow-first requirement maps to the Data pillar. The signed NEAR Intents quote serves as cryptographic proof that user funds exist. No speculation. No oracle dependency for the core swap. For same-peg stablecoin swaps (USDC to PYUSD, both nominally $1.00), the Oracle Problem is sidestepped entirely because the price relationship is defined rather than discovered.
Atomic settlement sequencing maps to the Governance pillar. The TEE enforces a strict execution path that functions as an embedded compliance mechanism. The solver cannot deviate. The code is the audit trail. This is policy-as-code applied to financial settlement, one of the Verifiable Stack’s governance primitives implemented at the protocol level.
The Black Box Leg
STP solves verification at the protocol layer. It does not solve verification at the execution layer.
Execution quality attestation is the first gap. The TEE proves the solver ran the correct code. It does not prove the solver achieved best execution at the off-chain venue. The CEX leg (Binance, Coinbase, Circle) is opaque. The swap executed, but was the fill price optimal? Was the order routed efficiently? Was there front-running? No attestation exists for what happens inside the centralized exchange [3].
The FX Oracle Problem is the second. Stablecoin-to-stablecoin swaps at approximately 1:1 parity avoid oracle dependency. But STP’s roadmap includes tokenized forex (JPY/USD, EUR/USD) and eventually tokenized RWAs (treasuries, bonds, stocks). At that point, the Data pillar’s Oracle Problem returns in full. The exchange rate was signed by someone. Cryptography can prove the signature is valid. It cannot prove the rate was fair at the moment of signing [3].
Agent decision provenance is the third. When AI agents, not human users, submit intents to STP, the question shifts from “did the swap execute correctly” to “should the swap have been initiated at all.” Which model decided to swap this stablecoin for that stablecoin at this moment? What data informed the decision? Was the model compromised by prompt injection? NEAR AI’s MPC-of-TEEs can verify the inference. STP’s Shade Agents can verify the execution. But the attestation chain connecting verified inference to STP solver attestation to NEAR Intents settlement does not exist as a unified standard [7].
The Unified Verifiable Commerce Receipt remains the missing artifact. STP proves solver execution. NEAR Intents proves settlement. NEAR AI proves inference. No protocol connects these three attestations into a single verifiable artifact that a regulator, auditor, or institutional counterparty can inspect end-to-end.
Regulatory Convergence
The regulatory pressure on stablecoin settlement is compounding from multiple directions simultaneously.
The GENIUS Act created the framework that enabled stablecoin fragmentation but does not mandate execution attestation. It standardizes what issuers must hold in reserve and how they must report. It says nothing about how swaps between stablecoins are verified at the transport layer [1].
The Bank of England’s systemic stablecoin consultation (November 2025, closed February 2026) proposed holding limits of 20,000 GBP for individuals and 10,000,000 GBP for businesses, with wholesale financial market settlement exempt. The BoE’s framework contemplates a world where stablecoins are systemically important payment instruments [8].
MiCA (Markets in Crypto-Assets) continues to impose compliance requirements on stablecoin issuers operating in the EU. The regulation addresses issuance, reserve management, and consumer protection but does not address cross-chain transport or execution attestation [8].
The EU AI Act intersection is the critical convergence point. When AI agents route stablecoin flows on behalf of users, these transactions become candidates for high-risk AI system classification under Article 6. Article 12 mandates automatic logging sufficient to reconstruct decisions. Article 13 mandates transparency provisions. Enforcement begins August 2, 2026 [9].
The implication is direct. Stablecoin flows executed by AI agents will require both financial compliance (GENIUS Act, MiCA, BoE framework) and AI compliance (EU AI Act). STP’s TEE attestation satisfies a portion of both: it proves what code ran and that the execution followed a specified path. The Verifiable Commerce Receipt that connects inference attestation to execution attestation to settlement proof is what satisfies both regimes completely. Neither STP nor any competitor provides this end-to-end today.
Who Is Building This
STP / Yonder Labs ( ): TEE-attested uncollateralized lending for stablecoin transport. Three security primitives. $1M-$10M+ capacity per swap. Live via StableFlow.
StableFlow / DapDap (@0xStableFlow): Production frontend. USDT across 9 chains. 0.01% fees. Roadmap: USDC, USD1, USDH.
@NEAR_Intents: ($13B+ all-time volume, 18.2M swaps, 130+ assets, 25+ chains): Settlement and escrow layer that STP depends on for the escrow-first security primitive [10].
NEAR AI (@near_ai): MPC across distributed TEEs. Shade Agent framework that STP solvers run on. D-Stack TEE infrastructure [4][5].
Chainlink CCIP: Cross-chain messaging with Risk Management Network and programmable token transfers. Does not address stablecoin-specific capital efficiency.
Eco Protocol: Stablecoin-specific, intent-based transport. Similar problem framing. Different execution architecture (no TEE attestation).
Circle CCTP: Native USDC burn-and-mint transfers. Chain-specific, single-issuer. Does not address cross-issuer stablecoin swaps.
Bridge / Stripe ($1.1B acquisition): Fiat-stablecoin rails. Enterprise-focused. Addresses on-ramp/off-ramp, not stablecoin-to-stablecoin transport.
USDT0 / LayerZero: Burn-and-mint OFT standard across 18+ chains. Single-issuer transport (Tether). Does not address cross-issuer pairs.
The gap everyone shares: no protocol connects settlement proof, execution attestation, and agent decision provenance into a single verifiable artifact. STP comes closest by embedding TEE attestation into the settlement mechanism. The CEX execution leg and agent reasoning layer remain unattested.
Connection to the Stack
Stablecoin settlement is where the Verifiable Stack thesis meets production economics. STP demonstrates that the Hardware pillar (TEEs), the Network pillar (attestation transport between solver and smart contract), the Data pillar (escrow-first as data integrity), and the Governance pillar (atomic sequencing as embedded compliance) can converge in a single protocol.
The remaining gap is the Application and Models pillars: when an autonomous agent decides to initiate a stablecoin swap, the reasoning behind that decision must be verifiable. STP proves the swap executed correctly. It cannot prove the swap should have happened at all.
The settlement layer now has a flight recorder for execution. It does not yet have one for decisions.
Sources
[1] GENIUS Act (July 2025). US stablecoin regulatory framework. Standardized issuer requirements, reserve obligations, reporting thresholds. Source: World Economic Forum coverage.
[2] McKinsey, “The Stable Door Opens.” Projects $3.7T stablecoin supply by 2030.
[3] Stablecoin Transport Protocol (STP) Litepaper. Yonder Labs, Proximity Labs ecosystem. Mechanism design: uncollateralized lending to TEE-attested Shade Agent solvers. Three security primitives: TEE attestation, escrow-first, atomic settlement sequencing.
[4] NEAR Shade Agents Documentation. Framework for cryptographically verified software instances running inside TEEs.
[5] dStack TEE Infrastructure. TEE infrastructure layer used by Shade Agents.
[6] StableFlow . Built by DapDap. USDT across 9 chains. 0.01% fees. @0xStableFlow
[7] NEARWEEK, “The Verifiable Stack” Series Opener. NEAR AI MPC-of-TEE architecture for verifiable inference.
[8] Bank of England, Systemic Stablecoin Consultation (November 2025, closed February 2026). Proposed holding limits: 20,000 GBP (individuals), 10,000,000 GBP (businesses). MiCA: EU regulatory framework for crypto-asset issuers.
[9] EU AI Act, Regulation 2024/1689. Article 6: Classification rules for high-risk AI systems. Articles 12–13: Record-keeping and transparency. Entry into force: August 2, 2026.
[10] NEAR Intents Dune Dashboard.
Disclaimer
This article is for educational and informational purposes only. It does not constitute legal, tax, investment, or financial advice. Token distribution mechanisms involve complex regulatory considerations that vary by jurisdiction. Protocols should consult legal counsel before implementing any tokenomics model discussed herein.
