-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
It is common in EVM-compatible chains to deploy "common good contracts" or "standards" using Nick's method, a way to send transactions using mocked signatures, which provides reassurance that no one actually has a private key for the generated address that sent the transaction.
Some example contracts that are deployed this way:
-
ERC-1820 Registry
- Implementation repo: https://github.com/0xjac/ERC1820
- Mainnet contract (0x1820a4B7618BdE71Dce8cdc73aAB6C95905faD24):
https://etherscan.io/address/0x1820a4B7618BdE71Dce8cdc73aAB6C95905faD24
-
Deterministic Deployment Proxy (0x4e59…b4956C)
- Implementation repo: https://github.com/Arachnid/deterministic-deployment-proxy
- Mainnet contract (0x4e59b44847b379578588920cA78FbF26c0B4956C):
https://etherscan.io/address/0x4e59b44847b379578588920cA78FbF26c0B4956C
-
EIP-2470 Singleton Factory
- Spec + reference code: https://eips.ethereum.org/EIPS/eip-2470
- Mainnet contract (0xce0042B868300000d44A59004Da54A005ffdcf9f):
https://etherscan.io/address/0xce0042B868300000d44A59004Da54A005ffdcf9f
-
Multicall3 (0xcA11…CA11)
- Implementation repo: https://github.com/mds1/multicall3
- Mainnet contract (0xcA11bde05977b3631167028862bE2a173976CA11):
https://etherscan.io/address/0xcA11bde05977b3631167028862bE2a173976CA11
All of these are “common good” or infrastructure-style contracts that are either keyless deployments using Nick’s method or are deployed via canonical, immutable factories to provide strong guarantees about code and address consistency across chains.
Metadata
Metadata
Assignees
Labels
No labels