Skip to content

Conversation

@coinables
Copy link
Contributor

This option is becoming more popular recently, and I propose an example to be shown in the bitcoin.conf.

@fanquake fanquake added the Docs label Mar 26, 2017
@laanwj
Copy link
Member

laanwj commented Mar 27, 2017

Concept ACK on adding the example.

Explicitly mentioning 3GB is not a good idea. These numbers peppered around the documentation tend to get outdated sooner than later. The size of the UTXO set is growing every day, and that can't be pruned.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You have the unit wrong, it's not in blocks but in MiB. Maybe you can borrow some description text from the help message:

  -prune=<n>
       Reduce storage requirements by enabling pruning (deleting) of old
       blocks. This allows the pruneblockchain RPC to be called to
       delete specific blocks, and enables automatic pruning of old
       blocks if a target size in MiB is provided. This mode is
       incompatible with -txindex and -rescan. Warning: Reverting this
       setting requires re-downloading the entire blockchain. (default:
       0 = disable pruning blocks, 1 = allow manual pruning via RPC,
       >550 = automatically prune block files to stay under the
       specified target size in MiB)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

requirements

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

550 is the minimum, but you describe entering 1...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

=550

@sipa
Copy link
Member

sipa commented Mar 29, 2017

ACK after squashing.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

space before "(". And please squash.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

requirments -> requirements

This option is becoming more popular recently, and I propose an example to be shown in the bitcoin.conf.

pruning comments

updated and corrected pruning comments

Revised details on pruning in bitcoin.conf

Revised details on pruning in bitcoin.conf

spelling and space

spelling and space

add details on pruning in bitcoin.conf
@fanquake
Copy link
Member

utACK c0651cc

@maflcko maflcko merged commit c0651cc into bitcoin:master Mar 31, 2017
maflcko pushed a commit that referenced this pull request Mar 31, 2017
c0651cc Update bitcoin.conf with example for pruning (Kyle Honeycutt)

Tree-SHA512: f27180ac5d5a4bd32c7a63de156ca14eb8068509e64d386ca84ee16d0dacfa8e1bab9a8e7b88175fae12c8d823f71f8705d413f224a15d5aa7cf059f416fa023
@laanwj
Copy link
Member

laanwj commented Mar 31, 2017

I think we should move this file somewhere else - doc/examples maybe? After all it is a general example of a bitcoin.conf and there is nothing debian-specific to it.

PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this pull request May 23, 2019
c0651cc Update bitcoin.conf with example for pruning (Kyle Honeycutt)

Tree-SHA512: f27180ac5d5a4bd32c7a63de156ca14eb8068509e64d386ca84ee16d0dacfa8e1bab9a8e7b88175fae12c8d823f71f8705d413f224a15d5aa7cf059f416fa023
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants