Disclosure of support for EIP-2537 on Arbitrum One and Nova

Technical Discussion
1

Offchain Labs (OCL) has recently been made aware that the precompiled contracts for performing various operations over the BLS12-381 elliptic curve, including BLS signature verification, were added but not properly enabled in ArbOS 40 Callisto as originally expected. This means that Arbitrum chains, regardless of ArbOS version, currently do not support any of the precompiles specified in EIP-2537.

Enabling the precompiles would require a new ArbOS release and a mandatory upgrade by node operators, alongside a Constitutional proposal with the ArbitrumDAO. Given the operational burden and required lead time, OCL’s current view is to include EIP-2537 in the next major ArbOS release (ArbOS 50), which we expect to align with Ethereum’s Fusaka upgrade. At the time of writing, Ethereum’s Fusaka upgrade is targeting for a mainnet upgrade in mid November 2025 and therefore we are planning to propose the enabling of the EIP-2537 precompiles alongside the other Fusaka EIPs earmarked for “ArbOS 50”.

Should there be any teams or members of the community who would like to voice their concerns or opinions about the proposed path forward, please do so on this forum post. That feedback will help the DAO and the community assess prioritization. As always, we would like to thank the ArbitrumDAO and builders in our ecosystem for their understanding on this matter.

In line with the new, proposed vision for the future of Arbitrum, Offchain Labs expects to increase its involvement and contributions to technical discussions/topics within the Arbitrum forums going forward when it makes sense. As always, robust, broad-based community engagement will continue to be encouraged.

4 Likes
2

why did this happen @offchainlabs ?
and can the Security Council fix it, instead?

3

All the work was prepared, but the enabling of the feature was inadvertently overlooked by our team and auditors.

Enabling this feature does fall under the scope of Non-Emergency Actions that the Security Council can take, as defined by the ArbitrumDAO Constitution, but we seek to limit Security Council actions to critical security bugs, as appropriate.

We propose that this feature be enabled via the ArbOS 50 AIP instead, given that the:

  • fix is trivial,

  • the feature is not critical for security,

  • the next major ArbOS release (ArbOS 50) is expected soon,

  • code is already written, and

  • code is being audited right now

1 Like