mirror of
https://github.com/monero-project/monero-site.git
synced 2024-12-23 12:09:49 +00:00
moneropedia: update unlocktime
This commit is contained in:
SamsungGalaxyPlayer
plowsof
parent
d151dce166
commit
fbb66f7819
14 changed files with 296 additions and 134 deletions
|
|
@ -1,19 +1,30 @@
|
|||
---
|
||||
summary: 'a special transaction where the recipient can only spend the funds after a future date, as set by the sender'
|
||||
terms: ["unlock-time"]
|
||||
summary: "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 can only spend the funds after a
|
||||
future date, as set by the sender.
|
||||
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 number of blocks, or until a certain
|
||||
time.
|
||||
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](https://en.bitcoin.it/wiki/NLockTime), in which the transaction
|
||||
is not valid until the given time.
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,20 +1,30 @@
|
|||
---
|
||||
summary: 'Eine besondere Art der Transaktion, bei welcher der Empfänger die Gelder erst nach einem vom Sender gesetzten zukünftigen Zeitpunkt ausgeben kann.'
|
||||
terms: ["unlock-time", "Freigabedauer", "Freigabedauer-von-Transaktionen"]
|
||||
terms: ["unlock-time"]
|
||||
summary: "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="yes" translationOutdated="no" %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
### Grundlagen
|
||||
### The Basics
|
||||
|
||||
Eine besondere Art der Transaktion, bei welcher der Empfänger die Gelder
|
||||
erst nach einem vom Sender gesetzten zukünftigen Zeitpunkt ausgeben kann.
|
||||
A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender.
|
||||
|
||||
Die Freigabedauer erlaubt es dir, eine Transaktion an jemanden zu senden,
|
||||
die dieser jedoch erst nach einer gewissen Anzahl von Blöcken oder nach
|
||||
einer bestimmten Zeit verwenden kann.
|
||||
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.***
|
||||
|
||||
Beachte, dass dies anders als Bitcoins
|
||||
[nLockTime](https://en.bitcoin.it/wiki/NLockTime) (englischsprachiger
|
||||
Artikel) funktioniert. Dort ist die Transaktion bis zum gesetzten Zeitpunkt
|
||||
ungültig.
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,14 +1,30 @@
|
|||
---
|
||||
terms: ["unlock-time"]
|
||||
summary: "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
|
||||
summary: "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 can only spend the funds after a future date, as set by the sender.
|
||||
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 number of blocks, or until a certain time.
|
||||
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](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,19 +1,30 @@
|
|||
---
|
||||
summary: 'a special transaction where the recipient can only spend the funds after a future date, as set by the sender'
|
||||
terms: ["unlock-time"]
|
||||
summary: "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 can only spend the funds after a
|
||||
future date, as set by the sender.
|
||||
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 number of blocks, or until a certain
|
||||
time.
|
||||
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](https://en.bitcoin.it/wiki/NLockTime), in which the transaction
|
||||
is not valid until the given time.
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,19 +1,30 @@
|
|||
---
|
||||
summary: "Une transaction spécifique où le destinataire ne peut dépenser les fonds qu'à une date ultérieure, définie par l'émetteur."
|
||||
terms: ["unlock-time", "durée-de-déverrouillage"]
|
||||
terms: ["unlock-time"]
|
||||
summary: "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="yes" translationOutdated="no" %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
### Les Bases
|
||||
### The Basics
|
||||
|
||||
Une transaction spécifique où le destinataire ne peut dépenser les fonds
|
||||
qu'à une date ultérieure, définie par l'émetteur.
|
||||
A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender.
|
||||
|
||||
La durée de déverrouillage vous autorise à envoyer une transaction à
|
||||
quelqu'un de sorte qu'il ne pourra dépenser le montant reçu qu'après un
|
||||
certain nombre de blocs, ou après un certain temps.
|
||||
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.***
|
||||
|
||||
Remarquez que cela fonctionne différemment du
|
||||
[nLockTime](https://en.bitcoin.it/wiki/NLockTime) de Bitcoin dans lequel une
|
||||
transaction n'est pas valide avant le temps indiqué.
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,19 +1,30 @@
|
|||
---
|
||||
summary: 'a special transaction where the recipient can only spend the funds after a future date, as set by the sender'
|
||||
terms: ["unlock-time"]
|
||||
summary: "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 can only spend the funds after a
|
||||
future date, as set by the sender.
|
||||
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 number of blocks, or until a certain
|
||||
time.
|
||||
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](https://en.bitcoin.it/wiki/NLockTime), in which the transaction
|
||||
is not valid until the given time.
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,19 +1,30 @@
|
|||
---
|
||||
summary: 'En spesiell transaksjon der mottakeren bare kan bruke midlene etter en fremtidig dato, som satt av senderen.'
|
||||
terms: ["unlock-time", "opplåsningstid"]
|
||||
terms: ["unlock-time"]
|
||||
summary: "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="yes" translationOutdated="no" %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
### Det grunleggende
|
||||
### The Basics
|
||||
|
||||
En spesiell transaksjon der mottakeren bare kan bruke midlene etter en
|
||||
fremtidig dato, som satt av senderen.
|
||||
A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender.
|
||||
|
||||
Opplåsningstiden lar deg sende en transaksjon til noen slik at de ikke kan
|
||||
bruke midlene etter et visst antall blokker, eller frem til et visst
|
||||
tidspunkt.
|
||||
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.***
|
||||
|
||||
Merk at dette fungerer på en annen måte enn Bitcoins
|
||||
[nLockTime](https://en.bitcoin.it/wiki/NLockTime), der transaksjonen ikke er
|
||||
gyldig før den utvalgte tiden.
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,19 +1,30 @@
|
|||
---
|
||||
summary: 'a special transaction where the recipient can only spend the funds after a future date, as set by the sender'
|
||||
terms: ["unlock-time"]
|
||||
summary: "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 can only spend the funds after a
|
||||
future date, as set by the sender.
|
||||
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 number of blocks, or until a certain
|
||||
time.
|
||||
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](https://en.bitcoin.it/wiki/NLockTime), in which the transaction
|
||||
is not valid until the given time.
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,18 +1,30 @@
|
|||
---
|
||||
summary: 'Specjalny rodzaj transakcji, gdzie odbiorca może wydać otrzymane środki dopiero po dacie ustalonej przez nadawcę.'
|
||||
terms: ["unlock-time", "czasem-na-odblokowanie"]
|
||||
terms: ["unlock-time"]
|
||||
summary: "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="yes" translationOutdated="no" %}
|
||||
{% include disclaimer.html translated="no" translationOutdated="no" %}
|
||||
|
||||
### Podstawy
|
||||
### The Basics
|
||||
|
||||
Specjalny rodzaj transakcji, gdzie odbiorca może wydać otrzymane środki
|
||||
dopiero po dacie ustalonej przez nadawcę.
|
||||
A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender.
|
||||
|
||||
Unlock time umożliwia dokonanie płatności, z której środków odbiorca nie
|
||||
może użyć aż do upłynięcia pewnego czasu lub pewnej liczby bloków.
|
||||
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.***
|
||||
|
||||
Zauważ, że działa on inaczej niż
|
||||
[nLockTime](https://en.bitcoin.it/wiki/NLockTime) Bitcoina, w którym
|
||||
transakcja nie jest ważna aż do ustalonego czasu.
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,19 +1,30 @@
|
|||
---
|
||||
summary: 'a special transaction where the recipient can only spend the funds after a future date, as set by the sender'
|
||||
terms: ["unlock-time"]
|
||||
summary: "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 can only spend the funds after a
|
||||
future date, as set by the sender.
|
||||
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 number of blocks, or until a certain
|
||||
time.
|
||||
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](https://en.bitcoin.it/wiki/NLockTime), in which the transaction
|
||||
is not valid until the given time.
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,20 +1,30 @@
|
|||
---
|
||||
summary: 'Особый случай транзакции, когда получатель может потратить средства только после какой-то определённой даты в будущем, которая устанавливается отправителем.'
|
||||
terms: ["unlock-time", "временем-разблокировки"]
|
||||
terms: ["unlock-time"]
|
||||
summary: "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="yes" translationOutdated="no" %}
|
||||
{% 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.***
|
||||
|
||||
Следует отметить, что этот механизм работает не так, как
|
||||
[nLockTime](https://en.bitcoin.it/wiki/NLockTime) у Bitcoin, где транзакция
|
||||
не считается действительной до какого-то указанного момента времени.
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,19 +1,30 @@
|
|||
---
|
||||
summary: 'a special transaction where the recipient can only spend the funds after a future date, as set by the sender'
|
||||
terms: ["unlock-time"]
|
||||
summary: "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 can only spend the funds after a
|
||||
future date, as set by the sender.
|
||||
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 number of blocks, or until a certain
|
||||
time.
|
||||
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](https://en.bitcoin.it/wiki/NLockTime), in which the transaction
|
||||
is not valid until the given time.
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,15 +1,30 @@
|
|||
---
|
||||
summary: 一种特殊的交易，在这种交易中，收件人只能在将来某个日期之后才可以使用资金，这是由发送者设定的。
|
||||
terms: ["unlock-time"]
|
||||
summary: "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="yes" translationOutdated="no" %}
|
||||
{% 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.***
|
||||
|
||||
注意，这与比特币的 [nLockTime](https://en.bitcoin.it/wiki/NLockTime)
|
||||
不同，在比特币的网络当中，交易直到给定的时间才有效。
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -1,19 +1,30 @@
|
|||
---
|
||||
summary: 'a special transaction where the recipient can only spend the funds after a future date, as set by the sender'
|
||||
terms: ["unlock-time"]
|
||||
summary: "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 can only spend the funds after a
|
||||
future date, as set by the sender.
|
||||
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 number of blocks, or until a certain
|
||||
time.
|
||||
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](https://en.bitcoin.it/wiki/NLockTime), in which the transaction
|
||||
is not valid until the given time.
|
||||
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/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.
|
||||
|
||||
Decoy outputs may be selected from these locked outputs, thus identifying them as provable decoy outputs. At the moment, this has little impact on wider network privacy since this unlock time feature is so rarely used.
|
||||
|
||||
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.
|
||||
|
|
|
|||
Loading…
Reference in a new issue