asciilifeform: decimation: one very obvious way for it to fuck, and be noticed, is to simply fail
asciilifeform: mircea_popescu et al were contemplating a surrender to ntp even.
asciilifeform: http://log.bitcoin-assets.com/?date=08-07-2015#1193951 << it's why they produce incompatible ones regularly. because no way to know if it happened or not yet, save for passage of time
asciilifeform: but not only it, but a complete recipe whereby i can regenerate it.
asciilifeform: and see example of CreateNewBlock
ascii_field: thestringpuller: i'm not even certain that the 'ocean of complaint' consists of real people
ascii_field: now if the node is 'live' and has net connection, hears tx, suffers possible fragging (see old threads) - then even more consumption.
ascii_field: (this was a node, i must remind the reader, with no mempool, on account of having no net connection and being fed blocks 'intravenously' if you will)
ascii_field: everything i did only ~increases~ bandwidth consumption
ascii_field: don't even need a computer.
ascii_field: and now compound the problem by supposing that it is not you and your best friend, but you and a network consisting, to an unknown degree, of devils
ascii_field: trinque: bad example. norton was popular.
ascii_field: what makes the exam champ the waste of oxygen that he is ?
ascii_field: i.e. 'champion at exams' vs the other kind.
ascii_field: 'If you want to end ISIS, teach it game theory and casebooks. "They['ll] get out their linear programming charts, statistical decision theories, minimax solutions, and compute the price-cost probabilities of their transactions and investments, just like we do," and lose.' (from the al schwartz link earlier)
ascii_field: in the case of the latter, it is necessary to have a ~complete~ picture of the vital organs
ascii_field: ('how it ends,' for the uninitiated, is that some time around when these fine folks are about half done, the chip will go out of print. and be replaced by an entirely incompatible one.)
ascii_field: try synthesizing ~anything~ of any serious complexity without exact timing data for ~every piece of shit on the die~
ascii_field: mircea_popescu: no, it isn't 'greatest leak ever' - but certainly the most complete gutting of a usg contractor in history
ascii_field: very short and simple to grasp
asciilifeform: but it will continue to suck in all sorts of other financial garbage and use it to spew forth Euros without comment, keeping other European countries on financial life support simply because they aren't Greece.'
asciilifeform: decimation: re: 'round trip' ntp - you still are at the mercy of local clock's accuracy when computing the trip time
asciilifeform: it'll be generations after a sane computer exists that this kind of thinking even gets a chance of drawing to a close.
asciilifeform: 'computer', to an experienced commander, means 'twerp will cast a spell and enemy will walk clean across, shredding you'
asciilifeform: the reason, afaik, why 'defuse with key' did not catch on is a ~well-founded~ distrust of computer
asciilifeform: comparing a subset of your field of vision with the rest does nothing against the latter.
asciilifeform: let me guess, by comparing the behaviour of one node with others
asciilifeform: 1) spray orange paint on 'thompson' 2) pull out in front of police 3) ??? 4) profit!!!111!
asciilifeform: 'Mr. Schumer said a federal law requires toy or imitation guns to feature a highly visible orange mark at the end of the barrel to identify them as harmless. Since the phone case does not have the marker, he said, he would work with customs officials to block its import and sale.' << l0l! srsly?
asciilifeform: the realization comes from the fact that you don't really need accurate time, just an oscillator that is reasonably independence of amplitude
ascii_field: (and before anyone chimes in with 'of course vs' - this is empirically false. can build arbitrarily complicated crapware for winblows with gcc)
ascii_field: the graph flabkebab_ showed does not even attempt to place symbols ~anywhere near~ even one of their links !!
ascii_field: https://romanegloo.files.wordpress.com/2012/03/callgraph_mmap_region.png << another example
ascii_field: http://iphome.hhi.de/suehring/tml/doc/lenc/html/image_8h_b1e3d8088c78040d3bf44c9ea3293ed7_cgraph.png << example of a ~readable~ callgraph
ascii_field: http://www.plugcomputer.org/405/us/plug-basic/documentation/Plug-PowerPlug-V1.3.pdf << another version
ascii_field: http://www.plugcomputer.org/405/us/plug-basic/documentation/Plug-6.0.1-Schematic.pdf << it
ascii_field: or nm, not complete
ascii_field: complete schematics and pedantically agonizing docs
ascii_field: http://www.plugcomputer.org/405/us/plug-basic/documentation/Plug-DevKit-Reference-Design-Rev1.1.pdf << incidentally, this is the reference design on which 'pogo' is based
ascii_field: not all isp will even let through icmp, no ?
ascii_field: ^ example
ascii_field: hell, folks in here were ringing the alarm on account of empty blocks
ascii_field: the basic, irrecoverable problem with ntp is that one can 'amplify'
ascii_field: but yes, if using block timestamps, pogos can only be mislead, cannot mislead others (unless some fool were to mine via 'getwork'-ing a pogo!)
ascii_field: and if it did, hitler could simply delay the packet
ascii_field: lamport's achievement was to abstract out some of the attributes of timekeeping we actually ~need~
ascii_field: punkman: we were contemplating a hypothetical clockless blockchain
ascii_field: when you ~actually~ (vs. academitard-pretend) nail something down - that is a reduction in complexity.
ascii_field: what we have now - ~that~ is complexity. just unexamined kind.
ascii_field: not complexity !
ascii_field: no need for sample
ascii_field: mircea_popescu: the speed of the sound of the drum is negligible in comparison to the speed at which push wave propagates through a crowd
ascii_field: next block is from hitler. it has timestamp of... yesterday.
ascii_field: how did the disk become not empty ?
ascii_field: all it sees is 'block was broadcast, has timestamp t, average it now'
ascii_field: fine, example. malicious miner starts crapping out blocks with timestamp more and more off in the future
ascii_field: i am not sure how this improves on anything
asciilifeform: what is the shortest known implementation ?
asciilifeform: jurov: classic chumpatron. exists on this side of the atlantic, too
asciilifeform: i am concerned with 'pogos will fall like dominoes from simple and cheap nudge' rather than 'in the dark future where being a known bitcoin user merits gassing'
asciilifeform: thestringpuller: machine with no keyboard, or display, or presumption of literate owner
asciilifeform: for folks who are seriously working on the problem: i presently suspect that the solution will resemble some mix of 'lamport clock' and 'the firing squad problem'
asciilifeform: incidentally, there is even an empty landing pad inside for rtc
asciilifeform: where such 'champions' exist
asciilifeform: punkman: this works only if you are the world champion by an unreasonable margin
asciilifeform: 'gets its time from the most recent block it accepts' is a logical impossibility given the current algo for 'accept'
asciilifeform: lamport (same as of the 'generals') clock.
asciilifeform: anyone else have examples of 'maths an exploiter must know' ?
asciilifeform: other pertinent maths include the proof of why 'homomorphic obfuscator' is impossible in the general case
asciilifeform: basic discretes is more important
asciilifeform: decimation: for a successful example of this, see 'kademlia'
asciilifeform: astonishingly useless no matter how implemented
asciilifeform: linked mainly on account of this http://russos.ru/img/trip/2009-kolskiy/b440-22.jpg mechanical computer.
asciilifeform: thestringpuller: or the survivors simply sign, on parchment, with their privkeys, ..., etc
asciilifeform: unrelated: folks competing for mircea_popescu's 1 btc prize for therealbitcoin callgraph can strike 'egypt' utility off the list. it is a worthless pile of shit, which produces worthless piles of shit (at least for cpp proggy)
ascii_field: i would like to compare it with mine.
ascii_field: ;;later tell mircea_popescu please consider posting your blkxxxx which encompass the two most recent forks
ascii_field: i suppose all the 'proper confucians' with millenium-long time cocks are employed as colonels in pla or whatnot
ascii_field: the reward could still follow the same asymptotic
ascii_field: mircea_popescu: why so certain that impossible ?
ascii_field: based on component cost
ascii_field: part of block validation is 'is the timestamp <2h from now'
ascii_field: they could still attempt to filter, but it would have to be an open declaration of war. something the gavinists are rather averse to
ascii_field: so i'm nearly certain that the timestamp ~2h epoch time window is the reason for wedged 0.5.x nodes, at this point
ascii_field: ^ re: block timestamping
ascii_field: the buildroot gives you the complete toolchain you need, independently from that of the box you're on
ascii_field: http://log.bitcoin-assets.com/?date=06-07-2015#1189379 << not sure if it's solely disk, or also net, as of this moment. and simply getting 2nd box may be more cost-effective.
ascii_field: http://log.bitcoin-assets.com/?date=06-07-2015#1189407 << probably should've been more specific - why does it matter if timestamp is 'too far in future' ?
asciilifeform: wtf does that thing even care about timestamps
asciilifeform: and also, as before, ERROR: CheckBlock() : block timestamp too far in the future ERROR: ProcessBlock() : CheckBlock FAILED
asciilifeform: just like an f-35 engine compressor made from monocrystalline shitanium with unobtainium alloy blades is far more lucrative than an ordinary steel one
asciilifeform: whether the compiler, the os, or satan is to blame - is secondary
asciilifeform: nor are the 'desert horde' exempt from the radiation damage of welfarism. ferfuxxsake they're getting free tanks by the column !
asciilifeform: (oop systems which aren't clos (or possibly smalltalk's, and generally meta-object-able) are like btc securities exchanges which aren't mpex.)
asciilifeform: the fella we keep bringing up, who directed his followers to use caesar's cipher, was actually being the very example of intellectual consistency here.
asciilifeform: (comparable on modulus)
asciilifeform: sure. just keep in mind the amperage of the dc power brick
asciilifeform: ERROR: CheckBlock() : block timestamp too far in the future
asciilifeform: "errors" : "Warning: Please check that your computer's date and time are correct. If your clock is wrong Bitcoin will not work properly."
asciilifeform: so yes, both of my 0.5.x nodes are still firmly wedged. no sign of attempted 'reorg', nothing.
asciilifeform: http://log.bitcoin-assets.com/?date=05-07-2015#1188105 << i've always said to phriends who played 'grind mmporgs' : 'there is a uranium mine somewhere missing a man. you are that man'
asciilifeform: ;;later tell danielpbarron wouldja mind dumpblock-ing a few blx at the wedgepoint ? ty
asciilifeform: mempool garbage by the megatonne, just like my earlier node
ascii_modem: but std compliant gcc
ascii_modem: compared to c++
ascii_modem: but farming is tempting, yes
ascii_modem: also touches on the mempool thread
ascii_modem: this incident makes it very tempting to just unzip, piss on satoshid, and go ada sanityfork (tm)
ascii_modem: the enemy accomplished his objective, which probably had something to do with discrediting chinese mines
asciilifeform: (not a connectivity problem - i'm getting mempoolisms just fine)
asciilifeform: as temporary workaround, replace the realpath thing (whole right side of equal sign) with the absolute path of 'ourlibs'
asciilifeform: decimation: bozos are stuffing'em full of garbage tx, in an attempt to prop up gavinism
asciilifeform: at any rate, various folks have mined empties before. afaik, it is not publicly known precisely why.
asciilifeform: this may well be one of those things that can be made 'as simple as possible but not simpler'
asciilifeform: if you want 'dumpblock' and 'eatblock', those are not included in stator
asciilifeform: http://log.bitcoin-assets.com/?date=03-07-2015#1186009 << a modern (vs. the infrared diode + mirror mat '80s kind) optic mouse is a pretty hefty computer by itself. complete with bugs
asciilifeform: they'd just all happen to be employees of the house.
ascii_field: (author explicitly subscribes to the 'short, readable, and compatible' thing)
ascii_field: ~reference client~ MUST have some example of working miner.
ascii_field: ^ uses gmp
ascii_field: pete_dushenski: as a pathological example: just about anybody's living costs could be lowered by moving to africa, but for some reason very few takers
ascii_field: this is amply described in the literature
ascii_field: well, more complicated
ascii_field: pete_dushenski: not sure this will show any symptoms of happening any time prior to the die-off
ascii_field: in other nyooz, apparently 'reddit' has imploded and replaced with a very similar service, 'voat.co'
ascii_field: afaik nobody predicted that ~dysfunctional~ computing would be the mechanism
ascii_field: now, plenty of folks predicted 'computer tyranny' - e.g, weizenbaum (of 'eliza' !) in his '70s 'computer power and human reason' - but,
asciilifeform: decimation: iirc, in mexico it is not unlawful to escape from a prison. (in the sense that such a prisoner will not have an additional sentence imposed if caught alive.) but, similarly to usa, it is permissible for police to shoot escapees if they feel like it.
asciilifeform: decimation: not comparable
asciilifeform: (see, for example, the 'millionaire protocol')
asciilifeform: now, it is not physically impossible to solve this problem
asciilifeform: for the specific purpose of running mpex
asciilifeform: more or less a throwback to very impoverished 1970s lisps
asciilifeform: the difference is important
asciilifeform: http://log.bitcoin-assets.com/?date=02-07-2015#1184666 << as i understand, this is an example of 'smv' (sexual market value) as described by mocsny and kokkarinen at work. it takes the form of 'man: what can i afford' 'woman: with your bid, you can afford to be my driver and pay two-thirds of my rent. in return, you get every 47th fuck, if good behaviour.'
asciilifeform: http://log.bitcoin-assets.com/?date=02-07-2015#1184659 << in a very important sense, those folks are the ~strongest~ believers in usg as a concept
asciilifeform: and not of computers (which, last i saw, did not program themselves) - but of ~people~
asciilifeform: http://log.bitcoin-assets.com/?date=02-07-2015#1184748 << in order to formulate ~rational~ distrust, you need literacy. which is not and cannot be a mass phenomenon. hence the choice, for the lumpens, is between mystical trust and mystical distrust
asciilifeform: (not that it is impossible, but there is nothing to recommend it vs any other hypothesis)
ascii_field: 'Be aware that, "out of the box", the wrapper only supports C applications, not C++. This is because the C++ libraries and headers are missing from the musl include/library path. The existing libstdc++ is actually compatible with musl in most cases and could be used by copying it into the musl library path, but the C++ header files are usually not compatible. One option may be rebuilding just libstdc++ against musl;
ascii_field: conditions in the original NPTL design. As for efficiency, the whole threads implementation weighs in at around 10-20k depending on target architecture and compiler settings.'
ascii_field: 'musl's efficiency is unparalleled in Linux libc implementations. Designed from the ground up for static linking, musl carefully avoids pulling in large amounts of code or data that the application will not use. ... musl features the first post-NPTL implementation of POSIX threads for Linux, and the first aimed at complete conformance and robustness. Thread cancellation has been re-designed to avoid serious race
ascii_field: 'Finally, I suppose one might wonder why something that seems so broken, as I've described fixincludes, might go undetected for so long. The explanation is simple: distros. Most users of GCC use binary packages prepared for a particular OS distribution, where the packager has already cleaned up most of the mess, either by building GCC in a sterile environment where it can't find any headers to pick up and hack up, or by
ascii_field: my current impression is that it once sucked an average amount, and then became what it is now
ascii_field: http://www.citlink.net/~bhima/emfcomp.htm << whole world of crackpottery. may be new to some folks
ascii_field: which is pumped away
ascii_field: shinohai: unlike the various arm dev boards folks like to overpay for, 'pogo' actually comes in a spiffy plastic chassis, complete with disk vagina
asciilifeform has not personally attempted this
asciilifeform: speaking of experiments for the brave, it turns out that you can indeed cut thin steel with a 40w co2 laser if you connect an o2 tank, rather than the usual compressor, to the head nozzle
asciilifeform: '... On the available evidence it seems the aspirations of a small arrogant bunch of men who decided to impose a "New World Order'" on a host of very unwilling small sovereign nations, did not think the exercise through to its perhaps inevitable conclusion. Those same arrogant men have placed tens of millions of citizens at risk because of their own gross incompetence and thirst for absolute power. The "New World Order" now se
asciilifeform: uried in advance. Forget the "garbage truck", which was merely a decoy device. The crater is very impressive, measuring roughly forty feet deep by sixty feet in diameter.'
asciilifeform: mats: as nato reich continues its path down the drainpipe to join the earlier reichs, various folks' temptation to find out 'if the nukes still work
asciilifeform: https://archive.org/stream/computer_ambush#page/n14/mode/1up << gotta love the 'biographies'
asciilifeform: https://archive.org/stream/computer_ambush/computer_ambush_djvu.txt << manual to 'ambush'
asciilifeform: punkman: considerably more interesting, imho, from same site: http://www.rockpapershotgun.com/2015/06/26/the-flare-path-computer-ambush
asciilifeform: bonus points for testing on heathen compilers
asciilifeform fwiw, when worked with robot, had all the 'safety' interlocks disabled. they make it damn-near impossible to get real work done
ascii_field: '(TS//SI//NF) BLARNEY Team assists S2C52 analysts in implementing Xkeyscore fingerprints that yield access to U.N. Secretary General talking points prior to meeting with POTUS.'
ascii_field: nothing earth-shaking, just a complete trojan system for idiots
ascii_field: pete_dushenski: at one point observed that 9 out of 10 malware samples i got to reverse were zeus variants
ascii_field: but afaik there was no simple, fast cutter
ascii_field: instead of dumping
ascii_field: it is called 'human compiler'
ascii_field mentally blows dust off his unwritten magnum opus re: ternary computing, 'tertium datur'
ascii_field: then we're left with the 30MB footprint of the bugger itself + mempools
ascii_field: it simply took the money and ran
ascii_field: financed with kyc/aml compliant kickstartgogo
ascii_field: 'In addition, to prevent future capital losses of this kind, we have contracted with a vendor to provide “multi-sig” technology to better protect our hot wallet (this particular transfer could not have happened today) and hired a skilled technology company, Xapo, to assist in managing our cold wallet.'
ascii_field: 'In addition, we have paid out approximately $250,000 to programmers hired to rebuild and improve our platform; paid approximately $250,000 (and counting) to the Stroz Friedberg team; and at least $150,000 more for various security reviews, and legal and financial advice. These out of pocket costs are continuing to accrue.'
ascii_field: best one can hope for is to get it an order of magnitude below 'asteroid hits your computer' probability
ascii_field: decimation: ecc cannot be implemented in software
ascii_field: mircea_popescu: put copy of same in another country, i'll compare.
ascii_field: and as someone pointed out in last night's thread, let's compute the energy lost by failing to boil visa, mastercard execs into biodiesel
ascii_field: http://log.bitcoin-assets.com/?date=01-07-2015#1182803 << NO! for fuxxsake, read it. it DOES NOT IMPLEMENT CRYPTO ROUTINES, rides on top of existing lib (e.g., openssl)
asciilifeform: 'Results of First 'Deterministic Sync' Experiment, With Memory Consumption Plots.'
asciilifeform: ben_vulpes, mod6, mircea_popescu, et al: anomaly from last night ~wasn't~ replicated. eater successfully ate blocks through 217336 (shat the day before using 'dumpblock' from earlier sync with mircea_popescu's node)
asciilifeform: - It's a symbol, in the shitvi, explained his father, the King. You have to experience real loss to understand the importance of respecting the subterranean world and its rules. It's not easy to do. That's why when someone does it, he's considered truly an adult and counted with people. Until then his notions don't matter. I know what I say may seem absurd to you, but then again one day you'll be prepared, and willing to cut o
asciilifeform: mircea_popescu correctly observed that perpetuum mobile is pretty much the only thing that could save the shitempire
asciilifeform: alternatively, write own (format is pretty simple)
asciilifeform: and compare individual ones
asciilifeform observes that the 'eater' has completed blk0001
asciilifeform: (because if sync is not complete, then naturally last blk**** will differ)
asciilifeform: mod6: differs ~while being complete~ ?
asciilifeform: this is an important point
ascii_field: mp_strange was on the 'stator' build
ascii_field: 'mp_strange' is the data set discussed earlier
ascii_field: $ sha256sum ~/.bitcoin_mp_strange/blk0001.dat
ascii_field: recall, we have 'dumpblock'
ascii_field: nor is mempool churning
ascii_field: and i never imagined i was the first to ever dump blocks - i think just about everybody had some 3rd party script thing to do it with
ascii_field: in other nyooz, 'dumpblock' for the sums.txt.gz mircea_popescu set 0..n and subsequent 'eatblock' in brand-new stator - works
ascii_field: now it gathers dust - keyboard has three or so keys that flip the thing into jp mode, and they 'get pressed' constantly (on account of how cramped the thing is)
ascii_field: ' the NEC still wins over most portable computers of any time for the quality of its keyboard. This is a machine for typing on, and producing content, not for consuming content... Even now, nearly 30 years after production, it still works perfectly. The larger capacity modern rechargeable AA cells means that four of these will keep it running for weeks. Astonishing battery life compared with modern devices.'
ascii_field: ben_vulpes: https://ontario.westburne.ca/shopimages/canadamedia/8/0/6/8796436299806.jpg << example
ascii_field: dumpblock is non-destructive, aha
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: i'm not certain that there ever was a ~less~ sympathetic bunch of dekulakized folks than the cuban 'refugees' in usa
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: (you ~can~, e.g., 'jmp rax')
asciilifeform: note that 'long' (64) mode has no absolute far jump
asciilifeform: otherwise a decent compiler does multiple passes
asciilifeform: mats: if within bounds for relative jump, uses that
asciilifeform: if they ever feel like having an actual economy (or simply switching 'sugar daddies') they know who to call
asciilifeform: no one ever really built a halfway decent compiler for 'vliw' machines (like itanic)
asciilifeform: 'von neumann arch' traditionally means simply the very idea of having separate devices called memory and cpu
asciilifeform: physically had no way to 'jump into' data
asciilifeform: http://log.bitcoin-assets.com/?date=30-06-2015#1181475 << this is not even the worst known abuse. one book (forget whose) actually suggested 'just in time compilation' on arbitrary (!) machines by snarfing up binary routines from function pointers and memcpying them into a buffer, then (*foo)()-ing in...
asciilifeform: it is now also possible to elementarily ferret out certain kinds of leaks - e.g., does importing the same bastard block ten thousand times result in an increase in ram footprint ? if so, we have leak
asciilifeform: mod6: i, for one, am rather curious whether we still get 200M+ footprint when there is ~no~ mempool
asciilifeform: will be interesting to compare their blocks with ours.
asciilifeform: this will also shed some light on the effect of the mempool on resource consumption...
asciilifeform: ben_vulpes, mod6, mircea_popescu, et al: in case this was not clear, it is now possible for the first time to carry out FULLY DETERMINISTIC tests of therealbitcoin (memory consumption, etc) by denying a node a net connection and syncing from disk using 'eatblock'.
asciilifeform: 'Using 'dumpblock' and 'eatblock', it is now possible to move blockchains around via various direct channels (e.g., pigeon.)'
asciilifeform: (before anyone asks: doesn't require the weird asciification that using 'getmemorypool' to import blocks would)
asciilifeform: the presumption is that a fella who is facing a return to life in hard prison might have an arse grenade, etc., or otherwise disinclined to 'go quietly'
asciilifeform: http://log.bitcoin-assets.com/?date=30-06-2015#1181387 << my igprof patch for therealbitcoin is almost certainly b0rked by the 'dumpblock' addition. but fixing it ought to be trivial - good project for any of the less-experienced folks here
asciilifeform: http://log.bitcoin-assets.com/?date=30-06-2015#1181371 << almost inevitably the result of this simple experiment is quite unreadable. anyone who wants to try is welcome to: gcc -E
ascii_field: The SC is different from the SC in projects like gcc in that it does not make decisions. On this front nothing changed. The only difference is that Stallman now has no right to complain anymore since the SC he wanted acknowledged the status quo. I hope he will now shut up forever.'
ascii_field: 'Stallman recently tried what I would call a hostile takeover of the glibc development. He tried to conspire behind my back and persuade the other main developers to take control so that in the end he is in control and can dictate whatever pleases him. This attempt failed but he kept on pressuring people everywhere and it got really ugly. In the end I agreed to the creation of a so-called "steering committee" (SC).
ascii_field: ben_vulpes, mod6, mircea_popescu, et al: last night i noticed that 'eatblock' is kinda already implemented: http://btc.yt/lxr/satoshi/source/src/bitcoinrpc.cpp#1780
ascii_field: anybody else (including mircea_popescu) compare their block hashes with those posted last night ?
asciilifeform: erratum: where i wrote 'O(N^2)' ought to be O(N). complexity of fetching ~all~ blocks is O(N^2).
asciilifeform is dumping and hashing all of the blocks he sucked from mircea_popescu's box earlier
asciilifeform: BingoBoingo: tried the block dumper patch yet ?
asciilifeform: (less, with compression)
asciilifeform: ./bitcoind dumpblock 217040 217040.bin
asciilifeform: ^ example, freshly pulled from mircea_popescu's box
asciilifeform: http://log.bitcoin-assets.com/?date=28-06-2015#1180504 << still need it, to, e.g., keep lusers from taking shits into the mempool
asciilifeform: hence why we need a mechanism to actually checksum the blocks and dump it to a man-readable form
asciilifeform is coming to think that we will be needing a mechanism for out-of-band (hashes, pgp) comparison of blockchains
asciilifeform: poettering et al are small change in comparison
asciilifeform: because literate folks, heard of 'tcpdump', 'wireshark', etc
asciilifeform: http://log.bitcoin-assets.com/?date=28-06-2015#1180198 << can't entirely agree here. every so often folks discover carriers diddling 'consumer' traffic in obscene ways (adding tracking crud to http, even) having gone by for years at a time with not a squeak from the chumps
asciilifeform: but of necessity many of the boxes involved in the ramp-up will be pc.
asciilifeform: until we actually get limited mempool, shoot fragging in the head, etc. pogo will be a bit slow
asciilifeform: mircea_popescu: i was actually thinking of doing for ibmpc something like what i did for pogo
asciilifeform: at this rate, the thing will sync some time after the eeproms in my computer lose 9/10th of their bits
asciilifeform: as soon as he's out, 'reasonable' people will crawl in and 'make compromises'
asciilifeform: i will note that llvm (since i mentioned it again) is upon the most cursory examination a piece of shit, that wasn't even built to 'be good' - but simply with the one and only purpose of killing gcc.
asciilifeform: and anything purporting to be a human-readable spec is necessarily incomplete
asciilifeform: what's next, uterus gives her cramps so she ejects it ?