Docs / Networks

Arbitrum

Arbitrum 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. Arbitrum One and Arbitrum Sepolia: an optimistic rollup with native USDC and Chainlink feeds; the same EVM binding applies unchanged.

EVM binding

At a glance

LOPW contracts

Arbitrum Sepolia

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

Arbitrum One

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

Oracle note

P6 terms on Arbitrum 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.

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