Fucory
@fucory
Big rule while building Tevm is keep everything maximally hackable - minimal api for 95% of use cases provided via a viem client and json rpc api - low level api I am using internally available on client._tevm - everything is extendable and swappable for custom implementations - internal packages are available on npm
0 reply
0 recast
0 reaction
