asciilifeform: unrelatedly, to whom does trb noad 69.197.146.42 belong ?? it's been wedged for year+

asciilifeform: ( for comparison: e.g. http://btcbase.org/log/2017-07-08#1680705 ; or, current trb is ~22k loc, ~not~ incl. the dep balls ) ☝︎☟︎☟︎

asciilifeform: near as i can tell, threatened to do ~sumthing or other~ with wallet trb... in 2017

asciilifeform: trb, emacs ( might be hard cookie, but gotta ) , various engineering tools

asciilifeform: mircea_popescu: trb dun use any 'wwwism' from ssl, only the ecc numerics, so i expect just about any extant version will link and run. the rub is how it'd behave in unexplored corner cases, as in the der sig affair

asciilifeform: the one where http://therealbitcoin.org/trb-howto.html : 0x12) Get http://deedbot.org/deed-422651-4.txt : name it 'openssl-1.0.1g.tar.gz.asc'

asciilifeform: mircea_popescu: so idea here is 1st to cut the classic tar to 'what used in trb' ?

asciilifeform: mircea_popescu's old observation re the dacia air filter still holds tho, potentially replacing the hairball in trb with a 100% correct numeric set, will result in a forkable.

asciilifeform: if mircea_popescu gives signal that we're fucking done with the old flintlock pistols, then i'ma start welding on ffa in trb as soon as the former is battlefield-ready.

asciilifeform: well yes, eventually all of trb oughta turn into 'our correct coad'

asciilifeform: mircea_popescu: afaik only in trb is needed

asciilifeform: ( ideally we'd simply keep the logic demanded by trb and burn the rest. but dunno that anyone has the free hands for this presently )

asciilifeform: mircea_popescu: there's an 'openbsd-branded' item, 'libressl', quite similar to the hairball carried along in trb but weighing slightly less

asciilifeform: if said bugs affect trb logic, than it oughta be in trb asap ; if they do not, then not clear to me why better

asciilifeform: for that matter, why does cuntoo need to include own sslism, afaik the only proggy that hard-depends on having one is trb

asciilifeform: trinque: now that i think about it -- what was the logic for including the alt-ssl in cuntoo, vs trb's frozen thing ?

asciilifeform: ( given a musltronic cuntoo, the 'rotor'-descended buildroot process for trb is theoretically redundant )

asciilifeform: will also be interesting to see if trb can sit down on trinque's libressl thing, instead of the frozen ancient openssl it currently goes with ☟︎

asciilifeform: they junkyardwars'd together a working ottoman-style org system ought of sumthing like '80s su -- sorta like we trb from prb etc

asciilifeform: jurov: can haz it again plox ? it was pretty great, i used it in all of my trb work

asciilifeform: ( recall the ancient trb flow chart thread )

asciilifeform: jurov i was gonna link to your lxr ( which i've used 9000 times in all trb work ) as example of why ^ , but it seems to be down

asciilifeform: mod6 & other trb folx ^^

asciilifeform: bvt: of course it does, trb is 100% static-linked and has plenty

asciilifeform: ( there's 200+ col. lines in trb )

asciilifeform: they're already in, e.g., trb. but was thinking, perhaps folx will eventually stop, cuz it's a headache and to fix it is not in any sense expensive imho.

asciilifeform: early trb , for instance. i had nfi how to cure the db locks thing until mircea_popescu supplied the pill.

asciilifeform: btw, BingoBoingo , re waaay upstack -- trb 'throws bastards' from the simple reason that it doesn't keep track of peer heights, and ~always~ retransmits any block that it gets and happily welds to longchain

asciilifeform: mircea_popescu was not fond of 'cement', because sees (correctly) that it is a kludge. but imho given the single-threaded classical trb, it or something like it, is necessary

asciilifeform: current flagship trb cannot be replayed 'from genesis', but can be from 168000, per http://btcbase.org/patches/genesis#L3542 . ☟︎

asciilifeform: speaking moar generally of replays -- because of the idjit method shitoshi used for block-gettin', where 1 peer can ~monopolize connection for just about as long as he wants -- a stock trb node , syncing from empty, is in fact in a position to be fed just about arbitrarily long replay chain. which is why my interest in sane checkpoint variant.

asciilifeform: tldr : the shitcoin people are in fact pretending to compatibility with ordinary btc protocol; even going as far as using unchanged version strings, and backdated block timestamps ( of course trb rejects the liquishit in O(1) , but it is entertaining )

asciilifeform: http://btcbase.org/log/2018-10-23#1865502 >> as promised >> http://nosuchlabs.com/pub/trb/fuckwads_in.pcap ( filtered , for convenience: only incoming crapola ) ☝︎

asciilifeform: wtf this idjit is doing connecting to trb noadez, is anybody's guess.

asciilifeform: i have not observed this on trb to date, but it is precisely the q i was posing, whether can happen ( i.e. reorg logic fails ) in some possible alignment of planets.

asciilifeform: afaik to date trb demonstrably did Right Thing on reorg of arity 6 ( july '15 incident )

asciilifeform: i definitely watched a 60 blox reorg, but this was in pre- trb era

asciilifeform: mircea_popescu: observed on a trb node concretely ?

asciilifeform: afaik this is not a test that has actually happened in trb history ( longest naturally-occurring reorg since trb first saw use in the battlefield was, iirc, 8 blox or so ? )

asciilifeform: seems that he wanted to test whether trb's miner component actually worked.

asciilifeform: $item pertains strictly to current-day trb

asciilifeform: mircea_popescu: unrelated to anyffing: i have a tentative thing that eats a http://btcbase.org/log/2018-10-20#1864354 and gives trb option of replacing 'checkpoints' with it ( i.e. on boot, tests all already-stored blox against it, and if any blox in the tape are not yet present, then it requests & accepts them and only them, 1 at a time ). do we want this for field use ? (if so i can put on conveyor for cleanup) ☝︎☟︎

asciilifeform: billymg: ( trb, for instance, doesn't even support dns lookup. i cut it with own hands; eats bare ip. )

asciilifeform: ( for the impatient : http://nosuchlabs.com/pub/trb/snap_546400.txt ) ☟︎

asciilifeform: already turned up a buncha oddities re noades -- for instance, just about errybody not-trb still sends out gavinalert (with 'key compromised!' message. wai -- i have nfi )

asciilifeform: ( in prelim experiment thus far, virtually errything that aint a known trb noad, appears to show one or more obv symptoms )

asciilifeform: in unrelated noose, mod6 et al : loox like trb doesn't remove banned peers from its addr table ! i.e. offers their addrs up to others, as if they were proper noades!! i never noticed this previously, it had to wait to be found empirically. really oughta be fixed, and pretty simple patch. ☟︎☟︎

asciilifeform: this line of thought was prompted by my 'trb observatory', which has uncovered a number of 'mpb'-style nodes, i.e. trb-like but not presenting 'modern' vers and therefore invisible from heathen www indices ☟︎

asciilifeform: phf: i was aiming for 3 basic things : 1) recursively getaddr entire reachable btc net, perhaps erry hour or so 2) find trb-compat (i.e. 'services' == 1 ) non-pseudos (i.e. if i pull block hash out of a hat, he quickly gives correct block) and eventually 3) get inv's and monitor tx propagations.

asciilifeform: worx ok with trb. but heathens do all kinds of weird things, throw up various garbage in place of e.g. getaddr answer

asciilifeform: it's a 2edged blade, as it would be a great temptation to 'light client' idjits to parasitize on trb. but would make for easy litmus.

asciilifeform: btw trb could in principle be made entirely distinguishable, if we were to permit asking for a ~tx~ in 'inv' command ( currently prohibited , because prb nuked indexing , but could be brought into trb with no ill effect aside from some cpu cost )

asciilifeform: re upstack -- as it happens, 'trb-compat' is pretty easy to distinguish mechanically -- anybody who has 'services' field != 1, aint trb-compat.

asciilifeform: individual display only of trb-compat folx.

asciilifeform: speaking of trb, i dusted off an old conveyor item, phuctor-like www proggy that maps out noadez ( you give it ips, and it connects to'em, then issues 'version' and 'getaddr', and builds a graph )

asciilifeform: lol, could even describe e.g. trb this way

asciilifeform: Mocky: 'aggressive' trb vs regular, is just about 'night and day'. i also have ben_vulpes's 'super aggression' item lined up for test.

asciilifeform: Mocky: keep in mind that 'aggressive' trb syncs in (pessimistically) 2-3 weeks. so not much point in throwing around whole balls of blox.

asciilifeform: ( all you need is that little bash , and a reasonably recent trb )

asciilifeform: mod6, jurov : trb ml down ??

asciilifeform: diana_coman: erry so often i try an' search for some symptom that heathens know of trb etc., ~never found

asciilifeform: mircea_popescu: something to this; 'aggression' removed most (not all) instances of trb 'sitting with mouth open'

asciilifeform: meanwhile, in trb observatory... nuffin on surface. but! loox like all of trb planet stuck on 544911 ( heathens : 544928 )

asciilifeform: http://btcbase.org/log/2018-10-07#1859231 << will need to be instructed re basic trb doctrine ☝︎