asciilifeform: recall dulap-1 and its phuctor.

asciilifeform: and i'ma test it as soon as dulap-III is up ( btw crate of raid cards just came in last hour )

asciilifeform: asciilifeform is also in the process of standing up trb on dulap-III , an opteron monster not yet homed.

asciilifeform: also notably, mircea_popescu , yer trb box was the champ medallist, outlived even dulap.

asciilifeform: reminds me, not long before the beginning of the time of dulap troubles, and the isp winter, asciilifeform was experimenting with statistical tests of the ~moduli~ a la dieharder

asciilifeform: when i sit to play a game, it feels like dereliction of duty, with, e.g., ffa yet undone, dulap not yet replaces, scintollator rng not complete, 9000 other processes ☟︎

asciilifeform: BingoBoingo: and so was dulap, a recent intel with 256G ram and 32core

asciilifeform: !#s dulap

asciilifeform: re dulap : it, mind-bogglingly, is... still up

asciilifeform: !~later tell hanbot http://thewhet.net appears to be down -- is it in same brother's grave as dulap ?

asciilifeform: ahref ! iirc accounted for 80+% of the http log lines on dulap.

asciilifeform: in other lulz, something closely resembling trb node on ex-dulap ( 46.166.165.30 ) still running... though i do not recommend it for any practical use

asciilifeform: dulap is up

asciilifeform went on a tr kick and noticed that dulap is a turkish, i.e. dolap ( crate )

asciilifeform was about to upload crc book'o'crypto and then remembered that dulap is gone...

asciilifeform: asciilifeform prepared a quantity of servers, each approx. similar to spec of dulap-II ; these will be colocated, under the banner of s.nsa, and a certain number leased to folx in l1 .

asciilifeform: i refreshed archive.is of all the major pages 2-3 day before dulap went ☟︎

asciilifeform: !~later tell mod6 >> http://btcbase.org/log/2017-10-03#1719958 << plox to remove the deceased dulap, 46.166.165.30 . and also note that 108.31.170.49 ( zoolag ) is at 382k and will remain useless as a public node for some weeks. ☝︎

asciilifeform: RIP dulap. ☟︎

asciilifeform: ( dulap -- believe or not -- is still up... ) ☟︎

asciilifeform: and re dulap : http://nosuchlabs.com/pub/dump_9_25_17.gz ( sha512: 886a750d8c1bc8a4e254824a267a407e651e31dce62aa29e2c85c07dfd6e25921671742d6c775df5ea2d065068d579a7e5922b4c36b0d263a7972afc10194164 )

asciilifeform: dulap is up, fwiw

asciilifeform: http://btcbase.org/log/2017-09-21#1716586 << dulap ( While Supplies Last!1111 ) is current fwiw ☝︎

asciilifeform: there ~is~ unfilled bandwidth on dulap.

asciilifeform: at any rate, worx via dulap.

asciilifeform: whoever walked off with dulap-I can prolly replicate..

asciilifeform: http://btcbase.org/log/2017-08-22#1702389 << .30 is dulap/snsa ☝︎

asciilifeform: outperforms dulap, which eats half a kw or so .

asciilifeform: hanbot: the 1st two are mine ( #1 -- zoolag, which is midway through a resyncing, on account of a dead ssd ; 2nd is dulap, which is humming along )

asciilifeform: http://btcbase.org/log/2017-08-06#1694445 << except that this node beat the living shit out of dulap previous 2 yrs, speedwise, because ssd. ☝︎

asciilifeform: i'll point out that this was the fiddybux 'celeron' box that beat the living shit out of $maxint dulap : strictly on account of having ssd

asciilifeform: mircea_popescu: the knowledge problem is not so simple as pictured here. husband may be at work but built camera into the floor long before he met the whore. phf may know re box but not care ( asciilifeform for instance regards contents of hdd of rental servers as sacrificial , esp after theft of the original dulap , etc )

asciilifeform: race included, e.g., dulap.

asciilifeform: actually i have dulap log on dedicated display, and every phuctor hit in l0gz is a hit from same ip, belonging to 'archive'.

asciilifeform: http://btcbase.org/log/2017-05-07#1652688 << what was the state of the wire to dulap at the time , ben_vulpes ? ☝︎☟︎

asciilifeform: achtung, panzers! anyone who noticed that his trb wire to dulap dropped last night -- the thing was rebooted (without my permission) ~13 hours ago.

asciilifeform: could be the case that dulap is 'grandfathered' physical box, but new ones are vm.

asciilifeform: and doesn't do full port scan, has, e.g., nfi that dulap has bitcoin on 8333

asciilifeform: http://btcbase.org/log/2017-03-15#1627306 << it worx great for zoolag-to-dulap, and ben_vulpes , trinque are also on ssh wires, no bug reports so far ☝︎☟︎

asciilifeform: ACHTUNG, panzers! ben_vulpes , trinque : dulap is back.

asciilifeform: ACHTUNG, panzers! ben_vulpes , trinque : trb node at dulap will be unavailable for next ~hour .

asciilifeform: and the ip is dulap's

asciilifeform: seems like a shit idea tho. 'oops there isn't a trb running on dulap, because ooops i broke the build'

asciilifeform: (right now, e.g., zoolag and dulap happily also find each other over ordinary peer table and connect plaintext)

asciilifeform: it'd suck if dulap ~and~ deedbot choked in same day, say.

asciilifeform: btw trinque lemme know if you'd like a 'wire' on dulap.

asciilifeform: congrats to ben_vulpes , the first d00d to request , and be issued, a wire to dulap.

asciilifeform: what_mp_had_and_dulap_didnt.txt << GRRRR ought to read 'zulag didn't'

asciilifeform: so looks like zoolag (and dulap, and everybody) reorged, but mircea_popescu's node didn't

asciilifeform: http://nosuchlabs.com/pub/wtf/what_mp_had_and_dulap_didnt.txt

asciilifeform: grep -wFf mp_but_not_zoolag.txt mp_blk0036.txt > what_mp_had_and_dulap_didnt.txt

asciilifeform: i'd like to connect dulap to one, instead of trudging through ocean of prb

asciilifeform: observe, no miners have written to asciilifeform asking for ssh-wire to dulap.

asciilifeform: it is running on dulap, and will run there until further notice.

asciilifeform: jurov: the most sane variant of your proposal i can think of would be to run the entire tx index in memory. this is just barely practical on dulap, a massive box. and would mean multi-hour regeneration of the index on warmup. but is at least theoretically an improvement, in that it does not threaten to randomly lose bits.

asciilifeform: so far it's dulap <--> zoolag.

asciilifeform: mircea_popescu: that was in re the verification blackhole (the most common type observed on dulap)

asciilifeform: mircea_popescu, ben_vulpes , mod6 , et al: http://wotpaste.cascadianhacker.com/pastes/FEYhA/?raw=true << thus far on dulap.

asciilifeform: but reorg on dulap on ~every restart.

asciilifeform: mircea_popescu: here's typical example: block 454521 on dulap : AddToBlockIndex: ~90 sec: http://btc.yt/lxr/satoshi/source/src/main.cpp?v=makefiles#1212 << 99.98% of this interval

asciilifeform: mircea_popescu: on dulap, zero instances in 84GB of log.

asciilifeform: and here we go, on dulap : ... SetBestChain: new best=000000000000000000d5 height=454507 work=79028340706396234909993360 ; AcceptBlock() success : 401334ms ; Tested candidate block in 401349ms

asciilifeform: 118979 (yes) connection attempts of this nonsense in 84GB (yes) of dulap log.

asciilifeform: in other updates, 0 blackholing since wiring zoolag to dulap. thus far.

asciilifeform: mircea_popescu: holy fuck, 454403 14 minutes (and counting) on dulap; verified on zoolag in 15 seconds

asciilifeform: (only node, rather, on dulap)

asciilifeform: dulap down for next 3 minutes, folx

asciilifeform: ok this is delicious, but i must briefly revisit upstack: mircea_popescu , mod6 , or anyone else in my l1 who wants to ssh+wire-peer with dulap: please gpggram a ssh rsa pubkey to me.

asciilifeform: in other noose! zoolag and dulap are now wire-via-ssh-tunneled together.

asciilifeform: !~later tell mircea_popescu in re: http://btcbase.org/log/2017-02-23#1617048 , interestingly zoolag -- despite being an x86 comp the size of a tea saucer, and weighing ~400 gram -- has roughly 3x faster block verification (of given block) than dulap ! -- on account of ssd. ☝︎

asciilifeform: PeterL: so far i've found ~0 net effect. (earlier today thought that it was a net loss, but dulap caught up and stayed caught up.)

asciilifeform: in other noose, dulap is caught up.

asciilifeform: in other noose, the goodbye_pingers experiment is not a mega-success, dulap is 30+ blox behind

asciilifeform: mircea_popescu: i'd like to leave dulap as it is , to see how this change affects blackhole, but it does carry some of the 'trucks of britain' problem (as described by mircea_popescu article -- 'trucks over 5 tonnes will experimentally drive on left side of road first!11')

asciilifeform: to clarify: dulap is running the revised patch.

asciilifeform: i am rather surprised, i admit, that dulap is speaking to ~anyone~

asciilifeform: mod6: dulap (with the new snip) is actually beating zoolag

asciilifeform: the other major disgrace is that i have no way to make, e.g., zoolag and dulap NEVER MOTHERFUCKING BREAK UP

asciilifeform: dulap down to 4.

asciilifeform: in other wtf's, banning pings took dulap from 50+ to 7 peers (1 of which is zoolag), and none of'em seem to know of any block past 454073

asciilifeform: BingoBoingo, jurov , and anybody else still running old prb nodes for whatever reasons of their own -- note that you will no longer be able to connect to dulap. (or to zoolag, when i patch it. or to anybody else who includes this patch.)