41 entries in 0.712s
: however, i might try a hand at keeping all but the most recent blk###.dat files, cutting them up with blkcut
, then feeding them back in with eatblock.
: wrote a perl one liner to cut them all apart with blkcut
... now just gotta feed 'em in.
: using blkcut
? that might be worthwhile
: ( i , like complete idiot, wanted to 'let's write a quick c proggy like blkcut
: ok, now question for ben_vulpes , trinque , mircea_popescu , et al : anybody got a quick c proggy that will eat blkcut
's blocks and produce a linear list of tx ? i'd like to actually calculate the current 32bit tabular collision rate.
: pete_dushenski: block debugger would be like my 'blkcut
', except for ~block~, as output by blkcut
, would display header, transactions, etc.
: at any rate plz don't lose that thing's blockchain, mircea_popescu , can use my 'blkcut
' or ben_vulpes's ver of same, to get at the blox
: but sequential tapes of blox, see the blkcut
: Logged on 2016-06-18 16:15 mod6: i may try to find some time yet this weekend to take a look at this blkcut
thing -- this may be away to roll life saving numbers on your block chain after a power outage in the future.
: i may try to find some time yet this weekend to take a look at this blkcut
thing -- this may be away to roll life saving numbers on your block chain after a power outage in the future. ☟︎
: asciilifeform: hey (i think I've asked this before) but; the blkcut
utility doesn't allow a guy to exacto-knife one block out of a blkindex file does it?
: ascii_field: saw it of course. i wanted to cut out the whole blkcut
-> block -> eatblock roundtrip, plus i want to see how fast it can eat at saturation. which is surprisingly not fast at all
: gernika: blkcut
for the former. but otherwise, yes.
: Logged on 20-07-2015 15:05:16; asciilifeform: somebody found a bug in 'blkcut
' but did not follow up re: replicating
: is this the one where blkcut
error made it fall over?
: somebody found a bug in 'blkcut
' but did not follow up re: replicating ☟︎
: decimation: there is no reason to reimplement bash loop, etc in something like blkcut
: that blkcut
utility is bitchin'
: how small can u make the files with blkcut
: ascii_field: re: blkcut
: 'Here is a 'blkcut
' utility. Cuts or counts.'