Implementation of RIP-7212 / EIP-7951

[garyschulte]

PR description

Draft Implementation of RIP-7212 / EIP-7951.

Outstanding to-dos:

• enable non-canonical/malleable signatures (needs besu-native and besu-native-ec changes)
• benchmarking
• check/verify malleable signatures with bouncycastle
• add secp256r1 to mainnet required native libs
• caching
• security fixes:
  • address point-at-infinity
  • modular comparison

Fixed Issue(s)

fixes #8605
blocked by pr 270
blocked by pr 22

Thanks for sending a pull request! Have you done the following?

• Checked out our contribution guidelines?
• Considered documentation and added the doc-change-required label to this PR if updates are required.
• Considered the changelog and included an update if required.
• For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

• spotless: ./gradlew spotlessApply
• unit tests: ./gradlew build
• acceptance tests: ./gradlew acceptanceTest
• integration tests: ./gradlew integrationTest
• reference tests: ./gradlew ethereum:referenceTests:referenceTests

[Gabriel-Trintinalia]

🔥🔥🔥🔥🔥🔥🔥

[Gabriel-Trintinalia]

ethereum/EIPs#9833

[garyschulte]

Neither bouncycastle nor OpenSSL secp256r1 verify implementations are particularly performant:

➜  besu git:(feature/rip-7212-eip-7951) build/install/besu/bin/evmtool benchmark --nonative p256verify
besu/v25.6-develop-ae99fb9/osx-aarch_64/corretto-java-22
Benchmarks for p256Verify
Java secp256r1
p256verify  3,450 gas @1,284.5 µs /     2.7 MGps

➜  besu git:(feature/rip-7212-eip-7951) build/install/besu/bin/evmtool benchmark --native p256verify 
besu/v25.6-develop-ae99fb9/osx-aarch_64/corretto-java-22
Benchmarks for p256Verify
Native secp256r1
p256verify  3,450 gas @  693.7 µs /     5.0 MGps

[garyschulte]

As far as I can tell, openssl and boringssl both implement the R' checks for point-at-infinity and R'.x % n ≡ r

I asked on eth r&d discord on the #cryptography channel to verify this assertion.

[garyschulte]

this implementation utilizes openssl, and will be superseded by boringssl, but the supporting config, classes and tests will be leveraged by the future besu-native implementation of boringssl

[Gabriel-Trintinalia]

LGTM