There are now two ways to sync a chain. They can take several times longer or shorter to complete, while requiring almost the same amount of verification.
One way is to download checkpoints accepted by most nodes from other nodes—one every 10,000 blocks, about 400 MB—and then import them and sync only the short stretch that follows. The other is for when no agreed-upon checkpoint is available: download a full index snapshot, about 2 GB, and verify it block by block against hashes built into the app.
What you save is download volume and wait time, not verification. Every block is checked either way; the difference is what it’s checked against: a checkpoint list or built-in hashes.
$DOGE produces one block per minute, or more than 520,000 a year. Pulling them one by one from scratch takes a significant amount of time—that’s what makes the difference between the two approaches matter.
Whether an agreed-upon checkpoint is available determines which approach to use.
#Dogecoin #Web3
Figures and mechanisms are based on official sources. DYOR.
One way is to download checkpoints accepted by most nodes from other nodes—one every 10,000 blocks, about 400 MB—and then import them and sync only the short stretch that follows. The other is for when no agreed-upon checkpoint is available: download a full index snapshot, about 2 GB, and verify it block by block against hashes built into the app.
What you save is download volume and wait time, not verification. Every block is checked either way; the difference is what it’s checked against: a checkpoint list or built-in hashes.
$DOGE produces one block per minute, or more than 520,000 a year. Pulling them one by one from scratch takes a significant amount of time—that’s what makes the difference between the two approaches matter.
Whether an agreed-upon checkpoint is available determines which approach to use.
#Dogecoin #Web3
Figures and mechanisms are based on official sources. DYOR.