Arkiv entity lifecycle

Use the installed SDK declarations and Tiramisu behavior. Writes use the native entity operation address 0x4400000000000000000000000000000000000044; this does not enable user-deployed contracts.

Choose the operation

• Use this skill for flags, patching, ownership transfer, replacement, deletion, and relationships between new keys.
• Use arkiv-entity-expiration for renewal targets and expiration monitoring, arkiv-write-safety for signer queues and uncertain receipts, and arkiv-query for paginated reads.
• Run the write examples only within the user's authorized scope. A read or estimate does not authorize deleting an existing entity or spending GLM.

Flags and permissions

Create uses flags: { readonly, permissionlessExtension }. Both default to false and are immutable: patching, extending, or transferring cannot change them.