asciilifeform: i strongly suspect that the general case of 'establish the troo historic longest chain, strictly from the network, consisting of arbitrary portions of honest and dishonest nodes', without some variant of cement, is not solvable in general case

asciilifeform: ( if were working strictly 'by the net rules', no one would ever do this, 'i have a node, it knows what the world height is', but this is not the actual practice )

asciilifeform: ( and i'll add that 'i sync all my new noades from existing ones' is a form of checkpointing , yer still weaseling out of using 'strictly clean' http://btcbase.org/log/2018-10-22#1865227 mechanism , there ) ☝︎

asciilifeform: mod6: in fact, and iirc i discussed this 2y or so ago in the l0g, by my current understanding of the reorg mechanism, it is possible to wedge ~any~ noad by throwing a specially- 'retro'-mined block with a higher work delta than the 'genuine' one at a particular point. then reorg dun trigger at all. ☟︎

asciilifeform: theoretically it'll get reorg'd when honest noad later connects. but afaik this has not been tested, i personally do not know if a 1000+ -blocks reorg will succeed.

asciilifeform: ( recall, i saved whole /16 from each range )

asciilifeform: mod6: i think there's also an ordinary (as they go) prb noad mixed into that pcap

asciilifeform: i can't picture against whom such 'replay' would possibly do anyffing, tho

asciilifeform: i dun have a tcpdump on that thing at all times, lol, no amt of disk count conceivably suffice

asciilifeform: mod6: they were not. see log, i set up the tcpdump ~after~

asciilifeform: BingoBoingo: nao i'm curious, how do they typically respond ☟︎

asciilifeform: !Q later tell bvt i left a comment on your www, should be in your queue

asciilifeform: i can't picture how it could hurt, tho. having a working artifact in yer hand readily distinguishes you from the indian 'my CREATIVE BIZNISS IDEA!111' folx.

asciilifeform: what i also dun know, is how well this meshes with Mocky/mircea_popescu's mission in Mockystan, presumably Mocky was not sent specifically to sell FG or mircea_popescu would have issued one already. so lessee what mircea_popescu says 1st.

asciilifeform: i.e. whether it is even possible to get Mocky a box prior to his expedition time running out

asciilifeform: what i dun presently know is, just how fascist are the customs in Mockystan

asciilifeform: Mocky: in usa i found that i had to get a postbox simply to get a lease for office that has own postbox, 'catch-22', but possib. other places moar sane

asciilifeform: Mocky ( and for the l0gz ) -- if it aint obvious from the FG src : the thing spends first six ticks of the clock on powerup listening for signs of a working external clock on CLK pin; if it finds one (i.e. it's pulled high on board, and can only fall low if there's a 'master' connected) it becomes 'slave' until powerdown.

asciilifeform: lessee what mircea_popescu thinks; this is a classic example of the type of knot i rely on him to cut.

asciilifeform: bvt: on contemplation, i'm thinking possibly mips should simply get own v-branch, if we ever actually get hold of a mips. ☟︎

asciilifeform: now, for an erryday piece of critical gear like otptron, i'd prefer an algo that ~provably~ terminates with correct (i.e. opposite polarity) pair, rather than 'oh it never ties in practice cuz no 2 crystals are exactly same' thing.

asciilifeform: mod6: dun burn much time on it, i suspect there is nothing much of interest ( they break some of the protocol format, but not, as far as i can tell, to any interesting end )

asciilifeform: mod6: lemme know if you see sumthing interesting that i missed. but seems to me that my earlier hypothesis holds, they were forkolade noades.

asciilifeform: incidentally, https://www.adacore.com/gems/gem-59 apparently exists, tho i confess that i really dislike the idea of automatic converters for coad ☟︎

asciilifeform: Mocky: i can think of several algos for reliably picking 'left' and 'right' without any manual config ( recall, 'a' and 'b' have the cards slotted in, in opposite orders, call'em pad 'x' and 'y' , 'a' has x-y and b y-x -- both get same final xor, x xor y, is used as pad p )

asciilifeform: my orig attempt at the udp thing tried to stick with purely pragma Import(...), but the result was definitely not portable, and so i rewrote it like-so

asciilifeform: if it weren't for struct sockaddr_in..., struct in_addr..., i'd've simply imported the calls via pragma Import(C, ... )

asciilifeform: bvt: i have a variant of this in ffa, and yet another subset in mmap

asciilifeform: i.e. mips linux was sabotaged.

asciilifeform: my mmap thing, which i've mostly finished rework to prepare for genesis, demands open(), mmap cannot eat fopen()

asciilifeform: bvt : i'ma have to implement something to make calls to open() portable, cuz this is riotously ridiculous

asciilifeform: bvt: http://btcbase.org/log/2018-10-23#1865503 << this is very interesting ! i had nfi that open() had been sabotaged on mips-linux ( observe , in your table, errybody has same flags but for mips ) ☝︎

asciilifeform: briefly revisiting http://btcbase.org/log/2018-10-23#1865463 >> nobody noticed the omission, but i oughta've pointed out that 'a' and 'b' gotta proceed from opposite ends of the pad, when sending, otherwise risk collision ☝︎☟︎

asciilifeform: i suspected shitfork, when realized that the 501 blox gotta be a few kB most, ea. -- my pipe couldn't disgorge 501 human-sized blox in <2sec ☟︎

asciilifeform: i gotta wonder nao, if prb's tx checker is porous enuff that it actually relays these !

asciilifeform: i admit that i'm pretty curious re just what it is that they're offering up as blox.

asciilifeform: if anybody notices moar of these, plox to share, so i can add'em to the glue trap

asciilifeform: or hey, wai not tcpdump -w fuckwads.pcap -i eth0 "net 165.227.0.0/16" or "net 178.238.0.0/16" .

asciilifeform: i'ma leave a tcpdump -w fuckwads.pcap -i eth0 "host 165.227.138.176" or "host 178.238.224.213" running on zoolag

asciilifeform: would be interesting to learn wtf is inside those blox. but i dun currently have the box configured to save liquishit ( no conceivable disk would suffice )

asciilifeform: i.e. nothing is sent until prev block ack'd

asciilifeform: and for point-to-point link, e.g., shell, can last for a good while ( i dun think i've put 1 whole GB through a shell in the past yr... )

asciilifeform: 1 of the things i like about otp box is that it is trivial to verify that it functions as specified ( can plug in a pad with known contents, throw in known plaintext, and observe -- with a comp of your choice -- what comes out )

asciilifeform: ( nao i'm curious, what, by d00d's lights, is 'full node', and where might one get such a thing ) ☟︎

asciilifeform: i suspect that there is a sane space b/w the classical design and http://btcbase.org/log/2016-09-12#1540775 extremity, simply gotta find what it is. ☝︎

asciilifeform: another pheature i've considered, is to give the thing a sd card slot, so it could fill it straight for otp use. but this is perhaps a bridge too far.

asciilifeform: i'ma let mircea_popescu ponder whether this kind of thing is worth doing ☟︎

asciilifeform: diana_coman: the 1 crackpottery i've considered adding to FG-2, is an 'authenticated' mode, where userland proggy gets ability to verify that rng bits actually came from a particular FG. the way to do it would be to have a keccak salt, printed on the board, and have the thing send , instead of naked bytes, packets, of b0,b1,...bN bytes, followed by keccak(salt, b0,b1,...bn) . could be enabled by jumper setting, conceivably.

asciilifeform: if receiving end were prb ( which last i knew, still had the 'orphanage' thing ) -- would balloon to fill ram

asciilifeform: i'ma describe , for the l0gz : ideal cpu for crypto would be something quite like the schoolbook mips.v -- no cache, no branch prediction, no pipeline, no dram controller (run off sram strictly), a set of large regs for multiply-shift , and dedicated pipe to FG (i.e. have single-instruction that fills a register with entropy ) ☟︎

asciilifeform: what i'd really like is to bake an entire comp, a la rockchip, with FG on board. but this too is in same budgetary ballpark as asic .

asciilifeform: ( plus i ~like~ that it gets made from off-the-shelf components, from strategic pov it is imho superior )

asciilifeform: i wouldn't even be opposed to putting usb logic on FG -- but to this very day have not found a sane (i.e. not reflashable via usb) interface ic , aside from the chinese dongles ( which i outboarded, because if a piece can be outboarded -- it oughta, per specificity-of-diddling )

asciilifeform: or at the very least , >1 serial port ( the current pizarro boxen, do have rs232 header on mobo, but only one, and at the traditional +/- 12v signal levels, rather than ttl, and i eschew the converters, because they all work by oscillating capacitor pump, hence noisy )

asciilifeform: mircea_popescu: classical FG also fits very reluctantly in servers, but currently i dun have a good idea re what specifically to do about this ( the 'obvious' pill is to have a pci variant, but ice40 is too small for the necessary logic, which in itself is quite gnarly )

asciilifeform: nao possibly i never suffer from this because i very rarely refer to bits explicitly