what can explain the difference in my copy?
1. Different full node software, which might store blockchain differently.
2. Few software such as Bitcoin Core doesn't remove orphaned block.
3. The statistic isn't frequently updated.
Topic: <solved> blockchain size on full node (Read 77 times)
1. Different full node software, which might store blockchain differently.
2. Few software such as Bitcoin Core doesn't remove orphaned block.
3. The statistic isn't frequently updated.
0.657 TB
That seems a bit much. Any chance there's 200 GB of other data included?Quote
Please explain chainstate.
Allow me to copy Pieter Wuille:Quote
the blocks directory contains the actual blocks. The chainstate directory contains the state as of the latest block (in simplified terms, it stores every spendable coin, who owns it, and how much it's worth).
Quote
Console command for that?
It's just a directory, by default on this location:Code:
cd .bitcoin/chainstate/
In case it helps, I have 418 GB blocks, 4.5 GB chainstate and 34.2 GB indexes (yes, I have indexes on). But (for personal reasons) my blockchain is not synced for 2 days, it was stopped.
PS. Beware that depending on how the HDD is formatted the actual size on disk may differ a little from one node to another.
PS. Beware that depending on how the HDD is formatted the actual size on disk may differ a little from one node to another.
Most sites don't update the total size, so the longer ago someone typed it, the smaller the number.
I currently have 4.6GB chainstate and 420 GB blocks.
thanks for the verification on your data
im running a full node on my raspberry pi and currently the blockchain data directories are taking up 425GB of space.
about 421GB in the blocks directory and 4.6GB in the chainstate directory.
i see on websites like ycharts dot com that the current blockchain size is about 396GB.
what can explain the difference in my copy?
about 421GB in the blocks directory and 4.6GB in the chainstate directory.
i see on websites like ycharts dot com that the current blockchain size is about 396GB.
what can explain the difference in my copy?
No pruning in your case? FYI, my directory properties indicate 0.657 TB "size on disk." There is another value, 0.676 TB indicated by properties which is something other than "size on disk." I don't know if that's the objective blockchain independent of a particular user's use case. I think that there must be differences in configuration that explain individual differences in the size of a blockchain that one has onsite in a Full Node versus the objective size.
Other thoughts:
I think that the objective size of the blockchain must have a constant value that only changes when another block is concatenated. And I wonder if each block is quantitatively identical or different. You could evaluate the size of the objective blockchain and divide by blockheight and at least get an average per block.
what can explain the difference in my copy?
Most sites don't update the total size, so the longer ago someone typed it, the smaller the number.I currently have 4.6GB chainstate and 420 GB blocks.
Please explain chainstate. Console command for that?
[moderator's note: consecutive posts merged]
what can explain the difference in my copy?
Most sites don't update the total size, so the longer ago someone typed it, the smaller the number.I currently have 4.6GB chainstate and 420 GB blocks.
im running a full node on my raspberry pi and currently the blockchain data directories are taking up 425GB of space.
about 421GB in the blocks directory and 4.6GB in the chainstate directory.
i see on websites like ycharts dot com that the current blockchain size is about 396GB.
what can explain the difference in my copy?
about 421GB in the blocks directory and 4.6GB in the chainstate directory.
i see on websites like ycharts dot com that the current blockchain size is about 396GB.
what can explain the difference in my copy?
Jump to: