Files
rea/experiments/analysis-efficiency/evm-interface-summary.md
T
Ysopwnableandfactory-droid[bot] f76163c246 feat(evm): add retained interface summary delivery (#2308)
Add opt-in EVM MCP summary delivery and retained/portable function and text views. Keep existing complete defaults, provider arguments and original full Evidence identities and records usable. Require retention before selected analysis; preserve inferred candidates, nulls, diagnostics, provenance and explicit unknowns.

Verify old schemas, historical Evidence migration, 64 focused feature checks, 30 affected MCP checks after latest-main rebase, 59 real EVM CLI/MCP cases and six shared-domain artifact workflows. Repeated SDK delivery is smaller; all real model trials and mixed token/time outcomes, limitation failures and resource qualification gaps remain documented without a uniform performance claim.

Refs #2016

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
2026-10-13 03:09:32 +08:00

13 KiB
Raw Blame History

EVM interface delivery and migration checkpoint

Continues #2016 after the static descriptor merged in #2261. Opt-in inspect_evm_interface MCP detail: "summary" returns every inferred interface candidate without bytecode hex or duplicate stdout. Complete Evidence remains retained under its original identity. Delivery bytes fall; the measured model cohort does not establish a stable token or task-time improvement.

Frozen scope

Control production is ad08510a113d7a9b8d92fb1e385757880e469869; candidate production is 32c7548b9ae5c8cda348653d177b1747127c74ba. Their compiled file-table SHA-256 values are respectively f68e85030cb05082520ea9f0d7650298ae316ce7bba59a8942e0cc1318ae9850 and 978b3a014e3b2a1e1c6620364dcd793fa7cb40f19892d44cfb0312739a8c14a3. The SDK driver SHA-256 is a95d8d8e9f72c0b2b885c61907ed13054ebf7d1642f6f13b0126163840b1221a. Driver commit 03bff83e70e09a917341c1fe3ebffbfdc67785c5 fixes only reading the public get_evidence_bundle.result.records envelope; production is unchanged. Both runtimes use Node 24.18.0, matching locked dependencies, SDK client/server 2.3.1 and unchanged bundled EVMole 0.9.3.

Inputs are the digest-pinned WETH historical hex carrier and Uniswap v3-core 1.0.1 Factory/Pool compiler runtime templates in corpus.json. Original carrier and decoded-byte identities remain distinct. Templates are not authenticated deployed instances; constructor-dependent values and absent immutable-reference metadata stay unknown. No chain, target execution or signature lookup is introduced.