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.
SubmissionAlreadyExists
Error Removed v361 → v385 (removed) 30.0An encrypted submission with the same ID already exists in the pending queue.
Encountered by: developerswalletsstakers
Why This Error Exists
Submission IDs are computed from commitment and ciphertext. Identical encrypted submissions produce identical IDs. The chain prevents duplicates to avoid confusion and double-processing.
From Chain Metadata
A submission with the same id already exists in `Submissions`.
What This Means
An encrypted submission with the same ID already exists in the pending queue.
Common Causes
- Duplicate submission of the same encrypted transaction
- Resubmitting before previous submission was processed
- Same commitment+ciphertext submitted twice
How to Fix
- Wait for existing submission to be processed
- Check if your submission is already in Submissions storage
- If intentional retry, wait for next block when old submission clears
Storage to Check
Thrown By
Runtime Info
- Pallet Index
- 30
- Error Index
- 0
- Error Code
- 30.0
- Removed In
- v385