Skip to main content
Caplane states its known weaknesses upfront. What survives an adversarial read is what you can trust. Two are worth declaring plainly, because a careful reader will find them anyway.

​
The gas-sponsorship underlying is commoditized

A paymaster that accepts USDC to front gas is not novel. Pimlico, Circle, Biconomy, and ZeroDev already do it. So a gas-only demonstration proves nothing about Caplane. The novelty is the primitive and its proven generality, not gas sponsorship. Gas is one adapter, included because “my agent has USDC but no ETH” is a real pain, not because it is the pitch.

​
The Timeboost resale market has largely collapsed

Caplane ships a Timeboost adapter (priority inclusion in an Arbitrum express lane) as a second, categorically distinct capability. But the express-lane resale market itself has largely collapsed: an empirical study of 11.5M transactions (arXiv:2509.22143) found two entities winning over 90% of auctions and roughly 22% of transactions reverting, and known operators found resale unprofitable. So Timeboost is in Caplane as a generality proof, the categorically-different second adapter that shows the primitive is not specific to one capability, not as a claim of live resale demand.

​
What this does not undercut

Generality is proven by at least two categorically distinct adapters running side by side: a consumable quota (an Allocation slot) and a scarce execution right (Timeboost). The value is the binding and the facilitator-free atomic settlement, which work for any scarce on-chain capability. The two landmines are about two specific underlyings, not about the primitive. The guaranteed floor is the AllocationAdapter, which has no external dependency and is the capability the Quickstart brokers.

​
What Caplane deliberately does not do

Caplane settles on-chain capabilities atomically. It does not validate off-chain deliverables. ERC-8004’s Validation registry targets off-chain work (did an agent actually do the compute it was paid for); Caplane has no such surface, because the grant self-validates in the same transaction as the payment, or the whole transaction reverts. Caplane composes with the parts of that ecosystem it actually uses (identity, reputation, the x402 transport, the MCP tool surface) and does not claim the parts it does not. See composes with, not competes.