Docs / Networks

Base

Base runs LOPW through the shared EVM binding: Solidity contracts, EIP-712 typed data signed with secp256k1, native USDC with 6 decimals, Chainlink feeds for P6 and x402 exact with EIP-3009. The first EVM network of the binding: the Solidity contracts, the TypeScript binding and the EVM reference service are built against Base Sepolia first.

EVM binding Base first

At a glance

LOPW contracts

Base Sepolia

Not deployed No LOPW deployment is published on this network yet.

Base

Not deployed No LOPW deployment is published on this network yet.

Oracle note

P6 terms on Base name a Chainlink AggregatorV3Interface feed and its pair label as bytes32. The seller cites the roundId it used; the validator reads getRoundData(roundId) on-chain, applies max_oracle_age to the round’s updatedAt, and proves a breach with the exact integer deviation test. Every feed address is verified on-chain (description(), decimals()) before use and recorded in deployments/<network>.json. Chainlink ETH / USD, 8 decimals, heartbeat 1200 s, 0.15 % threshold; Base Sepolia publishes no EUR/USD feed, so the EVM reference service quotes ETH/USD here.

What is identical to every other EVM network

• The Solidity contracts, their functions, errors and events.
• The EIP-712 type strings and the domain LOPW / 1; only chainId and verifyingContract change.
• The wire form: 0x-hex ABI encoding of SignedOffer and SignedReceipt.
• USDC with 6 decimals as stake and payment token; x402 exact with EIP-3009.
• Indexing after EVM_CONFIRMATIONS confirmations, writing the same events, services and claims rows with network set to the names above.

For agents