Preimage
#14Preimage storage for hashed data
Part of Utility & Tools: Batch operations, proxies, multisig, and scheduling
A preimage with this hash has already been stored. Preimages are identified by the Blake2 hash of their content, so identical call data will always produce the same hash.
A preimage has been cleared.
Ensures preimage status is current.
You are not authorized to remove (unnote) this preimage. Only the account that originally stored the preimage and paid the deposit can remove it.
Stores a preimage on-chain.
A preimage has been stored on-chain.
No preimage exists with this hash. The preimage was either never stored, already removed, or the hash is incorrect.
The preimage you are trying to unrequest is not currently in a requested state. It was either never requested or already unrequested.
Actual preimage data stored by (hash, length).
Requests a preimage for use.
A preimage has been requested.
This preimage is currently requested by the governance system (e.g., a pending proposal references it). It cannot be removed while something depends on it.
Request status for preimages.
Status of a preimage by hash (deprecated).
The preimage data exceeds the maximum allowed size. Preimages store encoded call data for deferred execution (e.g., governance proposals) and have a size limit to prevent state bloat.
Cannot decrease the request reference count below zero. This typically indicates an internal bookkeeping issue where unrequest was called more times than request.
The preimage has too many outstanding request references. There is a maximum number of concurrent requesters allowed per preimage.
Removes an unrequested preimage.
Removes request for a preimage.