AIP-2, 3, 7, 17: propozitiile la prezent despre sapte validatori datate (setul de zece din 2026-09-11, al doilea client validator); AIP-7 fara 'audited native code'

This commit is contained in:
Aere Network committed 2026-09-24 22:38:31 +03:00
1 parent 95ef18af25
commit b1f852bc52
4 files changed
+5 -13

No files matched your search

+2 -6
View File
@@ -40,7 +40,7 @@ roughly 10.5M gas inside a full userOp) are correct but expensive.
The fix that removes both limits is a native precompile: the dominant cost inside
every one of these verifiers is SHAKE / Keccak-f[1600] streaming plus lattice ring
arithmetic, and moving that into audited native code, wrapped as an EVM precompile,
arithmetic, and moving that into native code, wrapped as an EVM precompile,
reduces each verification by more than an order of magnitude. This is the same
approach Ethereum uses for other heavy primitives (RIP-7951 for native P-256,
EIP-2537 for native BLS12-381). Bundling the native EIP-2935 write path into the
@@ -170,11 +170,7 @@ fork would be false and must not be made. Isolated-testnet work on a Falcon quor
certificate and a second execution client is separate R&D and is not live on chain
2800.
**Single operator, one client.** Chain 2800 runs seven QBFT validators (f=2,
quorum 5-of-7), all Foundation-operated, on a single execution client (Hyperledger
Besu). Even at f=2, the validators are one operator and one client, so a consensus
bug in a precompile is not caught by client diversity, because there is no second
live client. This raises, not lowers, the bar for an external audit and for
**Single operator, one client (at the Created date).** Chain 2800 ran seven QBFT validators (f=2, quorum 5-of-7), all Foundation-operated, on a single execution client (Hyperledger Besu); since 2026-09-11 it runs ten (f=3, quorum 7-of-10), still all Foundation-operated, one of them on a second, Nethermind-derived client that executes the same precompiles. At that date the validators were one operator and one client, so a consensus bug in a precompile could not be caught by client diversity, because there was no second live client; since 2026-09-11 a disagreement between the two implementations would show up as the second client diverging from the others. This raises, not lowers, the bar for an external audit and for
extensive differential testing.
**Determinism and gas agreement.** Every node must compute the identical