From d2c88e11a4b742052595cd2e398bf957fd4d47b0 Mon Sep 17 00:00:00 2001 From: Carl Beekhuizen Date: Thu, 1 Feb 2024 08:39:12 -0700 Subject: [PATCH] Add EIP: Reserve Precompile Address Range for RIPs Merged by EIP-Bot. --- EIPS/eip-7587.md | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 EIPS/eip-7587.md diff --git a/EIPS/eip-7587.md b/EIPS/eip-7587.md new file mode 100644 index 00000000000000..efd055d988f2b4 --- /dev/null +++ b/EIPS/eip-7587.md @@ -0,0 +1,38 @@ +--- +eip: 7587 +title: Reserve Precompile Address Range for RIPs +description: Reserve precompile address range for use by the RIP process +author: Carl Beekhuizen (@carlbeek), Ansgar Dietrichs (@adietrichs), Danny Ryan (@djrtwo), Tim Beiko (@timbeiko) +discussions-to: https://ethereum-magicians.org/t/eip-75xx-reserve-precompile-address-range-for-rips-l2s/17828 +status: Draft +type: Informational +created: 2023-12-21 +--- + +## Abstract + +This EIP reserves precompile ranges to ensure there are no conflicts with those used by the Rollup Improvement Proposal (RIP) process. + +## Motivation + +As L2s begin to deploy RIPs, it is necessary to reserve an address range for use by the RIP process so as to ensure there are no conflicts between precompile addresses used by RIPs and EIPs. + +## Specification + +The address range between `0x0000000000000000000000000000000000000100` and `0x00000000000000000000000000000000000001ff` is reserved for use by the RIP process. + +## Rationale + +By reserving an address range for RIPs, it allows the RIP process to maintain it's own registry of precompiles that are not (necessarily) deployed on L1 mainnet, the EIP process is freed from having to maintain a registry of RIP precompiles while still having 255 addresses for it's own use. + +## Backwards Compatibility + +No backward compatibility issues found. + +## Security Considerations + +Nil. + +## Copyright + +Copyright and related rights waived via [CC0](../LICENSE.md).