The SDK call to the KMS Verifier contract on the FHEVM Host chain fails with CALL_EXCEPTION: missing revert data.
This happens with "@zama-fhe/relayer-sdk": "0.3.0-5" and also with "0.2.0".
- Install @zama-fhe/relayer-sdk@0.3.0-5 (or downgrade to 0.2.0)
- Initialize following the “Create an FHE instance” step
- During initialization, the call to the KMS Verifier contract fails
SDK 0.3.0-5:
Error: missing revert data (action="call", data=null, reason=null, transaction={ "data": "0x7eaac8f2", "to": "0xbE0E383937d564D7FF0BC3b46c51f0bF8d5C311A" }, invocation=null, revert=null, code=CALL_EXCEPTION, version=6.15.0)
SDK 0.2.0:
Error: missing revert data (action="call", data=null, reason=null, transaction={ "data": "0x7eaac8f2", "to": "0x1364cBBf2cDF5032C47d8226a6f6FBD2AFCDacAC" }, invocation=null, revert=null, code=CALL_EXCEPTION, version=6.15.0)
In a recent commit, the FHEVM Host chain KMS_VERIFIER_CONTRACT_ADDRESS changed from
0x1364cBBf2cDF5032C47d8226a6f6FBD2AFCDacAC to 0xbE0E383937d564D7FF0BC3b46c51f0bF8d5C311A (see screenshot).
Both addresses currently fail during initialization with “missing revert data”. The call selector is 0x7eaac8f2.

The SDK call to the KMS Verifier contract on the FHEVM Host chain fails with CALL_EXCEPTION: missing revert data.
This happens with "@zama-fhe/relayer-sdk": "0.3.0-5" and also with "0.2.0".
In a recent commit, the FHEVM Host chain KMS_VERIFIER_CONTRACT_ADDRESS changed from
0x1364cBBf2cDF5032C47d8226a6f6FBD2AFCDacAC to 0xbE0E383937d564D7FF0BC3b46c51f0bF8d5C311A (see screenshot).
Both addresses currently fail during initialization with “missing revert data”. The call selector is 0x7eaac8f2.