An essay on positioning
Where Radix is structurally built to win — and why it isn't where most people are looking.
§ 01 — The setup
When Tempo launched its mainnet in March, the framing was that agentic payments — AI agents transacting on behalf of humans, paying for paywalled content, calling paid APIs, settling micropayments at machine speed — were finally solved. Stripe and Paradigm shipped the standard, called the Machine Payments Protocol. Cloudflare and Coinbase shipped the competing standard, called x402. The infrastructure question, in the framing of the people building it, was no longer whether but which.
By May, the answer was mostly settled. RedotPay's seven million users were live on MPP. Walmart-backed OnePay had signed on. Tempo's design partner list ran through Anthropic, OpenAI, DoorDash, Mastercard, Nubank, Ramp, Revolut, Shopify, Standard Chartered and Visa. In the parallel x402 race, Solana had quietly taken around half of all agent-to-agent transaction volume. Base, Ethereum, Polygon, Arbitrum, Optimism, Avalanche, Aptos, Stellar, Sui and Hedera had all shipped native support. Coinbase, Cloudflare, Google and Visa had formed a foundation to govern the standard.
In the conversations that mattered for these decisions, Radix did not come up. Not once.
This is the part of the analysis that deserves to be stated plainly rather than danced around. The standards race is run. The MVP integration race is run. The early-distribution race is run. None of these will be re-run on terms favourable to a network that wasn't in the room when they were decided. The architecture of the agentic web has been chosen, and Radix was not one of the architects.
§ 02 — The catch
Two days ago, Cloudflare's CEO Matthew Prince was on Bankless making a different argument. AI traffic will exceed human traffic on the internet in the first half of 2027 — earlier than Cloudflare had previously estimated. Stablecoins and HTTP-native micropayments are part of the answer. But no current blockchain, he said plainly, supports the volume Cloudflare would actually require.
He is correct. Tempo's published benchmark is around one thousand transactions per second, with eleven validators most of which Tempo itself operates. Solana, which dominates x402 volume, is genuinely faster but has had outages and remains far below the throughput Cloudflare would need to underwrite global agent traffic. The standards have been settled. The infrastructure to actually carry the load has not.
This gap — between "MVP shipped" and "production at internet scale" — is the gap that Xi'an, Radix's hyperscale partial-execution sharding rollout, is aimed at. It is also the gap that nobody else has a credible answer to. So there is a temptation, particularly within the Radix community, to read this as a second-chance entry into agentic payments. The standards race was lost; the throughput race is open; Radix can win the throughput race; therefore Radix can still win agentic payments.
This reasoning is incomplete in a way that matters.
The production race is not just a throughput race. It is also a partnerships race, a capital race, and a timeline race against incumbents with ten to a hundred times the war chest, who will iterate on their own scaling roadmaps with the benefit of actual production volume to optimise against. Tempo did not win the early agentic phase because its block times were marginally better. It won because Stripe plumbed it in. Solana did not take half of x402 volume because of consensus innovations. It took half because Coinbase's facilitator made Solana the path of least resistance for developers already in that ecosystem.
Radix can plausibly win the technical side of the production race and still lose it on every other axis. That is the honest read, and treating it as anything else is wishful.
§ 03 — The actual ground
To understand where Radix should compete, it helps to look at what its architecture is unusually good at — not what it can do as well as everyone else, but what it does better than EVM, better than Solana, better than the chains currently winning the agentic narrative. Four things stand out, and they cluster around a coherent strategic territory.
On most chains, a token is a contract that maintains a ledger of who owns what. On Radix, an asset is a first-class object in the runtime. It cannot be duplicated by a buggy contract. It cannot be lost in a faulty transfer. It cannot be silently inflated. The implications are subtle but compound: an entire class of high-value smart-contract failures that EVM developers must actively guard against simply cannot occur. This matters most where the value at stake is large enough to attract sophisticated attackers, and where a single exploit ends careers.
Recallability, allowlists, denylists, transfer restrictions, freeze mechanisms — all available at the protocol layer, not bolted on through wrapper contracts whose enforceability under regulation depends on the issuer's legal opinion holding up in court. If a token issuer needs to revoke an asset for a sanctions match, a court order, or a fraud determination, Radix supports it natively. If an asset must only transfer between accounts on an approved list, Radix supports it natively. Most chains require bespoke contracts to approximate this, and the approximation is often the precise thing that fails an audit.
Atomic multi-party transactions where each party signs only their portion, and the entire transaction settles or fails as a single unit. Delivery-versus-payment, three-way trades, multi-party escrow, complex supply-chain disbursements: all of these are awkward or impossible on chains without this primitive. On Radix they are a natural expression of the transaction model. The competitive significance of this is consistently underrated.
A declarative, human-readable format that shows exactly what a transaction will do before it is signed. For a retail user, this means meaningful wallet preview. For a regulated entity, it means transaction logs that an auditor can read without translation. The compliance value of this is underestimated by people who have not sat across the table from an auditor.
§ 04 — The precedent
The first non-crypto-native value flow on Radix was not an agent paying for an API call. It was a New Zealand dairy farmer borrowing money. The lender, Ploughshare, is a licensed financial services provider with experienced founder-led underwriting and a regulatory wrapper that means the loan is a real loan, enforceable in real courts. The on-chain layer — SRWA's protocol — handles the asset representation, the compliance controls, and the settlement.
The shape of this deal is more significant than its current size. A regulated entity originates a real-world financial product. Radix provides the technical infrastructure that makes the compliance layer enforceable rather than aspirational. The result is inbound capital flow into the network from outside the crypto economy. A loan to a dairy farm is not a glamorous proof point, but it is a structurally clean one — and that cleanliness is the entire point.
The question that matters now is not whether Ploughshare itself scales. The question is whether the pattern it demonstrates — regulated originator, native compliance infrastructure, real-economy capital — replicates across other verticals. The remainder of this essay argues that it does, and sketches a map.
§ 05 — The map
Four verticals fit the Ploughshare shape closely enough to be candidates for deliberate cultivation. A fifth is contested territory worth a thoughtful narrower entry. Beyond that there is a longer tail of plausible but lower-priority wedges. They are sketched in order of fit, not size.
Trade finance is roughly a 2.5 trillion dollar annual market with a structural 2.5 trillion dollar financing gap that traditional banks cannot close because the underwriting is too operationally intensive for the margins. The transactions are inherently multi-party — buyer, seller, freight forwarder, financier, insurer, sometimes customs — and atomic settlement matters because no party will release their leg without simultaneous release by the others.
Radix's subintents map onto this almost too neatly. Letters of credit, invoice factoring, receivables financing, purchase-order financing all share this shape. The competitive landscape is surprisingly weak: Contour folded, Marco Polo folded, We.Trade folded. The only credible player is Komgo, which is centralised. A Radix-native trade finance origination platform with proper regulated wrappers in a trade-active jurisdiction — Singapore, Switzerland, the UAE — could be a Ploughshare-scale wedge into a vastly larger total market.
Tokenised money market funds and treasury funds have gone from effectively zero to over seven billion dollars in roughly two years. BlackRock's BUIDL, Franklin Templeton's BENJI, Ondo's OUSG and the wave behind them sit almost entirely on Ethereum or its L2s, where the compliance layer is bolted on via wrapper contracts that the issuer hopes will hold up in court.
Radix's recallable assets, allowlist and denylist primitives, and manifest-readable transactions are precisely what a fund administrator's general counsel would draw on a whiteboard if invited to specify the ideal chain from first principles. The wedge is partnering with a regulated fund administrator to issue a Radix-native version of a treasury or MMF product. Plume is targeting the same territory with EVM compatibility as its lever. Radix's lever is being structurally safer for the issuer — a meaningfully different pitch.
Private placements and Reg D / Reg S offerings sit between the two above. They need transfer restrictions — lockup periods, jurisdictional limits, accredited-investor verification — and the issuer needs ongoing visibility and control after issuance. Provenance Blockchain has spent years trying to own this category and is doing perhaps twenty billion dollars in cumulative volume, but with limited DeFi composability. Plume is the other meaningful entrant.
The competitive moat for Radix here is the combination of subintents and asset-oriented programming. Delivery-versus-payment settlement of cash and security in a single atomic transaction is structurally cleaner on Radix than on any EVM chain, because the atomicity is native rather than approximated by escrow contracts. For an institutional counterparty, structural cleanliness translates directly into reduced operational and counterparty risk — which translates into willingness to write the cheque.
B2B cross-border settlement is where Tempo is going directly, with Stripe distribution behind it. This is a harder fight for Radix to win head-on. But there is a defensible niche inside it: payments that need to settle across three or more stablecoin currencies in a single atomic transaction. Imagine a freight payment from a UK importer in GBP-stable to a Vietnamese supplier in USD-stable, financed by a Singaporean intermediary in SGD-stable, with FX rates locked through a market maker.
Radix's asset-oriented runtime handles multi-asset atomicity in a single transaction more elegantly than EVM. This is a niche play rather than a category play — but the unit economics of multi-currency B2B settlement are good, and the competition has not yet bothered to design for it specifically.
High compliance burden, frequent need to invalidate or recall fraudulent credits, and an integrity crisis in the voluntary carbon market that has buyers actively demanding stronger provenance. Radix's asset model is structurally suited to credits-as-objects rather than credits-as-ledger-entries. Market is smaller, but the structural fit is among the cleanest of any vertical here.
Multi-party — insured, insurer, reinsurer, oracle, payout — atomic, and asset-natured. Subintents fit. Companies like Arbol and Skyline have been working this on EVM with mixed results. A Radix-native parametric product with proper regulated wrappers in a sympathetic jurisdiction would be a credible second-order wedge once trade finance or tokenised funds had established the playbook.
§ 06 — The narrower thesis
The temptation, for a network in Radix's position, is to chase whichever narrative is currently loudest. In 2026 that narrative is agentic payments, and the gravitational pull to compete there is strong precisely because everyone else is competing there. The argument of this essay is that Radix should resist that pull.
The investment thesis that holds up under scrutiny is narrower and more disciplined: Radix is a specialised chain whose architecture genuinely shines on multi-party, compliance-heavy, atomically-settled financial activity. The Ploughshare result is a tell. The question for the Foundation, and for the Community Entity post-transition, is whether the next twelve months are spent cultivating more Ploughshare-shaped projects in the verticals sketched above — or scattered across categories where Radix's strengths do not matter and its weaknesses do.
If the bet is the former, the forward indicators are knowable. A second non-crypto-native lending or RWA origination deal closing within six months validates that the pattern is repeatable. A named integration with a trade finance platform, a fund administrator, or a securities tokenisation issuer signals movement into one of the strongest-fit verticals. A grant or incentive programme that explicitly targets regulated origination — rather than spreading thinly across consumer DeFi, gaming, and meme tokens — signals strategic discipline at the level it now needs to exist.
If the bet is the latter, the signal will be the absence of these things, and a continued attempt to be relevant in conversations where the relevance has already been allocated to other networks.
The agentic web will get built. It is being built. Radix will not be the chain it gets built on, and pretending otherwise costs credibility that this network cannot afford to spend twice. The ground worth holding is elsewhere, the map is legible, and the work to be done is to convert one demonstrated pattern into many.
That is the entire opportunity. It is also enough.