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: offers approx same ev as hunting rats in sewer for their skins

asciilifeform: ( bullet still costs a day's work, or so, to set up shitnode-of-the-day, then find some exchange where it can even be traded , etc )

asciilifeform: and they live, live, cuz not in fact worth the bullet

asciilifeform: suggests that the typical shitcoin-of-the-day nowadays is a bch-style phork, rather than 2013-style 'prb with genesis swapped'

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

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

asciilifeform: 'The installation is a three-by-three-meter replica of steel and wood reproducing the coin minting machine used by Spanish settlers in the gold and silver mines of Potosí, (Bolivia). The mill mints physical coins that are automatically registered in a blockchain...' blah blah

asciilifeform: as for *213 : behold : answer to this bermuda triangle : https://archive.is/9j7vx#selection-5463.0-5525.29 << tardstalk : 'interesting thing! a creativecoin clone ( with strange ico: real coins vs virtual coins ) ... if you want to add me: addnode=178.238.224.213:12358' etc etc

asciilifeform: defo seems to be a misconfigured/maliciously-configged shitfork noad, none of the tx hashes in the inv's line up with anything from human planet ☟︎

asciilifeform: update : so far only buncha addr's, getdata's, inv's, from *176, in the glue trap.

asciilifeform: will post the pcap once it fattens up. ☟︎

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: ( tho traditionally these have some means of sticking with their own kind, possibly this has changed )

asciilifeform: conceivably, these could be forkcoin noades behind a nat

asciilifeform: http://p.bvulpes.com/pastes/4GZTO/?raw=true << raw barfola. observe that NONE of the 'prev' hashes match any known bitcoin block .

asciilifeform: same algo, thing shits out 9000 shitblox and dumps at line speed

asciilifeform: jurov: neato ! ty

asciilifeform never used twatter, does not know

asciilifeform: BingoBoingo: 'It validates completely validates blocks and transactions' ?

asciilifeform: ( specifically: need to carry pads often (not any moar, carry 1TB disk etc ) ; reuse of pad ( nomoar, burn each block after use ) ; shit rng (nomoar, we have decent rng ) )

asciilifeform: and modern tech makes it possible to avoid the traditional fatal boojums connected with otpism.

asciilifeform: Mocky: it dun replace rsa, you can't sign with it, or speak to >1 counterparty . but imho has its uses

asciilifeform: can think of it as simply a very long untappable wire.

asciilifeform: imho the synchronous variant is preferable, when the underlying physical link permits it .

asciilifeform: in an asynchronous scheme, you gotta explicitly divide the pad in halves, one for a->b and one for b->a, so as to exclude any possibility of either end making use of a block of pad that may have already been made use of by other side meanwhile. ☟︎

asciilifeform: nao if you really must have an asynchronous link ( for e.g. delivery on carrier pigeons, or somesuch ) you can have sequence #s. but still must have authenticator mechanism similar to above, or enemy can force your pad forward by sending crapola.

asciilifeform: each side obtains proof that the other actually received and correctly decrypted a block, prior to sending another.

asciilifeform: the idea being, that nobody lacking a copy of the pad can cause you to wind yours forward. ☟︎

asciilifeform: correct, you need a sram big enuff to hold 2 blox.

asciilifeform: the link, being a physical object, can be disrupted by enemy, but there's nuffin anybody without a copy of the pads can productively do to the traveling bits.

asciilifeform: simple scheme, for example: 512 byte pad blocks; 1st 64 bytes are reserved for a-b keccak salt, last 64 bytes -- b->a salt, 384 in the middle for payload pad. say 'a' starts the convo: sends c = 384byte-plaintext xor 384byte pad . followed by h = keccak(a->b salt + c ). then he expects an ack in the form of keccak(b->a salt + c ) before he winds forward to next block.

asciilifeform: either you get the ack, or you don't

asciilifeform: what's a disconnect in this context ?

asciilifeform: that way you dun have to send block #s, or to risk the endpoints getting out of sync.

asciilifeform: Mocky: you'd want the link to be fully synchronous

asciilifeform: you only decrypt and wind forward the pad if the auth hash matches the expected one for the block salt.

asciilifeform: that way you can reject rubbish, if somehow enemy is able to send you any

asciilifeform: the 1 slightly subtle devil in the details, is that you gotta authenticate incoming data, or enemy can force you to burn your pad by sending rubbish. fortunately there are several easy ways of doing this ( the most obvious, is to use a small piece of each block as a hash salt, and send keccak(salt+ciphertext) after each N bytes of ciphertext )

asciilifeform: ( they're , what, a few bux ea. )

asciilifeform: and for good measure, use the cards 1ce, cremate'em when empty

asciilifeform: Mocky: well yes, you nuke each block on the card prior to xoring plaintext and sending

asciilifeform: the scheme of course lives and dies by the rng; but this is common to any form of crypto whatsoever.

asciilifeform: it is, really, 1970s tech, with the exception of the ssd.

asciilifeform: the 1 missing ingredient, is somebody who actually wants this.

asciilifeform: current FG moar than fast enuff, to do 1/year pad flights b/w 2 hypothetical points.

asciilifeform: but even with ordinary one, it aint much of a problem, just be sure to get the fillers started ~before~ current pad runs dry.

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: this kinda thing is 1 obvious application for a quality rng ( dun even have to be blazing fast rng, an ordinary FG handily fills a 1G card in ~week or so )

asciilifeform: the method where you exchange cards, has 2 wins: it is not enuff for enemy to get copy of simply 1 card, must get one of each ; and rng failure on 1 side doesn't sink you, you get combined reliability of the 2 rng's ( perhaps yours is of 1 type, and other fella's -- another )

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: Mocky: theoretically dun have to use with an actual comp, can have dumb glass terminal on the plaintext side of each box

asciilifeform: Mocky: idea is that you dun need to transport the unit itself

asciilifeform: ( he did same thing, on his end )

asciilifeform: Mocky: it's an old idea of asciilifeform's -- otptron gets 2 sd slots. fill switch triggers fill-up of both with identical otp. then you fly to bananistan with ~one~ and trade with the other fella for his. then you both have identical xor of pad-a and pad-b, in the respective slots.

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

asciilifeform: 'and here is where you strap a live snake, to bite-while-you-smite!'(tm)(r)

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: ( see, e.g., http://btcbase.org/log/2016-06-10#1480388 thread ) ☝︎

asciilifeform: ( tho quite possibly a FG2 that doubles as an iron otptron, could be a marketable win in itself )

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: ( if it isn't obvious to the reader -- the salt would have to be unique per-board, naturally )

asciilifeform: ( at the cost of occupying 2, rather than 1, serial ports )

asciilifeform: then the primary one could function exactly as the classical FG line did.

asciilifeform: 1 possible way around this, would be to send the hashes on a separate serial line.

asciilifeform: would have to actually process the stream before use.

asciilifeform: the obvious down-side, aside from the substantially moar complicated logic, would be that you could no longer dd if=/dev/fg | dieharder etc

asciilifeform: 1 of the wins from it would be that user could immediately verify that baud rate etc are set correctly, instead of relying on the convenient happenstance that a FG misconfigged serial line will produce low-entropy rubbish (with stuck bits)

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

asciilifeform: cuz right nao, theoretically, a supplier of e.g. usb-ttl dongles, or even bugged cable, could substitute prng for the FG bits, undetected

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: in other noose, 178.238.224.213 ( by all indications, does not contain a public node of any kind ) has been spamming randomly generated blox, incl. to zoolag, at the rate of 5-10 erry sec ☟︎

asciilifeform: in related lulz, '...following his brief sabbatical in which he pledged to shed his abusive tendencies, it's hoped a kinder and gentler Linus is ready to resume his duties. Perhaps not coincidentally, with the return of Torvalds will come a "harassment-free" code of conduct that is now part of the kernel source tree.'