From 52bafb746c47b5da6c5fddc672f5e3afecfb97ee Mon Sep 17 00:00:00 2001 From: erciccione Date: Mon, 23 Mar 2020 13:41:03 +0100 Subject: [PATCH 1/2] Moneropedia: add 'Pruning' and link to the Moneropedia entry from the 'Downloads' page --- _i18n/en.yml | 3 ++- _i18n/en/resources/moneropedia/pruning.md | 16 ++++++++++++++++ resources/moneropedia/pruning.md | 10 ++++++++++ 3 files changed, 28 insertions(+), 1 deletion(-) create mode 100644 _i18n/en/resources/moneropedia/pruning.md create mode 100644 resources/moneropedia/pruning.md diff --git a/_i18n/en.yml b/_i18n/en.yml index 60a2b964..68bc8660 100644 --- a/_i18n/en.yml +++ b/_i18n/en.yml @@ -167,7 +167,7 @@ downloads: fiatconv: in-app fiat conversion fiatconv1: No longer a need to check the value of your XMR online pruning: Blockchain pruning - pruning1: Not enough disk space? Just use pruning to download only 1/3 of the blockchain + pruning1: Not enough disk space? Just use @pruning to download only 1/3 of the blockchain langs: "30+ languages available" cli_intro: The CLI wallet gives you the total control over your Monero node and funds. Highly customizable and includes various analysis tools, as well as an HTTP RPC and 0MQ interface. currentversion: Current Version @@ -648,6 +648,7 @@ moneropedia: paperwallet: Paper Wallet paymentid: Payment ID pedersen-commitment: Pedersen Commitment + pruning: Pruning remote-node: Remote Node reseed: Reseed ringCT: Ring CT diff --git a/_i18n/en/resources/moneropedia/pruning.md b/_i18n/en/resources/moneropedia/pruning.md new file mode 100644 index 00000000..011f1242 --- /dev/null +++ b/_i18n/en/resources/moneropedia/pruning.md @@ -0,0 +1,16 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information. \ No newline at end of file diff --git a/resources/moneropedia/pruning.md b/resources/moneropedia/pruning.md new file mode 100644 index 00000000..cbce7e21 --- /dev/null +++ b/resources/moneropedia/pruning.md @@ -0,0 +1,10 @@ +--- +layout: moneropedia +title: titles.moneropedia +entry: moneropedia.entries.pruning +--- + +@moneropedia_article + +{% t global.lang_tag %} +{% tf resources/moneropedia/pruning.md %} From da7cec1cf692bdaacff0ffe1262be5476de2935f Mon Sep 17 00:00:00 2001 From: erciccione Date: Mon, 23 Mar 2020 13:59:14 +0100 Subject: [PATCH 2/2] Add 'Pruning' to all languages --- _i18n/ar.yml | 1 + _i18n/ar/resources/moneropedia/pruning.md | 17 +++++++++++++++++ _i18n/de.yml | 1 + _i18n/de/resources/moneropedia/pruning.md | 17 +++++++++++++++++ _i18n/es.yml | 1 + _i18n/es/resources/moneropedia/pruning.md | 17 +++++++++++++++++ _i18n/fr.yml | 1 + _i18n/fr/resources/moneropedia/pruning.md | 17 +++++++++++++++++ _i18n/it.yml | 1 + _i18n/it/resources/moneropedia/pruning.md | 17 +++++++++++++++++ _i18n/nl.yml | 1 + _i18n/nl/resources/moneropedia/pruning.md | 17 +++++++++++++++++ _i18n/pl.yml | 1 + _i18n/pl/resources/moneropedia/pruning.md | 17 +++++++++++++++++ _i18n/pt-br.yml | 1 + _i18n/pt-br/resources/moneropedia/pruning.md | 17 +++++++++++++++++ _i18n/ru.yml | 1 + _i18n/ru/resources/moneropedia/pruning.md | 17 +++++++++++++++++ _i18n/tr.yml | 1 + _i18n/tr/resources/moneropedia/pruning.md | 17 +++++++++++++++++ _i18n/zh-cn.yml | 1 + _i18n/zh-cn/resources/moneropedia/pruning.md | 17 +++++++++++++++++ _i18n/zh-tw.yml | 1 + _i18n/zh-tw/resources/moneropedia/pruning.md | 17 +++++++++++++++++ 24 files changed, 216 insertions(+) create mode 100644 _i18n/ar/resources/moneropedia/pruning.md create mode 100644 _i18n/de/resources/moneropedia/pruning.md create mode 100644 _i18n/es/resources/moneropedia/pruning.md create mode 100644 _i18n/fr/resources/moneropedia/pruning.md create mode 100644 _i18n/it/resources/moneropedia/pruning.md create mode 100644 _i18n/nl/resources/moneropedia/pruning.md create mode 100644 _i18n/pl/resources/moneropedia/pruning.md create mode 100644 _i18n/pt-br/resources/moneropedia/pruning.md create mode 100644 _i18n/ru/resources/moneropedia/pruning.md create mode 100644 _i18n/tr/resources/moneropedia/pruning.md create mode 100644 _i18n/zh-cn/resources/moneropedia/pruning.md create mode 100644 _i18n/zh-tw/resources/moneropedia/pruning.md diff --git a/_i18n/ar.yml b/_i18n/ar.yml index 7d650c00..54cf3109 100644 --- a/_i18n/ar.yml +++ b/_i18n/ar.yml @@ -632,6 +632,7 @@ moneropedia: paperwallet: Paper Wallet paymentid: Payment ID pedersen-commitment: Pedersen Commitment + pruning: Pruning remote-node: Remote Node reseed: Reseed ringCT: Ring CT diff --git a/_i18n/ar/resources/moneropedia/pruning.md b/_i18n/ar/resources/moneropedia/pruning.md new file mode 100644 index 00000000..346489c1 --- /dev/null +++ b/_i18n/ar/resources/moneropedia/pruning.md @@ -0,0 +1,17 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +{% include untranslated.html %} +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information. diff --git a/_i18n/de.yml b/_i18n/de.yml index f46ddd1f..e2028613 100644 --- a/_i18n/de.yml +++ b/_i18n/de.yml @@ -633,6 +633,7 @@ moneropedia: paperwallet: Paper-Wallet paymentid: Payment-ID pedersen-commitment: Pedersen-Commitment + pruning: Pruning remote-node: Remote Node reseed: Reseed ringCT: vertrauliche Ringtransaktionen (Ring CT) diff --git a/_i18n/de/resources/moneropedia/pruning.md b/_i18n/de/resources/moneropedia/pruning.md new file mode 100644 index 00000000..346489c1 --- /dev/null +++ b/_i18n/de/resources/moneropedia/pruning.md @@ -0,0 +1,17 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +{% include untranslated.html %} +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information. diff --git a/_i18n/es.yml b/_i18n/es.yml index 1f124d0e..b0533228 100644 --- a/_i18n/es.yml +++ b/_i18n/es.yml @@ -633,6 +633,7 @@ moneropedia: paperwallet: Monedero en Papel paymentid: ID de Pago pedersen-commitment: Compromiso Pedersen + pruning: Pruning remote-node: Remote Node reseed: Resembrar ringCT: Transacción Circular Confidencial diff --git a/_i18n/es/resources/moneropedia/pruning.md b/_i18n/es/resources/moneropedia/pruning.md new file mode 100644 index 00000000..346489c1 --- /dev/null +++ b/_i18n/es/resources/moneropedia/pruning.md @@ -0,0 +1,17 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +{% include untranslated.html %} +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information. diff --git a/_i18n/fr.yml b/_i18n/fr.yml index 3d9b9e5d..997f4e54 100644 --- a/_i18n/fr.yml +++ b/_i18n/fr.yml @@ -634,6 +634,7 @@ moneropedia: paperwallet: portefeuille Papier paymentid: ID de paiement pedersen-commitment: Engagement de Pedersen + pruning: Pruning remote-node: Remote Node reseed: Réensemencement ringCT: Transactions confidentielles de cercle diff --git a/_i18n/fr/resources/moneropedia/pruning.md b/_i18n/fr/resources/moneropedia/pruning.md new file mode 100644 index 00000000..346489c1 --- /dev/null +++ b/_i18n/fr/resources/moneropedia/pruning.md @@ -0,0 +1,17 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +{% include untranslated.html %} +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information. diff --git a/_i18n/it.yml b/_i18n/it.yml index 469187d3..97d9c73a 100644 --- a/_i18n/it.yml +++ b/_i18n/it.yml @@ -631,6 +631,7 @@ moneropedia: paperwallet: Portafoglio cartaceo paymentid: ID Pagamento pedersen-commitment: Pedersen Commitment + pruning: Pruning remote-node: Remote Node reseed: Reseed ringCT: Ring CT diff --git a/_i18n/it/resources/moneropedia/pruning.md b/_i18n/it/resources/moneropedia/pruning.md new file mode 100644 index 00000000..346489c1 --- /dev/null +++ b/_i18n/it/resources/moneropedia/pruning.md @@ -0,0 +1,17 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +{% include untranslated.html %} +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information. diff --git a/_i18n/nl.yml b/_i18n/nl.yml index 1587f221..aa770a15 100644 --- a/_i18n/nl.yml +++ b/_i18n/nl.yml @@ -634,6 +634,7 @@ moneropedia: paperwallet: Paper Wallet paymentid: Payment ID pedersen-commitment: Pedersen Commitment + pruning: Pruning remote-node: Remote Node reseed: Reseed ringCT: Ring CT diff --git a/_i18n/nl/resources/moneropedia/pruning.md b/_i18n/nl/resources/moneropedia/pruning.md new file mode 100644 index 00000000..346489c1 --- /dev/null +++ b/_i18n/nl/resources/moneropedia/pruning.md @@ -0,0 +1,17 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +{% include untranslated.html %} +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information. diff --git a/_i18n/pl.yml b/_i18n/pl.yml index 54756bfe..3531c0ea 100644 --- a/_i18n/pl.yml +++ b/_i18n/pl.yml @@ -633,6 +633,7 @@ moneropedia: paperwallet: Papierowy portfel paymentid: Numer identyfikacyjny płatności pedersen-commitment: Zobowiązanie Pedersena + pruning: Pruning remote-node: Remote Node reseed: Reseed ringCT: Poufne Transakcje Pierścieniowe diff --git a/_i18n/pl/resources/moneropedia/pruning.md b/_i18n/pl/resources/moneropedia/pruning.md new file mode 100644 index 00000000..346489c1 --- /dev/null +++ b/_i18n/pl/resources/moneropedia/pruning.md @@ -0,0 +1,17 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +{% include untranslated.html %} +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information. diff --git a/_i18n/pt-br.yml b/_i18n/pt-br.yml index 51342be3..f04559c4 100644 --- a/_i18n/pt-br.yml +++ b/_i18n/pt-br.yml @@ -634,6 +634,7 @@ moneropedia: paperwallet: Carteira em Papel paymentid: ID de Pagamento pedersen-commitment: Comprometimento de Pedersen + pruning: Pruning remote-node: Remote Node reseed: Reseed ringCT: Ring CT diff --git a/_i18n/pt-br/resources/moneropedia/pruning.md b/_i18n/pt-br/resources/moneropedia/pruning.md new file mode 100644 index 00000000..346489c1 --- /dev/null +++ b/_i18n/pt-br/resources/moneropedia/pruning.md @@ -0,0 +1,17 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +{% include untranslated.html %} +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information. diff --git a/_i18n/ru.yml b/_i18n/ru.yml index d6b35b61..d34c9685 100644 --- a/_i18n/ru.yml +++ b/_i18n/ru.yml @@ -638,6 +638,7 @@ moneropedia: paperwallet: Бумажный кошелёк paymentid: Идентификатор платежа pedersen-commitment: Обязательство Педерсена + pruning: Pruning remote-node: Remote Node reseed: Повторное заполнение ringCT: Ring CT diff --git a/_i18n/ru/resources/moneropedia/pruning.md b/_i18n/ru/resources/moneropedia/pruning.md new file mode 100644 index 00000000..346489c1 --- /dev/null +++ b/_i18n/ru/resources/moneropedia/pruning.md @@ -0,0 +1,17 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +{% include untranslated.html %} +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information. diff --git a/_i18n/tr.yml b/_i18n/tr.yml index add6d32e..aeffe138 100644 --- a/_i18n/tr.yml +++ b/_i18n/tr.yml @@ -633,6 +633,7 @@ moneropedia: paperwallet: Kâğıt Cüzdan paymentid: Ödeme ID pedersen-commitment: Pedersen Üstlenmesi + pruning: Pruning remote-node: Remote Node reseed: Tekrar-tohum ringCT: Halka CT diff --git a/_i18n/tr/resources/moneropedia/pruning.md b/_i18n/tr/resources/moneropedia/pruning.md new file mode 100644 index 00000000..346489c1 --- /dev/null +++ b/_i18n/tr/resources/moneropedia/pruning.md @@ -0,0 +1,17 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +{% include untranslated.html %} +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information. diff --git a/_i18n/zh-cn.yml b/_i18n/zh-cn.yml index caa02f07..a732ea21 100644 --- a/_i18n/zh-cn.yml +++ b/_i18n/zh-cn.yml @@ -632,6 +632,7 @@ moneropedia: paperwallet: 纸钱包 paymentid: 付款ID pedersen-commitment: Pedersen Commitment + pruning: Pruning remote-node: Remote Node reseed: Reseed ringCT: 环交易 diff --git a/_i18n/zh-cn/resources/moneropedia/pruning.md b/_i18n/zh-cn/resources/moneropedia/pruning.md new file mode 100644 index 00000000..346489c1 --- /dev/null +++ b/_i18n/zh-cn/resources/moneropedia/pruning.md @@ -0,0 +1,17 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +{% include untranslated.html %} +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information. diff --git a/_i18n/zh-tw.yml b/_i18n/zh-tw.yml index 6d97002c..33912816 100644 --- a/_i18n/zh-tw.yml +++ b/_i18n/zh-tw.yml @@ -631,6 +631,7 @@ moneropedia: paperwallet: Paper Wallet paymentid: Payment ID pedersen-commitment: Pedersen Commitment + pruning: Pruning remote-node: Remote Node reseed: Reseed ringCT: Ring CT diff --git a/_i18n/zh-tw/resources/moneropedia/pruning.md b/_i18n/zh-tw/resources/moneropedia/pruning.md new file mode 100644 index 00000000..346489c1 --- /dev/null +++ b/_i18n/zh-tw/resources/moneropedia/pruning.md @@ -0,0 +1,17 @@ +--- +terms: ["pruning"] +summary: "Feature that allows node operators to download and sync only 1/3 of the blockchain" +--- + +{% include untranslated.html %} +'Pruning' allows node operators to save 2/3 of storage space while keeping the full transaction history. Pruning works by removing 7/8 of unnecessary ring signature data. The 1/8 remaining data will be available to the other nodes and will be used to sync with the network. Other pruned nodes will have a random 1/8 of the data, which they will also make available to the network. There are no privacy or security downsides when using a pruned node. + +There are three ways to prune: + +- *Synchronize a pruned node from scratch:* You will download and sync only 1/3 of the full blockchain. +- *Prune an existing node:* The already existing blockchain will be pruned, but this will not result in a smaller blockchain. Instead, it will mark parts of the file as free, so that future data will use that free space, causing the file to not grow until free space grows scarce. +- *Create a new pruned blockchain from a full one:* A full blockchain that you already have will be used to create a new, pruned blockchain. + +Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary. + +The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.