log☇︎
209200+ entries in 0.126s
mircea_popescu: 0000000000000000000000000000000000000000000004 block is valid now, too.
mircea_popescu: that'd certainly be the right way to do it. it's not "must start with 5 0s, it's "must start with 5 bytes equal to prev block's"
mircea_popescu: yeah, but that fixes nothing. as long as you use hashing, you have collisions.
asciilifeform: there is also the possibility of not doing the idiot growing-string-of-zeroes method for difficulty growth
mircea_popescu: this is a fundamental and inescapable problem of usg-style hash functions. stuff like mpfhf mitigate THAT problem, but at a humongous cost.
mircea_popescu: the largest problem being that as difficulty increases, it becomes more and more feasible to simply seek a hash, in comparative terms. considering the disproportion of effect (one gives you a 1/2/2/2/2/2 of 50 btc, the other fucks up the toy entirely) it's a virtual certainty that eventually it will be economically reasonable to divert resources from mining to this hash colliding.
asciilifeform: but with different nodes having entirely different pictures of history, depending on which one they saw first
asciilifeform: you then can have forklets ~merge~, topologically, into what appears to be 1 chain
mircea_popescu: just have to put it in your story of the block
asciilifeform: as i currently understand, both x and y would have to be valid tx, for anything to happen (if y is invalid, it will not be mined).
asciilifeform: mircea_popescu: the obvious interesting sequel to the q, is what would be the first symptom of a colliding pair of tx having been fired.
mircea_popescu: tis been in the logs a few tiems.
asciilifeform: ditto blocks, it is retarded for their hash to uniquely identify them for other calculations
mircea_popescu: which explains a lot of things includingthe miner/node bug
phf: ben_vulpes: oh hey http://btcbase.org/patches/logbot-multiple-channels seems to be broken, missing antecedent for http://btcbase.org/hash/95A0046C0AF25E21DBA310217A289D7649DD86CB89709A89931BFE318A41022FFD4BA9DC046E04DAC1B32BC5304239866BF5CA9AD59328B7DA79B1D06437E273 ☟︎
mircea_popescu: i don't think at the time he did this he had a very clear idea of the mempool / blockchain tx disjunction.
asciilifeform: (i.e. by hash of antecedent, rather than by where-it-is-in-blockchain)
asciilifeform: which is one of the reasons why shitoshi's nonpositional tx indexing is retarded
asciilifeform: mircea_popescu: that's what i ended up concluding
mircea_popescu: asciilifeform the consequences would likely be dire, ie, irrecoverable/invisible variant blockchain
asciilifeform: phf: i suppose the correct term would be 'orphaned' patches
asciilifeform: and the pair -- broadcast
asciilifeform: mircea_popescu: i did not say that it is easy to find. but would like to know the consequences of one being found.
asciilifeform: phf: how did those end up existing ?
mircea_popescu: not so easy to find though.
phf: and finally grapher now properly shows broken vpatches (i.e. ones that don't have all of the antecedents), for example http://btcbase.org/patches?patchset=experimental all polarbeard ones, and my phf-shiva-swank are broken
asciilifeform: given that a tx is >256bits long, these pair necessarily exist.
asciilifeform: mircea_popescu: all you need is an x, y, x!=y, where sha256(sha256(x))==sha256(sha256(y)), and x is a valid tx
phf: (searching through a particular press doesn't work yet)
mircea_popescu: in principle it should not be possible to collide a tx.
phf: there's also a search function that lets you search through patchset, and it shows ~first appearance~ of particular string with corresponding file/vpatch
asciilifeform: nobody but mircea_popescu , hence the q
asciilifeform: mircea_popescu: unrelatedly, didja ever calculate what would happen to trb (or for that matter prb) if one were to produce a colliding txid ?
asciilifeform: mircea_popescu: the hilarious bit is that prb munged up the script system beyond recognition, BUT they kept this turd! merely moved it, http://btc.yt/lxr/satoshi/source/src/script/interpreter.cpp?v=0.10.0rc4#0256
mircea_popescu: people who magicnumber magicnumber, it's just how they go.
mircea_popescu: asciilifeform rat droppings are never found in singlets or how'd that go.
phf: ok, so experimental features on btcbase is that in memory presser now works. each patch has a "tree" link, that shows you a list of files (ones that are explicitly touched by the patch are marked as "modified"), and can look at each individual file
asciilifeform: http://btc.yt/lxr/satoshi/source/src/script.cpp?v=makefiles#0083 << holy fuq the magicnumberola never ever ends
mircea_popescu: you can in principle even have emacs-style "pile of all purpose tests" with refinements etc
asciilifeform: would seem to rely on traditional (push/pull) versionatrons tho
Framedragger: not obvious to some devops bros.
Framedragger: (obviously you need to have written those tests first...)
Framedragger: i thought mouseovers were already there? if you mean timestamps over nicks
mircea_popescu: asciilifeform ci as such is not even a bad idea. compile and run pile of tests frequently, an expansion of "save whenever you stop typing"
asciilifeform: seems like a shit idea tho. 'oops there isn't a trb running on dulap, because ooops i broke the build'
Framedragger: its tests*
Framedragger: (continuous integration is the keyword)
jurov: asciilifeform: "continuous integrastion" - running tests on every commit
Framedragger: guess that's a *good* sign
Framedragger: asciilifeform: where thing builds software and runs it tests every time a change is made. i assume you know his and are therefore asking rhetorically tho
scriba: Logged on 2017-03-11: [21:18:59] <Framedragger> :). one decent part of devops is CI, i thought. it's even mentioned as possibility for trb dev http://btcbase.org/log/2016-05-15#1466922
phf: you've been reading logs too long, if
Framedragger: #trilema is mircea_popescu's constant disappointment, then
mircea_popescu: phf not a bad heuristic, except for the part where 30odd yo is kinda too old to work for a salary just like 20something yo is kinda too old to "work in pr" / http://trilema.com/2010/bani-pentru-piariste/
mircea_popescu: in other news : if your horse is undisciplined it's not the harness that needs improving. it's the horse.
scriba: Logged on 2017-03-11: [21:20:45] <Framedragger> snarky trinque uses ssh and bash for 100 machine setups, too
mircea_popescu: ben_vulpes hey, at least she has the gap!
ben_vulpes: last few times i cracked a pyject, elpy and python-mode and friends proved...resistant to providing utility
phf: that's another reason, why i don't for example, "hack my python with vim like a real hacker". give me the filthiest, most feature rich IDE, where i can just push spacebar to get half of my scaffolding, or whatever kids these days ☟︎
trinque: as I understand it PostgreSQL is more or less "closest thing to oracle without having sold first-born per core"
a111: Logged on 2017-01-24 00:58 trinque: gonna DNS at all, might as well do it at the most-fed ministry
phf: when you're an astrologer, choose the client that pays the most? hmm, pissed opportunity there
a111: Logged on 2016-12-28 18:31 asciilifeform: 'when choosing astrologer, hire the cheapest'
phf: in my experience places that have oracle tend to pay best rates, and paraphrasing http://btcbase.org/log/2016-12-28#1592046 when choosing a zaibatsu to pledge allegiance, choose the one that pays the most ☝︎
ben_vulpes: jurov: i suppose that i'm pretty lucky to have never worked under anyone who thought oracle worth including in the matrix
ben_vulpes: once the category of sv finger-trap is introduced, every option must demonstrate that it is /not that/.
jurov: "let's buy oracle, they are solid"
ben_vulpes: "hey boss, this looks like something written to suck devs into paying a consulting company to fix bugs in their own software, shall we introduce it as a dependency in our stack?"
ben_vulpes: time-cost of audit impossible to estimate at least, and if so and security is a concern, why bother.
jurov: it is always incredible hairball of code, impossible to audit anyhow
ben_vulpes: time would be better spent curating a tumblr full of naked girls and american muscle
jurov: don't forget the part about proper management of secrets on the master and general resilience of master against attacks from clients/minions
ben_vulpes: rots the mind
Framedragger: what can i say, too much HN for me
ben_vulpes: Framedragger: 'tisn't as though hftbro is exhaustive banger-on of every dumb thing, just the ones he's faced with
Framedragger: i guess retort it "call me when you have 100 machines to adminster, kid"
Framedragger: snarky trinque uses ssh and bash for 100 machine setups, too
trinque: oh good then.
Framedragger: i agree, start from tests, of course.
Framedragger: (even hft guy doesn't have anything bad to say about ansible)
ben_vulpes: Framedragger: dude start by writing some tests mebbe
a111: Logged on 2016-05-15 15:56 mod6: what i also want to build is a CI thingy for trb
Framedragger: :). one decent part of devops is CI, i thought. it's even mentioned as possibility for trb dev http://btcbase.org/log/2016-05-15#1466922 ☝︎
jurov: Framedragger: experimenting really helps. i tried saltstack lightly, and the communication between master and minions was incredibly unreliable
Framedragger: the buttsex jokes are for reading teabreaks
Framedragger: "if you like report, pay bitcoin to this foundation address here -> " hey maybe one day it'll even happen
ben_vulpes: "can you give us a tldr, kiddo?" "NO TLDRS ARE FOR FAGGOTS SIX MONTHS STARTS YESTERDAY"
ben_vulpes: heh now i'm imagining a research report which is just a link to log line
trinque: oh hey teh forum works
Framedragger: @all thanks to this chat i'll now make some urgent recommendations to startup i'm involved with. maybe it's not even gonna be fucked in the ass if moves decisively away. a bit ashamed i had $opinion on $thing-not-researched in the first place. ☟︎
ben_vulpes: that's what they sell on, but it turns out that the insulation is measured in briefcases of hundies
jurov: yes hear, they insulated the app from pebkac well
jurov: glad I've never used docker. apparently they succeeded to reimplement oracle-corp-bezzle without backward compat, wd!
ben_vulpes: critical production as distinct from toy production?
Framedragger: (anyway, i never would have recommended to use it in critical production. but looks like it's shit for personal local machine projects, too)
Framedragger: trinque: not trying to redeem it any longer, at all, simmer down (but you were right.)
trinque: understand the only thing it exists is so some faggot at a web startup can make his makework job even more complicated so he can hide the fact (mostly from himself) ~that he produces nothing, and is nothing~
trinque: why teh fuck are you still trying to redeem it
trinque: you're not speaking to people who have not done this ~for long periods of their adult life~
asciilifeform: those hoses, they want to connect.