Forum logs for 01 Jul 2015
decimation
yeah if it's the last file, it's incomplete
[00:00]
asciilifeform
aha
[00:00]
mod6
these were fully sync'd up to ~320`000 blocks or so. they were shutdown after full sync was achieved. each goes upto like blk0017.dat
[00:00]
mod6
fa97f9f51bd130758910563ad7976014736b8b8ec021ed9f5dbc3c4b87d3703a blk0009.dat | 2f7acbd7b5603a845a5d380ffb6ff3be051ab8b192ae143b0916a07564d5cbc5 blk0009.dat | 1631edac873633135b9eb9b8214d6d2b30d708d00ec4dd1db6a9bf09f384551b blk0009.dat
[00:01]
decimation
mine stops at blk0008.dat
[00:01]
mod6
on a fully sync'd node?
[00:01]
mod6
whats the full size of your blockchain? mine's like ... ~38Gb
[00:02]
mod6
82397e804874de4709faa07515f6bedbeaa4b1cdc49846b96742bba925bad1cb blk0010.dat | d2bf09e41b6177d6f44a5b7983954c647ac2c983ac39af2e159261e8737f4662 blk0010.dat | baa5bbcdb388d707398d00de95df8d3c5d98d716842d1eea7ea51f3d4ed40695 blk0010.dat
[00:03]
mod6
seems to diverge for me starting with blk0008.dat
[00:03]
asciilifeform
8d8c80c9677d59856eb3ebb2e9d87ff2bc4cd416f02ae6d4d925e031fffb82e1 blk0001.dat
[00:06]
asciilifeform
ebbeef1641ca8b921652577f4917ad2f7391cb5067b7857819ed4a5fb4a35091 blk0002.dat
[00:06]
asciilifeform
c125ab7cbdf64b9d14c26adcc7638b2e7a62879cdd64a8897bbdb494360162569 blk0003.dat
[00:06]
asciilifeform
^^^ from my box circa 2013 !
[00:06]
mod6
huh. yours dont match ours or mps
[00:07]
asciilifeform
with ecc ram, no less
[00:07]
asciilifeform
and raid5
[00:07]
asciilifeform
(the latter with nightly parity checks!)
[00:07]
decimation
with orphans?
[00:09]
asciilifeform
almost certainly
[00:09]
asciilifeform
(for the same reason as mircea_popescu's)
[00:09]
asciilifeform
they were moved from an earlier disk, where the thing was going from late 2010
[00:10]
asciilifeform
iirc
[00:10]
*
asciilifeform observes that the 'eater' has completed blk0001
[00:14]
asciilifeform
is presently past 189070
[00:15]
asciilifeform
anomaly has not recurred yet
[00:15]
asciilifeform
(but is not expected for a while)
[00:15]
asciilifeform
sha256(blk0001.dat) is equal to the expected value.
[00:16]
asciilifeform
(on the 'eater' node)
[00:16]
mod6
18704088cd8518a05e173648622bdc86e695e6e551a9e669179dd26b4e40aab5 blk0011.dat | 18704088cd8518a05e173648622bdc86e695e6e551a9e669179dd26b4e40aab5 blk0011.dat | c39eeb00ee4489722f82f53667a71584aa571913c6c0116017682ed508e5adcd blk0011.dat
[00:16]
mod6
bdabb513c4ced2b592897757d1a137263f7d709a86040c41772288caea55fb14 blk0012.dat | bdabb513c4ced2b592897757d1a137263f7d709a86040c41772288caea55fb14 blk0012.dat | 7da33b5bc03fcba571b854172938f000a9d5241757f3b186de93da34ddcb889f blk0012.dat
[00:17]
mod6
35069477afe178861ddfe9d686625801e20fcb66b89d87b4a2730925aefd20a0 blk0013.dat | 35069477afe178861ddfe9d686625801e20fcb66b89d87b4a2730925aefd20a0 blk0013.dat | 25def233a2fa1c177169c74789070dc08de127b8447c7ee0784a8735353a42f8 blk0013.dat
[00:18]
asciilifeform
mod6: where are the 3rd items in these triples from ?
[00:18]
asciilifeform
anything peculiar about that node ?
[00:18]
mod6
0a7c6b1127af5f47afe3138eb206c736d8452256826d0c3e030c5cd8c289b6e6 blk0014.dat | fc6f19747098be62ccadffda61c7c302d57748e05d2de95f5ee226ac250c71e5 blk0014.dat | fc6f19747098be62ccadffda61c7c302d57748e05d2de95f5ee226ac250c71e5 blk0014.dat
[00:19]
mod6
so one of them seems to be more screwed up than the others. but there were blocks like blk0009.dat & 10 where all were different.
[00:20]
mod6
one was done in january, one in february, and one in march.
[00:20]
mod6
january was pre SSL 1.0.1g
[00:20]
asciilifeform
this is probably when i say that it will be necessary to walk the blocks.
[00:21]
asciilifeform
and compare individual ones
[00:21]
assbot
[MPEX] [S.MPOE] 11300 @ 0.00046595 = 5.2652 BTC [+]
[00:23]
mod6
yeah, totally agree.
[00:25]
mod6
im suprised they diverged that much.
[00:26]
mod6
i would have though with all the same version (pretty much) that they would have all been the same hashes.
[00:26]
asciilifeform
~recent~ syncs diverging is almost certainly a product of enemy fire
[00:26]
mod6
glad I looked at that
[00:26]
assbot
[MPEX] [S.MPOE] 64550 @ 0.00048971 = 31.6108 BTC [+] {3}
[00:27]
decimation
yeah, gotta take it block by block
[00:27]
decimation
the question is, how do we make a portable tool to suck blocks from bitcoin nodes?
[00:30]
decimation
something that parses .dat files?
[00:30]
asciilifeform
decimation: one way is what i'm doing
[00:30]
asciilifeform
but it's a bit slow
[00:30]
decimation
yes true
[00:30]
asciilifeform
there is a python thing floating around, iirc
[00:30]
asciilifeform
can try that.
[00:30]
asciilifeform
alternatively, write own (format is pretty simple)
[00:30]
mod6
yah, there's asciilifeform's way, and there's that python thing
[00:30]
asciilifeform
alternatively wait for me, but i'm up to my ears in backlog of work
[00:31]
asciilifeform
where the hell is mircea_popescu
[00:33]
asciilifeform
at this rate, he's gonna miss ragnarok.
[00:33]
asciilifeform
(then again, this ragnarok will still be there tomorrow..)
[00:34]
phf
fwiw dumpblock is expensive, because walks blockchain in order. a "dumpdb" that iterates over mapBlockIndex and does ReadFromDisk/js in 5-10 months, so everything i know is probably stale
[03:23]
ben_vulpes
funkenstein_: "hammered"?
[03:24]
trinque
ben_vulpes: yeah you can use reagent in this manner
[03:24]
funkenstein_
like, ddosed
[03:24]
trinque
wanted to know if the native thing would eat clojurescript, in case I end up having to use it
[03:24]
BingoBoingo
like, ddosed While I was away from the computer when Rassah finally stopped derping about "escrowless" escrow and his 1,000 BTC Prius and got down to business, here's what transpired when he did. bootstrap.dat
[20:09]
jurov
when later i got my hands on perma connection, UO's star faded or whatever
[20:10]
*
assbot removes voice from ValentinJesse
[20:13]
*
Phraust (~Phraust@unaffiliated/phraust) has joined #bitcoin-assets
[20:14]
asciilifeform
http://log.bitcoin-assets.com/?date=01-07-2015#1183832
Sunday, 24 November, Year 11 d.Tr.