Skip to content

Recognize schema-zero attribution in existing Base transfers - #4

Merged
Mabolla merged 1 commit into
mainfrom
fix/erc8021-schema-zero
Oct 1, 2026
Merged

Mabolla merged 1 commit into
mainfrom
fix/erc8021-schema-zero

Conversation

@Mabolla

@Mabolla Mabolla commented Oct 1, 2026

Copy link
Copy Markdown
Owner

The live release check found a real compatibility defect: the historical Base Receipt payment passed USDC settlement checks but its Builder Code was reported absent. Receipt uses ERC-8021 schema 0; the Meter parser only recognized x402 schema 2.

  • Recognize canonical schema-0 code lists using Ox and report the decoded format.
  • Preserve schema-2 application-code matching; service codes are not substituted for the application code.
  • Do not verify custom-registry schema-1 identity from a string match alone.
  • Pin Ox 1.7.4 and add seven regression tests.
  • Document the working hosted Meter interface and retain the old Railway outage notice.

Validation: all 35 tests, typecheck and build passed. Re-reading historical transaction 0xa7c0d15e190b7ab099c03013b14f07c6a58a7c15c8c1e7a8132bb7512c9e881d through the fixed code returned settlementVerified=true and builderAttribution.verified=true for bc_87fjmj1l. No transaction was submitted and no receipt claim was created. The host must update its pinned dependency after merge.

@Mabolla
Mabolla merged commit da65ede into main Oct 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant