[Reposted from FVM Forum] Go Client with FVM Ethereum JSON-RPC API

[trruckerfling]

As of Jan 2022, the FVM Forum will be merging into the Filecoin Community Discussion here, as FVM and Filecoin often go hand-in-hand for builders

[OP me, Dec 2022]

From a few teams testing this, it seems that Go Client like Go Eth faces some issues during implementation - stuff that can be fixed but its a hassle. There are no plans from FEVM team to build a Go FVM Client specifically for FEVM as FEVM is intended to work with all Eth tools.

Attempting to keep a log of known issues below and any known fixes. If unable to fix at integration, do tag @fvm-dx on #fvm Slack.

Thanks to @alexeyvexin from BSN for the flag

Discussion:

(@lalexgap) Here’s a couple of issues/workarounds we’ve run into using go-ethereum in golang against wallaby.

• Chain id assembly function returns wrong chain id. If you call the chainId assembly function in a solidity contract you get back an incorrect chain id. Pretty easy to workaround by passing the “wrong” chain id when calling your contract. (Or just avoid use of chainid in your contract.)
• eth_getTransactionByHash response contains empty signatures. This causes deserialization to fail when you call TransactionByHash. No great workaround for this besides avoiding calling TransactionByHash (or manually making and parsing the json-rpc call)
• eth_getLogs behaves inconsistently. It seems that certain query ranges can result in errors or return the wrong results. eth_getLogs has worked fine for us when polling for new events over short ranges. However depending on the query range you may miss results or generate an error. One workaround may be to use subscriptions over websocket instead of eth_getLogs. Otherwise, be careful about the range you specify, double check the results you get back.
• For reference here’s our (very rough) test that runs against wallaby and makes use of a few workarounds.

(@1db1) Another difficulty we encountered when working with FEVM in Wallaby testnet is the difference between the txHash you get when you use go-ethereum and the one you get when you send via JSON RPC.
As a workaround, we generate transactions using go-ethereum, but send them via JSON RPC eth_sendRawTransaction.