log☇︎
447700+ entries in 0.279s
punkman: I think we need to put a lot more comments on the code, kinda clunky to do through patches to ML though
ascii_modem: there are different schools of thought re how to furnish a room
mircea_popescu: and you don't even know about the used condoms behind the bed headboard
ascii_modem: right now we got an anthill in the living room
mircea_popescu: gotta make the fambly unit work.
mircea_popescu: gotta make the fambly unit work alfie.
ascii_modem: this incident makes it very tempting to just unzip, piss on satoshid, and go ada sanityfork (tm)
mircea_popescu: this is a major problem, and the fact we're looking into it one of the few things giving me solace and better rest at night
ascii_modem: how many other ways for fuckers to wedge us
thestringpuller: d00d i can't spend shit this weekend.
mircea_popescu: so what, is "95% consensus" going to gavincoin next ? for ... all of six blocks again ? cool.
mircea_popescu: anyway, i am very much amused at the way discussion with kakobrekla turned out. 600 hours "oh miners will just so and so " "nobody cares what miners do" ; 1800 "oh miners just so and so'd!!1" "and it turns out nobody cared".
trinque: cool, just wanted to post the link
mircea_popescu: ascii_modem anything will be spiffier than nil neh ?
trinque: added the --coverage flag to all the deps
ascii_modem: only the log
mircea_popescu: what's bitcoind debug toolset ?
mircea_popescu: i dun think i ever used the original.
ascii_modem: from your earlier pastes, mirceacoind has slightly spiffier debug...? than ri
mircea_popescu: im also going to have it unstuck, but i got a shitpile of stuff cooking atm.
mircea_popescu: but for now it can stay as it is, because i think more people were syncing to it.
mircea_popescu: i do intend to replace it with a foundation one as soon as practicable.
mircea_popescu: the original point of this thing i run here was to give all comers the historical chain as is in my custody.
mircea_popescu: now, since you're synced to my level, and you have a full validating node, i see no reason to not open the listen port. do you ?
ascii_modem: gonna plug in the one on dulap when i get home
mircea_popescu: which it's how it's made to work, better fail than be stupid.
mircea_popescu: specifically, what happens if you put the new chain into a node
mircea_popescu: which is why i said, perfect time to test our tools.
mircea_popescu: the only problem is that the clients ain't reorging properly, which needs looking into/
ascii_modem: my node is dead in the water
mircea_popescu: well, just let the chain reorg an' carry on, imo.
mircea_popescu: ascii_modem where were the daily forks b/w january (?) and now ? << costs a little to make one, nobody cared enough. (also lots of manual intervention and general ducttaping at the miner and relayer level - bitcoin is quickly becoming an excellent makework tool, keeping idiots both employed and in a delusion of importance)
mircea_popescu: none of this in any way invalidates anything about the new chain, nor is it a point of concern that i can distinguish
mircea_popescu: this utterly proves that a) the BIP system provides no benefit and should be disused ; b) the peoiple involved with all this nonsense should be muted ; c) voting does not work. nothing here is novel.
mircea_popescu: 4. the people who voted did so as all people voting ever do : blankly, mouth only. then, someone mined a v2 block on top of a v3 block (which to them look identical) and the supposed 95% majority that promised by that vote to distinguish failed to distinguish. well, half of them or so. the other half distinguished
mircea_popescu: and we'll never see an odd hash block for as long as they keep at it.
ascii_modem: where were the daily forks b/w january (?) and now ?
mircea_popescu: this, again, has nothing to do with us. if tomorrow miners decide as a social game to never communicate any blocks they find that hash to odd, it's THEIR problem
mircea_popescu: 3. in order to avoid the situation that happened tonight, a supposed "voting" mechanism was deployed where people switched an irrelevant byte in the blocks they mined, to go from 2 to 3, to indicate they are ready and willing to follow the new rules. ☟︎
mircea_popescu: it'd have been ideal to not import the satoshism in question into bitcoin, but before our time.
mircea_popescu: 2. a voluntary, user-enforced change to the protocol was proposed (iirc by petertodd) where only DER sigs are accepted anymore.
mircea_popescu: so 1. it was observed that the idiots running openssl, who for historical reasons are actually wholesale pulled into bitcoin, decided to fuck up the way they do signatures, which is to say, make items signed come out in rnadom shapes. this is obviously very dangerous for bitcoin
mircea_popescu: lemme lay out the issue here in detail, i think it's mebbe getting fudged.
mircea_popescu: how's it a gavinism to begin with ?
mircea_popescu: this, obviously, would also be where to bury who knows what. but if it's there, nobody's found it yet that i know
assbot: Trust relationship from user phf to user mod6: Level 1: 0, Level 2: 0 via 0 connections. |http://www.btcalpha.com/wot/trust/?from=phf&to=mod6 | http://www.btcalpha.com/wot/user/mod6/
mircea_popescu: the difference between v3 and v2 is , as best anyone can determine, actual fucking validation for the openssl nonsense. hardly avoidable.
mircea_popescu: atm the situation is that block 363730 is forked. one chain, 6 blocks long, proceeds atop a v2 block. the current main chain proceeds from 363730 on v3 blocks. ☟︎
ascii_modem: innit in there now? or am i confused
mircea_popescu: what happens if you import the 7 block alt-chain into the stator ?
mircea_popescu: ascii_modem this is incidentally an exceptional opportunity to test our recent toolset.
mircea_popescu: neway, of more interesting things : confirmed my seeder's stuck on 363736.
mircea_popescu: just because you have one, and it's a very reflective surface, doesn't mean it has one too.
mircea_popescu: i suspect this obviousness is a fruit of your eye, not of the thing you're lookling on. like people perceive souls in cats' eyes.
ascii_modem: not brownian - has very obvious aims (keeping turdalicious-bitcoind in circulation being one)
mircea_popescu: "the enemy" is barely cogent enough to be enmitous at all.
ascii_modem: the enemy accomplished his objective, which probably had something to do with discrediting chinese mines
mircea_popescu: the dead don't know they're dead ; the ridiculous don't know they're ridiculous. the world is well constructed for one's amusement.
mircea_popescu: but whatever, phantomcircuit is still the guy who ran "a security companmy" that oversaw 3 bitcoinica thefts, and still the guy who hacked a python one liner to send every customer an email with the full list of customer emails
mircea_popescu: there are some people that go around introducing themseves as "bitcoin devs" who just spectacularly failed the least controversial soft fork to date.
ascii_modem: so where are the pikes with the headz??
mircea_popescu: apparently in the world we live in, the best way to ensure nobody reads something is to publish it as code anyway
mircea_popescu: consider sign and submit to list.
mircea_popescu: this gotta be a... cultural thing.
mircea_popescu: "wangchunLuke-Jr: I do not know how that v2 pool was relayed, log was lost in a screen session"
mircea_popescu: also lulzy for all the people using blockchain.info to validate txn.
pete_dushenski: mats: aha thanks. just goes to show that there are shades of grey in the braindead morass of veecee moolah, not all are created equal.
mod6: haha. yeah, that too.
mircea_popescu: alternatively they could just shut down and stfu already.
mod6: <+mircea_popescu> here's what's the idea : after botching the soft fork, it seems illogical that the entire bip system should continue at all. << Very much agreed. If someone wants to change something they should write to The Foundation's btc-dev mailing list and submit a patch. And if they can't because they're not in the WoT, well they're not in the WoT. They can make a personal appeal here in person.
pete_dushenski: ;;later tell travispatron you sucked before, you suck now, and you will always suck. enjoy the periphery, derp. ☟︎
pete_dushenski: !gettrust travispatron
mircea_popescu: for the unsubstantiated delusionsm of a few random geeks, working to make the world believe they're knowledgeable and important, bitcoin hiccups every so often.
pete_dushenski: mircea_popescu: it's the broken window/car accident economy
mircea_popescu: so in this sense, BIP 999 : No more fucking BIPs.
mircea_popescu: right. splendid. how about go home and the problem goes away with you.
shinohai: ;;later tell mod6 new build successful and now in sync ...
mircea_popescu: this is EXACTLY how usg works throughout. first, cause black people to be poor and depenedent. then cause them to be violent. then go on press conferences about how "they're doing things about black violence"
mircea_popescu: then they go on reddit to "explain" why what they fucked up isn't their fault, and "what really happened" , and collect cheap applause from the celenterates therein living.
mircea_popescu: an abundance of instances can be documented where they fucked things up
mircea_popescu: there can not be a single instance documented where they did anything useful to any degree or in any sense
mircea_popescu: here's what's the idea : after botching the soft fork, it seems illogical that the entire bip system should continue at all. ☟︎
pete_dushenski: so the numbers are meaningless ?
jurov: yes.. that's why i say numbers are messed up
pete_dushenski: jurov: perhaps ima confoozed, but don't orphaned blocks have to be replaced with valid blocks in the main chain ?
jurov: https://blockchain.info/blocks just the numbering is messed up
jurov: no it reports them as orphaned
mircea_popescu: are they ? i've not looked.
pete_dushenski: mircea_popescu: ok, but assuming those 6 invalid orphan blocks are off on their own, how is it that some sites (eg. bc.i) are reporting that this foundation of sand is still being built on ?
mircea_popescu: pete_dushenski 6 blocks wouldn't necessarily be visible. even three deep reorgs happen with some regularity naturally.
assbot: Logged on 04-07-2015 04:15:35; ben_vulpes: simple rehash of the "let's probe network cohesion strength" fork
mircea_popescu: http://log.bitcoin-assets.com/?date=04-07-2015#1186531 << the clients do seem to run into similar problems eh. ☝︎
pete_dushenski: what i can't figure out is why the hashrate didn't seem to split with the ph0rk...
danielpbarron: jurov, by the time i can get my iphone out of pocket, unlocked, open the recording app, start recording.... the lunatic has already spouted off the gems worth recording
mircea_popescu: one could definitely have existed, on this basis.
pete_dushenski: mircea_popescu: you think there was a big transaction that got double-spent ? or...
mircea_popescu: incidentally, am i the only one finding it a wee bit suspicious that the orphan chain ended up 6 blocks long, ie, exactly the size normally deemed "safe" ?
trinque: danielpbarron: s-stop the surveillance!
assbot: Logged on 03-07-2015 23:48:17; mircea_popescu: http://log.bitcoin-assets.com/?date=02-07-2015#1184704 << dude you gotta wear a recording devince next and have someone transcribe it.
danielpbarron: http://log.bitcoin-assets.com/?date=03-07-2015#1186129 << a tape recorder is the one thing I forgot to bring (I had specifically prepared one for the event but forgot to pack it) -- the mere act of having such a device around free-staters would probably trigger them into a rage ☝︎☟︎