AuthorKeys
Storage Map v391 → v411 Changed in v411Per-block author public keys used to encrypt MEV -shielded extrinsics.
Explore chainQueried by: validatorsdevelopers
The Big Picture
MevShield rotates an encryption key on a fixed schedule. AuthorKeys preserves which key was active at each block so submissions can be matched back to their intended decryption epoch.
From Chain Metadata
Per-author ML-KEM-768 encapsulation key, updated each time the author produces a block.
Purpose & Usage
Purpose
Map block numbers to the rotating author public keys validators use to decrypt shielded submissions for that block.
Common Query Patterns
- Query by block number
- Look up the encryption key valid at submission time
Query Keys
| # | Name | Type | Description |
|---|---|---|---|
| 1 | blockNumber block raw: key1 | [u8; 32] [32] sr25519::Public | key1 ([u8; 32]) |
Stored Value
value (BoundedVec)
Code Examples
import { createClient, Binary } from "polkadot-api";
import { getWsProvider } from "polkadot-api/ws";
import { sub } from "@polkadot-api/descriptors"; // generated by: npx papi add sub -w wss://entrypoint-finney.opentensor.ai:443
const client = createClient(getWsProvider("wss://entrypoint-finney.opentensor.ai:443"));
const api = client.getTypedApi(sub);
// Query AuthorKeys storage
const key1 = "0x0000000000000000000000000000000000000000000000000000000000000000";
const result = await api.query.MevShield.AuthorKeys.getValue(key1);
console.log("AuthorKeys:", result);Version History
v391 block 7,782,857 Added
v394–v400 · runtime versions skipped on chain (never deployed)
v401 block 8,036,576 Internal re-bind
v403–v410 · runtime versions skipped on chain (never deployed)
v411 block 8,283,784 Internal re-bind Current
Runtime Info
View Source- Pallet
- MevShield
- Storage Kind
- Map
- First Version
- v391
- Current Version
- v411