zeekay 15e5648035 registry, modules: one record of where a precompile lives ...

registry kept ~400 address constants beside the addresses the precompiles
actually claim in their init(). Two records of one fact, and they had already
drifted: the prose mapped chain nibble 3 to D-Chain while the constants used it
for Q-Chain. The package now derives InFamily from modules.RegisteredModules(),
so a question asked here and an address dispatched by the EVM cannot disagree.
PrecompileAddress, ChainSlot and FamilyPage compute what the table enumerated.

RegisteredModules returned the package slice itself. The host walks it to build
the per-block precompile set, so its order is consensus-visible, and any caller
that sorted or truncated it reordered the registry for every subsequent block.
It returns a copy. The duplicate 0x9000-0x9FFF allowlist range is one entry.

2026-08-28 15:39:13 -07:00

..

module.go

dex(0x9999): always-on settlement precompile, runtime params, zero per-net config

2026-06-21 09:03:37 -07:00

registerer_test.go

registry, modules: one record of where a precompile lives

2026-08-28 15:39:13 -07:00

registerer.go

registry, modules: one record of where a precompile lives

2026-08-28 15:39:13 -07:00