Get desktop application:
View/edit binary Protocol Buffers messages
* The key of an EVM hook's storage slot. For each EVM hook, its storage is a mapping of 256-bit keys (or "words") to 256-bit values.
* The id of the EVM hook that owns this slot.
* The EVM key of this slot. Must be the minimal bytes representation (no leading zeros).
* The representation of an EVM hook in state, including the previous and next hook ids in its owner's list.
* For state proofs, the id of this hook.
* The type of the EVM hook.
* The type of the extension point the hook implements.
* The id of the contract with this hook's bytecode.
* If set, a key that that can be used to remove or replace the hook; or (if applicable, as with an EVM hook) perform transactions that customize the hook.
* For an EVM hook, its first storage key. Must be the minimal bytes representation (no leading zeros). An EVM hook with no storage slots and an EVM hook whose last-written storage slot was at the zero key can be differentiated by checking the `num_storage_slots` field.
* If set, the id of the hook preceding this one in the owner's doubly-linked list of hooks.
* If set, the id of the hook following this one in the owner's doubly-linked list of hooks.
* The number of storage slots an EVM hook is using.
* The type of a hook.
Used in:
* A general-purpose EVM hook.