asciilifeform: (and this is probably not measurably slower, in practice, than what mircea_popescu did)
asciilifeform: i suppose one way to rebuild the index using existing mainline trb would be to nuke the .bitcoin dir entirely, and refeed the node via 'eatblock'.
asciilifeform: (unless you're willing to live with random bitflippage, as jurov apparently is)
asciilifeform: so it isn't simply a matter of 'make a ramdisk', no.
asciilifeform: that's what's in mircea_popescu's patch presumably.
asciilifeform: trb does not have a knob for 'reindex and make sure blkxxxx matches the index'.
asciilifeform: mircea_popescu: what did you do with the index if power failed (or node -- crashed) or whatever disruption ?
asciilifeform: mircea_popescu: as per yesterday's thread -- running node per se is 'expensive and unrewarding activity' aha!
asciilifeform: mircea_popescu: plz consider publishing your patch where you made this happen; it is not a trivial change
asciilifeform: jurov: the most sane variant of your proposal i can think of would be to run the entire tx index in memory. this is just barely practical on dulap, a massive box. and would mean multi-hour regeneration of the index on warmup. but is at least theoretically an improvement, in that it does not threaten to randomly lose bits.
asciilifeform: copying 400GB takes 'few minutes' on jurov's disk ? where can i buy one ?
asciilifeform: ( does jurov volunteer to buy the double, triple, quadruple sets of disk, for all of my nodes, for these backups ? and what is the node to do while copying over a db ? say 'sorry , we're closed ' ? )
asciilifeform: nonsense like 'let's flush write cache once in a blue moon instead of normally', 'let's let the db corrupt and SURE I PROMISE WE CAN RECOVER' is what winblowz world is built from.
asciilifeform: the thread today where mircea_popescu sees something with even the superficial silhouette of a cheap prbistic hack, and barf mightily, taught you nothing, jurov ?
asciilifeform: if mining were not an intrinsically heathen activity, 'closed network' would solve the 'allcomers' problem. but as i currently understand, it'd simply ~move~ it.
asciilifeform: leading to very similar picture as today's.
asciilifeform: let's picture that whole deedbot l1 subscribes. the folx who run public/exposed node, so as to soak up blocks from heathen miners -- will be the ones to blackhole.
asciilifeform: very concretely: all enemy has to do, to gum up a trb node, is to repeatedly request blocks from 0 .. current, randomly, and switch ips as needed
asciilifeform: bitcoin as we have it, is almost the antithesis of 'tape problem', the ultimate in random access, to the point that it makes disk cache ~useless, every tx can depend on literally any block from 0 to current
asciilifeform: how do you randomaccessfully fetch blocks from tape ?
asciilifeform: something that bitcoin has very little use for
asciilifeform: general-purpose fs is likely to be extremely wasteful of space, because it carries the assumption of rewritability
asciilifeform: symlink gets you a file containing desired block, but there is no way on any unix fs that i know of, to symlink to ~an offset inside a file~
