264 entries in 0.836s
sgornick: Why? 100% of those will be rejected on the side of the
fork from nodes without the
hard-
fork implemented.
mircea_popescu: <davout> would transactions still propagated accross
fork branches in the event of a
hard fork scenario? <><
hard to tell, but mostly yes.
davout: would transactions still propagated accross
fork branches in the event of a
hard fork scenario?
mircea_popescu: a
hard fork that's not been ok'd by the bitcoin foundation (the real one, not vessenes' scam) is automatically an issue fort the obvious reason :
mircea_popescu: gavin does NOT have the authority to create a
hard fork.
mircea_popescu: "I agree a big discussion is necessary before changes are made, but we shouldn't act like a
hard fork is somehow inherently an issue."
mircea_popescu: there never was a
hard fork before. the march event was an observed
fork which was resolved by abandoning the new chain.
mircea_popescu: danielpbarron "This whole
hard fork drama is part of the bigger brain-damaged notion that Bitcoin isn't about money." << you actuyally have an excellent point here.
mircea_popescu: "I don't think a
hard fork would be very difficult, but only if the following two points are taken into account:
danielpbarron: if the
hard fork happens, it should be possible to cycle funds in and out of exchanges that are dumb enough to switch, splitting away real-bitcoin whenever the withdraw gives you an output that hasn't been doublespent yet -- or is this possibility too good to be true?
thestringpuller: This bet resolves no if Gavin's proposed
hard fork is launched, and in succession achieves 51% consensus of the network. This bet resolves yes, if the current Bitcoin
fork keeps 51% consensus of the network, or if Gavin's proposed
hard fork is never launched.
dartv: BingoBoingo: so far most people agree which address has how many BTC. i think I mean
hard fork mircea_popescu: asciilifeform: hence, they add up to an act of sabotage. what probably amounts to a
hard fork that 'no one' noticed. << i dun think so, fwiw
BingoBoingo: On it's own it's a naive thing, but the conversation around it will lead to bad things as it will probably lead to
hard fork talk to set the stage for the blocksize increase discussion.
thestringpuller: i just find it fascinating that the percent of redditards against any
hard fork is going up by a lot.
ben_vulpes: "death of the preivous
hard fork" meaning the actions that brought everyone onto the same chain?
mircea_popescu: well, the death of the previous
hard fork (the one gavin & hearn created) happened through the cooperation of the meanwhile defunct 50btc guild.
ben_vulpes: mircea_popescu: so the pool operators really decide if the
hard fork goes off, correct?
mike_c: also requires a "soft-
fork" of bitcoin, but don't worry, that's not as bad as a
hard fork.
mircea_popescu: asciilifeform: which'd be the earliest that would interoperate with the majority of extant nodes? << last
hard fork was to .4, so technically anything. but i'd say a .6 something'd be the best choice.
diametric: maybe i'm mistaken but doesn't the white paper basically state a
hard fork will be required in the future to address scalability?
mircea_popescu: this was the mechanism of the previous
hard fork : .8 miners included tx rejected by the network, moved on a different chain.
mircea_popescu: <ben_vulpes> if 0.9 says "this txn sucks!" but an 0.6 miner included it, this takes us right to a
hard fork << yep
ben_vulpes: if 0.9 says "this txn sucks!" but an 0.6 miner included it, this takes us right to a
hard fork mircea_popescu: thickasthieves the
hard fork is a problem, mostly because they're trying to introduce a whole slew of 0days into the protocol itself.
assbot: justusranvier comments on Gavin Andresen Proposes Bitcoin
Hard Fork to Address Network Scalability
cr_zoidberg: mircea_popescu: not really bug - it was bad design i guess. to fix it they need to make core changes and make
hard fork. we have just different transaction format.
assbot: 8 Million Vericoin Hack Prompts
Hard Fork to Recover Funds
mircea_popescu: GinAddict1 mike is the chief enemy plant in bitcoin. he's the guy that merged heartbleed in bitcoin for absolutely no legitimatereason, and he's the guy that forced a
hard fork, idem.
ThickAsThieves: "Update your client,
HARD FORK! Friday we will begin paying MasterNodes - Latest Client Stable: 9.10.1 and RC3 with Darksend is 10.10.1 - See downloads!" ~ Darkcoin developer
mircea_popescu: last time that happened we ended up with a
hard fork. so far ghash is 0-1 on the score.
benkay: so this implies a rather
hard fork.
pankkake: I don't think it will be an altchain. Just
hard-
fork the bitcoin blockchain into something actually better.
fluffypony: asciilifeform: I was just reading about that today (in the context of "Bitcoin will die because quantum computer!!!111") - general idea is that a
hard fork to something different if quantum computing was imminent would solve that
mircea_popescu: a
hard fork is a political event. they get the old chain coins they chose.
mircea_popescu: think for a moment. he's already demonstrated the ability to create a
hard fork, and the ability to pick the winning side IN SPITE of anything.
dub: a
hard fork to sink AM
mircea_popescu: remember the recent
hard fork ? i wouldn't trust the current codebase.
mircea_popescu: knowing in advance there will have to be a
hard fork is a weakness of the system.
ThickAsThieves: they will still need to
hard fork us again at some point, no?
mod6: Luke-Jr: what you're proposing is a
hard fork of the blockchain right?
smickles: but I can participate in a
hard fork if things go sour
davout: Luke-Jr: if you want to be actually productive here is my advice : modify your
fork so people can filter txes they wish to relay using arbitrary criteria, like regexp on the receiver address for example, make it consensual (that's probably where it's going to be
hard for you) enough so it is accepted upstream
BingoBongo: WHen you
hard fork over one issue the temptation arises to just incorporate your Mary Poppins nanny wishlist
mircea_popescu: next year the us govt will ask for a
hard fork to allow them to disallow selected transactions