
they get mad lost in managing stack, getting JUMP/DEST/PC right, sometimes memory
and do a better job on linear execution, with macros for common ops + Yul IR to asm for debugging / learning evm asm on the go
Also they tend to overthink and give up too fast initially, bla bla it’s better to use languages, muh undefined behaviour etc.
would let them build stack and memory trace harness right away, and instructing to write one opcode at a time + print trace on every step for immediate backtracking
worked quite well here
“JIT compiler” to (de)compress calldata via contract statediff
(for faster read-only eth_calls)
github.com/tadpole-labs/e…
English















