moneropedia: po/pot files for unlocktime.md

_i18n/ar/resources/moneropedia/unlocktime.md

@@ -1,30 +1,59 @@
 ---
+summary: 'a special transaction where the recipient(s) 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(s) 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 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.***
+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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/ar/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -19,7 +19,7 @@ msgstr ""
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
 #, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr ""
 
 #. type: YAML Front Matter: terms
@@ -41,15 +41,56 @@ msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-msgid "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."
+msgid "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.***"
 msgstr ""
 
 #. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

_i18n/de/resources/moneropedia/unlocktime.md

@@ -1,30 +1,60 @@
 ---
-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'
-summary: "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
+terms: ["unlock-time", "Freigabedauer", "Freigabedauer-von-Transaktionen"]
 ---
 
-{% include disclaimer.html translated="no" translationOutdated="no" %}
+{% include disclaimer.html translated="yes" translationOutdated="no" %}
 
-### The Basics
+### Grundlagen
 
-A special transaction where the recipient(s) 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 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.***
+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.
+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.
 
-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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/de/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -18,8 +18,9 @@ msgstr ""
 
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
-#, no-wrap
+#, fuzzy, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+#| msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr "Eine besondere Art der Transaktion, bei welcher der Empfänger die Gelder erst nach einem vom Sender gesetzten zukünftigen Zeitpunkt ausgeben kann."
 
 #. type: YAML Front Matter: terms
@@ -28,9 +29,9 @@ msgstr "Eine besondere Art der Transaktion, bei welcher der Empfänger die Gelde
 msgid "[\"unlock-time\"]"
 msgstr "[\"unlock-time\", \"Freigabedauer\", \"Freigabedauer-von-Transaktionen\"]"
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:7
-#
 msgid "{% include disclaimer.html translated=\"no\" translationOutdated=\"no\" %}"
 msgstr "{% include disclaimer.html translated=\"yes\" translationOutdated=\"no\" %}"
 
@@ -40,20 +41,65 @@ msgstr "{% include disclaimer.html translated=\"yes\" translationOutdated=\"no\"
 msgid "The Basics"
 msgstr "Grundlagen"
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-#
+#, fuzzy
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+#| msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr "Eine besondere Art der Transaktion, bei welcher der Empfänger die Gelder erst nach einem vom Sender gesetzten zukünftigen Zeitpunkt ausgeben kann."
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-#
+#, fuzzy
-msgid "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."
+#| msgid "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."
+msgid "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.***"
 msgstr "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."
 
-#. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
 #
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr "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."
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

_i18n/en/resources/moneropedia/weblate/unlocktime.pot

@@ -3,11 +3,11 @@
 # This file is distributed under the same license as the PACKAGE package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 #
-#
+#, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -19,7 +19,7 @@ msgstr ""
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
 #, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr ""
 
 #. type: YAML Front Matter: terms
@@ -43,17 +43,65 @@ msgstr ""
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
 #, markdown-text
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
 #, markdown-text
-msgid "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."
+msgid "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.***"
 msgstr ""
 
 #. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 #, markdown-text
 msgid "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."
 msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+#, markdown-text
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+#, markdown-text
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+#, markdown-text
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+#, markdown-text
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, markdown-text, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+#, markdown-text
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+#, markdown-text
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+#, markdown-text
+msgid "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."
+msgstr ""

_i18n/es/resources/moneropedia/unlocktime.md

@@ -1,30 +1,59 @@
 ---
+summary: 'a special transaction where the recipient(s) 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(s) 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 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.***
+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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/es/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -19,7 +19,7 @@ msgstr ""
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
 #, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr ""
 
 #. type: YAML Front Matter: terms
@@ -41,15 +41,56 @@ msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-msgid "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."
+msgid "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.***"
 msgstr ""
 
 #. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

_i18n/fr/resources/moneropedia/unlocktime.md

@@ -1,30 +1,59 @@
 ---
-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'
-summary: "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
+terms: ["unlock-time", "durée-de-déverrouillage"]
 ---
 
-{% include disclaimer.html translated="no" translationOutdated="no" %}
+{% include disclaimer.html translated="yes" translationOutdated="no" %}
 
-### The Basics
+### Les Bases
 
-A special transaction where the recipient(s) 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 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.***
+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.
+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é.
 
-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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/fr/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -18,8 +18,9 @@ msgstr ""
 
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
-#, no-wrap
+#, fuzzy, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+#| msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr "Une transaction spécifique où le destinataire ne peut dépenser les fonds qu'à une date ultérieure, définie par l'émetteur."
 
 #. type: YAML Front Matter: terms
@@ -28,9 +29,9 @@ msgstr "Une transaction spécifique où le destinataire ne peut dépenser les fo
 msgid "[\"unlock-time\"]"
 msgstr "[\"unlock-time\", \"durée-de-déverrouillage\"]"
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:7
-#
 msgid "{% include disclaimer.html translated=\"no\" translationOutdated=\"no\" %}"
 msgstr "{% include disclaimer.html translated=\"yes\" translationOutdated=\"no\" %}"
 
@@ -40,20 +41,65 @@ msgstr "{% include disclaimer.html translated=\"yes\" translationOutdated=\"no\"
 msgid "The Basics"
 msgstr "Les Bases"
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-#
+#, fuzzy
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+#| msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr "Une transaction spécifique où le destinataire ne peut dépenser les fonds qu'à une date ultérieure, définie par l'émetteur."
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-#
+#, fuzzy
-msgid "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."
+#| msgid "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."
+msgid "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.***"
 msgstr "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."
 
-#. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
 #
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr "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é."
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

_i18n/it/resources/moneropedia/unlocktime.md

@@ -1,30 +1,59 @@
 ---
+summary: 'a special transaction where the recipient(s) 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(s) 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 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.***
+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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/it/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -19,7 +19,7 @@ msgstr ""
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
 #, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr ""
 
 #. type: YAML Front Matter: terms
@@ -41,15 +41,56 @@ msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-msgid "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."
+msgid "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.***"
 msgstr ""
 
 #. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

_i18n/nb-no/resources/moneropedia/unlocktime.md

@@ -1,30 +1,59 @@
 ---
-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'
-summary: "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
+terms: ["unlock-time", "opplåsningstid"]
 ---
 
-{% include disclaimer.html translated="no" translationOutdated="no" %}
+{% include disclaimer.html translated="yes" translationOutdated="no" %}
 
-### The Basics
+### Det grunleggende
 
-A special transaction where the recipient(s) 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 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.***
+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.
+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.
 
-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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/nb-no/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -18,8 +18,9 @@ msgstr ""
 
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
-#, no-wrap
+#, fuzzy, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+#| msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr "En spesiell transaksjon der mottakeren bare kan bruke midlene etter en fremtidig dato, som satt av senderen."
 
 #. type: YAML Front Matter: terms
@@ -28,9 +29,9 @@ msgstr "En spesiell transaksjon der mottakeren bare kan bruke midlene etter en f
 msgid "[\"unlock-time\"]"
 msgstr "[\"unlock-time\", \"opplåsningstid\"]"
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:7
-#
 msgid "{% include disclaimer.html translated=\"no\" translationOutdated=\"no\" %}"
 msgstr "{% include disclaimer.html translated=\"yes\" translationOutdated=\"no\" %}"
 
@@ -40,20 +41,65 @@ msgstr "{% include disclaimer.html translated=\"yes\" translationOutdated=\"no\"
 msgid "The Basics"
 msgstr "Det grunleggende"
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-#
+#, fuzzy
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+#| msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr "En spesiell transaksjon der mottakeren bare kan bruke midlene etter en fremtidig dato, som satt av senderen."
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-#
+#, fuzzy
-msgid "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."
+#| msgid "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."
+msgid "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.***"
 msgstr "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."
 
-#. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
 #
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr "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."
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

_i18n/nl/resources/moneropedia/unlocktime.md

@@ -1,30 +1,59 @@
 ---
+summary: 'a special transaction where the recipient(s) 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(s) 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 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.***
+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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/nl/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -19,7 +19,7 @@ msgstr ""
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
 #, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr ""
 
 #. type: YAML Front Matter: terms
@@ -41,15 +41,56 @@ msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-msgid "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."
+msgid "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.***"
 msgstr ""
 
 #. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

_i18n/pl/resources/moneropedia/unlocktime.md

@@ -1,30 +1,59 @@
 ---
-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'
-summary: "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
+terms: ["unlock-time", "czasem-na-odblokowanie"]
 ---
 
-{% include disclaimer.html translated="no" translationOutdated="no" %}
+{% include disclaimer.html translated="yes" translationOutdated="no" %}
 
-### The Basics
+### Podstawy
 
-A special transaction where the recipient(s) 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 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.***
+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.
+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.
 
-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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/pl/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -18,8 +18,9 @@ msgstr ""
 
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
-#, no-wrap
+#, fuzzy, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+#| msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr "Specjalny rodzaj transakcji, gdzie odbiorca może wydać otrzymane środki dopiero po dacie ustalonej przez nadawcę."
 
 #. type: YAML Front Matter: terms
@@ -28,9 +29,9 @@ msgstr "Specjalny rodzaj transakcji, gdzie odbiorca może wydać otrzymane środ
 msgid "[\"unlock-time\"]"
 msgstr "[\"unlock-time\", \"czasem-na-odblokowanie\"]"
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:7
-#
 msgid "{% include disclaimer.html translated=\"no\" translationOutdated=\"no\" %}"
 msgstr "{% include disclaimer.html translated=\"yes\" translationOutdated=\"no\" %}"
 
@@ -40,20 +41,65 @@ msgstr "{% include disclaimer.html translated=\"yes\" translationOutdated=\"no\"
 msgid "The Basics"
 msgstr "Podstawy"
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-#
+#, fuzzy
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+#| msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr "Specjalny rodzaj transakcji, gdzie odbiorca może wydać otrzymane środki dopiero po dacie ustalonej przez nadawcę."
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-#
+#, fuzzy
-msgid "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."
+#| msgid "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."
+msgid "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.***"
 msgstr "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."
 
-#. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
 #
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr "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."
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

_i18n/pt-br/resources/moneropedia/unlocktime.md

@@ -1,30 +1,59 @@
 ---
+summary: 'a special transaction where the recipient(s) 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(s) 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 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.***
+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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/pt-br/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -19,7 +19,7 @@ msgstr ""
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
 #, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr ""
 
 #. type: YAML Front Matter: terms
@@ -41,15 +41,56 @@ msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-msgid "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."
+msgid "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.***"
 msgstr ""
 
 #. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

_i18n/ru/resources/moneropedia/unlocktime.md

@@ -1,30 +1,59 @@
 ---
-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'
-summary: "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
+terms: ["unlock-time", "временем-разблокировки"]
 ---
 
-{% include disclaimer.html translated="no" translationOutdated="no" %}
+{% include disclaimer.html translated="yes" 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.
+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.***
+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.
+Следует отметить, что этот механизм работает не так, как
+[nLockTime](https://en.bitcoin.it/wiki/NLockTime) у Bitcoin, где транзакция
+не считается действительной до какого-то указанного момента времени.
 
-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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/ru/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -18,8 +18,9 @@ msgstr ""
 
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
-#, no-wrap
+#, fuzzy, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+#| msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr "Особый случай транзакции, когда получатель может потратить средства только после какой-то определённой даты в будущем, которая устанавливается отправителем."
 
 #. type: YAML Front Matter: terms
@@ -28,9 +29,9 @@ msgstr "Особый случай транзакции, когда получа
 msgid "[\"unlock-time\"]"
 msgstr "[\"unlock-time\", \"временем-разблокировки\"]"
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:7
-#
 msgid "{% include disclaimer.html translated=\"no\" translationOutdated=\"no\" %}"
 msgstr "{% include disclaimer.html translated=\"yes\" translationOutdated=\"no\" %}"
 
@@ -40,20 +41,65 @@ msgstr "{% include disclaimer.html translated=\"yes\" translationOutdated=\"no\"
 msgid "The Basics"
 msgstr "Основная информация"
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-#
+#, fuzzy
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+#| msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr "Особый случай транзакции, когда получатель может потратить средства только после какой-то определённой даты в будущем, которая устанавливается отправителем."
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-#
+#, fuzzy
-msgid "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."
+#| msgid "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."
+msgid "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.***"
 msgstr "Время разблокировки позволяет вам направить кому-то транзакцию, и этот кто-то сможет потратить средства только спустя некоторое количество блоков или спустя определённое время."
 
-#. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
 #
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr "Следует отметить, что этот механизм работает не так, как [nLockTime](https://en.bitcoin.it/wiki/NLockTime) у Bitcoin, где транзакция не считается действительной до какого-то указанного момента времени."
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

_i18n/tr/resources/moneropedia/unlocktime.md

@@ -1,30 +1,59 @@
 ---
+summary: 'a special transaction where the recipient(s) 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(s) 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 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.***
+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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/tr/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -19,7 +19,7 @@ msgstr ""
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
 #, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr ""
 
 #. type: YAML Front Matter: terms
@@ -41,15 +41,56 @@ msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-msgid "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."
+msgid "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.***"
 msgstr ""
 
 #. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

_i18n/zh-cn/resources/moneropedia/unlocktime.md

@@ -1,30 +1,58 @@
 ---
+summary: 'a special transaction where the recipient(s) 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" %}
+{% include disclaimer.html translated="yes" 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.
+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.***
+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.
+注意，这与比特币的 [nLockTime](https://en.bitcoin.it/wiki/NLockTime)
+不同，在比特币的网络当中，交易直到给定的时间才有效。
 
-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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/zh-cn/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -18,8 +18,9 @@ msgstr ""
 
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
-#, no-wrap
+#, fuzzy, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+#| msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr "一种特殊的交易，在这种交易中，收件人只能在将来某个日期之后才可以使用资金，这是由发送者设定的。"
 
 #. type: YAML Front Matter: terms
@@ -28,9 +29,9 @@ msgstr "一种特殊的交易，在这种交易中，收件人只能在将来某
 msgid "[\"unlock-time\"]"
 msgstr ""
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:7
-#
 msgid "{% include disclaimer.html translated=\"no\" translationOutdated=\"no\" %}"
 msgstr "{% include disclaimer.html translated=\"yes\" translationOutdated=\"no\" %}"
 
@@ -40,20 +41,65 @@ msgstr "{% include disclaimer.html translated=\"yes\" translationOutdated=\"no\"
 msgid "The Basics"
 msgstr "基础知识"
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-#
+#, fuzzy
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+#| msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr "一种特殊的交易，在这种交易中，收件人只能在将来某个日期之后才可以使用资金，这是由发送者设定的。"
 
+#
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-#
+#, fuzzy
-msgid "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."
+#| msgid "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."
+msgid "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.***"
 msgstr "解锁时间允许您向某人发送一笔交易，而接收者就必须在一定数量的区块后，或者直到某一时间才能使用该笔资金。"
 
-#. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
 #
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr "注意，这与比特币的 [nLockTime](https://en.bitcoin.it/wiki/NLockTime) 不同，在比特币的网络当中，交易直到给定的时间才有效。"
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

_i18n/zh-tw/resources/moneropedia/unlocktime.md

@@ -1,30 +1,59 @@
 ---
+summary: 'a special transaction where the recipient(s) 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(s) 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 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.***
+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. 
+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. 
+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.
+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.
+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.
+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.
+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.

_i18n/zh-tw/resources/moneropedia/weblate/unlocktime.po

@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2021-10-14 10:41+0100\n"
+"POT-Creation-Date: 2022-12-12 10:09+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -19,7 +19,7 @@ msgstr ""
 #. type: YAML Front Matter: summary
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:1
 #, no-wrap
-msgid "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
+msgid "a special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender"
 msgstr ""
 
 #. type: YAML Front Matter: terms
@@ -41,15 +41,56 @@ msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:11
-msgid "A special transaction where the recipient can only spend the funds after a future date, as set by the sender."
+msgid "A special transaction where the recipient(s) can only spend the funds after a future date, as set by the sender."
 msgstr ""
 
 #. type: Plain text
 #: ../_i18n/en/resources/moneropedia/unlocktime.md:13
-msgid "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."
+msgid "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.***"
 msgstr ""
 
 #. type: Plain text
-#: ../_i18n/en/resources/moneropedia/unlocktime.md:14
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:15
 msgid "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."
 msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:17
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:19
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:23
+msgid "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."
+msgstr ""
+
+#. type: Title ###
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:24
+#, no-wrap
+msgid "Technical Use"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
+msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
+msgid "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."
+msgstr ""
+
+#. type: Plain text
+#: ../_i18n/en/resources/moneropedia/unlocktime.md:30
+msgid "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."
+msgstr ""

po/moneropedia/unlocktime.config

@@ -10,4 +10,4 @@
 
 [po4a_alias:markdown] text opt:"--option markdown"
 
-[type: markdown] ../_i18n/en/resources/moneropedia/unlocktime.md $lang:../_i18n/$lang/resources/moneropedia/unlocktime.md
+[type: markdown] ../_i18n/en/resources/moneropedia/unlocktime.md $lang:../_i18n/$lang/resources/moneropedia/unlocktime.md