Repository navigation
Deploy Meter attribution compatibility fix - #4
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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 Meter check verified the existing USDC transfer but missed its Builder Code because the previous core only decoded schema-2 attribution.
Update the pinned Meter core to da65ede903c22280020f5a31fe0417cbad14f0e3, which also verifies canonical ERC-8021 schema-0 code lists. Keep custom-registry identity unverified and preserve schema-2 application-code matching. Document the supported formats and give the Meter page its own browser title.
Validation: all 18 host tests, lint, typecheck and production build passed. The core's 35 tests and GitHub CI passed; its updated verifier checked the historical 0.01 USDC transfer and bc_87fjmj1l attribution successfully without submitting a transaction. After deployment, scripts/check-meter.mjs --network will repeat that proof through the public MCP endpoint.