log☇︎
111300+ entries in 0.032s
asciilifeform: i'll add to this that in trb as we have it, you ONLY need blockchain to verify a potential mempool tx
asciilifeform: how can it possibly answer immediately ?
asciilifeform: and either gets dropped by peer.
asciilifeform: queueing is sane but i will point out that from the other side, a node that doesn't answer immediately because it queued, is not distinguishable from one that doesn't answer because it is spinning wheels on block verification.
asciilifeform: you need the entire orchestra to decide whether to accept a tx for relay.
asciilifeform: ditto tx
asciilifeform: and to do this, you need the entire spittoon.
asciilifeform: this doesn't add up to a working btctron. in order to evaluate a peer, it is necessary to be able to distinguish block from rubbish.
asciilifeform: plox to elaborate
asciilifeform: aha.
asciilifeform: same process repeats.
asciilifeform: when it finally gets a peer going again,
asciilifeform: when it gets NEXT block, which happens more or less immediately after,
asciilifeform: what's more, this is a rinse-and-repeat
asciilifeform: (they -- elementarily -- time out)
asciilifeform: while it verifies, the thing sits around being very sad, and ends up losing most of its peers
asciilifeform: we get a block (dulap already saw same block; it was valid.) which simply takes ages to verify.
asciilifeform: http://wotpaste.cascadianhacker.com/pastes/SlwGQ/?raw=true << this is fresh from zoolag. and very typical.
asciilifeform: 'To Read the Full Story, Subscribe or Sign In' << lel
asciilifeform looks at his nodes, and discovers that, sure enough, both are blackholed at this very moment.
asciilifeform: cannot be ruled out.
asciilifeform: or conceivably the described bear trap will actually contain a bear at the end of the day.
asciilifeform: if done as described above.
asciilifeform: and it'd be a few megabyte of swamp
asciilifeform: but we would have the culprit, yes.
asciilifeform: whether it is waste of time, is separate question.
asciilifeform: after a few days of this, we have the culprit.
asciilifeform: so we get a snapshot of the, say, 20 minutes of tcpdump prior to node entering blackhole state.
asciilifeform: at the same time, tcpdump is running
asciilifeform: then we know. blackholed.
asciilifeform: if it times out !
asciilifeform: this will consist of a shell script that makes, e.g., getinfo api request, AND
asciilifeform: first you need a blackhole detector.
asciilifeform: but will anyway, just in case.
asciilifeform: the necessary experiment is i think quite obvious and i do not need to describe it in detail.
asciilifeform: aha.
asciilifeform: something that comes down the wire. precisely what, i do not yet know.
asciilifeform: what happens is that it makes ~your~ node sit retardedly instead of talking into socket at appropriate time.
asciilifeform: ben_vulpes: not what happens. those get banned quite normally.
asciilifeform: mod6: trb isn't multithreaded in the, e.g., apache, sense. it services clients round-robin style, and if it gets stuck at any point, this is what you get
asciilifeform: mod6: http://btcbase.org/log/2015-11-19#1327566 ☝︎
asciilifeform: !#s blackhole
asciilifeform: recall, whole thing deadlocks, won't accept any interactive command at all.
asciilifeform: ben_vulpes: it'd have to be continuously dumped
asciilifeform: and very much glued on with broken glass.
asciilifeform: it is atrocious design, as is the whole thing.
asciilifeform: i.e. is the very worst kind of mutilation of 'grandfather's pistol' conceivable.
asciilifeform: which potentially changes the semantics of EVERYTHING ☟︎
asciilifeform: the only boojum is that parallelizing would require removing the locks.
asciilifeform: wireshark, and a good deal of patience, would answer it.
asciilifeform: it does not.
asciilifeform: (it is idiotically serial and the entire thing locks, won't respond to rpc commands, etc)
asciilifeform: http://btcbase.org/log/2016-12-20#1586638 << i was able to reproduce a very similar effect. simply throw blocks at a node that don't fail verification until the very end. ☝︎
asciilifeform pictures him resembling baron harkonen in david lynch's film of 'dune'
asciilifeform: failed generation, or ran out of corpse to eat..?
asciilifeform: aha.
asciilifeform: catch'em off the clock -- they'll talk.
asciilifeform: popes are, on some level, people also, theoretically.
asciilifeform: aha.
asciilifeform: 'The raw power of computers has advanced at a stunning speed, but has this advance translated into a comparable improvement in their usefulness? Word processing, to take the most obvious example, hasn't fundamentally improved since the late '80s. And in the view of many people I know, WordPerfect 5.1 for DOS was actually better for their purposes than any of the bloatware that has followed.'
asciilifeform: oh huh, looks like mettler toledo bought'em
asciilifeform: (why the 'rainin' pipette ran on them, i have nfi to this very day, ask the french not me)
asciilifeform: funnily enough, at my first paying jerb i used up dozens of these batteries, electric pipette ran on'em, and i had nfi why they were interesting other than 'bitch to get'
asciilifeform: which afaik no other battery does.
asciilifeform: and the bugger runs a-ok at -55C.
asciilifeform: mircea_popescu: aha, it is lovely, a FUCKGOATS rng board could run for year+ on one.
asciilifeform: in other olds, http://trilema.com/2015/open-parasitic-p2p-relay/#comment-120120 .
asciilifeform: afaik they don't exist.
asciilifeform: btw if anyone knows where one might buy breadboard bigger than this, i'm all ears.
asciilifeform: the loose-hanging wires - were attached to logic analyzer, which had to visit bench in other room when this pic was taken.
asciilifeform: (the fat connector is a chained jtag for handy simultaneous reflash of both yoked units)
asciilifeform: unrelated, and of 'historical' interest, http://nosuchlabs.com/fg/photo/yoke.jpg << first FUCKGOATS slave yoke test, from last week.
asciilifeform: phf: 3ware
asciilifeform: worx even with ancient controllers.
asciilifeform: it's the correct way to use'em
asciilifeform uses ssd raid ☟︎
asciilifeform: no shortage of one; while the other showing up on ebay in qty==1 is 'world' news...
asciilifeform: 'cheap' in the antique comp business means in practice 'everyone who wants, has'. as, e.g., 'commodore 64', vs, say, lispm.
asciilifeform: ( most famously, smbx lispm was findable for a few hundy during a very brief burst when amex flooded the market with theirs, which had been replaced with java shitware )
asciilifeform: and yes, cheap today, unobtainable tomorrow.
asciilifeform: which is what subj is
asciilifeform: there is 'cheap' in the junk business.
asciilifeform: and in most cases still readily had.
asciilifeform: though i can think of a few exceptions ( transport for, e.g., cray, or connection machine - and yes, i knew a d00d whi bought connection machine! is not easy or cheap ) -- generally old hardware of the interesting sort ( vs everybody's old 386 ) is cheap
asciilifeform: these expired some time around ivan 4.
asciilifeform: the one full of ukrs? or the other one, that wasn't even any colour of ukr whatsoever until idiot hruschev redrew the map.
asciilifeform: which ua
asciilifeform: in recent orlolz, http://cluborlov.blogspot.com/2016/12/brain-parasite-gonna-eatcha.html
asciilifeform: ( http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2baa891e42d84159b693eadd44f6fe1486285bdc )
asciilifeform: or hm, lemme guess, MTRR
asciilifeform: something other than version?
asciilifeform: (standard linux kernel won't load mods that aren't versioned for it. unless 'forced')
asciilifeform: danielpbarron: doesn't force-load either ?
asciilifeform: persistent little bugger.
asciilifeform: ^ obscure box with ssh on nonstandard port
asciilifeform: in other lulz, http://wotpaste.cascadianhacker.com/pastes/YmlTD/?raw=true
asciilifeform: post log? ☟︎
asciilifeform: ben_vulpes: i, for one, do not know the answer
asciilifeform: they take ~only~ coinbase?!
asciilifeform reads on, in sidebar, 'Dec 13: For your Bitcoin payments, remember that we need the Coinbase transaction ID in order to track your deposit. We encourage you to write down that ID to avoid delays in your Bitcoin payment processing. Thanks for your comprehension.'