📅 Original date posted:2014-04-07
📝 Original message:I hope I'm not thread-jacking here, apologies if so, but that's the approach I've taken with the node I'm working on.
Headers can be downloaded and stored in any order, it'll make sense of what the winning chain is. Blocks don't need to be downloaded in any particular order and they don't need to be saved to disk, the UTXO is fully self-contained. That way the concern of storing blocks for seeding (or not) is wholly separated from syncing the UTXO. This allows me to do the initial blockchain sync in ~6 hours when I use my SSD. I only need enough disk space to store the UTXO, and then whatever amount of block data the user would want to store for the health of the network.
This project is a bitcoin learning exercise for me, so I can only hope I don't have any critical design flaws in there. :)
From: tamas at bitsofproof.com
Date: Mon, 7 Apr 2014 21:20:31 +0200
To: gmaxwell at gmail.com
CC: bitcoin-development at lists.sourceforge.net
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
Once headers are loaded first there is no reason for sequential loading.
Validation has to be sequantial, but that step can be deferred until the blocks before a point are loaded and continous.
Tamas Blummerhttp://bitsofproof.com
On 07.04.2014, at 21:03, Gregory Maxwell <gmaxwell at gmail.com> wrote:On Mon, Apr 7, 2014 at 12:00 PM, Tamas Blummer <tamas at bitsofproof.com> wrote:
therefore I guess it is more handy to return some bitmap of pruned/full
blocks than ranges.
A bitmap also means high overhead and— if it's used to advertise
non-contiguous blocks— poor locality, since blocks are fetched
sequentially.
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140407/8d2a8562/attachment.html>;
Paul Lyon [ARCHIVE] /
npub1j7…nz4rc
2023-06-07 15:17:42
in reply to nevent1q…40cm
Author Public Key
npub1j7aht4gsujjs429043y5rz6yn75xm32tm42wunpc5kwp7mdxuscsknz4rcPublished at
2023-06-07 15:17:42Event JSON
{
"id": "cc9ee0fe76f3a8282880ac25a2f5b77c8fd241a125956dfc39a222f90854f2bf",
"pubkey": "97bb75d510e4a50aa8afac49418b449fa86dc54bdd54ee4c38a59c1f6da6e431",
"created_at": 1686151062,
"kind": 1,
"tags": [
[
"e",
"376923b22263ee9091876d1ae02202112b3aeaa7a25d30e967b871af6956d76a",
"",
"root"
],
[
"e",
"6f1b970a82a42c35d113fba6157056b9491c0dd22121bf29b25e1eee84fc1de4",
"",
"reply"
],
[
"p",
"aa5cd512f153f77aa335d71793f2cd219569188aedabd7d0239386b17f7728d8"
]
],
"content": "📅 Original date posted:2014-04-07\n📝 Original message:I hope I'm not thread-jacking here, apologies if so, but that's the approach I've taken with the node I'm working on.\nHeaders can be downloaded and stored in any order, it'll make sense of what the winning chain is. Blocks don't need to be downloaded in any particular order and they don't need to be saved to disk, the UTXO is fully self-contained. That way the concern of storing blocks for seeding (or not) is wholly separated from syncing the UTXO. This allows me to do the initial blockchain sync in ~6 hours when I use my SSD. I only need enough disk space to store the UTXO, and then whatever amount of block data the user would want to store for the health of the network.\nThis project is a bitcoin learning exercise for me, so I can only hope I don't have any critical design flaws in there. :)\n\nFrom: tamas at bitsofproof.com\nDate: Mon, 7 Apr 2014 21:20:31 +0200\nTo: gmaxwell at gmail.com\nCC: bitcoin-development at lists.sourceforge.net\nSubject: Re: [Bitcoin-development] Why are we bleeding nodes?\n\n\nOnce headers are loaded first there is no reason for sequential loading. \nValidation has to be sequantial, but that step can be deferred until the blocks before a point are loaded and continous.\nTamas Blummerhttp://bitsofproof.com\n\n\nOn 07.04.2014, at 21:03, Gregory Maxwell \u003cgmaxwell at gmail.com\u003e wrote:On Mon, Apr 7, 2014 at 12:00 PM, Tamas Blummer \u003ctamas at bitsofproof.com\u003e wrote:\ntherefore I guess it is more handy to return some bitmap of pruned/full\nblocks than ranges.\n\nA bitmap also means high overhead and— if it's used to advertise\nnon-contiguous blocks— poor locality, since blocks are fetched\nsequentially.\n\n\n\n------------------------------------------------------------------------------\nPut Bad Developers to Shame\nDominate Development with Jenkins Continuous Integration\nContinuously Automate Build, Test \u0026 Deployment \nStart a new project now. Try Jenkins in the cloud.\nhttp://p.sf.net/sfu/13600_Cloudbees\n_______________________________________________\nBitcoin-development mailing list\nBitcoin-development at lists.sourceforge.net\nhttps://lists.sourceforge.net/lists/listinfo/bitcoin-development \t\t \t \t\t \n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140407/8d2a8562/attachment.html\u003e",
"sig": "d49ea25be5d7c3d7d635e60c6559825fbb2897392fa289ab24c4d709f549bcbe5dd3f05e09d67233765efbc25469b08ad497c1d907cdff2412e624ef2016e63a"
}