|
1 | 1 | # Locktime |
2 | 2 |
|
3 | | -Locktime creates a transaction that only broadcasts when a certain time or block height has been reached. Setting a locktime is as simple as stating a blockheight or Unix timestamp at which it should broadcast, and then signing the transaction as usual. |
| 3 | +Locktime creates a transaction that only broadcasts when a certain time or block height has been reached. Setting a locktime is as simple as stating a blockheight or date at which it should broadcast, and then signing the transaction as usual. |
4 | 4 |
|
5 | 5 | Broadcast is turned off by default when using locktime, meaning you will receive raw text data to broadcast from a node. If Broadcast is on, the transaction will be sent over the current network. |
6 | 6 |
|
7 | 7 | #### How to set a locktime |
8 | 8 |
|
9 | | -You can set a Locktime while creating a transaction: |
| 9 | +To set a Locktime while creating a transaction: |
10 | 10 |
|
11 | | -1. Click **Add Locktime.** |
12 | | -2. Enter a block height or Unix timestamp when it should broadcast. |
13 | | -3. Set a fee. |
14 | | -4. Confirm transaction details on your Trezor. |
15 | | -5. You will be shown confirmation details. |
16 | | -6. Copy the data to your clipboard or save it as a text document. When Broadcasting (only after the block height has been reached) click Send instead. |
17 | | -7. Later, ideally from another network, use Send RAW or visit a block explorer to send the raw transaction data. |
| 11 | +1. Click **Add Locktime:** |
18 | 12 |
|
19 | | -#### How to set a precise Locktime |
| 13 | +<figure><img src="../../../.gitbook/assets/Send_Add-Locktime-HL.png" alt=""><figcaption></figcaption></figure> |
20 | 14 |
|
21 | | -Using block height to set a Locktime is not very accurate, as new blocks are mined on average once every 10 minutes, meaning around 144 blocks are mined per day. This number varies depending on the state of the network, and some blocks can take much longer to be mined. |
| 15 | +2. Use the drop-down menu to set the Locktime format to either **Block** or **Date (UTC):**  |
22 | 16 |
|
23 | | -Unix timestamps are used for more precise timing synchronized across computers. They track the number of seconds which have passed since January 1, 1970. |
| 17 | +<figure><img src="../../../.gitbook/assets/Add-Locktime-Menu-HL.png" alt=""><figcaption></figcaption></figure> |
24 | 18 |
|
25 | | -Use a [Unix timestamp converter](https://www.unixtimestamp.com/) to see the current timestamp and calculate a timestamp for a precise time in the future. Setting a Locktime is as simple as increasing the current timestamp by the number of seconds it should be delayed. |
26 | | - |
27 | | -For example, if the current timestamp is 1625215800 and the desired Locktime is one week, the Unix timestamp to enter would be 1625820600 (the current timestamp plus one week, which is equivalent to 604800 seconds). |
| 19 | +3. Enter a block height or date when it should broadcast. |
| 20 | +4. Set a fee. |
| 21 | +5. Confirm transaction details on your Trezor. |
| 22 | +6. You will be shown confirmation details. |
| 23 | +7. Copy the data to your clipboard or save it as a text document. When broadcasting (only after the block height has been reached) click Send instead. |
| 24 | +8. Later, ideally from another network, use Send RAW or visit a block explorer to send the raw transaction data. |
28 | 25 |
|
29 | 26 | > 💡 Learn more about the [locktime feature](https://trezor.io/learn/a/locktime-in-trezor-suite-app) on the Trezor knowledge base |
0 commit comments