Any thought to reduce downloading time of blockchain ?

[allwelder]

The moderator delete my post,post again,DO NOT DELETE AGAIN,THIS IS NOT SPAM.

There are already coins(Tera) that can reduce the time.
It download blockchain data from end rather than beginning,so when user start client,no need to wait for downloading whole blockchain data,just use it,and let the downloading run at the same time.

Even though this did not reduce the whole time needed for downloading,but reduce waiting time.

This is also can be use to many coins,including bitcoin.

[1715425728]

1715425728

[1715425728]

1715425728

[1715425728]

1715425728

[Wind_FURY]

The moderator delete my post,post again,DO NOT DELETE AGAIN,THIS IS NOT SPAM.

There are already coins(Tera) that can reduce the time.
It download blockchain data from end rather than beginning,so when user start client,no need to wait for downloading whole blockchain data,just use it,and let the downloading run at the same time.

In context of this topic. You still can't use it, it's not a full node, because your client hasn't completely validated everything.

The mod deleted your post because he probably believes you don't understand.

Even though this did not reduce the whole time needed for downloading,but reduce waiting time.

You're still required to wait.

This is also can be use to many coins,including bitcoin.

No. I can use Electrum while my node is syncing.

OP, to help reduce the initial blockchain download as time passes by? Smaller blocks.

[DaCryptoRaccoon]

If you're feeling incredibly brave, you can test out the pull requests from this user on github which all together can apparently cut the IBD time by ~14%.

But 14% is not big enough to justify such a risky move, these are testing changes, and as such are not for real-world use in their current state. Although this particular change has been pulled into 0.19.0 release candidate, and is perhaps lower risk. I would still advise against it if you're expecting stability, there is a big risk that the full consequences of these changes have not yet been observed, as they've only seen limited testing.

Did your even read what I posted..

"It is advisable to download from the network but this is a way for those who struggle with downloading or have poor connection."

and how is it any more irresponsible to be downloading and running pull request code that is "such a risky move" and "perhaps lower risk"..

If you validate the downloads there is no issue.

TBH I don't know why they don't offer a more up-to-date way to download this and then validate there are a lot of people who still struggle and bootstrapping the data helps.

[Carlton Banks]

@magic byte

you're replying to the wrong post


(I predict more confusing replies from Magic Byte to follow )

[achow101]

https://bitcoin.org/bin/block-chain/

You can bootstrap download the chain from here just make sure to check the signatures it will help you.

It is advisable to download from the network but this is a way for those who struggle with downloading or have poor connection.

this is a bad idea, do NOT listen to the above advice under any circumstances.

You risk being connected to a fake blockchain if you download random torrents without knowing what you're doing

@MagicByte your post is irresponsible

It actually isn't. It's just the original bootstrap.dat file (that is no longer being updated) that people previously used. Notice how it is hosted on bitcoin.org.

The original thread announcing it is at https://bitcointalk.org/index.php?topic=145386.0. That message is signed with Jeff Garzik's old PGP key: https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x3710408162759fc5a4296536e7a58e337adca079

"It is advisable to download from the network but this is a way for those who struggle with downloading or have poor connection."

and how is it any more irresponsible to be downloading and running pull request code that is "such a risky move" and "perhaps lower risk"..

If you validate the downloads there is no issue.

TBH I don't know why they don't offer a more up-to-date way to download this and then validate there are a lot of people who still struggle and bootstrapping the data helps.

Because it isn't any faster to use the bootstrap.dat file. It has not been faster to use it since 0.10.0 when headers first sync and out of order download were first introduced. The bootstrap.dat file was useful prior to that, but it no longer is.

The reason it is slower to use the bootstrap.dat file is because it just contains the blocks. Your node still has to read them off disk and validate them. It also happens to be one big file and the node does not know where each block is in that file, so it can only go through it one at a time. This is much slower than how syncing works now where multiple blocks are downloaded in parallel, and because the node is the one writing them to disk, it also knows exactly where in each file the blocks are stored so they can be pulled up later for the final step of validation. This parallelization also allows validating things that are independent of each other to be done in parallel which speeds up the sync.

It is important to note that the primary slow down in syncing is due to the processing, storage (disk I/O), and validation of blocks, not the network speed.

[Carlton Banks]

https://bitcoin.org/bin/block-chain/

You can bootstrap download the chain from here just make sure to check the signatures it will help you.

It is advisable to download from the network but this is a way for those who struggle with downloading or have poor connection.

this is a bad idea, do NOT listen to the above advice under any circumstances.

You risk being connected to a fake blockchain if you download random torrents without knowing what you're doing

@MagicByte your post is irresponsible

It actually isn't. It's just the original bootstrap.dat file (that is no longer being updated) that people previously used. Notice how it is hosted on bitcoin.org.

The original thread announcing it is at https://bitcointalk.org/index.php?topic=145386.0. That message is signed with Jeff Garzik's old PGP key: https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x3710408162759fc5a4296536e7a58e337adca079

right, but not everyone is necessarily going to do a search to find out what the origin of the torrent link is, or to find out whose PGP created the signature.

and the fact that it's hosted on bitcoin.org is a little meaningless on it's own, the admin/owner of that site started to behave a little strangely in public over the last few years, you should know that Bitcoin releases are released primarily through https://bitcoincore.org, as you know.

and was the checkpoint code not substituted for the assumevalid model of chain authentication? i.e. is it not possible for someone to download a genuine Bitcoin client from http://bitcoincore.org, be given a bootstrap dat for a fake chain that never reaches the assumevalid blockheight, then get conned into e.g. buying BTC and receiving outputs that would be invalid on the genuine chain?

[achow101]

right, but not everyone is necessarily going to do a search to find out what the origin of the torrent link is, or to find out whose PGP created the signature.

The thread was linked in the message...

and the fact that it's hosted on bitcoin.org is a little meaningless on it's own, the admin/owner of that site started to behave a little strangely in public over the last few years, you should know that Bitcoin releases are released primarily through https://bitcoincore.org, as you know.

Sure, but it's not some random website or link. Bitcoin.org is still somewhat trustworthy. And tbf, Bitcoin Core releases are still posted to bitcoin.org in addition to bitcoincore.org.

and was the checkpoint code not substituted for the assumevalid model of chain authentication? i.e. is it not possible for someone to download a genuine Bitcoin client from http://bitcoincore.org, be given a bootstrap dat for a fake chain that never reaches the assumevalid blockheight, then get conned into e.g. buying BTC and receiving outputs that would be invalid on the genuine chain?

Checkpoints are still there. They are effectively consensus required. So if someone wanted to make a fake bootstrap.dat, they would have to fork from the most recent checkpoint (block 200000 something) and still do all of the work to mine valid blocks.

[Carlton Banks]

Checkpoints are still there. They are effectively consensus required. So if someone wanted to make a fake bootstrap.dat, they would have to fork from the most recent checkpoint (block 200000 something) and still do all of the work to mine valid blocks.

hmmm, this is correct. Longest most work chain would still be the genuine chain subsequent to the last checkpoint. My bad, sorry everybody