asciilifeform: fwiw i've confirmed that #1 is ~not~ any of the privkeys published at various times in their shithub.
asciilifeform: ( for n00bz / folx innocent of ida : the procedure names in the screenshits, are naturally asciilifeform's , they are not present in the bin )
asciilifeform: ^ phf , mircea_popescu , other interested folx ^
asciilifeform: going in order: (1) is the sig header tested by the boot maskrom ( contents not known, but can be guessed at, it has 1 hard-wired pubkey ). this we will call cr50 hitler key #0 . it cannot be changed by fw updater.
asciilifeform: in other publish-or-perish : ...i'ma prolly burn in hell for this, but ida shits out wincrapola line endings and so for now these 'pre-print' screenshits will have to do :
asciilifeform: fwiw ru emigres (esp of the elderly sort) often stuck in exact same mode
asciilifeform: can even make a sort of conversation with these, once succeed in snapping'em out of that human ant mode where the most interesting thing in the universe is the petrol station where 2cents cheaper etc
asciilifeform: BingoBoingo: oh hah, i thought today was Getting Keys day
asciilifeform: fwiw it's been in continuous test on zoolag since day1 ( http://btcbase.org/log/2017-12-23#1757668 ) ; iirc several other folx also tested ( incl. 'side by side' nodez ) , see what they have ( ben_vulpes ? possibly mircea_popescu )☝︎
asciilifeform: in my book, turning '6 month sync' into '3 week sync' is a win.
asciilifeform: would be interesting to hear, if anybody can think of one.
asciilifeform: and i've yet to hear of anyffing like an argument for keeping shitoshi's idiocy of 'boot time is speshul', even as devil's advocate exercise
asciilifeform: mod6: i see it as moar of a bugfix ( a la mircea_popescu's fix of the db locks constant ) rather than troo patch, fwiw
asciilifeform: mod6: up to my nose in saecular liquishit. how'bout you?
asciilifeform: http://btcbase.org/log/2018-06-25#1829397 << imho a genesis oughta be a proggy, if a minimal one, that introduces some basic functionality of the larger item ( as seen in ffa ch1 ) , rather than a placeholder, '[this is genesis and blah and other things will also go here]' -- if this makes sense☝︎
asciilifeform: spyked: prolly i oughta elaborate re the item in your 4th footnote. a compact lisptron has no particular reason to have any notions of parsing baked in; all it needs is 1) a basic i/o mechanism 2) a way to load an initial pre-built s-expression into the working memory and immediately evaluate it.☟︎
asciilifeform: , still waking along, mostly torso-less and wingless...
asciilifeform: this reminds me, not long ago asciilifeform picked up a little chinese toy, item shaped like tennis raquet but the wires are charged to 4000v and connect to (small) cap; a sort of mechanized fly swatter, they pop, little blue plasma burst, vapour. nominally. so then , having used it, later i see a most peculiar insect, did not immediately realize what it is, never having seen before. looked closely, turns out -- fly head + front legs☟︎
asciilifeform: ( btw, this does not appear to be in the l0gz as-such, so asciilifeform will note : c was an evil thing from ~birth~. on machines so impoverished that 'c is necessary', oughta be writing in asm; on machines where not necessary -- well, obvious )
asciilifeform: writing parsers in overflowsanddanglingpointers-lang is braindamaged.
asciilifeform: 'this arg parser, with all of the eggog handlings/safeties already weighs 85% of lisp interpreter...'
asciilifeform: ben_vulpes: funnily enuff, ~this very item~ is how asciilifeform got mired in attempt to bolt a lisp onto trb
asciilifeform: srsly we have enuff pistols that fire from 2 ends. time for a normal one.
asciilifeform: or some other name, but idea being that it must be 1) impossible to confuse it with old 2) keywords ~named~, no order dependency plox
asciilifeform: e.g. 'sendbtc to=<destaddr> change=<chgaddr> [from=<optionalfromaddr_0,optionalfromaddr_1,...,optionalfromaddr_n>]'
asciilifeform: eliminate possibility of confusion with old , or reactor meltdown if new trb is plugged into a scriptolade harness meant for old, etc
asciilifeform: ben_vulpes: if changing the semantics, i recommend new names ( new commands )
asciilifeform: nao this is imho hard to swallow ('submarine with screen door') and so currently i'm assuming that i simply missed something. will have to test, at any rate.
asciilifeform: the other interesting bit ( from asciilifeform's disasm of the 3.4 fw) is that there doesn't seem to be any pinning of the keys! ( i.e. i can't currently find any reason why it wouldn't eat a rw-fw update signed with a variant key, so long as said key is stuffed in where expected)
asciilifeform was aiming to nail down from what derives what, rather than flooding phf, lel
asciilifeform: ben_vulpes: absolutely, this has been a sore spot of asciilifeform's since day1
asciilifeform: possibly the 2nd dumbest thing shitoshi did, after the mining algo -- the coin fragging nonsense.
asciilifeform: http://btcbase.org/log/2018-06-22#1828901 << this kind of thing was a multi-week headache for asciilifeform the last time he had to actually uncork the launch codes and move coin; and i expect that it will only ever get worse☝︎
asciilifeform: btw i did figure out the http://btcbase.org/log/2018-06-22#1828757 matter -- their key format reserves 1st 4bytes for 'keyid' . but the lulzimplementation pictured in the (useless, doesn't seem to occur in the bin) published 'loader', treats the key as starting there . as i currently understand, couldn't actually work as written, barring some mathematical curio☝︎
asciilifeform: since his monumental 'nobody has the keys!' gem, all i saw of him was that 1 time he popped in here and drooled for coupla min.
asciilifeform: pretty great lolcow, btw, that d00d. spilled what he thought was a carefully incomplete pile of beans to 'get asciilifeform to waste months making debug cable', i suspect, didn't quite expect us to get a working one in 1wk
asciilifeform: the only even mild surprise is the sheer pile of echafaudage
