Repository navigation
The registry evidence reads the receipt signer from chain state - #37
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.
Requested by chris · project thread
User-facing change
public/evidence/registry/README.mddocuments the on-chain binding of receipt signer0xa41494…1eecto ERC-8004 agent 1135859 (setMetadata, tx0xe3c78307…4a24, Base block 53386669), with thegetMetadataread. It no longer says no rotation record exists: the registry'sMetadataSetevents are that record.Changelog
## [Unreleased]inCHANGELOG.md.How you checked it
MetadataSettopic00x2c149ed5…and key hash0xf89b17b3…, which equals keccak256("x_proofable.receiptSigner"). The value names the signer.sha256sum -c SHA256SUMSOK, markdownlint 0 errors, language gate clean.Generated by Claude Code