asciilifeform: granted this is less of a headache in 'minerless' trbi variants.

asciilifeform recently on yet another kick of 'what do re hashing' , if nobody guessed

asciilifeform: and for thread-completeness i gotta point out that 'Until the day Bitcoin mining uses up 50%+1 of all electricity generated on planet Earth, this theoretical avenue remains open, if very theoretical' isn't necessarily guaranteed : there always remains ( because Hashing Is Voodoo (tm) ! ) the possibility of discovering shortcut to the mining process ( we had the 'satcoin' thread; possibly other variations on the theme also )

asciilifeform: aa

asciilifeform: mircea_popescu: the only obvious problem with 'oppenheimer' hypothesis is that shitoshi iirc walked away ~prior~ to bitcoin 'chain reaction'

asciilifeform: diana_coman, mircea_popescu : that was my only hypothesis. i haven't another.

asciilifeform: can anyone 'devil's advocate' this one ?

asciilifeform: WHY should boot time be special ?

asciilifeform: to me it looks completely indefensible.

asciilifeform: btw i'm still waiting for anybody to try to defend the original shitoshi sync behaviour, somehow

asciilifeform: but the up/down sides of this method are i think obvious

asciilifeform: btw i'll mention again a simple method to speed up sync (to a point) 1,000x or moar -- signed hashes ( a la the programmable checkpoint thread from 2yrs ago ) ☟︎

asciilifeform: ( dulap had ~ok trb performance on spinning rust, but it had striped raid . and STILL couldn't keep up with ssd zoolag, despite the latter being a box the size of my fist, with no raid, on residential fiber )

asciilifeform: i.e. screamingly short of the system requirements

asciilifeform: spinning rust, at this point i dare say, is like running node on 486

asciilifeform: mod6: it

asciilifeform: n00b wants to run trb. which trb will he run ? ☟︎

asciilifeform: imho 'trb release' makes sense as a thing -- conservative 'this worx' item

asciilifeform: in trbland

asciilifeform: trinque: this is sorta how releases work already iirc

asciilifeform: for instance, a release is a suggested starting point for patch work

asciilifeform: it means, simply enuff, whatever item ben_vulpes & mod6 proclaim 'this is a trb release'

asciilifeform: this goes for ~all~ 'experimentals'

asciilifeform: e.g. 'i ran node with this for 60 d, and it worx , nomoar fallbehind' etc

asciilifeform: with commentary

asciilifeform: sign it !

asciilifeform: incidentally ben_vulpes , mod6 , anybody else who tested 'experimental' patch, is invited to...

asciilifeform: recall ?

asciilifeform: ben_vulpes: there is such a thing as ' ben_vulpes & mod6 Troo Release ' !

asciilifeform: ben_vulpes: well considering that it only snips off an obvious birth wart

asciilifeform: for which there can be NO justification.

asciilifeform: the 'boot time is SPESHUL' is an idjit winblowzism

asciilifeform: the old sync behaviour is profoundly retarded tho, asciilifeform felt quite stupid for not having fixed it in the first yr of trb's life

asciilifeform can't find any argument against this

asciilifeform: ( iirc mod6 also has a node with it, runs smoothly, talk with him. possibly ben_vulpes also )

asciilifeform: nowadays i dun see any reason not to mainline it

asciilifeform: trinque: indeed i marked it as experimental. did not know if, e.g., prb would shun the patched nodes, say

asciilifeform: asciilifeform's working node has been 100% free of 'falls behind and cured by restart' since patched.

asciilifeform: cuz if not, this is elementary

asciilifeform: ( i.e. does it have the sync retardation cure )

asciilifeform: trinque: what patch set on this node ?

asciilifeform: trinque: do you know of a particular reason why you have a -3k node ? ( it is a young node, not yet grown ? or -- blackholed ? which )

asciilifeform finds the 'tx references outputs of old tx, rather than addrs' to be a profoundly trisomistic shitoshiism -- but we can come back to this at next 'trb-i' thread

asciilifeform: clearly.

asciilifeform: 'this tx may have come from parallel universe, we won't know until we intern its parents'

asciilifeform: it ain't 'empty', just orphanistic.

asciilifeform: but i'll agree that 'empty' is idiotic way to describe it

asciilifeform: dunno, it was enuff for asciilifeform to say what was the eggog

asciilifeform: caseclosed.

asciilifeform: ding.

asciilifeform: ( and what was the generating node's ? )

asciilifeform: and, importantly -- what is the node's height ?

asciilifeform: hm, interesting

asciilifeform: is tx of unusual size ?

asciilifeform: or was this a process flow that worked 9000 times before, and otherwise virginal

asciilifeform: right, but is there any diff b/w how trinque fed it to 'other tool' and how he fed to this one

asciilifeform: ( is it possible that it got cut or mutilated ? )

asciilifeform: i gotta ask : how didja generate the txturd

asciilifeform: but with ^this patch ? or another ?

asciilifeform: and http://btcbase.org/patches/polarbeard_add_sendrawtransaction_rpc is the press point ?

asciilifeform: 'CTransaction::CheckTransaction() : vin empty' ?

asciilifeform: trinque: which eggog, exactly , do you get ?

asciilifeform: trinque: plox to describe the experimental setup ( not pedantism for the sake of pedantism, this, it's important )

asciilifeform: ( modified ? if so how? or a well-known press ? or wat )

asciilifeform: trinque: which trb is this

asciilifeform: so potentially findable there, if only anybody remembered the actual phrasing

asciilifeform: in other finds, unlike google, yandex indexes ~all of trilema

asciilifeform: mircea_popescu: http://trilema.com/2015/carnita/ ?

asciilifeform: ( i dun have a greppable trilema here, so can't immediately say where )

asciilifeform: it was

asciilifeform: it was in a trilema article

asciilifeform: err, orwell

asciilifeform: orlol

asciilifeform: but yes

asciilifeform: oh hah i misparsed 'got 0' lol

asciilifeform has nfi

asciilifeform: but the point stands.

asciilifeform: fwiw the deep historicalcrackpots seem to think it wasn't even arabs, but the now-vanished aryans or whoever.

asciilifeform: the sad part re inventing things.

asciilifeform: more or less.

asciilifeform: *there'dve been

asciilifeform: if we wrote like arabs, there've been no controversy, i bet

asciilifeform: aha!!

asciilifeform: 67 45 23 01

asciilifeform: i'll spoil it for littleendian :

asciilifeform: try likewise with 'long' instead of 'int', to see effect on 64bit parcel

asciilifeform: try this on littleendian and bigendian box.

asciilifeform: and afterwards, ./endian | hexdump -C

asciilifeform: gcc -o endian thisitem.c

asciilifeform: }

asciilifeform: fwrite(&i, sizeof(i), 1, stdout);

asciilifeform: int i = 0x01234567;

asciilifeform: void main() {

asciilifeform: #include <stdio.h>

asciilifeform: ok, here goeth :

asciilifeform preparing snippet, brb

asciilifeform: aite, let's:

asciilifeform: whether this matters, is obviously arbitrary q.

asciilifeform: mircea_popescu: re the 'guillotine neck vs mandible', if it ain't obvious, i'll spell it out ftr : bigendian nums look 'ffaistic' when hexdumped, i.e. correct . littleendian -- you gotta mentally flip'em. ☟︎

asciilifeform: ( further reading for aficionados : http://www.yarchive.net/comp/endian.html , http://yarchive.net/comp/linux/bitfields.html )