Overview
Precompiled contracts exist on Base at predefined addresses. They are similar to predeploys but are implemented as native code in the EVM as opposed to bytecode. Precompiles are used for computationally expensive operations, that would be cost prohibitive to implement in Solidity. Where possible predeploys are preferred, as precompiles must be implemented in every execution client. Base contains the standard Ethereum precompiles as well as a small number of additional precompiles. The following table lists each of the additional precompiles. The system version indicates when the precompile was introduced.| Name | Address | Introduced | Gas Cost |
|---|---|---|---|
| P256VERIFY | 0x0000000000000000000000000000000000000100 | Fjord | 6,900 (updated in Azul) |
P256VERIFY
TheP256VERIFY precompile performs signature verification for the secp256r1 elliptic curve. This curve has widespread
adoption. It’s used by Passkeys, Apple Secure Enclave and many other systems.
It is specified as part of RIP-7212 and was added to
the Base protocol in the Fjord release with a gas cost of 3,450.
With the Azul hardfork, the gas cost was updated to 6,900 to match EIP-7951 and maintain strict equivalence with L1 precompile pricing.
Address: 0x0000000000000000000000000000000000000100
Standard Ethereum Precompile Modifications (Azul)
The Azul hardfork introduced changes to two standard Ethereum precompiles:MODEXP (address 0x05)
- EIP-7823 — input fields are capped at 1,024 bytes each. Calls with larger inputs are rejected.
- EIP-7883 — minimum gas cost raised from 200 to 500; the general cost formula is tripled.