The Expire Action
Someone didn't renew this awesome handle - let's get it!
Last updated
Someone didn't renew this awesome handle - let's get it!
Last updated
Note: The expire action code be found .
When handles expire, they're auctioned off by using a second pricing puzzle. Usually (and by default), the other pricing puzzle will use the time when the handle expired and the registration time to calculate a premium, which is added to the base price. The premium decreases (exponentially in the puzzle used at launch) as more time passes - essentially creating a public 'auction' where potential owners are 'forced' by game theory to pay their maximum price for the handle.
Because the handle is changing owners, precommitment coins are used to solve the concern of potential mempool snipers (malicious farmers). The value of a precommitment coin will be the same as that for registrations, namely (c refund_info_hash (c (c secret handle) (c start_time (c new_owner_launcher_id new_resolved_launcher_id))))
. Note that the pricing puzzle for refund_info
will now describe the auction puzzle, not the 'standard one.'
The action also creates a puzzle announcement that be asserted to ensure the dApp singleton is running the right action with the right parameters. For the extend action, the announcement prefix, x
, is concatenated to (sha256tree (handle new_expiration new_owner_launcher_id . new_resolved_launcher_id))
.
Written by from on Feb 15th, 2025.