log☇︎
99500+ entries in 0.031s
asciilifeform: oh hey!!
asciilifeform: http://btc.yt/lxr/satoshi/source/src/script.cpp?v=makefiles#0083 << holy fuq the magicnumberola never ever ends
asciilifeform: would seem to rely on traditional (push/pull) versionatrons tho
asciilifeform: Framedragger, mircea_popescu : i can picture it
asciilifeform: neato
asciilifeform: phf: oh hey mouseovers
asciilifeform: seems like a shit idea tho. 'oops there isn't a trb running on dulap, because ooops i broke the build'
asciilifeform: believe it.
asciilifeform: Framedragger: in point of fact i did not
asciilifeform: http://log.mkj.lt/trilema/20170311/#873 << lemme guess, a 'bashop' is a bishop who is handy with bash ?
asciilifeform: http://log.mkj.lt/trilema/20170311/#870 << what is 'CI' ?
asciilifeform: log
asciilifeform: phf: lol 404 ?
asciilifeform: those hoses, they want to connect.
asciilifeform: (presumably it is the called one, ack'ing the call, that sets it off)
asciilifeform: trinque: how close does the pnoje have to sit to the lappy ?
asciilifeform: trinque: if you can reproduce this on demand, you can make 'nsa airgap receiver', give lulztalk at some shitcon.
asciilifeform: trinque: was this in the logs ?
asciilifeform: his thing has 6-10hr 'ups'.
asciilifeform: and iirc ben_vulpes works mainly on laptops. what ups does he need.
asciilifeform: (it gets test-drained weekly, also.)
asciilifeform: ben_vulpes: belt and suspenders, my comp worx 100% deterministically if i were to pull out the ups. disk controller battery.
asciilifeform: ben_vulpes: you don't have a mains failure alarm ?!
asciilifeform: if i find that a piece of iron behaves nondeterministically in whatever way (purpose-built rngs aside) -- i throw it out.
asciilifeform: this is the elementary, 0th thing required of a comp.
asciilifeform: ben_vulpes: dunno about you, i don't buy or keep around boxes that randomly lose bits.
asciilifeform: ben_vulpes: none of these liquishits 'work' per sane people definitions of working
asciilifeform: was sop
asciilifeform: mircea_popescu: we had wallpaper AND carpets
asciilifeform: wall carpeting.
asciilifeform: i keep waiting for someone to introduce this fine tradition in usa
asciilifeform: trinque: reminds me of the multiple legends that abound re the old sov habit of hanging carpets on walls. 'we're eastern orcs, we've been doing this since the mongols' -- nope. false. 'it's because of cold cement in hruschev-era flats' -- possible. 'it was so as not to hear the neighbours fuck' -- most likely.
asciilifeform: ^
asciilifeform: ben_vulpes: no moar so than the 'illusion' of the multi-directory hdd
asciilifeform: lol
asciilifeform: ben_vulpes: i think he had that one burned in rom
asciilifeform: Framedragger: 'isolation' in the sense you picture it, would be a useful thing if it actually worked. items like, e.g., vmware, come close, but still no cigar (you can leak bits via cache skulduggery, as discussed every six months or so in the log for past 3+ yrs, and various other ways)
asciilifeform: i saw that pisser befoar!!
asciilifeform: mircea_popescu: rerun !
asciilifeform: i did say separate machines neh
asciilifeform: http://btcbase.org/log/2017-03-11#1625637 << isolation is , at MINIMUM, is when you have a rack of... isolated machines ☝︎
asciilifeform: in other noose, hey, hey, lbj, my CsI:Tl scintillator diode is here
asciilifeform: for whoknowshowlong
asciilifeform: brits still technically in eu
asciilifeform: '49
asciilifeform: since day0 neh
asciilifeform: let'splaypretend.
asciilifeform: hey if there can be a 'latvian army' why not a dutch one.
asciilifeform: happy nato friendz
asciilifeform: basic neh
asciilifeform: naggum was afaik the first to formally write down this observation, in his perl essays
asciilifeform: Framedragger: you will notice that tools which 'invites lazy people to be even more lazy and reckless' proliferate, whereas ones that penalize shaved chimps for being the worthless biowaste that they are, tend to disappear and then have to be excavated from 1km of dirt, or evaporate entirely ☟︎
asciilifeform: forget about python, nobody wants to wait for two weeks for the result.
asciilifeform: Framedragger: ben_vulpes already wrote a block & tx parser, his is the closest we have right now to a usable one
asciilifeform: aah
asciilifeform: mircea_popescu: you have a bash script that parses tx ?!
asciilifeform: must've used bci or one of whatever other heathentrons existed in those days.
asciilifeform: 'On May 13th 2012 we downloaded the full public record of this system in one of its two major forms, which consisted of about 180,000 HTML files. After parsing and processing these files, we built a graph...'
asciilifeform: or hm, looks like they didn't
asciilifeform: Framedragger: if i had to guess -- probably by munging bdb
asciilifeform: don't wait for me ben_vulpes
asciilifeform: ( i , like complete idiot, wanted to 'let's write a quick c proggy like blkcut' )
asciilifeform: nope, and not likely to any time soon, realized that shitoshi left us blocks where you have to PARSE ALL TX TO SPLIT INTO TX motherfucker
asciilifeform: 'Anti-transaction replay in a hardfork'. just for mircea_popescu apparently.
asciilifeform: meanwhile, in heathendom (not quite noose, but lulzy) https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-January/013473.html
asciilifeform: https://archive.org/stream/HarrisonBergeron/Harrison%20Bergeron_djvu.txt << the 20th c. american take on this.
asciilifeform: lol
asciilifeform: i thought philosophy was supposed to distinguish man from rat
asciilifeform: (iirc reiser is what i originally suggested for this experiment)
asciilifeform: but it has own problems
asciilifeform: the 1 fs i know of that MIGHT come close, is reiser
asciilifeform: or rebalances, etc.
asciilifeform: and you don't need variably-sized turds, or deletion, or defrag
asciilifeform: konsoomer fs is liquishit. esp. when you entirely do NOT fit the profile of 'konsoomer', who sits and creates file and is happy is it takes less time than for the enter key to bounce back up
asciilifeform brb
asciilifeform: mircea_popescu: could be interesting to test for double spends 'manually' (using specially written proggy that walks the blox)
asciilifeform: mircea_popescu: you're talking 'substantial rewrite'.
asciilifeform: (permits double spend)
asciilifeform: it isn't clear why to preserve anything else, if this is amputated. it is the very example of 'grandfather's pistol' -- any mistake is a) not necessarily detectable with ANY kind of testing b) potential reactor melt
asciilifeform: without gutting and replacing the entire logic of trb.
asciilifeform: which prevents the use of ANY sane (fixed-length keys to fixed-lenght values) db !!
asciilifeform: and in turn this relies on storing the spend-tx-array (yes) INSIDE the indices db!! http://btc.yt/lxr/satoshi/source/src/main.h?v=makefiles#0713 <<
asciilifeform: sooo mircea_popescu , to revisit upstack , the entire doublespendpreventer mechanism in trb relies on this nonsense , http://btc.yt/lxr/satoshi/source/src/main.cpp?v=makefiles#0855 << is where it marks spent, and http://btc.yt/lxr/satoshi/source/src/main.cpp?v=makefiles#0847 is the doublespendtrap
asciilifeform: 'let's make blocks variable length' 'let's make tx variable length' 'let's make tx INDICES variable and UNBOUNDED length' 'because mother dropped me as a baby'
asciilifeform: and which created 1,001 new problems that had no business existing.
asciilifeform: he did something entirely opposite.
asciilifeform: eeeevery single fucking time i sit down and assume that shitoshi did the obvious, simple, correct thing, and build a hypothetical on ~that~, i later open the binder and find that -- guess what
asciilifeform: (when new block comes in, to lengthen one end or the other of the snake tongue, the antecedent blocks get checked O(N), 'manually')
asciilifeform: if trb is in a state of snake tongue, ALL of the affected tx do not belong in the index table
asciilifeform: the Right Thing, as i see it, is : if a tx is in orphaned block, it does not belong in the index table
asciilifeform: there are two possible places for a duplicated tx: an orphaned (nonlongestchain) block, and a snake-tongue (if you will), one of two fork prongs of equal length, on the leading end.
asciilifeform: however it is possible to handle this sanely:
asciilifeform: namely, that a particular tx can reside in more than one block, if the leading end frays (forks)
asciilifeform: now, there is one nuance ( that i'm not convinced shitoshi adequately dealt with, either , see http://btc.yt/lxr/satoshi/source/src/main.cpp?v=makefiles#0755 for instance )
asciilifeform: (there is no actual reason to cache where-spents! aside from how the tard probably thought 'my db is slow. let's make it store redundant liquishit, that'll help')
asciilifeform: so neither my 'bitcoinfs', nor mircea_popescu's let's-abuse-ext, will work, until this garbage is excised
asciilifeform: he stores TX-WHERE-SPEND lists!!!
asciilifeform: BUT the tard HAD TO, for some reason, make these variably-sized!
asciilifeform: notice, they aren't simply block indices. these'd be fixed length, and might even get reasonable performance in ye olde bdb;
asciilifeform: http://btc.yt/lxr/satoshi/source/src/main.h?v=makefiles#0709 << these are what shitoshi actually stored with the txid