A key slot stores secure assets and up to 32 bits of additional metadata. Assets greater than 128 bits must be divided and distributed over multiple key slot instances.
The following table summarizes what can be stored in a key slot.
| Field | Size [bits] | Description |
|---|---|---|
| METADATA | 32 | A text field that can be used for any purpose. This field can be read by secure code using the READMETADATA task. |
| DEST | 32 | The destination address used for the push, and used by the PUSH operation. |
| VALUE | 128 | The secure asset. This field cannot be read, only pushed to its destination address using the PUSH task. |
| RPOLICY | 2 | The revocation policy for the key slot. See Provisioning for a detailed definition of this field. |