Repository navigation
Recognize schema-zero attribution in existing Base transfers - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
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.