The Initiate Update Action

This will be your new owner

Note: The initiate update action code can be found here (Chialisp).

This action handles owner-specific update abilities for every entry. Namely, owners can transfer ownership of their entry or set it to resolve to another singleton. To do so, the owner singleton must create a coin-puzzle message with the contents of (sha256tree (c handle_hash (c new_owner_launcher_id new_resolved_launcher_id))).

To prevent certain attacks, an update cannot be completed instantly. Rather, the owner must initiate the update, wait for a 'safe' number of blocks (32 - enough to make blockchain re-orgs extremely unlikely), and then complete the update by having the child of the coin that initiated the update send another message to the registry.

The singleton keeps track of initiated updates via update slots (nonce 2). An update slot's value is:

((initiator_coin_id . min_execution_height) . (handle_hash . (new_owner . new_resolved)))

In Rue:

export struct UpdateSlotValueA {
    initiator_coin_id: Bytes32,
    ...min_execution_height: Int,
}

export struct UpdateSlotValueB {
    handle_hash: Bytes32,
    ...new_data: HandleSlotData,
}

export struct XchandlesUpdateSlotValue {
    a: UpdateSlotValueA,
    ...b: UpdateSlotValueB,
}

min_execution_height is an absolute block height (not a relative block count).

This puzzle does not create a puzzle announcement, as the owner can be assured the update is initiated only if the message sent to the singleton is consumed. An initiated update is canceled simply by spending the child of the owner singleton coin that initiated it.

Written by yakuhito from FireAcademy.io on Feb 15th, 2025. Updated Jul 2026.