📅 Original date posted:2017-04-06
📝 Original message:On Fri, Apr 7, 2017, at 02:32, Gregory Maxwell wrote:
> Perhaps a simple question would help:
>
> What is the minimal amount of space your system requires to take a new
> block received from the P2P network and verifying that all its spends
> were valid spends of existing coins unspent coins today?
>
> For Bitcoin Core the answer is ~2GB (plus the configuration handling
> currently forces you to keep another 550MB of blocks for reorgs).
Bitcrust separates script validation (base load, when transaction come
in) from order validation (peak load, when blocks come in).
For script validation it would obviously need the ~2GB (or I think
~1.5GB) of outputs needed to validate these. For order validation it
needs ~200mb or the spent-index (for bit-lookups) and I would guess
roughly ~500mb of the spent-tree (for scanning), though I don't think
the 5.7GB full spend tree isn't worth pruning anytime soon.
Then it is currently using a ~1.5GB index for transaction hash to
fileptr lookups, though this could be made more space efficient.
Tomas [ARCHIVE] /
npub1rs…9evk4
2023-06-07 17:59:43
in reply to nevent1q…7u9k
Author Public Key
npub1rsp4w56r24w3zv4xy8zfgesep45qmf9rq6aghxfw3wr7yemqnnwsf9evk4Published at
2023-06-07 17:59:43Event JSON
{
"id": "af4efc3a015fd7e187b5f4e56510c6220281b18ce66852efa56bfedf7e820c80",
"pubkey": "1c03575343555d1132a621c49466190d680da4a306ba8b992e8b87e267609cdd",
"created_at": 1686160783,
"kind": 1,
"tags": [
[
"e",
"d4a682be1f6603f0ff8798c52b7225cac6554e21f3aedb0c80e7d41cf71983ad",
"",
"root"
],
[
"e",
"32933114e97d483c0b33310203b786624b9c0ed016883414afcfdd0aa4a7e371",
"",
"reply"
],
[
"p",
"de834b230daa8e6d04c44e51929c52dfdc36dc2f4105a0b67060d9dfc30d6ccc"
]
],
"content": "📅 Original date posted:2017-04-06\n📝 Original message:On Fri, Apr 7, 2017, at 02:32, Gregory Maxwell wrote:\n\n\u003e Perhaps a simple question would help:\n\u003e \n\u003e What is the minimal amount of space your system requires to take a new\n\u003e block received from the P2P network and verifying that all its spends\n\u003e were valid spends of existing coins unspent coins today?\n\u003e \n\u003e For Bitcoin Core the answer is ~2GB (plus the configuration handling\n\u003e currently forces you to keep another 550MB of blocks for reorgs).\n\nBitcrust separates script validation (base load, when transaction come\nin) from order validation (peak load, when blocks come in).\n\nFor script validation it would obviously need the ~2GB (or I think\n~1.5GB) of outputs needed to validate these. For order validation it\nneeds ~200mb or the spent-index (for bit-lookups) and I would guess\nroughly ~500mb of the spent-tree (for scanning), though I don't think\nthe 5.7GB full spend tree isn't worth pruning anytime soon.\n\nThen it is currently using a ~1.5GB index for transaction hash to\nfileptr lookups, though this could be made more space efficient.",
"sig": "61820d5248e70273b87ac3c6f9f3d8f965355ec90dd26a46297c14540027694deb0234809a5376a7b3e531f3cf677cc0217a2b6e9860470b64a876eeb74b2d5c"
}