2.4 KiB
| summary | terms | |
|---|---|---|
| a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender |
|
{% include disclaimer.html translated="no" translationOutdated="no" %}
The Basics
A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender.
Unlock time allows you to send a transaction to someone, such that they can not spend it until after a certain block height, or until a certain time. These locks are per transaction, not per output. This means any returning change will be locked too. Do not unintentionally lock your change outputs.
Note that this works differently than Bitcoin's nLockTime, in which the transaction is not valid until the given time.
Using unlock_time has privacy consequences for the user(s) (and the wider
Monero network if it is flooded with these). The value is public on the
blockchain, so be aware of potential clustering. The feature is rarely used
and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Further, true spends after a reasonably long lock time (more than several days) may be heuristically identified as the true spend, since there will be fewer other transactions using those outputs as decoys around that time period.
Users should verify that the outputs they receive from others are not
encumbered by an unexpected unlock time. Users may want to hold off acting
upon such a transaction until the unlock time lapses. The show_transfers
command includes the unlock time.
Technical Use
Usage when using the transfer command: unlock_time + unsigned int
Integer values less than 500,000,000 are interpreted as absolute block height. Values greater than or equal to 500,000,000 are interpreted as an absolute Unix epoch timestamp. The Monero CLI wallet only supports values less than 500,000,000; Unix timestamps must be submitted via RPC or another custom software.
The integer value will be interpreted by the protocol as an absolute block height value or Unix epoch timestamp, not a relative value. Using an integer value less than the current block height or a Unix epoch timestamp less than the current Unix epoch timestamp makes no sense. For example, if you want the Monero transaction to unlock 100 blocks from now, add 100 to the current block height.