assbot: Logged on 03-07-2015 00:07:59; trinque: asciilifeform: the thought actually was... "so emacs is a sort of masamune... lol!"
mircea_popescu: now that usg finally arrayed enough ethereum shitfountains to imagine it can pull it off, the tune changed. and it changed mid sentence and full spin around.
mircea_popescu: this is why i have people doing summaries of the shit, which summaries i generally do not read.
mircea_popescu: i dunno how or why it'd be worth anyone's time, outside of the perverse interests of entomologists etc.
assbot: Logged on 03-07-2015 01:27:53; asciilifeform: shinohai: mircea_popescu has one up
shinohai: on block 217340, will publish ip when synced fully
assbot: Logged on 03-07-2015 01:34:33; asciilifeform: all i can personally say about this is that it serves up (big fat surprise!) apparently correct blocks
assbot: [MPEX] [S.MPOE] 17321 @ 0.0005028 = 8.709 BTC [+] {2}
assbot: Logged on 03-07-2015 01:39:38; asciilifeform: or does it open ordinary sockets and expect a tcp stack
assbot: Logged on 03-07-2015 01:54:30; decimation: if house always wins, people will realized and move on
assbot: Logged on 03-07-2015 01:56:25; asciilifeform: whose only purpose is to be one of the 'provably fair' winners that day
assbot: Logged on 03-07-2015 02:19:38; trinque: the docker daemon itself is this vast wad o' golang that runs as root
mircea_popescu: nobody could distinguish its output from normal reddit functioning.
mircea_popescu: this difference is a lot more marked than the subtle contortions the supreme court's been using these last years to rule in favour of unexamined hipsterism
assbot: Logged on 03-07-2015 11:01:01; jurov: plus some utterly vexing and hapless dreams gratis
assbot: [MPEX] [S.MPOE] 103350 @ 0.00051533 = 53.2594 BTC [+]
assbot: Logged on 03-07-2015 11:58:29; jurov: she wore out several of them
assbot: Logged on 03-07-2015 12:03:45; diana_coman: very solid for a piece of thread basically :)))
assbot: Logged on 03-07-2015 13:37:30; decimation: oh no the reddit owners treat the tens of thousands of people that work for them for free as slaves!
assbot: Logged on 03-07-2015 23:58:23; mircea_popescu: this is rank nonsense if you think any about it. the only part of sex that's in short supply is the erect penis. everything else is overabundant. how exactly would the owners of the only rare part be paying anyone for anything whatsoever ?
assbot: Raising Darwin's Consciousness: An Interview with Sarah Blaffer Hrdy on Mother Nature - The Primate Diaries - Scientific American Blog Network ... (
http://bit.ly/1GVaeVi )
assbot: Raising Darwin's Consciousness: Sarah Blaffer Hrdy on the Evolutionary Lessons of Motherhood - The Primate Diaries - Scientific American Blog Network ... (
http://bit.ly/1GVafIN )
assbot: Raising Darwin's Consciousness: An Interview with Sarah Blaffer Hrdy on Mother Nature - The Primate Diaries - Scientific American Blog Network ... (
http://bit.ly/1GVafZf )
assbot: Logged on 03-07-2015 17:50:03; phf: i was exploring block storage format, so i wrote some lisp code to read blocks out of .dat in sequence or directly from dumpblock'ed file
http://paste.lisp.org/+38JG. i'm not sure where i'm going with it, so i'm leaving it here for interested parties.
ben_vulpes: asciilifeform: blockchain->sexprs or ragel parser
ben_vulpes: leading any charge is risky and painful
ben_vulpes: asciilifeform: that cutblock c util was very instructive, ty
☟︎ ben_vulpes: phf: (v. instructive among other good things)
assbot: Logged on 03-07-2015 11:58:29; jurov: she wore out several of them
phf: ben_vulpes: like asciilifeform said there are better approaches, but yw
phf: the general pattern is a bunch of read-* functions, that are all ultimately reduced to read-byte or read-sequence. the an (unsigned-byte 8) stream and return whatever datrastructure
punkman: I think the problem was I didn't have "realpath"
assbot: Logged on 03-07-2015 21:35:10; kakobrekla: the switch happens when there is 90% of miners on the new chain (determined by checking last n blocks rolling window)
assbot: Logged on 03-07-2015 21:48:42; mircea_popescu: meh. what causes optic mice to acquire pointer jitter ?
assbot: [MPEX] [S.MPOE] 96700 @ 0.00051396 = 49.6999 BTC [-] {2}
assbot: Logged on 04-07-2015 00:47:53; ben_vulpes: asciilifeform: that cutblock c util was very instructive, ty
trinque gets a funny feeling like he's watching a fast-forward replay of history itself whenever syncing a new blockchain
trinque: all the events which transpired which are marked by a particular transaction
trinque: deedbot- fascinates me for precisely this reason
assbot: [MPEX] [S.MPOE] 55900 @ 0.00051544 = 28.8131 BTC [+] {2}
trinque: pulled the trigger on this one just to see whether it'd fire up and work, but yeah, I'll use mircea_popescu's node for the gcov run
trinque: I am currently syncing from deedbot-'s node
trinque: oh, I am using stator with no additional patches
trinque: which others should I apply?
decimation: asciilifeform: it's lulzy that they regulate the shit of out freon for hvac, but use in fire extinguishers?
decimation: seems like co2 would be useful for many situations
punkman: ok, stator compiled successfully I think, anyone wanna give me a node IP?
assbot: [MPEX] [S.MPOE] 107000 @ 0.00050961 = 54.5283 BTC [-] {3}
decimation: why do half the distros use it, others use readlink
trinque: I'm going to grab some food, then read up on gcov
DanyAlos: Sorry for the sudden change of topic:
assbot: [MPEX] [S.MPOE] 40900 @ 0.00051748 = 21.1649 BTC [+] {3}
assbot: Logged on 03-07-2015 01:28:04; asciilifeform: 188.68.240.167
punkman: asciilifeform: it's working, good job on the stator
punkman: it complained about getaddrinfo, that's to be expected then?
punkman: yeah I tried to find it in the src, nothing there
mats: DanyAlos: this channel has the flag +s, and so it is unlisted
punkman: yeah I don't pull back from github, only push
decimation: I'm syncing static node with some random ip, to see if I get the same blkxxxx.dat results
decimation: asciilifeform: did we do a thread on 'headers only' block data?
decimation: it occurs to me that it would be useful to broadcast a digest of a block in addition to the actual block data
decimation: mainly for users on bandwidth constrained channels
decimation: For something like shortwave broadcast, this is what you would want
decimation: aye, that would be useful for a 'starter pak' node
decimation: one wonders why this hasn't been done already, seems an obvious fix to 'node takes forever to sync'
decimation: yeah okay, that would be useful for double-checking chain integrity yes
decimation: for the headers thing, I'm imagining a scenario where someone is waiting for a transaction to clear
decimation: it would be useful to know when a new block is found, so you can ask your peers for a copy
decimation: I suppose if a peer is available, you could do that. but then you are only trusting one node's say
decimation: imagine three frequencies with three different nodes around the world, all with agreement on headers
decimation: at any rate, I'm imagining ways to sew parachutes before they are needed
decimation: unfortunately with the effective bandwidth needed by the current blockchain makes global synchronization quite expensive
decimation: weird, the last four blocks had no transactions
decimation: I guess as long as they find a block that matches difficulty it will be valid
decimation: it would sure make it simpler to devise a big asic machine to find hashes if it doesn't need to bother with transactions
decimation: the big blocks are running nearly a mb or so
assbot: [MPEX] [S.MPOE] 90320 @ 0.00051341 = 46.3712 BTC [-] {2}
decimation: asciilifeform: maybe the naked blocks are a counterpoint :)
decimation: 5 blocks. 4 are attributed to f2pool, one to antpool by blockchain.info
assbot: [MPEX] [S.MPOE] 13830 @ 0.00051629 = 7.1403 BTC [+]
punkman: didn't those guys want 8mb blocks?
decimation: asciilifeform: I've tried printing such things before, even on a big plotter the results are disappointing
decimation: plotter is usually limited to 4 ft rolls I think
decimation: sure, but you gotta spend time massaging the graph into something legible even at that size
decimation: what comes out of 'dot' tends to be fucktarded with complex graphs
decimation: to be clear, my experience is mainly with feeding dot such things, not from codeviz
decimation: I think you can massage valgrind to dump callgraph
mod6: <+asciilifeform> mod6, ben_vulpes ^^^ who wants to try << i might be able to give it a go later this weekend ... maybe.
decimation: as in, all possible routes into and out of functions?
mod6: any idea how old of a version is required?
mod6: ah, i can give it a go with something as old as like 4.5.4 for sure.
mod6: maybe even 4.0.4 (if it'll build)
decimation: the egypt thing appears to have limited support for C++
cazalla: apparently network forked or some business
assbot: F2Pool is not properly validating blocks, their fork is winning temporarily. SPV clients and Blockchain.info are inaccurate : Bitcoin ... (
http://bit.ly/1Kzrh5m )
assbot: [MPEX] [S.MPOE] 10653 @ 0.00051757 = 5.5137 BTC [+]
decimation: it does seem blockchain.info and insight.bitpay.com have two different chains
punkman: "BIP66 protocol rule changes have gone active in part thanks to Antpool and F2Pool's support of it - but their pool appears to not actually be enforcing the new rules, and is now mining invalid blocks."
assbot: [MPEX] [S.MPOE] 84234 @ 0.00051578 = 43.4462 BTC [-] {3}
punkman: "SPV nodes and Bitcoin Core prior to 0.10.0 may get false confirmations, possibly >6 blocks long, until this is resolved."
mats: so you're saying now is the time to fleece bitpay
assbot: [MPEX] [S.MPOE] 66300 @ 0.0005095 = 33.7799 BTC [-] {2}
gribble: Current Blocks: 363736 | Current Difficulty: 4.940201493122746E10 | Next Difficulty At Block: 364895 | Next Difficulty In: 1159 blocks | Next Difficulty In About: 1 week, 0 days, 13 hours, 48 minutes, and 14 seconds | Next Difficulty Estimate: None | Estimated Percent Change: None
decimation: and apparently several folks fucked it up too
decimation: so this 'IsSuperMajority' code is totally absent in 0.5.3.1
mircea_popescu: <asciilifeform> they'd just all happen to be employees of the house. << if you only divulge winning tickets you get the natural occurence of winners + extras.
mircea_popescu: <asciilifeform> ben_vulpes, mod6, mircea_popescu, et al: anybody interested in multiprocessorizing bitcoin sig check ? << i don't see the benefit.
☟︎ decimation: do they reject 0.5.3.1 blocks because the nVersion = 1?
mircea_popescu: <assbot> Raising Darwin's Consciousness << all this "consciousness" bs reads to me like direct pastiche from "class consciousness" or however that nonsense was translated to english
mircea_popescu: i don't run one so nfi what its problem would be. ion all likeliness something stupid.
mats: looking forward to seeing the post mortem in the morning
mircea_popescu: <ben_vulpes> of the active users. << well, like a dozen or so people, spent a month in game last month. so like, 2 hrs / day or somesuch
mats: and hopefully discount coins
mircea_popescu: heh we actually are forked nao. i dun see any such 738
decimation: yeah I think we were forked a long time ago actually
assbot: Logged on 04-07-2015 03:50:47; mircea_popescu: <asciilifeform> ben_vulpes, mod6, mircea_popescu, et al: anybody interested in multiprocessorizing bitcoin sig check ? << i don't see the benefit.
mircea_popescu: none of my nodes verify the imaginary 737-738 blockchain.info claims to exist.
phf: somebody was saying bitcoind doesn't build on a 32 bit system?
mircea_popescu: i guess they eventually settled on pretending it's an accident or what ?
mircea_popescu: i dun see another peer other than the 148 above that claims to have 738
mircea_popescu: ( cat debug.log | grep -B3 "blocks=363738" if nothing else)
mircea_popescu: anbd how teh fuck does it continue on an orphan block anyway
ben_vulpes: "However, this also means they're not checking the new BIP66 rule, and are now mining invalid blocks because of it. (another miner happened to create an invalid, non-BIP66 respecting block) If you're not using Bitcoin Core, you might be accepting transactions that won't be on the longest valid chain when all this is fixed." << curious to see if 0.5.whatever comes out on top at the end of this
ben_vulpes: my position being "if your notion of a valid block has to patch 0.5.*, get fucked."
decimation: yeah but this apparently happened awhile ago
decimation: when they put the IsSuperMajority code check in
ben_vulpes: "The majority of hashing power is mining an invalid chain - it's not going to "win" - they're just wasting their effort." << euheuheuheuheuheheehueheuheuheehu
ben_vulpes: simple rehash of the "let's probe network cohesion strength" fork
☟︎ mircea_popescu: ben_vulpes wait, the usg dept of stupid is now on the record that miners don't, after all, decide ?
ben_vulpes: so what, f2pool and phrenz dies next week?
mircea_popescu: anyway, foundation ppl : plox to make a statement on this matter
ben_vulpes: "Except BIP 66 received 95% support from the relevant group (miners). " << ehuehuehehueeueueueueueeeee
mircea_popescu: gotta explain to the masses 1) how irresponsible it is to empower scammers, whjether they call themselves "pirate", "Gavin" or anything else
mircea_popescu: BIP66 protocol rule changes have gone active in part thanks to Antpool and F2Pool's support of it - but their pool appears to not actually be enforcing the new rules, and is now mining invalid blocks << lulzy.
ben_vulpes: Bitcoin 0.5.3 is the canonical reference implementation. If a fork occurs and one side validates on the 0.5.3 codebase while the other does not, the chain that validates under 0.5.3 is the only valid chain.
mircea_popescu: Bitcoin Core (after 0.10.0) rejects these invalid blocks, but a lot of other stuff doesn't. SPV Bitcoinj wallets do no validation what-so-ever, blindly following the longest chain. blockchain.info doesn't appear to do validation as well; who knows what else? <<
mircea_popescu: anyway, todd is right. the only way this affects us is that we don't really give much of a shit.
ben_vulpes: mod6 if you feel compelled to elaborate on this, go ahead.
ben_vulpes: i have a porch of meatwot and babes that actually need attending to.
mircea_popescu: i have nfi how the power rangers imagine they'll manage a hardfork when they can't as much as get a "relevant support" softwork that's fairly uncontroversial.
ben_vulpes: i've not yet accepted this soft/hardfork duality.
ben_vulpes: things either validate under 0.5.whatever or they don't.
mircea_popescu: well, any people can at any time decide to narrow the rules. this makes some sense.
decimation: actually I think this is gonna be fine on 0.5
mircea_popescu: the idea is they don't want to see some stuff that validates anymore
mod6: <+ben_vulpes> Bitcoin 0.5.3 is the canonical reference implementation. If a fork occurs and one side validates on the 0.5.3 codebase while the other does not, the chain that validates under 0.5.3 is the only valid chain. << I have nothing further to add to this at this time.
decimation: the problem is that 0.5.3 blocks generated by 0.5.3 won't validate if those IfSuperMajority rules check
mircea_popescu: decimation provided their "mine support" actually materializes
decimation: because they already did a 'softfork' on the nVersion
decimation: I'm not sure if there are enough blocks to trigger it
ben_vulpes: mircea_popescu: anyone can narrow the rules, but whether that's "bitcoin" is an open question.
mircea_popescu: i dun see it. the rule is "come to school dressed". if you all agree to wear skirts or all agree to wear cardigans, it's still school.
ben_vulpes is also curious to see how much "political capital" the derpdation burns today
decimation: if (block.nVersion < 2 && IsSuperMajority(2, pindexPrev, consensusParams.nMajorityRejectBlockOutdated, consensusParams))
ben_vulpes: i never did anything, we all know that. joke's almost too easy.
ben_vulpes: "Updating to the latest when what you have works is how you break things.
mircea_popescu: anyway, this is jit to lay kakobrekla's wonderments to rest.
ben_vulpes: "They're not running full nodes because the current 500KB blocks are too big.
assbot: [MPEX] [S.MPOE] 32404 @ 0.00051768 = 16.7749 BTC [+]
ben_vulpes: reddit, for all the silencing and muting of the actual bitcoin foundation, seems to be turning the corner on sense
ben_vulpes: "Most likely this is caused by broken-by-design-for-profit mining code, but none of their stuff is open source AFAIK. Maybe more details will be known with time."
ben_vulpes: ;;later tell lukejr listen you gotta stop it wiht this "i can tell miners what's right and wrong" bs
mircea_popescu: why ? he's a god fearing rotinculo from wisconsin or whatever.
mircea_popescu: on the record having lied for profit and all that good stuff, but why should anything matter.
ben_vulpes: man all i can do is nail this coffin closed
ben_vulpes: hey kakobrekla how much can i cram into a rating field?
ben_vulpes: i want a man in the ground, i don't make that dependent on his wife squirting or w/e
mircea_popescu: Uh oh all these block explorers just flipped over to the invalid chain:
☟︎ mircea_popescu: "Current status: F2Pool still broken; Antpool fixed (but no promise they won't intentionally re-break in the future)." is really all that one needs to lol
decimation: this is the dumbest fucking thing I've seen in all my years with bitcoin
decimation: if there's any reason why bitcoin will never be adopted, it's this kind of shit
mircea_popescu: nah, the "we'll move to this new db system one schmuck that gofer'd coffee at google wrote with his chest hairs and nobody tested in any way" was the stupidest sahit
ben_vulpes: meaning adopt the power ranger braindamage again?
mircea_popescu: but the "we'll make wallet a plaintext file" and the "we'll target windows" and the "you know what's better than boost ? qt!" were pretty epic turn points too
mod6: shinohai: is your v0.5.3.1-RELEASE node up to dayte?
☟︎ mircea_popescu: i don't think any sane nodes can be up to date atm, until this resolves.
mircea_popescu: anyway, having been duly amused for the evening, i retire to my eulorean empire.
mod6: the hope was to find if he can verify if v0.5.3.1 rejected or accepted the blocks in question; 363738
trinque: just deleted muh blockchain to resync
mod6: mine is currently sync'ing against mp's seed.
trinque: this laptop has not infinite gigs
trinque: was syncing pretty quick, but I stopped and deleted for to be syncing against mircea_popescu's node
trinque: got to like 150k I think before I stopped
ben_vulpes: i thought you were running a conformal impl somewhere
trinque: I am, how is it handling what though
trinque: would the logs be interesting in any way?
mod6: sure, dpaste 'em up for maxtime
ben_vulpes: "the chain that is the real chain is the chain that verifies under 0.5.3"
ben_vulpes: this is almost as bad as defining a word with the word to be defined
trinque: man chrome sucks at big pastes
decimation: 'you may not be interested in a fork, but...'
ben_vulpes: mircea_popescu, mod6, asciilifeform: i don't see a reason to make this much more than 25 words. do you think much detail or polemic is necessary here?
decimation: better to say less until we know wtf is going on
ben_vulpes: perhaps a hash of the codebase instead of the semver crap?
ben_vulpes is somewhat at sea w/r/t propaganda semantics
decimation: I would say that on its face, bip66 isn't such a terrible idea
☟︎ decimation: but the way it's being forced is pretty stupid
mod6: s/must be considered/is a/ ?
decimation: yeah, it's not the bip66 issue, it's the mechanism they inserted for forcing change
ben_vulpes: well this signature issue is tricky as shit already - openssl is already blowing up validating the chain with anything other than...
ben_vulpes: what was the version number of openssl we determined necessary to validate the full chain?
mod6: otherwise we had issues on 168`001 iirc
mod6 doublechecks the SoBAs
decimation: 'please sir, accept my resonable patch in exchange for agreeing to forever accept what 'our mechanism' brings'
decimation: although as I've noted, they already incremented this machine
assbot: [MPEX] [S.MPOE] 8100 @ 0.00052134 = 4.2229 BTC [+]
decimation: asciilifeform: I can already hear jwz saying that he doesn't want politics, just to do the right thing
ben_vulpes: an informal signoff from y'bosses would be nice before i deposit this in the white porcelain turdotron
assbot: [MPEX] [S.MPOE] 33230 @ 0.0005207 = 17.3029 BTC [-] {2}
ben_vulpes was looking through recent "bitcoin-core" pull requests, found many integration testing scripts
ben_vulpes: looks like the shitgnomes have been working overtime to address my complaints.
ben_vulpes is amused, but not honored. if ye'd only had actual management once upon a time, this'd not be a notable achievement.
assbot: Logged on 21-01-2015 02:48:11; Luke-Jr: it can't, if you don't have the 0.8.1 hardfork patched in..
mod6: ok mp says he can see signing that statement ben_vulpes. go ahead, he'll even sign later when he gets on his other box.
assbot: Logged on 21-01-2015 02:59:30; mod6: it was selected because "reasons"
assbot: [MPEX] [S.MPOE] 33267 @ 0.00052134 = 17.3434 BTC [+]
mod6: <+ben_vulpes> << this still hurts, every time i see it << awe!
decimation: where did this consensus shit enter into the code base?
mod6: anyway, you think i should have just called him out instead of saying "reasons"?
assbot: [MPEX] [S.MPOE] 84850 @ 0.00052155 = 44.2535 BTC [+] {2}
ben_vulpes: "reasons" being that i wrote a blog post saying "i don't think much happened after this"
mod6: yeah, i should have just pointed him to your blog.
ben_vulpes: those hafta be the 2 derpiest typos of my life.
trinque: ben_vulpes: guess what else I'll be rewriting in cl at some point.
trinque: the golang part gets into some dumb state where it wont reconnect.
decimation: at any rate this whole rejection machine can be permanantly jammed by setting nversion to MAX_INT
☟︎ decimation: I'm fairly certain that if 0.5.3.1 were used to mine a block with nVerion=1 it would be rejected
decimation: as more than 950 blocks have passed since the first instance of the IsSuperMajority machine being used
mod6: i put it out there on derp-media too
decimation: I would also note that the bitcoind github commits and comments lie about the IsSuperMajority machine. They say that the mandatory rejection won't take effect until 95% of the blocks are incremented - but in fact it's only 950
☟︎ decimation: hardly 'consensus' in view of the 363000 block history of bitcoin
decimation: which amounts to one week of 'voting window'
decimation: one week out of years of doing things a certain way
assbot: [MPEX] [S.MPOE] 16414 @ 0.0005214 = 8.5583 BTC [-] {2}
assbot: Use CTransaction/CBlock version numbers for smoother upgrades by gavinandresen · Pull Request #1525 · bitcoin/bitcoin · GitHub ... (
http://bit.ly/1LNKrVq )
assbot: Transition to requiring block height in block coinbases by gavinandresen · Pull Request #1526 · bitcoin/bitcoin · GitHub ... (
http://bit.ly/1LNKrVs )
decimation: which would have been released in 0.7rc1 roughly
assbot: [MPEX] [S.MPOE] 51000 @ 0.0005145 = 26.2395 BTC [-] {3}
midnightmagic: decimation: 1000 blocks is a couple percent of all work done ever on the entire blockchain since inception, and the current hashrate could rewrite the entire history up to something like august 2014 in somewhere close to the span of time that non-vote took place over, times a very small number. :( unfortunately.
decimation: this machine is braindamaged in my opinion
decimation: at any rate, it's not like you couldn't jam it by changing nversion to an arbitrary value
decimation: to spite, you could even pick a value between 4 and MAX_INT randomly
midnightmagic: i'm just saying that it sounds like a little bit in comparison to both time, and integerial block height, but actual work-wise it a significant chunk. again, very unfortunately.
phf: ha, stator build on openbsd i386
ben_vulpes: midnightmagic: this is a basic feature of integrals and curves.
decimation: midnightmagic: the "amount of work" argument utterly fails to impress
decimation: also, it's probably not going to be true in a year or two as 14 nm asics fan out and become barely economic
midnightmagic: that is the inverse of what will happen as more-efficient mining equipment arrives.
☟︎ decimation: also, your argument would also be true if nMajorityWindow=10000 or 100000
ben_vulpes: decimation is ready to bet against diff increases?
decimation: I think it's likely to level out in the coming year or two, maybe longer
ben_vulpes: midnightmagic is ready to work more student exercises?
decimation: unless someone can tell me exactly how they are going to 'get efficient'
ben_vulpes: efficiency is not a prerequisite for fab runs.
decimation: no, but it is for profitability in the face of non-zero electric rates
ben_vulpes: since when has midnightmagic's employer given a shit about profitability?
midnightmagic: ben_vulpes: #trollfail. That sort of thing doesn't work on me, especially when it comes from someone like you.
midnightmagic: ben_vulpes: You would call a bite any response. That is the fundamental nature of #trollfail.
ben_vulpes: y'ever hear the line: "don't feed the trolls"?
midnightmagic: Regardless, a 1000-block window is not unreasonable if one accepts that mining hashpower is the vote that counts.
decimation: nor does this argument hold for 1000, because the same argument can be made for 50000
ben_vulpes: midnightmagic: you make this mistake of letting the plants control the conversation. "what's the right magic number of blocks to signal fork acceptance?" answer: there isn't. there is only the long-term behavior of the network.
midnightmagic: Correct. I am saying your complaint about it being unreasonable is illogical by any measure of the mining work done: there *is* no other meaningful window, or measurement, of the bitcoin network without shifting to PoS or DPoS. But if you want to do that, fork bitshares.
ben_vulpes: this moronic 'acceptance-in-blockchain' algo doesn't work, because hashpower can revert and rewrite an arbitrarily-lengthed blockchain.
midnightmagic: ben_vulpes: On that at least, we agree. I agree with that: the current hashrate is as illegitimate as a vote of private keys would be in determining a softfork. What else is there?
ben_vulpes: just the network. that, only that, no more, no less.
midnightmagic: Thus, backing up further, there is the legitimacy of BIP66 at all. If it is not legitimate, we have a consensus code failure every time openssl decides they want to change behaviour.
ben_vulpes: midnightmagic: art thou familiar with the 1.0.1g issue?
decimation: you are subjugating human judgement to unthinking machinery - this can never be reasonable
ben_vulpes: openssl changed behavior. bitcoin did not.
decimation: midnightmagic: who is holding a gun to your head, requiring you to update openssl?
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.
☟︎ decimation: why isn't anyone seriously attempting to extract the open-ssl code paths used by bitcoin?
☟︎ ben_vulpes: bitcoind's built with openssl versions after 1.0.1g don't sync.
midnightmagic: decimation: Nobody, of course. Then we go back to static builds and what happens when an actual bug hits and the fork is so old that the fix doesn't backport? How divergent are we willing to accept?
midnightmagic: lol. No, it's not news to me. Yes, I already knew that.
decimation: midnightmagic: the cure to that problem is not forcing changes of an uncertain nature, but to gain certainty in the codebase
decimation: why wouldn't we want a static bitcoind that is correct for all time?
ben_vulpes: midnightmagic: you were probably just on the cusp of killing hitler too.
ben_vulpes: <decimation> why wouldn't we want a static bitcoind that is correct for all time? << we do. midnightmagic does not.
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?
☟︎ decimation: understand the code, make sure it doesn't happen
decimation: pretending like others are there to solve your problems seems like a poor approach
midnightmagic: ben_vulpes: You can keep guessing what I mean without actually asking me, but you're no less wrong.
ben_vulpes: decimation: no but you see we need to slurp the spitoon because if we don't something terrifying that we can't reason about won't happen!
ben_vulpes: midnightmagic: no less wrong than what now?
midnightmagic: I'm not pretending that; I'm explicitly saying, divergence implies there is no reason to even *use* openssl at that point. strip out the components, use them, skip openssl entirely, and, I guess, trust in your ability to monitor the progenitor of your codebase for bugs that *explicitly affect your consensus-critical code*.
decimation: agreed, except "consenus-critical" means "compatible with what satoshi wrote" in my book
☟︎ assbot: [MPEX] [S.MPOE] 159666 @ 0.00052679 = 84.1105 BTC [+] {5}
midnightmagic: or, do what sipa did and write a secp256k1 lib because the openssl people don't give a shit they're wrecking dependencies.
midnightmagic: because, like I said, I think some people in there appear to be adding exploitable code with absurd frequency.
☟︎ decimation: again, nobody is forcing anybody use a version of openssl they don't want to use.
midnightmagic: ehh. satoshi's code, bugs and all. we could also stick with bdb and accept the quirks like the old accidental fork post-leveldb.
midnightmagic: .. which appears to have been a gavin/hearn originated bug.
ben_vulpes: it's all well and good to say "strip out the components", i just don't buy that that's possible.
decimation: his code sucks, I don't deny, but it's the closest thing to a spec that we have
decimation: start there and iterate the code toward perfection
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.
☟︎ assbot: [MPEX] [S.MPOE] 69387 @ 0.00053112 = 36.8528 BTC [+] {2}
midnightmagic: Say, why did you guys stop openly calling out Gavin and Hearn anyway?
decimation: gavin is mentioned on here from time to time
assbot: [MPEX] [S.MPOE] 126663 @ 0.00053379 = 67.6114 BTC [+] {5}
midnightmagic: Yeah, I mean aside from the grumbling in here which nobody but people *in here* seems to read.
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.
decimation: well, it wasn't me doing any of this stuff
decimation: he did a few times, rather unimpressively
ben_vulpes: <midnightmagic> Yeah, I mean aside from the grumbling in here which nobody but people *in here* seems to read. << how could you possible know
ben_vulpes: <midnightmagic> Once everyone else started, you stopped. How come? << hipsters always move on, boss
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: I don't really read reddit or twitter, but I recall that gavin captiulated, more or less
midnightmagic: And here they are, going on little half-drunken joke-rants about how maybe they should just remove everyone else's commit access and unilaterally take control again.
ben_vulpes: midnightmagic: reddit? twitter? d'you want to roll medium and perhaps bitcointalk.org into that as well?
midnightmagic: You guys *heads* were exploding in here, and then when "the rest" of the bitcoin-core devs took up the flag you all went quiet again. wtf?
ben_vulpes: for a grand coup of shit-as-what-don't-matter?
ben_vulpes: so we won, and you want to 3/10 troll on the topic?
midnightmagic: I presumed your head would explode if I mentioned forbes (due to its primary bitcoin author being a douchebag), or mainstream media.
trinque: gcovr outputs a nice html version of the gcov output
trinque: gonna let this run for a while, then I'll share the results
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.
decimation: if bitcoin core devs agree with what people here are writing, why don't they venture here to make their case?
ben_vulpes: moreover, if the decisions made here trickle down to "bitcoin core", why should we pursue them further?
decimation: umm, why would we give a shit about what they are saying otherwise? I donno bro, you're the one accusing here.
midnightmagic: Besides, you went quiet well before he "capitulated".
ben_vulpes: why bang on about points that are already settled?
decimation: all I can say, for myself, is that folks write stuff on this channel, I would read; comment - as would others
decimation: with respect to bip 66 in particular, it's not a terrible idea, but it strikes me as backwards
ben_vulpes: midnightmagic: re #trollfail it's supposed to be lighthearted elbows-in-ribs
assbot: [MPEX] [S.MPOE] 36350 @ 0.00053547 = 19.4643 BTC [+] {2}
decimation: why not solidify the questionable openssl code first, before lightly restricting certain signature forms?
☟︎ 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. :(
assbot: [MPEX] [S.MPOE] 64050 @ 0.00053567 = 34.3097 BTC [+] {2}
ben_vulpes: anyways, chickens run around with their heads cut off for minutes. what of it? they still lost to the butcher.
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
midnightmagic: Maybe my appraisal is just wrong. Could be. Seems to me they're just taking a breather to set up the schism.
decimation: yes. ultimately this is war, and we have a strategy
ben_vulpes: nah we seem to have defused the antagonism for now
midnightmagic: thestringpuller: not at all, I mainly wanted to know why you all were being so quiet lately. :-P
ben_vulpes: dumpblock, eatblock, exposure of the ancient blockchain is quiet now?
ben_vulpes: i thought you said you were reading logs!?
decimation: midnightmagic: yeah actually we are mostly focusing on building a working, sane bitcoind
thestringpuller: midnightmagic: cause I fucked up my shoulder being on the computer all day at work so I read comic books instead after work.
decimation: I think there's a general ambivalence about what bitcoin-devs want or do
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: at any rate, I'm going to sleep, I'm sure others will comment tomorrow on this discussion.
ben_vulpes: midnightmagic: that's some wack ass disingenuous shit. you jumped in on the n block consensus line.
assbot: [MPEX] [S.MPOE] 10788 @ 0.00053569 = 5.779 BTC [+]
assbot: [MPEX] [S.MPOE] 115612 @ 0.00053634 = 62.0073 BTC [+] {3}
assbot: Logged on 04-07-2015 01:14:46; asciilifeform: (virgin tears? vodka ?)
trinque: nice way to read the source
assbot: Logged on 04-07-2015 02:07:07; DanyAlos: I was looking for #bitcoin-assets on this search engine (
http://irc.netsplit.de/channels), and realized that it is not listed. Is there any particular reason for not being there?
mircea_popescu: (an important point about co2 extinguishers is that they also cool when deployed. this effect is significant. heavier gases - not so much)
assbot: Logged on 04-07-2015 02:46:46; asciilifeform: what i think would be considerably more useful is a provision for 'programmable checkpoints'
assbot: Logged on 04-07-2015 03:04:15; asciilifeform: but it would stand to reason that miners will eventually exert more tx fee pressure
assbot: [MPEX] [S.MPOE] 60112 @ 0.00053707 = 32.2844 BTC [+] {2}
assbot: [MPEX] [S.MPOE] 21038 @ 0.00053837 = 11.3262 BTC [+]
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: nevertheless, being critted for > 9k ironies over something like this is beyond comedic.
assbot: Logged on 04-07-2015 04:51:34; asciilifeform: (for as long as it carries under 'technical', the weasels can whine, wheedle, emit 'reasonable reasonings', even persuade the persuadable)
assbot: Logged on 04-07-2015 05:13:46; decimation: at any rate this whole rejection machine can be permanantly jammed by setting nversion to MAX_INT
mircea_popescu: but at any rate : setting the "nversion" to maxint has at least the important symbolic significance of saying "this is the last version".
☟︎ assbot: Logged on 04-07-2015 05:26:45; decimation: I would also note that the bitcoind github commits and comments lie about the IsSuperMajority machine. They say that the mandatory rejection won't take effect until 95% of the blocks are incremented - but in fact it's only 950
mircea_popescu: i mean, other than painting the picture of the vermin in unflattering tones, which it does. in the field it can do precisely jack.
assbot: Logged on 04-07-2015 05:54:09; midnightmagic: that is the inverse of what will happen as more-efficient mining equipment arrives.
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: pure spaghetti mess, wherein no soul can tell where the pasta ends and the cook's hairs begin
assbot: Logged on 04-07-2015 06:06:56; decimation: why isn't anyone seriously attempting to extract the open-ssl code paths used by bitcoin?
mircea_popescu: an exquisitely african thing this, as late as 2000 one could notice that all the egyptians seem willing to do is stand in front of the pyramids with their chests pushed out, or else gesturing importantly. meanwhile... the people who built those things don't look anything like the arab mongrels currently populating the place, if extant statues are to be believed.
mircea_popescu: whose great-grand parents noticed, while taking the upper-middle class mandatory "tour of europe", that the italians similarly etc etc.
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?
midnightmagic: Almost like a sort of mass-ennui/retirement mentality. Tired of working for something they don't believe in anymore.
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: I meant to suggest that the amount of effort of doing it oneself compared with the projected risk of it happening while someone else is working on it.. which option is less expensive/reliable?
midnightmagic: And sipa, it seems, agrees with you, hence the existence of libsecpblah
mircea_popescu: you familiar with my observation re alf's "folk with brains are useless - they want to use the brains" that in terms of "optimal impact", you're always better off waiting ?
midnightmagic: No, but I do know for a fact that procrastination has saved my life at least six or seven times. :)
assbot: Logged on 04-07-2015 06:13:58; decimation: agreed, except "consenus-critical" means "compatible with what satoshi wrote" in my book
assbot: Logged on 04-07-2015 06:14:44; midnightmagic: because, like I said, I think some people in there appear to be adding exploitable code with absurd frequency.
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.
assbot: Logged on 04-07-2015 06:19:59; midnightmagic: Once everyone else started, you stopped. How come?
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:33:28; decimation: why not solidify the questionable openssl code first, before lightly restricting certain signature forms?
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.
assbot: Logged on 04-07-2015 06:38:25; midnightmagic: The Satoshi-Halo-Wearers.
midnightmagic: He is while he's riding around on Gavin's back. The Halo's right there above him.
mircea_popescu: in this sense the halo's about as stretched as gavin's mother.
midnightmagic: Externally combating a blocksize increase with articles, comments, and discussion external to -ass.
mircea_popescu: why ? point's well made, everyone's happy to be part of bitcoin by standing on borrowed intelligence. let them.
mircea_popescu: next time they'll need some they... ahem... won't read b-a logs etc once more.
midnightmagic: Because they haven't stopped yet. Hearn's submitting pullreqs he's going to use as propaganda to push people to -XT, and Gavin's going through the bip/pullreq motions when he knows he's going to be voted down. Again.
mircea_popescu: and lawsky's going around trying to scam people like a resurected antonopopo derpopopop.
midnightmagic: "Miners, merchants, and exchanges," all agree with him. Supposedly.
mircea_popescu: any idea how long the list is ? even nefario is making the occasional reappearance.
mircea_popescu: every bum drunk has a story of greatness. go, listen. care.
midnightmagic: What? Nefario is back?! His huge black eyes all healed up?!
mircea_popescu: heck, kenna and the armandi fellow are prolly due for a novel attempt too
mircea_popescu: the legions of hell are truely an infinite headcount. why do you care so much about some particular schmucks in the chorus ? why not that tv scammer dude while you're at it, what was his name
assbot: [MPEX] [S.MPOE] 28500 @ 0.00052491 = 14.9599 BTC [-] {2}
midnightmagic: Dude wears the Halo. The other scammers don't matter so much. And if I really cared, I'd be doing something other than flicking out belly button lint in the shower. I'm just curious to know why *you guys* stopped.
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: your experiences and inner life are not nearly as universal as you imagine before you examine it.
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: to most everyone else, gavin's just another washed up website designer with a great story from five years ago.
mircea_popescu: sort-of like how rassah bought a car or some guy bought a pizza.
midnightmagic: Nobody wears a halo to me. Well. Maybe Grigori Perelman..
mircea_popescu: "and then we came THIS CLOSE to selling out to amazon for 5 trtillion"
midnightmagic: (but Perelman's a safe bet because he's a recluse and there's no possibility of that image ever being shattered)
mircea_popescu: he's still alive. never trust the living. for all you know he ends up like donald trump, doing reality shows in his 70s
assbot: [MPEX] [S.MPOE] 59300 @ 0.00051343 = 30.4464 BTC [-] {2}
assbot: [MPEX] [S.MPOE] 30341 @ 0.0005312 = 16.1171 BTC [+]
assbot: [MPEX] [S.MPOE] 25159 @ 0.00053427 = 13.4417 BTC [+]
assbot: [MPEX] [S.MPOE] 16351 @ 0.00052446 = 8.5754 BTC [-]
assbot: [MPEX] [S.MPOE] 45400 @ 0.00053618 = 24.3426 BTC [+]
assbot: [MPEX] [S.MPOE] 55800 @ 0.0005281 = 29.468 BTC [-]
punkman: so... did the DER chain lose the race?
punkman: I just started a stator patched to not skip VerifySignature, wonder if it'll work this time
assbot: [MPEX] [S.MPOE] 51900 @ 0.00053626 = 27.8319 BTC [+] {2}
assbot: Logged on 04-07-2015 04:30:43; mircea_popescu: Uh oh all these block explorers just flipped over to the invalid chain:
assbot: [MPEX] [S.MPOE] 55900 @ 0.00053217 = 29.7483 BTC [-]
shinohai: I'm at 254300 this morning, yay
assbot: Logged on 04-07-2015 04:33:37; mod6: shinohai: is your v0.5.3.1-RELEASE node up to dayte?
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: lukejr: "Sorry, accident, ignore."
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."
assbot: If you are using any wallet other than Bitcoin Core 0.10.x or 0.9.5 (or something backed by one of those versions), then you should not trust incoming transactions until they have ~30 confirmations. : Bitcoin ... (
http://bit.ly/1G0jGVG )
kakobrekla: so if nothing else, cpu mining code needs to be updated in the ref implementation now or what
punkman: cpu mining code probably needs more than a couple fixes
kakobrekla: or does it need to work only on alpha centauri?
mircea_popescu: check out all the miners that were mining off thin air, incidentally. because the bandwidth doubled so much.
kakobrekla: fees not large enough to offset the finite speed of light
shinohai: It appears f2p pool "almost" mined them out xD
assbot: [MPEX] [S.MPOE] 36150 @ 0.00052768 = 19.0756 BTC [-] {2}
assbot: [MPEX] [S.MPOE] 37849 @ 0.00052533 = 19.8832 BTC [-] {2}
punkman: in other news, stator (with openssl1.0.1g) patched to not skip VerifySignature, has not barfed up to block 146k (previous attempt barfed earlier than that)
assbot: [MPEX] [S.MPOE] 143250 @ 0.00051227 = 73.3827 BTC [-] {4}
punkman: "Two other male students, both also 17 years old, came forward as victims after Fichter was arrested." << lol assholes
assbot: [MPEX] [S.MPOE] 37400 @ 0.00050978 = 19.0658 BTC [-]
assbot: Teacher, accused of threesome with student, avoids jail time; posts gleeful pic to Instagram | myfox8.com ... (
http://bit.ly/1HD738B )
cazalla: tbh at 17 i think i would've been willing to do 22 years to fuck my english teacher
assbot: [MPEX] [S.MPOE] 8034 @ 0.00050978 = 4.0956 BTC [-]
shinohai: I always wanted to fuck my math teacher. She was smokin'
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: [MPEX] [S.MPOE] 58519 @ 0.00050549 = 29.5808 BTC [-]
assbot: [MPEX] [S.MPOE] 14500 @ 0.0005057 = 7.3327 BTC [+]
assbot: [MPEX] [S.MPOE] 66800 @ 0.00050579 = 33.7868 BTC [+] {2}
assbot: [MPEX] [S.MPOE] 12091 @ 0.00051471 = 6.2234 BTC [+] {2}
assbot: [MPEX] [S.MPOE] 5909 @ 0.00052578 = 3.1068 BTC [+] {2}
assbot: [MPEX] [S.MPOE] 25303 @ 0.00050549 = 12.7904 BTC [-]
assbot: [MPEX] [S.MPOE] 11639 @ 0.00050549 = 5.8834 BTC [-] {2}
assbot: [MPEX] [S.MPOE] 32411 @ 0.000505 = 16.3676 BTC [-]
assbot: [MPEX] [S.MPOE] 71600 @ 0.000505 = 36.158 BTC [-]
assbot: [MPEX] [S.MPOE] 11000 @ 0.000505 = 5.555 BTC [-]
assbot: [MPEX] [S.MPOE] 90650 @ 0.00050402 = 45.6894 BTC [-] {4}
assbot: [MPEX] [S.MPOE] 136900 @ 0.00052845 = 72.3448 BTC [+] {3}
assbot: [MPEX] [S.MPOE] 143014 @ 0.00050724 = 72.5424 BTC [-] {3}
assbot: [MPEX] [S.MPOE] 2732 @ 0.00053217 = 1.4539 BTC [+]
assbot: [MPEX] [S.MPOE] 20250 @ 0.00053628 = 10.8597 BTC [+]
assbot: Logged on 04-07-2015 07:21:18; mircea_popescu: but at any rate : setting the "nversion" to maxint has at least the important symbolic significance of saying "this is the last version".
assbot: Logged on 04-07-2015 10:56:06; kakobrekla: so we are stuck on v3 now.
assbot: Logged on 04-07-2015 07:33:02; mircea_popescu: and that's 40 gb's worth of magic number.
shinohai: congrats, I am still about 167k or so
assbot: [MPEX] [S.MPOE] 19150 @ 0.00053628 = 10.2698 BTC [+]
punkman: no-verifysig-skipping stator reached 169k, so I'm gonnna call this a success for now.
punkman: maybe we should add a .conf option that lets whoever really wants it to skip VerifySig between checkpoints
☟︎ punkman: asciilifeform: what do you think about making no-verifysig-skip the default for next release?
punkman: as it is 0.5.3.1/0.5.4 versions will accept blocks of version 1 and 2, allowing shitgnomes to induce forks. what's gonna happen with this?
☟︎ punkman: (can be combined with very-slow-to-verify block for bonus points)
punkman: sig op parallelism would help in that regard
assbot: [MPEX] [S.MPOE] 9000 @ 0.00053639 = 4.8275 BTC [+]
assbot: [MPEX] [S.MPOE] 1980 @ 0.00053639 = 1.0621 BTC [+]
assbot: 2 police detectives showed up to my house for cyber crime yesterday. - GoFuckYourself.com - Adult Webmaster Forum ... (
http://bit.ly/1UlYt3p )
mod6: my stator is @ 281k
phf: so stator builds and syncs on openbsd 5.6 i386
phf: OpenBSD 5.6 GENERIC#274 i386; -rwxr-xr-x 1 root wheel 5.0M Jul 4 02:34 bitcoind; bitcoind: ELF 32-bit LSB executable, Intel 80386, version 1, for OpenBSD, statically linked, stripped
phf: asciilifeform: it pretty much builds out of the box. the only tricky part is the " -Wl,--whole-archive -lpthread -Wl,--no-whole-archive" business
phf: apparently gcc doesn't always include all the necessary pthread bits (not just openbsd but other unixes), which results in segfault on launch
punkman: 30k student email list? I scraped like 5mil for leet sv startup last year.
☟︎ 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: 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!!! "
mod6: <+asciilifeform> phf: you may be the first to achieve openbsd build! consider posting recipe << please do!
mod6: <+phf> apparently gcc doesn't always include all the necessary pthread bits (not just openbsd but other unixes), which results in segfault on launch << on my obsd 5.6 on x86-64 that's the same problem i kept running into; segfault at execution time.
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
assbot: [MPEX] [S.MPOE] 24100 @ 0.00053639 = 12.927 BTC [+]
mod6: thx for posting dpb
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
assbot: [MPEX] [S.MPOE] 4200 @ 0.00053732 = 2.2567 BTC [+]
assbot: [MPEX] [S.MPOE] 203404 @ 0.0005391 = 109.6551 BTC [+] {4}
trinque: I am seeing a bunch of ERROR: AcceptToMemoryPool() in my stator run
punkman: trinque: what does it say after "AcceptToMemoryPool()"
williamdunne: PRNGs selecting 50 random stocks each month from S&P 500 vs S&P 500 index:
trinque: williamdunne: I tend to take stock market prices as inflation indicators these days
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
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: well, matters how you measure inflation too
trinque wanders in search of coffee
williamdunne: True, some things are deflationary too, dependent on how you measure 'em
trinque: you have to measure inflation from the balls!
punkman: trinque: I think that's to be expected with orphanage amputations. I have those and also plenty of "ERROR: AcceptToMemoryPool() : nonstandard transaction type"
williamdunne: trinque: I always measured from my asshole, am I doing something wrong?
trinque: williamdunne: no one can tell you where your dick begins and ends... this is AMERICA!
williamdunne: Wooo, now I get to brag about my 3 inch glory!
assbot: [MPEX] [S.MPOE] 19800 @ 0.00053612 = 10.6152 BTC [-] {2}
assbot: [MPEX] [S.MPOE] 51717 @ 0.00054114 = 27.9861 BTC [+] {2}
jurov: lol, that's actually true that dick continues deeper in the body
mod6: shinohai: is that with your v0.5.3.1-RELEASE node?
shinohai: @ mod6 yes, other one still not built yet
assbot: [MPEX] [S.MPOE] 61337 @ 0.00054139 = 33.2072 BTC [+]
assbot: Logged on 04-07-2015 06:19:59; midnightmagic: Once everyone else started, you stopped. How come?
assbot: [MPEX] [S.MPOE] 38350 @ 0.00054139 = 20.7623 BTC [+]
assbot: [MPEX] [S.MPOE] 36083 @ 0.00053589 = 19.3365 BTC [-]
shinohai: @ danielpbarron I like table-flipping Jesus best.
assbot: [MPEX] [S.MPOE] 68550 @ 0.00054113 = 37.0945 BTC [+] {2}
assbot: [MPEX] [S.MPOE] 47200 @ 0.00054139 = 25.5536 BTC [+]
assbot: [MPEX] [S.MPOE] 72200 @ 0.00054139 = 39.0884 BTC [+]
assbot: [MPEX] [S.MPOE] 30400 @ 0.00054147 = 16.4607 BTC [+] {2}
trinque: mircea_popescu: is your node down?
trinque: getting connection refused
assbot: [MPEX] [S.MPOE] 34200 @ 0.00054188 = 18.5323 BTC [+]
trinque: I got connection refused starting at 07/04/15 20:02:12 UTC
trinque: came back at 07/04/15 20:09:46
trinque: ass-goblins in the intertubes
mircea_popescu: Cut 6 start 000000000000000006a3 end 000000000000000013fe
mircea_popescu: Add 7 start 000000000000000006a3 end 0000000000000000014e"
assbot: Shout out to the American Core Devs that are spending their 4th ensuring the health of the blockchain : Bitcoin ... (
http://bit.ly/1TcE1R7 )
trinque: speaking of which, I'm adding the coverage flag to the deps too, and will regen that gcovr html thereafter
trinque: I was surprised to find that bitcoin doesn't actually look that *big* compared to other C++ projects I've seen
trinque: it'll be neat to see for example how much of boost or openssl is actually used
trinque: might be able to just rip those bits off from the dep, then cut off the dep
jurov: !s openssl monkeys
jurov: trinque and anyone other: mandatory reading
punkman: you'll just have to reimplement everything
trinque: it'd be boost's interconnectedness that might prevent it, maybe
trinque: anyhow this is what I wanna see with the gcov thing
assbot: Logged on 15-02-2015 22:34:28; asciilifeform: 2) tearing out 'boost' while keeping the project in cpp will turn it into an unreadable morass of crud that makes the existing turd look like the finest sausage
assbot: [MPEX] [S.MPOE] 60200 @ 0.00054492 = 32.8042 BTC [+] {2}
mircea_popescu: trinque, asciilifeform, wimc : if client fails to progress past 363736, the likely culprit is the db locks limit. look in derp.log (assuming standard derp) for "REORGANIZE\nREORGANIZE: Disconnect 6 blocks; 000000000000000006a3..000000000000000013fe\nREORGANIZE: Connect 7 blocks; 000000000000000006a3..0000000000000000014e\n\n\n************************\nEXCEPTION: 11DbException\nDb::get: Cannot allocate memory\nbitcoin i
mircea_popescu: n ProcessMessage()\n\nProcessMessage(block, 947244 bytes) FAILED\n" which is the confirmation. then increase the number o' locks.
mircea_popescu: alternatively, feed it the last few blocks through the mechanism discussed that alf created recently i guess.
mircea_popescu: <trinque> might be able to just rip those bits off from the dep, then cut off the dep <<< ahahaha you.
trinque: mircea_popescu: I'm sure I'm about to see a nightmare when I pull the deps into the gcov thinger
trinque: but bitcoin! it seems so simple!
jurov: can gcov cope with templated function generated by macros?
trinque: danielpbarron: s-stop the surveillance!
jurov: you can record with cellphone, no?
jurov: or is removing battery mandatory at such meetings?
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" ?
pete_dushenski: mircea_popescu: you think there was a big transaction that got double-spent ? or...
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
pete_dushenski: what i can't figure out is why the hashrate didn't seem to split with the ph0rk...
jurov: pete_dushenski does anyone do such fine statistics?
assbot: Logged on 04-07-2015 04:15:35; ben_vulpes: simple rehash of the "let's probe network cohesion strength" fork
mircea_popescu: pete_dushenski 6 blocks wouldn't necessarily be visible. even three deep reorgs happen with some regularity naturally.
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 ?
jurov: no it reports them as orphaned
pete_dushenski: jurov: perhaps ima confoozed, but don't orphaned blocks have to be replaced with valid blocks in the main chain ?
jurov: yes.. that's why i say numbers are messed up
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.
☟︎ mircea_popescu: these are people who have been so far causing nothing but problems for bitcoin.
mircea_popescu: there can not be a single instance documented where they did anything useful to any degree or in any sense
mircea_popescu: an abundance of instances can be documented where they fucked things up
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.
assbot: [MPEX] [S.MPOE] 24700 @ 0.00054516 = 13.4655 BTC [+]
pete_dushenski searches memory for instances of useful 'devs'... blank.
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"
shinohai: ;;later tell mod6 new build successful and now in sync ...
mircea_popescu: right. splendid. how about go home and the problem goes away with you.
pete_dushenski: mircea_popescu: it's the broken window/car accident economy
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.
assbot: travispatron is not registered in WoT.
assbot: [MPEX] [S.MPOE] 170149 @ 0.00054549 = 92.8146 BTC [+] {4}
pete_dushenski: ;;later tell travispatron you sucked before, you suck now, and you will always suck. enjoy the periphery, derp.
☟︎ jurov: pete_dushenski: looks like b.info is hopelessly stuck on showing only orphaned blocks
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: alternatively they could just shut down and stfu already.
mod6: haha. yeah, that too.
mats: pete_dushenski: coinbase
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.
mircea_popescu: also lulzy for all the people using blockchain.info to validate txn.
jurov: or b1ockchain.info or other similar derivatives
assbot: [MPEX] [S.MPOE] 58249 @ 0.00054577 = 31.7906 BTC [+]
mircea_popescu: "wangchunLuke-Jr: I do not know how that v2 pool was relayed, log was lost in a screen session"
mats: le pgp key server almost done cooking
mats: mircea_popescu: should i make it publicly available for auditing?
mats: or keep it in house; perhaps jurov or asciilifeform would be interested in doing it
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: there is no physical punishment for being extremely ridiculous.
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.
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: yet he's still walking around as if he were somehow still a person.
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.
ascii_modem: the enemy accomplished his objective, which probably had something to do with discrediting chinese mines
mircea_popescu: "the enemy" is barely cogent enough to be enmitous at all.
ascii_modem: not brownian - has very obvious aims (keeping turdalicious-bitcoind in circulation being one)
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: just because you have one, and it's a very reflective surface, doesn't mean it has one too.
assbot: [MPEX] [S.MPOE] 25300 @ 0.00054735 = 13.848 BTC [+]
mircea_popescu: neway, of more interesting things : confirmed my seeder's stuck on 363736.
mircea_popescu: ascii_modem this is incidentally an exceptional opportunity to test our recent toolset.
mircea_popescu: what happens if you import the 7 block alt-chain into the stator ?
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: the difference between v3 and v2 is , as best anyone can determine, actual fucking validation for the openssl nonsense. hardly avoidable.
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
mircea_popescu: lemme lay out the issue here in detail, i think it's mebbe getting fudged.
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: 2. a voluntary, user-enforced change to the protocol was proposed (iirc by petertodd) where only DER sigs are accepted anymore.
mircea_popescu: this is neither a bad idea nor in any sense avoidable. because, again, without it we'll fork daily.
mircea_popescu: it'd have been ideal to not import the satoshism in question into bitcoin, but before our time.
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: 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
ascii_modem: where were the daily forks b/w january (?) and now ?
mircea_popescu: and we'll never see an odd hash block for as long as they keep at it.
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: 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: 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: 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: i still don't see how it affects us / anything of concern.
mircea_popescu: the only problem is that the clients ain't reorging properly, which needs looking into/
mircea_popescu: specifically, what happens if you put the new chain into a node
mircea_popescu: well you're only looking at mine, and mine's not relaying.
mircea_popescu: which it's how it's made to work, better fail than be stupid.
ascii_modem: gonna plug in the one on dulap when i get home
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 ?
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: i do intend to replace it with a foundation one as soon as practicable.
mircea_popescu: but for now it can stay as it is, because i think more people were syncing to it.
mircea_popescu: im also going to have it unstuck, but i got a shitpile of stuff cooking atm.
ascii_modem: from your earlier pastes, mirceacoind has slightly spiffier debug...? than ri
trinque: added the --coverage flag to all the deps
ascii_modem: trinque: neato - will read as soon as i'm not on street
trinque: cool, just wanted to post the link
ascii_modem: fellas, we gotta infer, divine, & reimplement mircea_popescu's mega-debugger
mircea_popescu: i run a public company wut do you want from me, blood ?
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".
mircea_popescu: so what, is "95% consensus" going to gavincoin next ? for ... all of six blocks again ? cool.
ascii_modem: how many other ways for fuckers to wedge us
assbot: [MPEX] [S.MPOE] 142438 @ 0.00054539 = 77.6843 BTC [-] {2}
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: this incident makes it very tempting to just unzip, piss on satoshid, and go ada sanityfork (tm)
mircea_popescu: i know she's stupid and fat and you want a divorce, but...
ascii_modem: right now we got an anthill in the living room
mircea_popescu: and you don't even know about the used condoms behind the bed headboard
ascii_modem: there are different schools of thought re how to furnish a room
punkman: I think we need to put a lot more comments on the code, kinda clunky to do through patches to ML though
mircea_popescu: an' signed, an' people will prolly prefer referencing yours unless it's dumb
mircea_popescu: in which case they'll prolly change it rather than start from the original. unles it's VERY dumb.
mircea_popescu: which sort of reorg apparentyly happens, or used to happen, a whole lot.
assbot: [MPEX] [S.MPOE] 45900 @ 0.00054068 = 24.8172 BTC [-]
ascii_modem: so far i'm not sure any of you apprehend just what a steaming turd the thing is
punkman: in other news, ATMs getting ddos'd even at 1am. rejects transaction, spits out card, and you gotta start over. perhaps intentional rate-limiting.
mircea_popescu: anyway, the main sufferance in my head atm is that reading the chinese stuff (in translation) clarifies in my head an objection that may well be a second major flaw to the protocol, after the "relay nodes gotta do it for the glory" : its altogether unclear a purely financial incentive is the correct solution for miners.
☟︎ mircea_popescu: specifically : atm there is an arbitrage open, where you can either make money by "brute forcing" it ie hashing,
mircea_popescu: or else by fucking up other people's miners. i ordered a listing of "all the ways you could exploit a miner with crafted comms for a hash advantage"
mircea_popescu: the process hasn't returned yet, the list is already hundreds of entries long
mircea_popescu: most only apply to specific implementationms etc, but! fuck me...
mircea_popescu: it pays more as a pool operator to be into skulldugery than into running your pool
mircea_popescu: ipso facto "running pool" ===== "nefariousness in layers"
mircea_popescu: sure, people don't do it yet. mostly because lazy, 2nd mostly because stupid, 3rd mostly because it's not even txn time yet.
mircea_popescu: but when that begins all this may fucking collapse under the weight of... if money's the incentive to mine mining will not exactly allign with "securing the network"
mircea_popescu: (txn time = when most miner revenue comes from block txn)
ascii_modem: the mire scant the crumbs, the bloodier the crumbfight
mircea_popescu: ascii_modem more specifically put : currently everyone is mining with a "god given" known tx of 25 btc + whatever they pick off the ground.
mircea_popescu: tomorrow, they will not KNOW immediately through act of god where that 25 btc comes from
mircea_popescu: atm 99.x% of income comes through this immediate, sent-from-heaven-above channel
mircea_popescu: if as much as 66% comes that way and the other 33% has to be found out about... o baby.
mircea_popescu: hard to convey what the changes in dynamic such a thing brings.
mircea_popescu: really the % of income "just known" vs "information acquired" is the proper measure.
mircea_popescu: atm the split is .999 - .001 or somesuch. this will change monotoniucall;y the other way
punkman: "A blockchain that does not validate under 0.5.3 is an altcoin blockchain." << both forks were valid in 0.5.3, right?
ascii_modem: so far there is no structure remotely enough to take up the weight if the duct tape is ripped out
mircea_popescu: punkman right. hence all the "We don't give a shit" verbiage here.
mircea_popescu: anyway, i don't envisage as much as an inkling of a solution. just more stuff to worry about.
ascii_modem: one one hand, i don't give a shit, yes. on the other, a human turd pressed a button, my nodes are halted, and there is no guarantee that they don't have a bottomless magazine of these
mircea_popescu: but this situation is why im so cold on your ada idea. sure, you go put all the god damned effort into writing a fully correct, fully specified implementation oif an... broken idea.
assbot: [MPEX] [S.MPOE] 57600 @ 0.00053931 = 31.0643 BTC [-] {3}
mircea_popescu: until we know exactly wtf to do about relayers, about miners now, there is no point. the prototype's still prototypin'.
☟︎ mircea_popescu: dude, how about you actually get some data first omfg.
mircea_popescu: yea, i get it, may mean that this makes your fate be to muddle in the dirt, piling up data for your kid, who maybe might do it.
mircea_popescu: fuck you, your grandparents were farmers. it's how this fucking world works.
ascii_modem: would really help to have a fucking reasonable platform for this
ascii_modem: actually ~my~ grandparents were approx. what i am now, l0l
punkman: "Chrome extension "BitcoinWisdom Ads Remover" by MasterX will change your btce deposit address after page is loaded. Do not use this app or remove it if you installed."
punkman: surprised we aren't seeing more of these
punkman: wait until you try to debug plants
mircea_popescu: asciilifeform just sayin, humanity was built by originally trudging the muck with no tools.
mircea_popescu: there is no reason to expect any better in this new field. it is, after all, a field.
mircea_popescu: and yes, most men died before seeing the thing they were working for. historically, to date.
mircea_popescu: <punkman> wait until you try to debug plants << he has a point there. tho in fairness iirc alf debugged mice at some point.
mircea_popescu is mildly impressed at alf's lineage in any case. my grandparents were teachers and whatnot, but great-grandparents deifnitely farmers.
punkman: I get very frustrated at things like "o hey we've sprayed 12 different solutions at it and the damn lemon tree still has fungus"
mircea_popescu: punkman i had problems with, "artichoke does so well here, it actually STAYED GREEN THROUGH WINTER, suppoirting an inch of snow on its upturned broad leaves. meanwhile, magnolia sapplings grow < 1inch per year and will never flower"
mircea_popescu: the town was fully of blooming magnolias and i never saw a single artichoke plant outside of my garden
punkman: for a short time I believed in the mythical farmer that actually knows what he's doing. But after watching the experts debug these things, my only conclusion is they sometimes get lucky and that's the best I could hope for.
punkman: maybe they got better corn science over in the US, dunno.
mircea_popescu: yeah, if you agree to make unedible crud you may have better control.
assbot: Logged on 04-07-2015 16:52:19; danielpbarron: my 0.7.2 node is at height=363815
mircea_popescu: danielpbarron are yuou up to date ? what's lastblock ?
punkman: I tried heirloom tomatos for a bit. I now know why everyone's using the same boring/bland strain.
☟︎ mircea_popescu: punkman meanwhile hanbot used to grow cherry tomatoes on her windowsill.
danielpbarron: aha my isp provided modem/router is working again. will have ip in a moment
danielpbarron: (previously forwarded all ports to one DMZ machine)
hanbot: oh yeah, those windowtomatoes were great.
mod6: <+danielpbarron> height=363856 << your v0.5.3.1ish node has this height?
hanbot: you don't understand the way the windowmato works.
mircea_popescu: just some nodes have trouble unsticking, which as i said above, great place to test our new block manip tools etc.
mod6: mp, you're right, should test the new dump/eat tools with the orphan blocks
mircea_popescu: i still dunno why they do it. i've not yet managed to unstick a stuck one from last night
mod6: danielpbarron: great! thanks
assbot: [MPEX] [S.MPOE] 80000 @ 0.0005447 = 43.576 BTC [+] {2}
mircea_popescu: superficially it seemed reorg blocks like it did in 2013, but maybe deeper than that. have not yet gone too deep into
punkman: we need something that stores these forks for inspection and replaying. I think ben_vulpes had a thread about that
mircea_popescu: this is exactly the sortt of situation the entire deterministic thing he was crowing about is meant for.
mircea_popescu: which, in terms of parachutes.. .you gotta admit... perfect timing
danielpbarron: 71.232.150.212 port 8139 is a fully synched 0.5.3.1~ node
☟︎ mircea_popescu: almost as if someone was holding off hitting the muppets over the head with a 2x4 until b-a crowd had its ducks lined
punkman: yeah but after reorg it throws the things away right? you'd have to shitblock at just the right time
assbot: Logged on 04-07-2015 22:58:41; punkman: I tried heirloom tomatos for a bit. I now know why everyone's using the same boring/bland strain.
punkman: cazalla: I fucked the up with too much sunlight many times.
cazalla: mircea_popescu, nope, good water in the evening and morning but the 4-5 days of 40-44 degree heat toppled em
mircea_popescu: a gallon of water makes half hour's mist, protects the plant if there's any air draft at all
cazalla: might've been the uv damage that killed em, i don't really know other than summer 2013 provide no tomatos
assbot: [MPEX] [S.MPOE] 17800 @ 0.00054735 = 9.7428 BTC [+]
cazalla: thinking about making some tomato wine this coming summer but from what i've read, it isn't that nice
punkman: cazalla: might as well get some grapes
cazalla: unfortunately i don't really have a place suitable for a few vines
punkman: cazalla, you can grow a tall vine and have it hang from a pergola type thing
assbot: Logged on 04-07-2015 22:03:31; 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.
cazalla: punkman, no pergola but we have a clothesline i could commandeer but doubt the missus would like that heh
cazalla: punkman, that's lovely, just wish i had the room :\
punkman: used to have one of these on 2nd floor roof, vine roots at ground floor
punkman: shade's good for the bunnies too, such synergy
cazalla: punkman, killed em off a while ago, might take em up again once i own a larger block of land
assbot: [MPEX] [S.MPOE] 165384 @ 0.00053421 = 88.3498 BTC [-] {3}
punkman: "Después de encontrar una vulnerabilidad grave en el sistema de voto electrónico a #MSA estan allanando mi casa, los de delitos informaticos."
assbot: [MPEX] [S.MPOE] 57908 @ 0.00053236 = 30.8279 BTC [-]
assbot: Logged on 04-07-2015 23:07:30; mircea_popescu: punkman which is why im keeping stuck nodes.
assbot: [MPEX] [S.MPOE] 8306 @ 0.00053236 = 4.4218 BTC [-]
gernika: For any interested: using phf's patch with a few mods for amd64 I have successfully built stator on OpenBSD.
ben_vulpes: so's this phr0k the nail in 20mb blocks' coffin?
punkman: gernika, maybe write up your process/mods
gernika: Will do. Need to sign up for the mailing list.
ben_vulpes: pete_dushenski: "i sell bitcoins and bitcoin-backed derivatives"
mircea_popescu: <punkman> "Después de encontrar una vulnerabilidad grave en el sistema de voto electrónico a #MSA estan allanando mi casa, los de delitos informaticos." << in case anyone else missed it, this country is mostly a parody.
ben_vulpes: clearly you don't fight enough zombies
assbot: You have not rated gernika.
mircea_popescu: !v assbot:mircea_popescu.rate.gernika.1:eb318647a108e0be29f9865dd2fdfb67a3b866e012eab068bab5f31c1d2db831
assbot: Successfully added a rating of 1 for gernika with note: New blood.
mircea_popescu: <punkman> gernika, maybe write up your process/mods << also a good idea. submit to mail list, now you can.
punkman: he voiced himself, could post at ml already
shinohai: @ ben_vulpes did you need anything important when you pinged me earlier? It was like 4 am here, so I missed it
assbot: Logged on 04-07-2015 16:02:26; punkman: maybe we should add a .conf option that lets whoever really wants it to skip VerifySig between checkpoints
pete_dushenski: alas, some cabin and some party with some people beckon. a demain !
assbot: Logged on 04-07-2015 16:04:00; asciilifeform: can't think of any reason not to
assbot: Logged on 03-07-2015 18:17:00; ascii_field: and shamir for the original poker
assbot: Logged on 04-07-2015 16:06:20; punkman: as it is 0.5.3.1/0.5.4 versions will accept blocks of version 1 and 2, allowing shitgnomes to induce forks. what's gonna happen with this?
ben_vulpes: shinohai: wanted to know about your 0.5.3.1's behavior during the phr0k
ben_vulpes: ;;later tell pete_dushenski king of the hill: "i sell cars and car backed securities"
punkman: mircea_popescu: well it costs 25btc, if they can doublespend more than that somewhere...
mircea_popescu: if that costs 25btc then any chip alf wants costs ~50 cents
punkman: yeah that was stupid, never mind
punkman: but still, any derpy miner can do this
mircea_popescu: best i can discern, this is not only legitimate, but will be the ultimate end situaiton
mircea_popescu: one day, someone WILL mine a version 1 block that WILL stick.
ben_vulpes: eh, alf may actually get to the ada impl before a block v1 sticks again.
mircea_popescu: "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!!!"
ben_vulpes: d'you mean that management is about "you may do XXX but not YYY" when you say "doors"?
mircea_popescu: no, i mean, sure, maybe x will happen. but then again maybe x won't.
assbot: Logged on 03-07-2015 19:21:32; mod6: I will work on a patch list and maybe a script later this month. It is a bit hard to follow.
assbot: Logged on 04-07-2015 16:19:51; punkman: 30k student email list? I scraped like 5mil for leet sv startup last year.