Record: Base Sepolia EntryPoint v0.8 Deployment - #118
Merged
Merged
Conversation
address.json goes back to being a flat address lookup, one line per contract, the same shape every other entry has. Everything else the deploy captured lives in its own file next to it.
The full record for the Base Sepolia deployment on EntryPoint v0.8 is now deployments/base-sepolia-84532-entrypoint-v8.json. The filename is the key the scripts build from the chain id and EntryPoint version, so it cannot disagree with the chain it describes and the scripts can find it without being told.
address.json is the address book, a flat name to address map per chain, and that is all it holds. The build provenance, constructor arguments, role holders and status that later scripts read move to deployments/<recordKey>.json, one file per deployment. The deploy now writes both, so the address book stays current without anyone editing it by hand. Its already-deployed guard checks both files, since either one alone is enough to make a redeploy overwrite something live.
The rehearsal now clears both its address book entry and its record file on exit, and refuses to start when either exists. compute-initCode reads the record file, since the address book no longer carries a contracts section.
Each contract address in the current deployment column now points at its Basescan page, so the record can be checked without leaving the README.
Updated README to include a link to the deployment commit.
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 this deployment changes
This redeploys the full contract suite to Base Sepolia on EntryPoint v0.8, replacing the v0.7 deployment. Two things drove it: gas sponsorship needed a newer EntryPoint, and the old admin setup put every wallet one stolen key away from being drained.
Admin control no longer sits behind one key
The old deployment: one EOA owned the registry, both factories, and both wallet beacons. Whoever held that key could push an upgrade or change protocol settings instantly, with the transaction sitting in the public mempool for anyone to see coming.
The new deployment: ownership moves to a timelock contract (
ProtocolAdmin).In practice: a stolen key can no longer touch user funds in a single transaction. The two-day window gives the team time to notice and react before any change takes effect.
Gas sponsorship now works
The wallets sit on EntryPoint v0.8. The paymaster that sponsors gas for users only supports v0.7 and v0.8, so this was required to keep gasless transactions running.
Because the EntryPoint address is baked into each wallet's bytecode, moving versions meant redeploying rather than upgrading in place. Every proxy, factory, and beacon here is new.
Testing and security work behind this deployment
This deployment sits on top of a hardening pass, not just a version bump.
audits/2025-03-CDSecurity.pdf); this pass covers everything added or changed since.Everything shipped with a paper trail
What stays the same
Device registration and the eSIM data purchase flow are unchanged in behavior. The v0.7 deployment stays live and untouched for anything still pointed at it.