log☇︎
153400+ entries in 1.199s
mircea_popescu: this is neither a bad idea nor in any sense avoidable. because, again, without it we'll fork daily.
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: how's it a gavinism to begin with ?
ascii_modem: we involuntarily backport a gavinism?
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. ☟︎
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.
mircea_popescu: yet he's still walking around as if he were somehow still a person.
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: 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"
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.
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.
mircea_popescu: there can not be a single instance documented where they did anything useful to any degree or in any sense
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" ?
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 ☝︎☟︎
trinque: jurov: according to this you lose a lot of detail, i.e only get statistics for the line of the macro call http://codingfreak.blogspot.com/2009/02/gcov-analyzing-code-produced-with-gcc.html
trinque: mircea_popescu: I'm sure I'm about to see a nightmare when I pull the deps into the gcov thinger
assbot: 1 results for 'openssl monkeys' : http://s.b-a.link/?q=openssl+monkeys
mircea_popescu: fork's only been actually resolved a few hours ago.
williamdunne: jurov: Quite a bit further IIRC
fluffypony: is that a post-coital penis joke?
williamdunne: I'm not going to disagree with you completely, but I do still believe that S&P500 beats inflation by a couple of percent
trinque: I'm sure they used to mean something else, but we're in bizarro land where the length of a meter changes day to day
assbot: A Random Ass Kicking of Wall Street | Following the Trend ... ( http://bit.ly/1LKBFH4 )
williamdunne: http://www.followingthetrend.com/2015/06/a-random-ass-kicking-of-wall-street/
trinque: I am seeing a bunch of ERROR: AcceptToMemoryPool() in my stator run
danielpbarron: https://bitcointalk.org/index.php?topic=1108304.0 >> F2Pool is building on a wrong side and there is fake confirmation since block 363731. (EDIT: the bogus chain of 363731 is already orphaned and not relevant to normal users)
danielpbarron: the one stuck at 36 is not limited to one seed, but it is running 0.5.3.1ish on a pogo with archlinux
asciilifeform: (not a connectivity problem - i'm getting mempoolisms just fine)
mod6: <+asciilifeform> has anybody as of this moment received a block past 363734 from mircea_popescu's node ? << im a day a way or so yet
williamdunne has a mailing list of 13,000 bitcoiners
punkman: heh "I shook hands with the man I did most of the talking with and they took off... I was a little shooken up but realized I made a big mistake! I forgot to shake the black police detective's hand... shit!!! "
asciilifeform: has anybody as of this moment received a block past 363734 from mircea_popescu's node ?
asciilifeform: ;;later tell mircea_popescu i built stator on dulap just now. unchanged from public recipe other than the 'realpath' thing (mentioned earlier.) same process ought to work on your other centos boxes. it will run as a public node as soon as i shove a blockchain in there.
phf: asciilifeform: i have a small backlog of things i want to send to the list, i'll wrap it up sometime over the weekend
punkman: maybe we should add a .conf option that lets whoever really wants it to skip VerifySig between checkpoints ☟︎
punkman: no-verifysig-skipping stator reached 169k, so I'm gonnna call this a success for now.
asciilifeform: http://log.bitcoin-assets.com/?date=04-07-2015#1186991 << nah, more practically, a few dozen MB (sha512 sums) ☝︎
cazalla: now and then i've thought of the few teacher's aids that would come for a school term as part of their studies.. they were so young and pretty but would be old bags now
assbot: New Bitcoin vulnerability: A transaction that takes at least 3 minutes to verify ... ( http://bit.ly/1HD6BHo )
punkman: cpu mining code probably needs more than a couple fixes
punkman: petertodd: "Honestly I was half-expecting this to happen, and was actually busy writing up a warning for SPV wallets users when this issue came up."
mircea_popescu: oh a mistake ? aww.
punkman: "We are using 10.2 but got this message anyway: "Your node software is out of date and may accept an invalid blockchain fork. Do not trust confirmation."" "There was a mistake made and an alert that showed up on v0.10.2 was sent out accidentally; should be now fixed."
punkman: I just started a stator patched to not skip VerifySignature, wonder if it'll work this time
midnightmagic: (but Perelman's a safe bet because he's a recluse and there's no possibility of that image ever being shattered)
midnightmagic: Nobody wears a halo to me. Well. Maybe Grigori Perelman..
mircea_popescu: sort-of like how rassah bought a car or some guy bought a pizza.
mircea_popescu: to most everyone else, gavin's just another washed up website designer with a great story from five years ago.
midnightmagic: No, not to me. He wears the halo that makes large audiences cheer for him instead of throwing spitballs, when he says he should revoke everyone's commit access and be a dictator.
mircea_popescu: he only wears the halo ~to you~. because you're a particular sort of inner build, and because you ate a particular diet.
mircea_popescu: heck, kenna and the armandi fellow are prolly due for a novel attempt too
mircea_popescu: every bum drunk has a story of greatness. go, listen. care.
mircea_popescu: and lawsky's going around trying to scam people like a resurected antonopopo derpopopop.
mircea_popescu: next time they'll need some they... ahem... won't read b-a logs etc once more.
midnightmagic: Externally combating a blocksize increase with articles, comments, and discussion external to -ass.
mircea_popescu: i think what ? how is this even a problem ?
midnightmagic: :-P No, just wondering why you think anyone else is more capable than you are at ensuring a value-destroying fork doesn't happen.
mircea_popescu: it's a complete re-write. ask anyone.
assbot: Logged on 04-07-2015 06:24:27; midnightmagic: Unless you are implying people outside the bitcoin world are voracious readers of the -ass logs, as far as I can tell in all the articles, reddit posts, twitter feeds, etc, I don't see more than a passing mention. But even if that weren't so, really I'm a little disappointed the wind all went out of your sails, as it were.
assbot: Logged on 04-07-2015 06:18:37; midnightmagic: it's all a question of how much you trust your ability to make code that converges on consensus. are you so awesome you can either sit on an old openssl, or write your own replacements? are you so godlike you can write testcases for every corner-case, bugs and all? I know I'm not. Maybe you guys are. I dunno.
mircea_popescu: http://log.bitcoin-assets.com/?date=04-07-2015#1186854 << it's a complex mess. satoshi generally wrote stuff that didn't actually work for the intended purpose. it is very far from inconceivable we shall in a year discover a fundamental bug in any of a dozen dozens different essential components. ☝︎
mircea_popescu: this is not actually a rational reason to wait.
midnightmagic: No, but I do know for a fact that procrastination has saved my life at least six or seven times. :)
mircea_popescu: it is in point of fact better to have a static build that specifically ennumerates blocks prior to height X and then proceeds from there, than to have the present situation.
midnightmagic: Almost like a sort of mass-ennui/retirement mentality. Tired of working for something they don't believe in anymore.
assbot: Logged on 04-07-2015 06:11:21; midnightmagic: well, then we have the forking risk I mentioned above: what happens when the openssl people make a fix or the internet finds a bug in the component that we depend on? If we sit on 0.9.8 or whatever the version was before those idiots got their hands on it and started adding malicious exploits, what happens?
mircea_popescu: http://log.bitcoin-assets.com/?date=04-07-2015#1186847 << while this problem exists, i think the case that it is strictly preferable to attempt building a functional system than to bemoan one's fate of having been born to parents this poor, stupid and useless needs not be further pressed. ☝︎
assbot: Logged on 04-07-2015 06:06:14; midnightmagic: I'm familiar with the DER-encoding change they made, and I'm aware of, if not familiar with, every major bug in openssl since 2001 or so. Could I draw a line between releases that had bugs and releases that fixed them? No. Not even close.
mircea_popescu: which may be a valuable thing.
mircea_popescu: http://log.bitcoin-assets.com/?date=04-07-2015#1186723 << it has historically proven to have been a massive mistake, perhaps the largest mistake on record, that people in the early f/oss made to argue on supposed technical merits and play-pretend the "impartial scientists". ☝︎
assbot: Logged on 04-07-2015 04:47:46; decimation: I would say that on its face, bip66 isn't such a terrible idea
mircea_popescu: http://log.bitcoin-assets.com/?date=04-07-2015#1186389 << for a long time in 2012/2013 there were "gencoin only" miners, at the peak doing like 15% ish of total hashing ☝︎
assbot: Logged on 04-07-2015 02:46:46; asciilifeform: what i think would be considerably more useful is a provision for 'programmable checkpoints'
mircea_popescu: http://log.bitcoin-assets.com/?date=04-07-2015#1186358 << also touched upon in here a few times. definitely the right way to do this. ☝︎
mircea_popescu: currently the cannonical b-a log service is http://log.bitcoin-assets.com
thestringpuller: midnightmagic: there really isn't news. just gavin/hearn having a temper tantrum like a little kid because they want more subsidies for poor people.
decimation: I think there's a general ambivalence about what bitcoin-devs want or do
decimation: midnightmagic: yeah actually we are mostly focusing on building a working, sane bitcoind
decimation: yes. ultimately this is war, and we have a strategy
midnightmagic: Maybe my appraisal is just wrong. Could be. Seems to me they're just taking a breather to set up the schism.
ben_vulpes: <midnightmagic> ben_vulpes: Dude man, with the shit you guys say in here, I have no idea when you're ribbing someone, or promising a spear in the gut. :( << the ambiguity has to be completely intolerable
ben_vulpes: you're not in line for a stake
midnightmagic: ben_vulpes: Dude man, with the shit you guys say in here, I have no idea when you're ribbing someone, or promising a spear in the gut. :(
decimation: with respect to bip 66 in particular, it's not a terrible idea, but it strikes me as backwards
decimation: umm, why would we give a shit about what they are saying otherwise? I donno bro, you're the one accusing here.
midnightmagic: What? He's pushing his BIP and pullreq, and Hearn is busy doing pullreqs which he knows doesn't have a chance of making it.
trinque: gonna let this run for a while, then I'll share the results
trinque: gcovr outputs a nice html version of the gcov output
midnightmagic: I presumed your head would explode if I mentioned forbes (due to its primary bitcoin author being a douchebag), or mainstream media.
ben_vulpes: for a grand coup of shit-as-what-don't-matter?
midnightmagic: Unless you are implying people outside the bitcoin world are voracious readers of the -ass logs, as far as I can tell in all the articles, reddit posts, twitter feeds, etc, I don't see more than a passing mention. But even if that weren't so, really I'm a little disappointed the wind all went out of your sails, as it were. ☟︎
decimation: he did a few times, rather unimpressively
midnightmagic: For a while you were writing reddit posts and qntra articles and all sorts of stuff. Half the time you got Gavin himself "derping" as you put it, in your comments.
assbot: 43 results for 'usgavin' : http://s.b-a.link/?q=usgavin
midnightmagic: it's all a question of how much you trust your ability to make code that converges on consensus. are you so awesome you can either sit on an old openssl, or write your own replacements? are you so godlike you can write testcases for every corner-case, bugs and all? I know I'm not. Maybe you guys are. I dunno. ☟︎
decimation: ideally, writing a damn spec first