docs: sync deployed-contracts registry with live chain + verify ERC-4337 infra#176
Merged
Merged
Conversation
…4337 infra - Fix stale bytecode counts: SidecarRegistry 4572->7200, CredentialAudit 3043->2584 (verified via cast code against Heima mainnet). - Add live bytecode counts for P256Verifier (3428), K11Verifier (2033), EntryPoint (11810), P256AccountFactory (4591) as drift-detection anchors. - Note VerifyingPaymaster.sol is intentionally NOT deployed (direct EntryPoint.handleOps; no paymaster). - operator-workstation.env: add ENTRYPOINT_ADDRESS_HEIMA + P256_ACCOUNT_FACTORY_ADDRESS_HEIMA (#164) -- the operational source of truth was missing the deployed ERC-4337 pair. - verify-heima-contracts.sh: add step 5 -- checks EntryPoint + P256AccountFactory bytecode + the factory entryPoint()/k11Verifier() constructor wiring, conditional so non-ERC-4337 chains skip cleanly. Verified green end-to-end.
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
1 participant
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.
What
Audited
docs/spec/deployed-contracts.mdagainst the live Heima mainnet (cast code). The registry is complete — all 8 deployed contracts are present — but it carried stale/missing bytecode counts and two operational-tracking gaps for the ERC-4337 pair.Changes
docs/spec/deployed-contracts.mdSidecarRegistry4572→7200,CredentialAudit3043→2584 (the 4572 was a copy-paste of AgentKeysScope's count).P256Verifier3428,K11Verifier2033,EntryPoint11810,P256AccountFactory4591 — drift-detection anchors.VerifyingPaymaster.solis intentionally not deployed (directEntryPoint.handleOpsfrom a pre-funded account; no paymaster).scripts/operator-workstation.envENTRYPOINT_ADDRESS_HEIMA+P256_ACCOUNT_FACTORY_ADDRESS_HEIMA(Migrate master authority to an ERC-4337 P-256 smart-account (resolves §11 gating findings) #164). The doc had these but the env — the operational source of truth per CLAUDE.md's registry policy — did not.scripts/verify-heima-contracts.shEntryPoint+P256AccountFactorybytecode presence and the factory'sentryPoint()/k11Verifier()constructor wiring. Conditional on the env vars being set, so non-ERC-4337 chains (Paseo) skip cleanly.Verification
AGENTKEYS_CHAIN=heima bash scripts/verify-heima-contracts.sh→ all 5 steps pass, exit 0 against live Heima mainnet; the run's byte counts match the corrected doc.🤖 Generated with Claude Code