update i18n moneropedia entry unlocktime

This commit is contained in:
erciccione 2023-10-26 10:43:49 +02:00
parent 1d97ced684
commit 4777a0e6df
No known key found for this signature in database
GPG key ID: 762AF8C608E56CDF
29 changed files with 132 additions and 266 deletions

View file

@ -27,10 +27,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,13 +16,13 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
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
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -61,36 +61,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""

View file

@ -28,10 +28,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,14 +16,14 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, 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(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
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -70,36 +70,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,13 +16,13 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
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
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -67,41 +67,35 @@ 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."
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: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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, markdown-text, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
#, markdown-text
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#, 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
#, 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 ""

View file

@ -27,10 +27,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,13 +16,13 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
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
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -61,36 +61,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""

View file

@ -27,10 +27,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,14 +16,14 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, 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(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
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -70,36 +70,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""

View file

@ -27,10 +27,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,13 +16,13 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
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
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -61,36 +61,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""

View file

@ -27,10 +27,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,14 +16,14 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, 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(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
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -70,36 +70,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""

View file

@ -27,10 +27,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,13 +16,13 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
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
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -61,36 +61,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""

View file

@ -27,10 +27,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,14 +16,14 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, 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(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
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -70,36 +70,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""

View file

@ -27,10 +27,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,13 +16,13 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
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
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -61,36 +61,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""

View file

@ -1,19 +1,20 @@
---
summary: 'total number of possible signers in a ring signature'
terms: ["ring-size"]
summary: 'общее количество подписантов участвующих в формировании кольцевой подписи'
terms: ["ring-size", "размер-кольца"]
---
{% include disclaimer.html translated="no" translationOutdated="no" %}
### The Basics
### Основная информация
Ring size refers to the total number of signers in a @ring-signature. Before
release [0.13.0 "Beryllium Bullet"]({{ site.baseurl
}}/2018/10/11/monero-0.13.0-released.html), it was possible to select an
arbitrary number of signers. With release 0.13, it was decided to set this
number to 11 to enforce transaction uniformity.
Размером кольца называется общее количество подписантов, присутствующих в
@кольцевой-подписи. До выхода версии [0.13.0 "Beryllium Bullet"]({{
site.baseurl }}/2018/10/11/monero-0.13.0-released.html) можно было выбрать
любое произвольное количество подписантов. При реализации этой версии
протокола было решено сделать данный параметр фиксированным и равным 11, что
обеспечивало бы единообразие транзакций.
`Ring size (16) = foreign outputs (15) + your output (1)`
`Размер кольца (16) = чужие выходы (15) + ваш выход (1)`
Foreign outputs are typically called "decoys," and the number of decoys was
previously called the "mixin" size.
Чужие выходы, как правило, называют «ложными», а количество ложных выходов
ранее называли размером «миксина».

View file

@ -27,10 +27,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -10,22 +10,19 @@ msgstr ""
"POT-Creation-Date: 2021-10-04 11:57+0100\n"
"PO-Revision-Date: 2022-02-25 14:34+0000\n"
"Last-Translator: v1docq47 <chiptune@protonmail.ch>\n"
"Language-Team: Russian <https://translate.getmonero.org/projects/"
"getmonero-moneropedia/ring-size/ru/>\n"
"Language-Team: Russian <https://translate.getmonero.org/projects/getmonero-moneropedia/ring-size/ru/>\n"
"Language: ru\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n"
"Plural-Forms: nplurals=3; plural=n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n"
"X-Generator: Weblate 4.8\n"
#. type: YAML Front Matter: summary
#: ../_i18n/en/resources/moneropedia/ring-size.md:1
#, no-wrap
msgid "total number of possible signers in a ring signature"
msgstr ""
"общее количество подписантов участвующих в формировании кольцевой подписи"
msgstr "общее количество подписантов участвующих в формировании кольцевой подписи"
#. type: YAML Front Matter: terms
#: ../_i18n/en/resources/moneropedia/ring-size.md:1
@ -36,8 +33,7 @@ msgstr "[\"ring-size\", \"размер-кольца\"]"
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/ring-size.md:7
msgid "{% include disclaimer.html translated=\"no\" translationOutdated=\"no\" %}"
msgstr ""
"{% include disclaimer.html translated=\"no\" translationOutdated=\"no\" %}"
msgstr "{% include disclaimer.html translated=\"no\" translationOutdated=\"no\" %}"
#. type: Title ###
#: ../_i18n/en/resources/moneropedia/ring-size.md:8
@ -48,22 +44,14 @@ msgstr "Основная информация"
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/ring-size.md:11
msgid "Ring size refers to the total number of signers in a @ring-signature. Before release [0.13.0 \"Beryllium Bullet\"]({{ site.baseurl }}/2018/10/11/monero-0.13.0-released.html), it was possible to select an arbitrary number of signers. With release 0.13, it was decided to set this number to 11 to enforce transaction uniformity."
msgstr ""
"Размером кольца называется общее количество подписантов, присутствующих в "
"@кольцевой-подписи. До выхода версии [0.13.0 \"Beryllium Bullet\"]({{ "
"site.baseurl }}/2018/10/11/monero-0.13.0-released.html) можно было выбрать "
"любое произвольное количество подписантов. При реализации этой версии "
"протокола было решено сделать данный параметр фиксированным и равным 11, что "
"обеспечивало бы единообразие транзакций."
msgstr "Размером кольца называется общее количество подписантов, присутствующих в @кольцевой-подписи. До выхода версии [0.13.0 \"Beryllium Bullet\"]({{ site.baseurl }}/2018/10/11/monero-0.13.0-released.html) можно было выбрать любое произвольное количество подписантов. При реализации этой версии протокола было решено сделать данный параметр фиксированным и равным 11, что обеспечивало бы единообразие транзакций."
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/ring-size.md:13
msgid "`Ring size (11) = foreign outputs (10) + your output (1)`"
msgstr "`Размер кольца (11) = чужие выходы (10) + ваш выход (1)`"
msgid "`Ring size (16) = foreign outputs (15) + your output (1)`"
msgstr "`Размер кольца (16) = чужие выходы (15) + ваш выход (1)`"
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/ring-size.md:14
msgid "Foreign outputs are typically called \"decoys,\" and the number of decoys was previously called the \"mixin\" size."
msgstr ""
"Чужие выходы, как правило, называют «ложными», а количество ложных выходов "
"ранее называли размером «миксина»."
msgstr "Чужие выходы, как правило, называют «ложными», а количество ложных выходов ранее называли размером «миксина»."

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,14 +16,14 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, 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(s) can only spend the funds after a future date, as set by the sender"
msgstr "Особый случай транзакции, когда получатель может потратить средства только после какой-то определённой даты в будущем, которая устанавливается отправителем."
#. type: YAML Front Matter: terms
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -70,36 +70,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""

View file

@ -27,10 +27,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,13 +16,13 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
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
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -61,36 +61,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""

View file

@ -26,10 +26,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,14 +16,14 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, 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(s) can only spend the funds after a future date, as set by the sender"
msgstr "一种特殊的交易,在这种交易中,收件人只能在将来某个日期之后才可以使用资金,这是由发送者设定的。"
#. type: YAML Front Matter: terms
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -70,36 +70,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""

View file

@ -27,10 +27,6 @@ and may be removed in a future Monero release, so the Monero developers
advise against building critical infrastructure that depends on this
feature.
Decoy outputs may be selected from these locked outputs, thus identifying
them as provable decoy outputs. At the moment, this has little impact on
wider network privacy since this unlock time feature is so rarely used.
Further, true spends after a reasonably long lock time (more than several
days) may be heuristically identified as the true spend, since there will be
fewer other transactions using those outputs as decoys around that time

View file

@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2022-12-12 10:09+0000\n"
"POT-Creation-Date: 2023-10-26 10:42+0200\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"
@ -16,13 +16,13 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: YAML Front Matter: summary
#. type: Yaml Front Matter Hash Value: summary
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
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
#. type: Yaml Front Matter Hash Value: terms
#: ../_i18n/en/resources/moneropedia/unlocktime.md:1
#, no-wrap
msgid "[\"unlock-time\"]"
@ -61,36 +61,31 @@ 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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:21
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:22
#, no-wrap
msgid "Technical Use"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
#: ../_i18n/en/resources/moneropedia/unlocktime.md:25
msgid "Usage when using the `transfer` command: `unlock_time` + unsigned int"
msgstr ""
#. type: Plain text
#: ../_i18n/en/resources/moneropedia/unlocktime.md:29
#: ../_i18n/en/resources/moneropedia/unlocktime.md:27
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
#: ../_i18n/en/resources/moneropedia/unlocktime.md:28
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 ""