Infrastructure

EIP-1014 introduced CREATE2, which calculates a contract address from a deployer, salt and exact initialization code before deployment. Counterfactual wallets can use this when they have a supported factory and verified control path. A predicted address alone does not guarantee deployment, sponsorship or safe recovery of funds.

Category: Infrastructure

ERC-1167 defines minimal clones that delegate calls to a fixed implementation address. Many instances can share code while keeping separate storage. The small runtime can reduce deployment gas, but the actual fee and confirmation time depend on the factory, initialization and network.

Category: Infrastructure

ERC-1967 defines storage slots for a proxy's implementation, beacon, and admin information. Tools can resolve supported proxies and show the code they delegate to. Discover actual upgrade authority and source verification separately; standard slots do not establish safe code or universal explorer support.

Category: Infrastructure

ERC-2535 lets a diamond route function calls to multiple facet contracts at one address. Facet composition and any upgrade authority must be inspected for that deployment. The pattern does not remove transaction gas limits or make a diamond safe or necessarily upgradeable.

Category: Infrastructure

ERC-5202 identifies blueprint bytecode that stores initialization code for later deployment. The blueprint is not a callable application. A deployment action needs a compatible factory or tool, and the resulting instance has its own address, initialization, and control policy.

Category: Infrastructure

ERC-7201 defines named storage namespaces and their location formula. Correct implementations can reduce storage-collision risk, while developer tools can explain the checks performed. A namespace check alone does not prove that an upgrade is safe.

Category: Infrastructure