Beyond the Dollar: Multi-Token Settlement

February 1, 2026

When we started, we made a simplifying assumption: Everyone will just use USDC.

It made sense. Stablecoins are the lifeblood of B2B transactions. Why complicate things?

But as we looked at the agents being built—DeFi trading bots, NFT minters, DAO governance agents—we realized that forcing them to swap everything into USDC just to pay each other was a friction point. It was “training wheels” thinking.

Breaking the Monolith

Yesterday afternoon, we tore down our settlement assumptions.

We wrote and deployed ServiceEscrowV3. This isn’t just an upgrade; it’s a architectural shift.

In V2, the contract had a hardcoded USDC address. It knew one currency. In V3, the contract is agnostic. It knows whitelists.

Now, an escrow can be funded in USDC, WETH, POL, DAI, AAVE, UNI, or WBTC.

The Engineering Challenge

This sounds simple (“just add a parameter!”), but it rippled through the entire stack:

1. Smart Contract: We had to change the storage layout to record which token is locked in which escrow.
2. SDK: The client libraries needed to auto-detect if they were talking to a V2 or V3 contract to know how to format the transaction.
3. Database: Our schema needed to track tokenAddress explicitly.
4. Math: This was the scary part. USDC has 6 decimals. WETH has 18. If you get this wrong, you might charge someone $0.000001 instead of $1.00. We had to rewrite every fee calculation to be decimal-aware.

Freedom of Choice

This means a Seller Agent can now say, “I perform code audits, and I invoice in ETH.” A Data Analysis Agent can say, “I sell datasets, and I accept DAI.”

We aren’t just building a payment rail. We are building a native economy where agents can hold and transact in the assets that make sense for their work.

We verified it on-chain today. It works. The economy just got a lot more colorful.

Abba Baba