Tracking issue for the engineering work that has to land before Base/EVM can be called the canonical AgentVouch chain. Context: the gas-free UI + live x402 agent purchase (#53) settled the UX question, but the deployed AgentVouchEvm (Base Sepolia 0x5D90…913E) is Phases 0–4 only — the trust-enforcement half of the protocol does not exist in Solidity yet. Decision framing in docs/KORA_VS_BASE_X402.md (#54) and docs/BASE_POC_INTERIM.md.
This issue makes the "fund the bet" sequence actionable. It is gated on an explicit decision (item 0) — none of the build work below should start until the x402/agent-commerce distribution bet is committed.
0 · Decision gate (blocks everything below)
1 · Port Phases 5–7 to the EVM contract (parity with Solana)
The Solana program has these; the EVM contract does not. Port by spec, not transpilation, matching the Solana semantics.
2 · Fix Lane B F-1 (EIP-3009 fund-stranding)
The signed authorization names the contract as to, so it can be replayed straight to USDC — funds land in the contract with no purchase receipt, stranded (test_laneB_frontRunStrandsFundsNoReceipt). Re-surfaced in #53.
3 · Production hardening (before any hosted/mainnet surface)
4 · Migration & operations
Parallel track (not blocked by item 0)
Refs: #53 (UX + x402 POC), #54 (decision doc), docs/BASE_POC_INTERIM.md (Phase 4.5 gate).
Tracking issue for the engineering work that has to land before Base/EVM can be called the canonical AgentVouch chain. Context: the gas-free UI + live x402 agent purchase (#53) settled the UX question, but the deployed
AgentVouchEvm(Base Sepolia0x5D90…913E) is Phases 0–4 only — the trust-enforcement half of the protocol does not exist in Solidity yet. Decision framing indocs/KORA_VS_BASE_X402.md(#54) anddocs/BASE_POC_INTERIM.md.This issue makes the "fund the bet" sequence actionable. It is gated on an explicit decision (item 0) — none of the build work below should start until the x402/agent-commerce distribution bet is committed.
0 · Decision gate (blocks everything below)
.agents/plans/kora-usdc-fee-abstraction.plan.md).1 · Port Phases 5–7 to the EVM contract (parity with Solana)
The Solana program has these; the EVM contract does not. Port by spec, not transpilation, matching the Solana semantics.
openDispute/resolveDispute, dispute statuses (Open/Resolved/SlashingVouchers), and the bond/listing locks (the EVM contract already hasDisputeLocked/BondExposureLockederrors +openDisputescounters wired as no-op guards — fill in the lifecycle that sets them).AuthorBondOnly,AuthorBondThenVouchers), theVouchStatus.Slashedtransition (Phase 5 residual rules referenced atAgentVouchEvm.solvouch), and stake reduction accounting.2 · Fix Lane B F-1 (EIP-3009 fund-stranding)
The signed authorization names the contract as
to, so it can be replayed straight to USDC — funds land in the contract with no purchase receipt, stranded (test_laneB_frontRunStrandsFundsNoReceipt). Re-surfaced in #53.receiveWithAuthorization(bindsmsg.sender == to) or a documented reconciliation/sweep path. Note: a sweep tends to reintroduce some settlement-authority trust — weigh against Lane B's trust-minimization, the whole reason it exists.agent-x402-demo.ts) + UI accordingly.3 · Production hardening (before any hosted/mainnet surface)
VITE_CDP_RPC_URLin feat(base-poc): Base Sepolia gas-free UI + x402 agent purchase flow #53's UI); a hosted UI makes it a drainable sponsorship endpoint. Allowlist the contract + USDCapprove/transfercalls and rate-limit.contracts/base-poc/ui+harnessinto CI typecheck (currently outside the repo's scoped typecheck —tsc --noEmitis a local-only claim).4 · Migration & operations
docs/DATABASE_CUTOVER.mdfor prior cutover shape).web/lib/chains.tsalready carrieseip155:8453).Parallel track (not blocked by item 0)
.agents/plans/kora-usdc-fee-abstraction.plan.md). Removes live "you need SOL" friction now, keeps Solana usable through any migration window, and is not wasted if Base wins.Refs: #53 (UX + x402 POC), #54 (decision doc),
docs/BASE_POC_INTERIM.md(Phase 4.5 gate).