Files
rea/third_party/evmole
Ysopwnable 7af7bc88ce feat(evm): inspect offline bytecode interfaces through EVMole (#1051)
* feat(evm): inspect offline bytecode interfaces through evmole

* fix(evm): distinguish unsupported bytecode targets

* style(evm): format verifier string-prefix checks
2026-10-08 15:32:05 +08:00
..

EVM interface upstream profile

REA integrates unchanged EVMole as the exact npm dependency [email protected], with lockfile integrity verification. Tag 0.9.3 resolves to commit 0409707c2efef11a9043f9b4505cad5719054a7e.

The JavaScript binding and WASM engine remain in the original upstream package; REA contains only carrier validation, a worker adapter and portable contracts. No submodule or vendored engine fork is required. No signature database, LLM decompiler, blockchain node or RPC dependency is acquired.

Upstream is MIT, copyright (c) 2023 Maxim Andreev. Its npm tarball omits the license file, so REA packages the unchanged tag's LICENSE here. The engine is initialized through the upstream no_tla/initSync interface only inside an owned worker; importing REA services performs no WASM/file I/O.

Initial interface analysis uses contractInfo with selectors, arguments and stateMutability enabled. Selector recovery also extracts/reports terminal metadata; its reported representation is retained with explicit unknown precision/coverage. Other upstream outputs are separate future contracts; in particular, CFG destination IDs are not byte addresses and terminal CBOR metadata cannot establish a lossless integer claim through the current binding.