feat(eip8130): re-pin Keystore contract set to finalized deployment

[chunter-cb]

Summary

Re-pin the EIP-8130 system-contract set in addresses.rs to the finalized base/eip-8130 deployment (contract renamed AccountConfiguration → Keystore).

• The whole set is now deployed under a single mined, non-zero CREATE2 salt shared across every contract (yielding the Keystore's 0x8130… vanity address). Updates SALT (was B256::ZERO), all seven addresses, and the four changed init-code hashes.
• P256/WebAuthn/AlwaysValid init-code hashes are unchanged — only their addresses moved with the salt.
• High-rate-payer proxy code hash updated to match the new implementation.

Verified against the base/eip-8130 Deploy.s.sol broadcast (chain 84532): each address CREATE2-derives from factory + shared salt + init-code hash.

Stacked on #4302 (feat/eip8130-admin-actor-delegation).

Test plan

• cargo test -p base-common-consensus --lib addresses:: (incl. addresses_match_create2_derivation) passes

[github-actions]

Self::ALWAYS_VALID_AUTHENTICATOR won't resolve in a module-level //! doc comment — there's no Self at module scope. This will produce a broken intra-doc link (rustdoc warns / errors depending on lint level). Should be Eip8130Contracts::ALWAYS_VALID_AUTHENTICATOR.

Suggested change

	//! contract shares the `0x8130…` vanity prefix (except
	//! [`Self::ALWAYS_VALID_AUTHENTICATOR`], a test/keyless helper deployed under the
	//! contract shares the `0x8130…` vanity prefix (except
	//! [`Eip8130Contracts::ALWAYS_VALID_AUTHENTICATOR`], a test/keyless helper deployed under the

[cb-heimdall]

🟡 Heimdall Review Status

Requirement	Status	More Info
Reviews	🟡 0/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1

[github-actions]

Review Summary

Single-file constant-value update re-pinning the EIP-8130 contract set to the finalized deployment. No issues found.

What changed:

• Removed shared SALT (was B256::ZERO), replaced with 6 per-contract *_SALT constants mined for the 0x8130… vanity prefix
• Updated all 6 contract addresses and 4 init-code hashes (P256/WebAuthn init-code hashes unchanged, addresses moved with new salts)
• Updated CANONICAL_HIGH_RATE_PAYER_PROXY_CODE_HASH (ERC-1167 runtime embeds the implementation address, which changed)
• Removed ALWAYS_VALID_AUTHENTICATOR and its init-code hash — no remaining references anywhere in the codebase
• Tests correctly adapted from 2-tuples (address, hash) to 3-tuples (address, salt, hash)

Verified:

• All 6 new addresses start with 0x8130, consistent with the module doc claim
• No dangling references to removed ALWAYS_VALID_AUTHENTICATOR or old SALT constant
• No consumers outside this file reference the removed constants
• CREATE2 derivation test structure is sound — each triple is checked against factory.create2(salt, init_code_hash)

No correctness, safety, or API design concerns.

[github-actions]

Base Std historical fork tests

Fork	Result	Passed	Failed	Skipped	base/base	base-anvil	base-std
Beryl	pass	616	0	13	a10b0bb2	6d744e03	4658f1b7
Cobalt	pass	718	0	14	a10b0bb2	ae7557c4	38567e20

View run