asciilifeform: how found that he's a blue muppet ? ( caught and connected to 220v and confessed? ) or indirect ?
asciilifeform: ( and with modern-day ru-style cyrillic, rather than the slavonic pre-1860 thing seen in ro museums )
asciilifeform: re moldavia : asciilifeform has a hilarious ro textboot, from sovok-era moldavia. exactly , near as i can tell, ordinary ro, but cyrillicized
asciilifeform: or how routers on erry hop of a connection are forced to maintain a 'circuit' state in memory, as if they were telco switches
asciilifeform: tcp shows erry possible sign of having been designed, from the start, to extend the ease of snoopage from traditional circuit-switched telco grid, to the packet world. consider e.g. the 'helpfully' plaintext sequence numbers.☟︎
asciilifeform: the protocol is 'fractally retarded' -- i.e. broken on absolutely erry possible level. starting from where it takes exactly 1 trivially forged packet to close someone's connection, to where 'allcomers' get a substantial chunk of memory allocated , and make ddos trivial , to where it forces 9000x moar complicated design of routing gear, to... could continue but why.
asciilifeform: i vaguely suspect that it may have been the original usg-'standards committee'-powered explicitly-organized nobus generator
asciilifeform: spyked: not only is the implementation what it is, but tcp per se is massive pile o'shit, where it aint even possible to implement it w/out 9000 tonnes of state machine gnarl
asciilifeform: the usual megatonne-of-c-liquishit style of 'works'.
asciilifeform: ( to date -- no reports of a live specimen of constructed wedge chain, afaik )
asciilifeform: theoretically if you built with 'dumpblock', can debug this scenario by hand.
asciilifeform: ( it'd be easier to say something concrete on this subj if ye olde shitoshi had actually included a reasonable set of debug knobs. but, unsurprisingly, did not, and made it quite difficult to retrofit, also )
asciilifeform: to round out this thrd : asciilifeform suspects that some unknown but nonzero % of 'perma-wedged noad' cases, are accounted for by adhoc attempts to carry out this experiment
asciilifeform: by constructing a set of successively-longer reorgable chains that take X 'on credit to allcomer' buffers to actually evaluate
asciilifeform: nao that i think about it, iirc we indeed had thread where calculated that with 10 or so % of total hash horse , could frag the net ~by orphanage size~ ( us, 0, heathens, a range of x's )
asciilifeform: there was at least 1 where we both went 'bbbut x'
asciilifeform: from the 1000000-byte block thing, to this
asciilifeform: it's funny, erry yr or so asciilifeform goes 'bbbut i distinctly recall, protocol went like x' ...then dig in the sores again and 'mno, instead did the retarded thing'
asciilifeform: mp_en_viaje: theoretically even nao 'longest chain is the 1 with highest hash' . problem is that this takes arbitrary space to evaluate.
asciilifeform: but iirc i never published this ( not that it's hard to make ) , cuz wasn't burning ( and still unsure whether this was the right approach as such )
asciilifeform: hence why asciilifeform wrote a 'cement' mechanism, where you can explicitly feed in a signed list of hashes to newborn noad
asciilifeform: therefore there's an intrinsic wot component in noad bringup
asciilifeform: well for 2-level db ( 'nursery' where blocks that are thought to be part of the snake's tongue that may still reorg ; 'graveyard' where errything else ) does require a number.
asciilifeform: granted i cannot say how he ought to have decided on concrete number 'down below which not mutable.' he would've had to 'guts' .☝︎
asciilifeform: can point to ~concrete~ braindamages of orig author that resulted in the sad db. one was the expectation that tx 'down to genesis' are mutable 4evah; the other, the idea that 'utxo set' is what matters to fetch quickly, rather than ~any~ tx
asciilifeform: it's a ~linear trade of time for space tho, conceivably could use same scheme with various sizes of table, at predictable cost
asciilifeform: for uses where absolutely gotta fetch arbitrary tx in O(1) , indeed >=32G
asciilifeform: ( the remainder, end up asking for a second lookup )
asciilifeform: handily fits in a reasonable ram. and 99.9999% of queries will land in it in O(1)
asciilifeform: mp_en_viaje: no elaborate massage needed -- simply need 32GB or so hashtable . ( who wants, can dig up old thread with the exact algo, atm asciilifeform's hands somewhat full )
asciilifeform: and mp_en_viaje's napkin figure is correct (and pessimistic, could easily ~day on existing irons if rewritten properly )
asciilifeform: mp_en_viaje: db could be not only parallelized but made O(1) , iirc we had lengthy worked example of just how
asciilifeform: this is true even with 'aggressor', the latter merely asks ~newly connected~ peers to give blox
asciilifeform: it's spent waiting for someone to 'please drop a block in my gaping mouth'
asciilifeform: BingoBoingo: most of the time aint spent in verify tho
asciilifeform: still gotta add, that trb bringup takes weeks not because the set weighs 100TB ( as erryone already knows, it's below 300GB atm ) but cuz the sync mechanism is rather sad
asciilifeform: mp_en_viaje: iirc this is 1st recorded such case ( d00d took the sweat to build trb, note that there ain't a '4lusers' binariola package or anyffin of the kind) but then went and planted it on a lolhost
