mirror of
https://github.com/monero-project/monero-site.git
synced 2025-01-13 14:24:42 +00:00
Merge !1256
Moneropedia: add 'Pruning' Closes #1013 See merge request monero-project/monero-site!1256
This commit is contained in:
commit
9ac0c1c90c
27 changed files with 244 additions and 1 deletions
_i18n
ar.yml
ar/resources/moneropedia
de.ymlde/resources/moneropedia
en.ymlen/resources/moneropedia
es.ymles/resources/moneropedia
fr.ymlfr/resources/moneropedia
it.ymlit/resources/moneropedia
nl.ymlnl/resources/moneropedia
pl.ymlpl/resources/moneropedia
pt-br.ymlpt-br/resources/moneropedia
ru.ymlru/resources/moneropedia
tr.ymltr/resources/moneropedia
zh-cn.ymlzh-cn/resources/moneropedia
zh-tw.ymlzh-tw/resources/moneropedia
resources/moneropedia
|
@ -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
|
||||
|
|
17
_i18n/ar/resources/moneropedia/pruning.md
Normal file
17
_i18n/ar/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
|
@ -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)
|
||||
|
|
17
_i18n/de/resources/moneropedia/pruning.md
Normal file
17
_i18n/de/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
|
@ -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: "<b>30+ languages</b> 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
|
||||
|
@ -651,6 +651,7 @@ moneropedia:
|
|||
paperwallet: Paper Wallet
|
||||
paymentid: Payment ID
|
||||
pedersen-commitment: Pedersen Commitment
|
||||
pruning: Pruning
|
||||
remote-node: Remote Node
|
||||
reseed: Reseed
|
||||
ringCT: Ring CT
|
||||
|
|
16
_i18n/en/resources/moneropedia/pruning.md
Normal file
16
_i18n/en/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
|
@ -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
|
||||
|
|
17
_i18n/es/resources/moneropedia/pruning.md
Normal file
17
_i18n/es/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
|
@ -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
|
||||
|
|
17
_i18n/fr/resources/moneropedia/pruning.md
Normal file
17
_i18n/fr/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
|
@ -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
|
||||
|
|
17
_i18n/it/resources/moneropedia/pruning.md
Normal file
17
_i18n/it/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
|
@ -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
|
||||
|
|
17
_i18n/nl/resources/moneropedia/pruning.md
Normal file
17
_i18n/nl/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
|
@ -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
|
||||
|
|
17
_i18n/pl/resources/moneropedia/pruning.md
Normal file
17
_i18n/pl/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
|
@ -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
|
||||
|
|
17
_i18n/pt-br/resources/moneropedia/pruning.md
Normal file
17
_i18n/pt-br/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
|
@ -638,6 +638,7 @@ moneropedia:
|
|||
paperwallet: Бумажный кошелёк
|
||||
paymentid: Идентификатор платежа
|
||||
pedersen-commitment: Обязательство Педерсена
|
||||
pruning: Pruning
|
||||
remote-node: Remote Node
|
||||
reseed: Повторное заполнение
|
||||
ringCT: Ring CT
|
||||
|
|
17
_i18n/ru/resources/moneropedia/pruning.md
Normal file
17
_i18n/ru/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
|
@ -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
|
||||
|
|
17
_i18n/tr/resources/moneropedia/pruning.md
Normal file
17
_i18n/tr/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
|
@ -632,6 +632,7 @@ moneropedia:
|
|||
paperwallet: 纸钱包
|
||||
paymentid: 付款ID
|
||||
pedersen-commitment: Pedersen Commitment
|
||||
pruning: Pruning
|
||||
remote-node: Remote Node
|
||||
reseed: Reseed
|
||||
ringCT: 环交易
|
||||
|
|
17
_i18n/zh-cn/resources/moneropedia/pruning.md
Normal file
17
_i18n/zh-cn/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
|
@ -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
|
||||
|
|
17
_i18n/zh-tw/resources/moneropedia/pruning.md
Normal file
17
_i18n/zh-tw/resources/moneropedia/pruning.md
Normal file
|
@ -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.
|
10
resources/moneropedia/pruning.md
Normal file
10
resources/moneropedia/pruning.md
Normal file
|
@ -0,0 +1,10 @@
|
|||
---
|
||||
layout: moneropedia
|
||||
title: titles.moneropedia
|
||||
entry: moneropedia.entries.pruning
|
||||
---
|
||||
|
||||
@moneropedia_article
|
||||
|
||||
{% t global.lang_tag %}
|
||||
{% tf resources/moneropedia/pruning.md %}
|
Loading…
Reference in a new issue