Skip to content

spec: use canonical base/commerce-payments addresses #43

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
A1igator merged 14 commits into from
May 9, 2026
Merged

spec: use canonical base/commerce-payments addresses #43

Changes from all commits
Commits
Show all changes
14 commits
Select commit Hold shift + click to select a range
e708f94
spec: point AuthCapture addresses at the live base/commerce-payments …
A1igator May 8, 2026
3f10452
spec: clarify multichain wording — `commerce-payments` maintainers, n…
A1igator May 8, 2026
72c46d5
spec: simplify multichain wording — "every chain it's deployed to"
A1igator May 8, 2026
2bf606c
spec: drop "audited" — editorial, not in the requested change
A1igator May 8, 2026
b9a351e
spec: restore @v1.0.0 release-tag pin on the Source link
A1igator May 8, 2026
d83e628
spec: drop "Audited" at line 7 — editorial leftover
A1igator May 8, 2026
f2a94ca
spec: line 7 — back to bracket form, matching the line-62 phrasing
A1igator May 8, 2026
d97d110
spec: line 62 — back to minimal-diff form, matching line 7
A1igator May 8, 2026
e38e700
spec: Canonical Addresses section — minimal-diff form
A1igator May 8, 2026
14f8298
spec: collapse duplicate address tables; link to upstream sources
A1igator May 8, 2026
efedf62
spec: drop the Requirement blockquote in Canonical Addresses annex
A1igator May 8, 2026
bb434b5
spec: match scheme_exact_evm.md's Permit2 link target
A1igator May 8, 2026
6cfe567
spec: match wording across the two Canonical Addresses pointers
A1igator May 8, 2026
b7978b7
spec: capitalize link text — "Base Commerce-Payments contracts"
A1igator May 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 3 additions & 23 deletions specs/schemes/authCapture/scheme_authCapture_evm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

The `authCapture` scheme on EVM uses the [base/commerce-payments](https://github.com/base/commerce-payments) contract stack:

- **AuthCaptureEscrow**: Singleton — locks funds, enforces expiries, distributes on capture/refund. Universal canonical address (CREATE2-deployed; same address on every supported chain).
- **AuthCaptureEscrow**: Singleton — locks funds, enforces expiries, distributes on capture/refund. Universal canonical address (same address on every supported chain).
- **Token Collectors**: Universal canonical addresses, one per `assetTransferMethod`:
- `EIP3009_TOKEN_COLLECTOR_ADDRESS` — collects funds via `receiveWithAuthorization` signatures (USDC, EURC, etc.)
- `PERMIT2_TOKEN_COLLECTOR_ADDRESS` — collects funds via Uniswap Permit2 `permitTransferFrom` (any ERC-20)
Expand Down Expand Up @@ -59,17 +59,6 @@ AuthCapture-accepting servers advertise with scheme `authCapture`:
| `autoCapture` | No | `bool` | `true` → facilitator calls `charge()` (atomic). `false` → `authorize()` (two-phase). Default: `false`. |
| `assetTransferMethod` | No | `"eip3009" \| "permit2"` | Which token collector to use. Default: `"eip3009"`. A server MAY list multiple `accepts[]` entries with different `assetTransferMethod` values so clients can pick the method matching their token approvals. |

**Universal contract addresses** (same on every supported EVM chain via deterministic CREATE2):

| Constant | Address |
| :------------------------------------ | :------------------------------------------- |
| `AUTH_CAPTURE_ESCROW_ADDRESS` | `0xF8211868187974a7Fb9d99b8fFB171AD70665Dc6` |
| `EIP3009_TOKEN_COLLECTOR_ADDRESS` | `0x7561DC178D9aD5bc5fb103C01f448A510d2A36D0` |
| `PERMIT2_TOKEN_COLLECTOR_ADDRESS` | `0xD8490609d2da0ee626b0e676941b225cbc1A8C08` |
| `PERMIT2_ADDRESS` (Uniswap canonical) | `0x000000000022D473030F116dDEE9F6B43aC78BA3` |

See [Canonical Addresses](#canonical-addresses) for the salt scheme.

### Spec → on-chain field name mapping

The wire-format extra uses spec-level field names. The on-chain `PaymentInfo` struct keeps canonical Solidity names so the EIP-712 typehash matches the AuthCaptureEscrow contract byte-for-byte.
Expand Down Expand Up @@ -303,15 +292,6 @@ Fees are enforced on-chain by the escrow contract:

### Canonical Addresses

> **Requirement**: The escrow and token collectors are deployed at the same address across every supported EVM chain via deterministic CREATE2. Bytecode is byte-identical (locked compiler, optimizer, and dependency pins); anyone with the source can reproduce and verify the addresses, and any first-mover deployer who broadcasts the canonical bytecode at the canonical salt lands at the same address.

**Source**: [base/[email protected]](https://github.com/base/commerce-payments/releases/tag/v1.0.0).

**Salt scheme**: `bytes20(0) || 0x00 || bytes11(keccak256(label))`. The leading 21 bytes are constant; the label is the per-contract namespace below.
The `AUTH_CAPTURE_ESCROW_ADDRESS`, `EIP3009_TOKEN_COLLECTOR_ADDRESS`, and `PERMIT2_TOKEN_COLLECTOR_ADDRESS` constants resolve to the canonical [Base Commerce-Payments contracts](https://github.com/base/commerce-payments/releases/tag/v1.0.0).

| Constant | Salt label | Canonical Address |
| :------------------------------------ | :------------------------------------------------ | :------------------------------------------- |
| `AUTH_CAPTURE_ESCROW_ADDRESS` | `commerce-payments::v1::AuthCaptureEscrow` | `0xF8211868187974a7Fb9d99b8fFB171AD70665Dc6` |
| `EIP3009_TOKEN_COLLECTOR_ADDRESS` | `commerce-payments::v1::ERC3009PaymentCollector` | `0x7561DC178D9aD5bc5fb103C01f448A510d2A36D0` |
| `PERMIT2_TOKEN_COLLECTOR_ADDRESS` | `commerce-payments::v1::Permit2PaymentCollector` | `0xD8490609d2da0ee626b0e676941b225cbc1A8C08` |
| `PERMIT2_ADDRESS` (Uniswap canonical) | (Uniswap canonical, not CREATE2'd by this scheme) | `0x000000000022D473030F116dDEE9F6B43aC78BA3` |
The `PERMIT2_ADDRESS` constant resolves to the canonical [Uniswap Permit2 contract](https://docs.uniswap.org/contracts/v4/deployments).
Loading