log☇︎
194500+ entries in 0.044s
asciilifeform: http://btc.yt/lxr/satoshi/source/src/main.cpp#0643 << and.
asciilifeform: http://btc.yt/lxr/satoshi/source/src/main.h#0932 << required reading
asciilifeform: (well, certainly not after longest-chain is established)
asciilifeform: they have nothing to do with bdb and should not vary at all (once they reach full size, ~2GB) between nodes
asciilifeform: this is an important point
asciilifeform: http://log.bitcoin-assets.com/?date=30-06-2015#1182036 << see thread ☝︎
asciilifeform: mircea_popescu made same mistake earlier
asciilifeform: which are derived from blocks
asciilifeform: bdb only stores indices
asciilifeform: they're raw blocks
asciilifeform: these aren't bdb though!
asciilifeform: aha
asciilifeform: blk0002 - a certain number, certainly smaller, after that
asciilifeform: ^ in blk0001
asciilifeform: http://log.bitcoin-assets.com/?date=01-07-2015#1182166 ☝︎
asciilifeform: the 'magic moment,' whatever its nature, happened well into blk0002
asciilifeform: but the blocks are starting to get fatter there
asciilifeform: thing is just about past 177000 now
asciilifeform: if i replicate the anomaly, i will post the 'interesting' region
asciilifeform: it should not be difficult to find out, right now, if you have the same blockchain
asciilifeform: the sha512 checksums were posted earlier
asciilifeform: the dataset in question - blocks pulled from mircea_popescu's node on the night of june 28-29 - is ~5.5GB
asciilifeform: will, once i find a place to drop these where i'm not paying per byte
asciilifeform: of course
asciilifeform: BingoBoingo: http://farm2.static.flickr.com/1307/4681642407_3537daf466_b.jpg
asciilifeform: phf: why these were absent from the original bitcoin is still an enigma to me
asciilifeform is trying and failing to think of a benign explanation for the anomaly
asciilifeform: in the 'longest chain' sense
asciilifeform: (recall, in a 'bastard-free' bitcoind - which is what i have - no block can be 'eaten' unless it squarely agrees with its immediate antecedent block)
asciilifeform: i set it up earlier today and mostly forgot about it
asciilifeform: it did not even occur to me that the 'eater' might barf
asciilifeform: original purpose of this experiment was to gather 'pmap -XX <pid>' stats for plotting
asciilifeform: *circa
asciilifeform: but devil only knows
asciilifeform: one might naively imagine that obvious bugs cirta '12 will not turn up today
asciilifeform: phf: it is difficult to rule anything out at this point
asciilifeform: (checksum spoken of earlier agrees with every copy of blk0001 i've been able to locate, other than the one cited by mircea_popescu)
asciilifeform: the only thing i'm pretty sure of at this point is that nothing peculiar happened - at least on this machine - through block 188529.
asciilifeform: http://log.bitcoin-assets.com/?date=30-06-2015#1181921 << the experiment in question, for anyone who missed ☝︎
asciilifeform: (technically, one ~could~ retrofit it, with some glue logic)
asciilifeform: z80 never supported ecc
asciilifeform: and this is just about my copy, not even starting with mircea_popescu's
asciilifeform: ~3 hours from now, will know...
asciilifeform: 'is it my instruments? lsd in the water?'
asciilifeform has the same ill feeling an astronomer might have were 'seti' signal to appear
asciilifeform: mircea_popescu ^^^^
asciilifeform has not verified the latter
asciilifeform: claims 188529 blocks ☟︎
asciilifeform: ^ he got 7aac5826b91b4f87a2e9534e0e38e8d64ed21aff8a4eb8ff8dde4e726e67fe1a as well
asciilifeform: https://bitcointa.lk/threads/reduced-final-state-blk0001-dat-with-pruned-index.59545
asciilifeform: if anyone can remember what blocks fit in there, please post
asciilifeform: (same as for all my synced 0.5.3's)
asciilifeform: sha256(blk0001.dat) for this run: 7aac5826b91b4f87a2e9534e0e38e8d64ed21aff8a4eb8ff8dde4e726e67fe1a
asciilifeform: it'll be hilarious if we're hitting the limits of non-ecc ram or the like
asciilifeform: on the output of the present 'eat'
asciilifeform: will run those again also
asciilifeform: thing was running on a portable, in a knapsack, in a car...
asciilifeform: the best-case scenario is that this is a 'cosmic ray'
asciilifeform: presently running the entire experiment again, to verify
asciilifeform: re: http://log.bitcoin-assets.com/?date=30-06-2015#1182007 ☝︎
asciilifeform: some time near after 208000, a block is rejected!
asciilifeform: so it turns out that i spoke too soon:
asciilifeform: !up ascii_field
asciilifeform: !up ascii_field
asciilifeform: '...anyone who knows mathematics can see that the United States is on the verge of collapse because its debt has gone exponential. These aren't words that an American or a European politician can utter in public, and perhaps not even whisper to their significant other while lying in bed, because the American eavesdroppers might overhear them, and then the politician in question would get the Dominique Strauss-Kahn treatment...' ☟︎
asciilifeform: http://cluborlov.blogspot.com/2015/06/the-care-and-feeding-of-financial-black.html << pretty fine orl0l re: greece
asciilifeform: hard to picture a sorrier bunch of bitter schmucks, eagerly taking it up the arse from history's biggest and most obscene communist mega-empire (usg) to spite their little piss-ant one ☟︎
asciilifeform: (by some versions, these are the people who gave us... bush II)
asciilifeform: i'm not certain that there ever was a ~less~ sympathetic bunch of dekulakized folks than the cuban 'refugees' in usa
asciilifeform: http://log.bitcoin-assets.com/?date=30-06-2015#1181553 << yes, there will be plenty of 'work' to be had there, re-converting the island back into a u.s. bordello as it was in batista's time; 'privatizing' and demolishing the spiffiest pharama plants in the western hemisphere; shipping the best doctors to drive cabs in nyc; etc ☝︎☟︎
asciilifeform: mats: some of the more interesting aspects are, as always, corner cases. e.g., how does x86-64 treat self-modifying code? how does this impact cache? can unpriv. ('ring 3') code learn cache state? (to some extent - always!) etc.
asciilifeform: there are at least two sub-fields here - how the machine is put together; and, what idioms are common (i.e. what does a particular compiler crap out and why?)
asciilifeform: and experiment
asciilifeform: mats: the only cure is to not only read but write
asciilifeform: (mentioned earlier today)
asciilifeform: anyone for whom this question is a routine matter really ought to own the book
asciilifeform: (you ~can~, e.g., 'jmp rax')
asciilifeform: or rather, has no such with immediate value
asciilifeform: note that 'long' (64) mode has no absolute far jump
asciilifeform: http://x86.renejeschke.de/html/file_module_x86_id_147.html << 32-bit
asciilifeform: otherwise a decent compiler does multiple passes
asciilifeform: mats: if within bounds for relative jump, uses that
asciilifeform: mats: interesting! did not know this.
asciilifeform: (or do they)
asciilifeform: if they ever feel like having an actual economy (or simply switching 'sugar daddies') they know who to call
asciilifeform: (the one and only purpose it serves)
asciilifeform: decimation: yes, can go into infinite debt; while usg uses the island for bomb practice
asciilifeform: (e.g., the 'uncle fed to dogs' has since been seen, the gurlphriend beheaded for starring in pr0n has been appearing in public, the footballists 'shot for losing' are playing today...)
asciilifeform: to be fair, pretty much everything we know about him comes from south kr (read: usg) mediatrons
asciilifeform: if kim jong un had balls, perhaps he'd buy it. ☟︎
asciilifeform: http://www.nbc-2.com/story/29430125/governor-puerto-rico-near-death-spiral
asciilifeform: no one ever really built a halfway decent compiler for 'vliw' machines (like itanic)
asciilifeform: this is not an accident; amd hired away most of the old dec team who built alpha
asciilifeform: it is ~almost~ like a rationally-designed (e.g., 'alpha') cpu
asciilifeform: speaking of 64-bit ('long') mode here
asciilifeform: (mostly)
asciilifeform: ~segmentation~, that grim old idiocy from the 16-bit 8086 days, gets disabled
asciilifeform: where each process thinks it owns the machine
asciilifeform: how else could you do the whole mmu thing
asciilifeform: of course it did