The Refund Action

Something went wrong - but worry not, you can get your funds back.

Note: The refund action code can be found here (Chialisp). The SDK driver is CatalogRefundAction.

Registering an entry in CATalog requires two transactions. First, a user must create a precommitment coin. Second, after waiting for relative_block_height blocks (typically 32 on mainnet), the user needs to interact with the registry, which checks (spends) their precommitment coin.

During the period between the two actions, it is possible that the precommitment becomes invalid. This would happen if:

• The CAT maker puzzle of the registry changes (e.g., the price singleton updated the payment CAT to a different asset, so the precommitment coin is now in the wrong CAT)

• The precommitment amount is wrong (e.g., the price singleton changed the registration price)

• The TAIL hash has been registered

When refunding, the action sends SendMessage with message 0 (refund mode) to return the precommit CAT to the refund puzzle hash.

If the TAIL is already registered but the precommit is otherwise invalid, the refund action also spends and recreates the existing slot with counter + 1.

The action also creates a puzzle announcement. This announcement can be asserted to ensure the dApp singleton is running the right action with the right parameters. For the refund action, the announcement prefix, '$', is concatenated to (sha256tree (tail_hash . initial_nft_owner_ph)).

The CLI exposes refunds via catalog register --refund (same command as registration, different code path). See CLI Reference.

Written by yakuhito from FireAcademy.io on Feb 14th, 2025.