You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the Hello ZoKrates! demo from the docs, the proof verification reverts with an InvalidFEOpcode error when calling the deployed verifier, which is given by the output of running zokrates export-verifier.
Environment
Compiler version: 0.8.25 (but tested also with 0.8.18)
Operating system: macOS Sonoma 14.5
ZoKrates version: 0.8.8
Steps to Reproduce
I'm using the code and commands from the Hello ZoKrates! tutorial from the docs. The only part that I coded myself was the decoding of the JSON data and the call to verifyTx():
When running it against an anvil node, it throws this warning before reverting:
EIP-3855 is not supported in one or more of the RPCs used.
Unsupported Chain IDs: 31337.
Contracts deployed with a Solidity version equal or higher than 0.8.20 might not work properly.
For more information, please see https://eips.ethereum.org/EIPS/eip-3855
But when I run it against a mainnet fork the same error gets thrown, just that without the warning (tried with 0.8.18 and same issue).
The text was updated successfully, but these errors were encountered:
Description
When running the Hello ZoKrates! demo from the docs, the proof verification reverts with an
InvalidFEOpcode
error when calling the deployed verifier, which is given by the output of runningzokrates export-verifier
.Environment
Steps to Reproduce
I'm using the code and commands from the Hello ZoKrates! tutorial from the docs. The only part that I coded myself was the decoding of the JSON data and the call to
verifyTx()
:The revert happens in this assembly block of the call to the internal function
pairing()
, inside the verifier:When running it against an anvil node, it throws this warning before reverting:
But when I run it against a mainnet fork the same error gets thrown, just that without the warning (tried with 0.8.18 and same issue).
The text was updated successfully, but these errors were encountered: