Timeline for How is data in a blockchain stored? Structure of block and blockchain
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 1, 2020 at 22:41 | comment | added | Oscar Serna | block size after segwit soft fork allowed blocks to be up to 4 MB. Check out this new question: bitcoin.stackexchange.com/questions/98810/… | |
| Sep 1, 2020 at 17:25 | comment | added | Oscar Serna | I don't know exactly how the latest blocks interact with the blk.dat file being created right at the moment, but I guess it works similar to how rotating-log-files work. But again, I don't really know the exact mechanics of it. | |
| Sep 1, 2020 at 17:23 | comment | added | Oscar Serna | A single file contains many blocks because blocks have a size limit of 1 MB, and the files have a limit of 128MiB. You can find these files in a folder called 'blocks', and they are formatted like this: blkxxxxx.dat (xxxxx is the 5 digit consecutive index of the file). Every block has an id which is calculated through the information in the block, and part of that information is the id of the previous block. In this way, the block knows after what block it comes in the blockchain. | |
| Sep 1, 2020 at 8:08 | comment | added | mmaciek | Ok I almost got it, but one more thing. Every block is an independant file and all these files have some kind of reference to the previous file (block), or there is one blockchain file which is updated every time when a new block is added? | |
| Sep 1, 2020 at 0:36 | comment | added | Oscar Serna | Thanks man. You always give me great inputs and updates. I still have a lot to learn. | |
| Sep 1, 2020 at 0:06 | comment | added | Pieter Wuille | Full nodes can be pruned, in which case only recent blocks are stored (old ones are still downloaded, verified, and processed, but thrown away after some time). The "full" aspect refers to validation. | |
| Aug 31, 2020 at 23:20 | history | answered | Oscar Serna | CC BY-SA 4.0 |