nah, i don't think you deduplicate their block storage, just think of it as a backup, that's the thing
btcd has a really awful database that is extremely slow, you think it's slow with bitcoind, almost 4x or more slower
you can have one as a primary, and a second one that is just a block-only and index one and use the "connect" (iirc, meaning connect only to this peer) and it will only listen for new blocks and when they arrive, update the indexes for you... the same data directory can do the same work simply by disabling that connect peer option
in fact, if you are only running it for service to other servers you don't need it to do any transaction caching at all, make it a "blocksonly" node and also there is a setting to contain how much bandwidth that uses too, i forget what it is now, but during times of ordinal spam full bitcoin nodes can use a lot of bandwidth relaying transactions, disabling them is one thing, but also limit the amount of data it uploads to other peers for their IBDs
there's a lot of neat things you can do to make a bitcoin node operate differently... the indexes aren't that big, btw, maybe around 120gb at this point for tx and address but if you are pinching for space you can keep a block only replica, i don't recommend it though, rebuilding the indexes is like 2/3rds of the IBD process
mleku / mleku™️
npub1fj…mleku
2024-09-15 19:24:44
in reply to nevent1q…d24x
Author Public Key
npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmlekuPublished at
2024-09-15 19:24:44Event JSON
{
"id": "a07df7cb743813b98256ffd28ba6bd43621979d577459f5de4cb681fe487d25c",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1726428284,
"kind": 1,
"tags": [
[
"p",
"036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
"wss://relay.nostr.band/",
"ChipTuner"
],
[
"e",
"22d0f1ae4a8b552e1c9ab9a10cfaacd535731ecc9f70025bd2cc85fda5fc85ad",
"wss://relay.nostr.band/",
"root"
],
[
"e",
"9a4e152795707790a7c205513d5ed886eb5e1896417bfe01321a8509ec80437c",
"",
"mention"
],
[
"e",
"fa2f7d2e1862d220df58e4cfcbd49fc24956dd7f1333ad9818fd0dfc5c6746ce",
"wss://relay.nostr.band/",
"reply",
"036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58"
]
],
"content": "nah, i don't think you deduplicate their block storage, just think of it as a backup, that's the thing\n\nbtcd has a really awful database that is extremely slow, you think it's slow with bitcoind, almost 4x or more slower\n\nyou can have one as a primary, and a second one that is just a block-only and index one and use the \"connect\" (iirc, meaning connect only to this peer) and it will only listen for new blocks and when they arrive, update the indexes for you... the same data directory can do the same work simply by disabling that connect peer option\n\nin fact, if you are only running it for service to other servers you don't need it to do any transaction caching at all, make it a \"blocksonly\" node and also there is a setting to contain how much bandwidth that uses too, i forget what it is now, but during times of ordinal spam full bitcoin nodes can use a lot of bandwidth relaying transactions, disabling them is one thing, but also limit the amount of data it uploads to other peers for their IBDs\n\nthere's a lot of neat things you can do to make a bitcoin node operate differently... the indexes aren't that big, btw, maybe around 120gb at this point for tx and address but if you are pinching for space you can keep a block only replica, i don't recommend it though, rebuilding the indexes is like 2/3rds of the IBD process",
"sig": "5a462d33ffcefcba16ff78fdc862614120c263c9e8b2b55c1be8e80bbc1388bcea59a7efd3e0d7320ce0824a2f890796049a2c91fe9768ad227ce3d59759098b"
}