PulseVerificationError
Error v216 → current 26.5An error occurred during the pulse verification process.
Why This Error Exists
This is a lower-level verification error compared to UnverifiedPulse. It may indicate structural issues with the pulse data itself, not just a signature mismatch.
Deep Dive
While UnverifiedPulse typically means 'signature invalid', PulseVerificationError can indicate problems earlier in the process - parsing failures, config issues, or library errors. Check data formats and encoding.
Debugging Example
Pulse submission fails with PulseVerificationError. Check: Is pulse data hex-encoded correctly? Is the signature the right length? Is BeaconConfig populated with valid data? Any of these being wrong can cause verification to fail before signature checking.
Prevention Tips
- Validate pulse data format before submission
- Ensure offchain worker correctly serializes Drand API responses
- Test with known-good pulse data to isolate issues
From Chain Metadata
the pulse could not be verified
What This Means
An error occurred during the pulse verification process.
Common Causes
- Malformed pulse data (wrong encoding or structure)
- BLS signature verification library error
- Corrupt beacon configuration
How to Fix
- Check pulse data encoding matches expected format
- Verify BeaconConfig is properly initialized
- Check for runtime version compatibility issues
Storage to Check
Thrown By
Runtime Info
- Pallet Index
- 26
- Error Index
- 5
- Error Code
- 26.5
- Runtime Version
- v393