mirror of
https://github.com/luxfi/evmgpu.git
synced 2026-10-30 16:57:11 +00:00
zeekayandHanzo Dev
e50df1e4ca
Two separate faults, both in the code generator's own coverage. The precompile module template never emitted MakeGenesisConfig, which contract.Configurator has required for some time. Every precompile generated by precompilebind therefore failed to compile against the interface it is generated to satisfy. The template now emits it, matching the config template's NewConfig signature in both the plain and allow-list shapes. The test's stand-in address also predated the LP-aligned reserved range, so registration panicked with "not in a reserved range" the moment the generated code did compile; it now sits at the top of 0x10000-0x1ffff, clear of every precompile this repo registers. The binding test built its generated module against github.com/luxfi/evmgpu resolved from the proxy, so it measured the last published release rather than the working tree -- it fails when the release has drifted and, worse, passes when the tree is broken. Pointing it at the tree alone was not enough: a from-scratch tidy re-resolves every version, because the go command ignores exclude and replace directives in a module that is not the main one. That pulled warp v1.24.1, which this repository does not build with and where warp.UnsignedMessage no longer exists. The test now copies go.mod and go.sum across and renames the module, so the generated code builds against the same build list the repository uses. accounts/abi/bind and accounts/abi/bind/precompilebind now pass. Co-authored-by: Hanzo Dev <[email protected]>