proof-verification-failed
The actual cryptographic verification operation failed. This occurs when all cryptographic infrastructure is properly set up, but the verification process itself determines the proof is invalid.
Causes
Section titled “Causes”List of possible causes for this error.
- The cryptographic signature verification returned false (signature does not match the data)
- The data has been tampered with since the proof was created
- The wrong verification key was used to verify the signature
- The challenge value in the proof does not match the expected challenge
- The proof has expired and is no longer valid
- The verification method relationship does not match the proof purpose
- Required authentication parameters are missing or invalid
- JWT-SD key binding verification failed
Solutions
Section titled “Solutions”List of possible solutions to resolve this error.
- Verify that the proof data has not been modified since creation
- Ensure the correct verification key is being used for signature verification
- Provide the expected challenge value when verifying the proof
- Check that the proof has not expired
- Verify the verification method has the correct relationship for the proof purpose
- Include all required authentication parameters in the proof
- Ensure JWT-SD key binding is properly formatted and matches the proof content
- Re-create the proof if the original data or keys have changed