This storage item was removed in v385

This storage item is no longer available in the current runtime. Existed from v361 to v385. Shown here for historical reference.

Submissions

Storage Removed Map v361 → v385 (removed)

Buffered encrypted transaction submissions waiting for decryption.

Queried by: developersanalyticswallets

The Big Picture

After you call submit_encrypted, your encrypted transaction lands here. It waits until the next block, when the block author (who announced the encryption key) decrypts it and executes the inner transaction. Once processed (success or failure), the submission is removed.

Why This Matters

If you submitted an encrypted transaction, you can verify it's pending by checking this storage. Once it's gone, check for DecryptedExecuted, DecryptedRejected, or DecryptionFailed events.

Example Scenario

You called submit_encrypted and got back id=0x123... Query Submissions(0x123...) - if Some(data), your submission is pending. If None, it's been processed. Check events for the outcome.

Common Questions

How long do submissions stay pending?
Just one block. They're processed in the immediately following block by the key announcer.
What's in the Submission data?
The commitment hash, ciphertext blob, submitter address, and epoch key hash binding.

Use Cases

  • Verify your encrypted submission was accepted
  • Monitor pending MEV-protected transactions
  • Debug submission status

From Chain Metadata

Buffered encrypted submissions, indexed by wrapper id.

Purpose & Usage

Purpose

Stores encrypted wrappers until the next block author decrypts and executes them.

Common Query Patterns

  • Query specific submission by ID
  • Check if your submission is pending

Notes

  • Keyed by submission ID (H256 hash)
  • Contains commitment, ciphertext, and metadata
  • Cleared after decryption (success or failure)
Part of: MEV Shield

Query Keys

#NameTypeDescription
1
key1
H256 key1 (H256)

Stored Value

Submission

value (Submission)

Relationships

Code Examples

import { ApiPromise, WsProvider } from "@polkadot/api";
import { stringCamelCase } from "@polkadot/util";

const provider = new WsProvider("wss://entrypoint-finney.opentensor.ai:443");
const api = await ApiPromise.create({ provider });

// Query Submissions storage
const key1 = 0 as any /* H256 */;

const result = await api.query
  [stringCamelCase("MevShield")]
  [stringCamelCase("Submissions")](
  key1
);

console.log("Submissions:", result.toHuman());

Runtime Info

View Source
Pallet
MevShield
Storage Kind
Map
First Version
v361
Removed In
v385
Back to MevShield Storage