This event was removed in v385

This event is no longer emitted in the current runtime. Existed from v361 to v385. Shown here for historical reference.

DecryptedExecuted

Event Removed v361 → v385 (removed) #1

Emitted when an encrypted submission was successfully decrypted and the inner transaction executed.

Useful for: stakersdevelopersanalyticswallets

The Big Picture

This is the happy path for MEV protection. Your encrypted transaction was submitted, the block author decrypted it with their ML-KEM key, verified the commitment matched, and executed the inner transaction successfully. Your swap, stake, or other operation is now complete with MEV protection.

Why This Matters

After submitting an encrypted transaction, this event confirms everything worked. The decryption succeeded, the inner transaction executed, and you got MEV protection. Check the inner transaction's events (which also fire) to see what actually happened.

Example Scenario

Your encrypted stake submission (id=0x123...) was pending. DecryptedExecuted(0x123..., signer=your_address) fires, meaning: 1) Decryption worked, 2) Your stake transaction inside executed. Look for StakeAdded in the same block to confirm your stake went through.

Common Questions

Where are the inner transaction's events?: They fire in the same block alongside DecryptedExecuted. If your inner transaction was a stake, you'll see both DecryptedExecuted and StakeAdded events.
What's the difference between 'id' and 'signer'?: id is the submission identifier (links to EncryptedSubmitted). signer is the account that signed the inner transaction - typically your account.

Use Cases

Confirm your MEV-protected transaction completed successfully
Track execution of decrypted transactions
Audit MEV protection system effectiveness
Build end-to-end MEV-protected flows

How to Use This Event

→ Subscribe and filter by submission ID from EncryptedSubmitted
→ Track signer address for your transactions
→ Index to measure MEV protection success rate

From Chain Metadata

Decrypted call executed.

Part of: MEV Shield

Triggers

Preconditions

Valid encrypted submission existed in Submissions
Decryption succeeded (correct key, valid ciphertext)
Inner transaction executed successfully

Effects

Postconditions

Submission removed from Submissions storage
Inner transaction's effects applied
Inner transaction's events also emitted

Side Effects

May trigger additional events from inner transaction (e.g., StakeAdded)
Signer's nonce incremented for inner transaction

Event Data

#	Name	Type	Description
0	id → submission_id	H256	Identifier of the submission that was decrypted and executed
1	signer → inner_signer	AccountId	Account that signed the inner (decrypted) transaction (hex -> SS58)

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 });

// Subscribe to DecryptedExecuted events
api.query.system.events((events) => {
  events
    .filter(({ event }) =>
      event.section === stringCamelCase("MevShield") &&
      event.method === "DecryptedExecuted"
    )
    .forEach(({ event }) => {
      console.log("DecryptedExecuted:", event.data.toHuman());
    });
});

Runtime Info

View Source

Pallet Index: 30
Event Index: 1
First Version: v361
Removed In: v385

Back to MevShield Events