Skip to content

docs(IActivationRegistry): warn integrators not to use code presence as activation signal (BOP-322) #151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rayyan224 wants to merge 1 commit into from
Closed

docs(IActivationRegistry): warn integrators not to use code presence as activation signal (BOP-322) #151

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/interfaces/IActivationRegistry.sol
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,12 @@ pragma solidity >=0.8.20 <0.9.0;
/// @title IActivationRegistry
/// @notice Singleton precompile that gates Base-native features behind an activation admin. Each feature
/// is identified by an opaque `bytes32` id and is either active or inactive.
///
/// @dev INTEGRATION NOTE — do not use code presence as a feature gate. The precompile writes a
/// bytecode marker to its own storage account on the first successful `activate` call and does
/// not clear it when features are subsequently deactivated. `EXTCODESIZE` and `EXTCODEHASH` at
/// this address therefore reflect initialisation state, not live activation state. Always use
/// `isActivated(feature)` as the authoritative signal.
interface IActivationRegistry {
/*//////////////////////////////////////////////////////////////
ERRORS
Expand Down
Loading