I think you have kinda confused original vision and the effect of having the most and best devs on one coin.....
Lol. The whale who owns a million BTC explained what he thought of the Core developers. They have hence created what is alleged to be a Rube Goldberg machine to fool users into issuing SegWit transactions which are donations to pay to anyone in Satoshis protocol:
BTCSatoshi has never forked. There was an instance of some bug fixes only, which
made the whales furious:
Again a rule-of-thumb in software engineering is complexity kills. And the founder of Trilema had
a scalding thread on BCT explaining his anger about how the Core devs were incompetent, adding unnecessary complexity, and not developing a specification (the code was the only specification) formalism. He was pointing out that getting the foundation perfected and clean was a higher priority than attaching bells & whistle experiments.
But just to make it clear to the kids following along at home-- the consequence of all that is you were evicted from the channel, apparently to the reasonable satisfaction of "my betters".
This is actually untrue. The two bans quoted are the only bans MP ever had in -otc, and there was no "eviction", he simply stopped showing up. Which makes you a liar. Again, if anyone were counting.
Not to worry, I'm sure the consummate scammers of BTC will be more than willing to vouch for your "gold star" reputation. Like the people that shilled for Pirate. Or like the people that shilled for BFL. Or you know, all those respectable folk you hang out with. GLWT. For anyone else "keeping score at home" you're still an untrustworthy, duplicitous piece of shit.
At least you're enough of an idiot to manage getting yourself caught in your own lies within the space of a single forum page. Always good for a chuckle, such intellectual performance.
Recently Bitcoin came close to unmitigated disaster, in the following way: Gavin diplomatically suggested that miners increase their block size, from the previous magic number of "250k" to something they themselves pick. This approach is flawed: the solution to the problem of having a magic number in the code is not passing the responsibility of choosing it to a larger group. It may work politically, in the sense that where large, vague groups are responsible for a bad move nobody will ever be hung. It does not work practically.
This point does not begin to get sufficient emphasis: stop thinking politically, stick to thinking practically. The political importance, usefulness or competence of a dev is nil. This is not your job, and more importantly this is one of the things you suck at the most. A casual skim through the -dev sessions is ample proof for this, more ridiculous dickwad posturing and knowshitism has never before been seen (outside of the mailing lists of some meanwhile failed open source projects). Snap out of it. Stick to writing code.
But we digress: as a result of a number of miners implementing their own version of a magic miner, a number of large blocks were created and mined by them, as long as they ran 0.8. Miners running 0.7 failed to mine these same blocks, and a fork developed.
The reason is that Bitcoin code sucks. It's not that "the blocksize", it's not that "the database", it's not that "nobody could have foreseen their using a plane like a rocket". That shit does not belong in this discussion, passing the buck is not and cannot be accepted in Bitcoin. The reason is that Bitcoin code sucks, and Bitcoin code sucks because people want to be Bitcoin devs, people want to call each other Bitcoin devs, people want to participate in idle irc chatter as if they in fact were Bitcoin devs, but those same people do not have either the ability or intellectual resources to write dependable, usable, good, clean code.
This is a problem, and this problem needs to be resolved, preferably by the people who are causing it. You know yourselves, I won't name and shame. Fix your heads. You won't be getting much more warning.
Today will go down in history as the day when Bitcoin nearly died, and its fate depended on BTC-Guild staying online. Stop and think for a minute. What are you doing here? Why are you here, really?
Like I said I will be holding my main stack on legacy format so im not worried, but the price crash would be obvious and pretty much everyone on Core would be on suicide watch after a such a fuck up.
Lol. Great. Couldnt happen to nicer group of Hitlers who hijacked Bitcoin with deception. Why didnt they just go create their own altcoin like the rest of us are doing? Because they are special Hitlers.
As a non programmer, I never understood why all these people which are supposed to be super smart, would all gamble with the project they've put endless hours at, their entire careers, and potentially their lives because there would be a lot of pissed off people at them if it happens. So I assumed the chances of segwit fucking up are unrealistic, otherwise I just fail to understand it. Why would they all be for segwit if the fuck up is a realistic scenario?
[
] I wasnt the only person who noticed this
schizophrenic, wolf-in-sheepskin wannabe-overlord mentality (some
Redditard threads about it) [
]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The approach proposed is fundamentally flawed in multiple places.
First and foremost, the only reasonable authority in Bitcoin is derived through the working of
contracts. Put another way this states that the power of "a collective", ie a group of users no
matter how large to dispose for the future is nil. Put in yet another way, Bitcoin is not a
democracy, but a republic.
Consequently, to propose that MPEx breach its contract with SatoshiDICE because you would like
me to is a waste of breath : you are not a party to that contract, and consequently you have no
standing whatsoever in that relationship. The contract specifies clearly how it works, and it
will work as such.
Secondly, and just as importantly : the current codebase is broken beyond belief. As explained
in an earlier Trilema article, the main problems Bitcoin faces currently come from the general
inability and ineptitude of the de facto dev team. These problems are a. that users can not
create arbitrary size transactions up to the size of one full block ; b. that the client does
not correctly select the best possible combination of available inputs to feed a list of
arbitrary outputs. More generally speaking the codebase is replete with magic numbers, which is
no way to code. The fact that a 7Gb download takes an hour if we're talking a movie and a week
if we're talking the blockchain - especially considering that the average torrent rarely has
over 100 seeders and the Bitcoin blockchain rarely has under 1k - is further testament to the
utter inability of the core team.
Consequently, the correct approach is for these people to either fix the codebase - which will
require serious work - or else step down and let other people do it. The early enthusiasm of
"everyone's welcome and we're glad to have you" may have bridged us between Bitcoin being worth
nothing and Bitcoin being worth 1/10`000th of a pizza, but we are now playing in the grown-up
league and as such we need grown-up code. It is certainly not acceptable to proceed as proposed,
from a "this is what the codebase can do, we will pretend to limit usage of Bitcoin to that"
perspective, as is contemplated here. The only acceptable and the only correct approach is,
"this is how Bitcoin can be used, therefore this is how Bitcoin should be used, therefore this
is what our code must accomodate, let's get to work on it."
The fact that a number of people - such as Luke-jr, Gmaxwell, Mike Hearn etc - feel inclined to
compensate for their modest technical ability with a disproportionate and unwarranted political
preocupation is of course to be expected : the marginal and the stupid have tried to propel
themselves in the position of populist "leaders" for as long as humanity existed. This will not
work in Bitcoin, because that is not how Bitcoin works. It is specifically designed to foil the
very common alliance between the stupid but lazy and the ambitious but inept that regularly
wrecks fiat ventures of all sorts, from small business to entire countries. It will work as
intended for that purpose.
Please you idiots, fix the codebase. If you can't do that, go away.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBAgAGBQJROkypAAoJEIpzbw4vt7RS3O4QAKZyWxOUMWdpQ3MEompzsUo1
bL3hqboerqzmGH2qVoYApAt9UkydQoZjpIhfme7jUf48qkrrStsattS0l8Q45BbH
2r1ii4Xz7bvN0OZgHb6+1VAM/1FUN8S++t4AMcOpw+H7HbE2sRMDGC0yH7WgUHbV
NUaplFGC6Y+eQZUtQ/vfJPXc7ne28d/NaeyuOU2RKRQg6AhLGDlueUOwE5GSnQhJ
bcvPuQZgNipjLvvlRorNTXH/l75qDKaVR7mysA7gzXMLZXdJa70BH4BI4BrBwVCn
Qv2XADv2l/KYoZ4VMiZA6MLYBZg0bsjwCwBd8axiq/m+o/1Iejn7VuE/R0Yp9kwV
wdKoQlsjZu/79H1y9oP8A2tHvgspCktcQuT6BgXak89xx1hE+A2PfPv/eveqlKA1
6Bcd0sy8/zAeJ/5eJC+IOmhRAcZwRxz4wCf7pO0MPNsDe43vnCg5OQzqdz/2i9XU
BpYYTe4QIEcYeh/XhQZvm6oqIXZN9a7eVPBKN4So9I33wzzAydwnzYiB4heAen//
y8dGyiBUcKXxnAF1H7w/7awju6ljmD5sQK5CoXMZ4aCd51xzxhPzFYWt8O0raYs6
Cu5ILnBFdL9qD6pg90Tamy6RbEslTsMCzv0X3hSRXOp+Ny1eu0UCovdzVW7VMcvA
ivgJ7R1lWvYCQ9I0QkNG
=THL3
-----END PGP SIGNATURE-----