pull down to refresh

100 sats \ 10 replies \ @SimpleStacker 13h \ parent \ on: Why I'm Against Covenants (Jimmy Song) bitcoin
UTXO set bloat is one of them. IBD on same hardware went from 3 days to 1 month for me. There is some discussion here that I was a part of: https://github.com/raspibolt/raspibolt/issues/1482#issuecomment-3263903647, to show that it's being experienced by multiple people.
One could say, get better hardware, but I thought one principle was trying to keep the cost of node running down.
write
preview
30 sats \ 6 replies \ @optimism 13h
what are you writing the block data to?
reply
100 sats \ 5 replies \ @SimpleStacker 12h
https://www.amazon.com/dp/B0874Y5XFG
reply
90 sats \ 4 replies \ @optimism 12h
That's odd. I have plenty of these, so the disk is not an issue. I used it on an older Rockchip board (comparable to Pi4 except it has sha256/crypto extension) and it took 4 days back in April. I'll try to source me a Pi4 next week - worth looking into.
reply
100 sats \ 3 replies \ @SimpleStacker 12h
Thanks. The github discussion I linked above (copied again for convenience) shows that multiple users are experiencing this. My hypothesis was that the UTXO got too large to hold in RAM and so it is using HD, but I could easily be wrong.
https://github.com/raspibolt/raspibolt/issues/1482#issuecomment-3263903647
reply
0 sats \ 2 replies \ @optimism 10h
Saw your comment on there previously. I haven't tried raspibolt personally and there is some ongoing work w/ core towards this - I must admit I used 27.x, and there are reports of a regression with 29.x: see https://github.com/bitcoin/bitcoin/pull/32043 and https://github.com/bitcoin/bitcoin/issues/32832
Shall I get a 4GB RPi4?
reply
100 sats \ 1 reply \ @SimpleStacker 10h
Interesting about the regression. That's up to you! I currently don't have any new insights, and my node is finally fully synced.
reply
0 sats \ 0 replies \ @optimism 10h
Never mind, I didn't read well and you have an 8GB - I'll try to get that.
Edit: will get it next week.
reply
0 sats \ 2 replies \ @ek 13h
Okay, fair, I forgot about this!
reply
100 sats \ 1 reply \ @SimpleStacker 13h
I think it's easy to forget because it's not a big problem if you're already running a node that's been up for a long time, since you only need to validate once every 10 minutes or so. I only realized it when I decided to rebuild my node from scratch.
reply
100 sats \ 0 replies \ @lightcoin 13h
it is worth noting that this same "problem" would also occur if bitcoin had a large number of UTXOs for other reasons (like lots of users taking self-custody)
it's a problem that would need to be solved (and is being solved by solutions like zerosync and utreexo) regardless of the use-case that caused it.
reply