[spam][personal][crazy] Trying to Build Bitcoin from Source

[Karl]

1850 it was such a small issue in the end.  [inhibited: i didn't think
i'd be able to do it.]

the next step is to see if i can sync the whole chain, which is rare
for me.  they've really made the syncing phase lighter weight, i
think, nowadays, unsure.

i'd also like to get the bitcoin-sv chain.  not sure how big it is.

1851 my raid claims it has 276G free.  not that much.  3.3T are used.

1852 i'm looking for information on the bitcoin blockchain size using
google.  my network might be saturated by downloading the
blockheaders; the result i clicked is not loading.

1853 the loaded-without-images result said the blockchain was about
360G large.  so i'm either going to be deleting files or pruning it.

i really want to scrub the whole chain for content, but i'm more
likely to lose it to corruption or something before i do that, so
pruning makes sense.

it also sounds like i should be using a further harddrive, and i still
have an enclosure indoors.

1855 i'm using zstd to compress some files to save space.  from the
cornucopia of facebook, inc.

1858 is there some magical thing that gives you infinite diskspace?
there's some new tool that i vaguely recall might do something like
this.  it might not work for a blockchain.

1901 rclone!  rclone can mount with fuse and has a variety of storage
backends.  i dunno if it would work, maybe it would at least work for
archiving other stuff.

1904 anyway my blockchain is now updating tips so i have the space
issue developing.  i guess i'll stop it and configure it to prune.

1908 i had actually deleted the binary to rebuild in release mode, so
stopping the node prevents restart until the rebuild finishes.  oops.

1920 blockchain is syncing with -prune=$((1024*16)) i.e. 16 gigabytes
of blocks are kept.  and i have 3 huge files compressing with zstd,
using --ultra --long -22 so it is very slow.

with this compression i may have space for bitcoin-sv.  i also have a
blockchain folder named bitcoin-sv.  it's only 2.5G large ... but uses
another symlink .. which is also broken.

i guess i'll try to build bitcoinsv too, maybe it has a pruned mode.  1922

1929 bitcoin sv build has started.  bitcoin is at 2010-11-30.  maybe
there's some way to checkpoint for last-mile folks, dunno, haven't
looked into it.

system's pretty taxed now.

1930 a hard thing that's remaining is software to archive files on
bitcoinsv.  as mentioned long ago i've slightly worked on some messy
software for this.  it relied on apis that have since changed, so
development work is needed.  the current state is messy and i don't
recall my plans for it.  great topic for these spamlogs, since it's
very hard to move forward on.

might be time for another task tonight, like sleeping, unsure.  1931