EvmError with Forge for any call to xcDOT on Moonbeam about moonbeam-docs HOT 4 CLOSED

@vminkov We have the same issue with Hardhat forking. The main problem is that precompile contracts (such as xcDOT) provide functions that access Moonbeam's runtime directly. Note that xcDOT address has only a basic opcode stored in it, that is because calls to precompiles are intercepted by Moonbeam's EVM and is not executed "opcode-by-opcode", but it is executed by the runtime itself.

Consequently, when forking, the forked network (with Forge in this case) works as a "Geth client" fork, in which these things don't work. The approve call would have the following function signature 0x75247a58 which does not exist in the precompile's bytecode (eth_getCode RPC call).

Hope this clarifies why it is not working, regards!

from moonbeam-docs.

Hey @vminkov are you testing against Moonbase Alpha? Moonbeam? I'm guessing Moonbeam as you are referring to xcDOT, but just wanted to confirm. Can you provide a bit more of context?

Thanks in advance

from moonbeam-docs.

Hey @vminkov are you testing against Moonbase Alpha? Moonbeam? I'm guessing Moonbeam as you are referring to xcDOT, but just wanted to confirm. Can you provide a bit more of context?

Thanks in advance

Hey there, @albertov19

I am testing against Moonbeam with this command:
forge test --fork-url https://rpc.api.moonbeam.network -vvvv --match-test testDotSwap

from moonbeam-docs.

Hey @vminkov are you testing against Moonbase Alpha? Moonbeam? I'm guessing Moonbeam as you are referring to xcDOT, but just wanted to confirm. Can you provide a bit more of context?
Thanks in advance

Hey there, @albertov19

I am testing against Moonbeam with this command: forge test --fork-url https://rpc.api.moonbeam.network -vvvv --match-test testDotSwap

I'm almost certain that Mainnet Forking is not compatible with our precompile contracts. We'll do some internal testing and get back to you.

from moonbeam-docs.