This error was removed in v385
This error is no longer present in the current runtime. Existed from v361 to v385. Shown here for historical reference.
CommitmentMismatch
Error Removed v361 → v385 (removed) 30.2The decrypted inner transaction doesn't match the commitment hash provided.
Encountered by: developersstakers
Why This Error Exists
The commitment is a hash of the signed inner transaction. This binding ensures nobody can substitute a different transaction after encryption.
From Chain Metadata
The recomputed commitment does not match the stored commitment.
What This Means
The decrypted inner transaction doesn't match the commitment hash provided.
Common Causes
- Commitment computed incorrectly on client side
- Wrong transaction encrypted vs committed
- Data corruption during transmission
How to Fix
- Verify commitment = hash(signed_inner_transaction)
- Ensure the same exact bytes were committed and encrypted
- Re-encrypt with correctly computed commitment
Storage to Check
Runtime Info
- Pallet Index
- 30
- Error Index
- 2
- Error Code
- 30.2
- Removed In
- v385