|
Carlton Banks
Legendary
Offline
Activity: 3430
Merit: 3093
|
 |
August 23, 2015, 04:03:18 PM |
|
The dev team is necessarily centralised. When centralised is the only ideology that works, I'm in favour.
Pick your centralising influence: amorphous Core team or Mike Hearn's self described "benevolent dictatorship". Benevolent in respect of who, exactly?
|
Vires in numeris
|
|
|
Peter R (OP)
Legendary
Offline
Activity: 1162
Merit: 1012
|
 |
August 23, 2015, 04:10:15 PM Last edit: August 23, 2015, 04:39:30 PM by Peter R |
|
The dev team is necessarily centralised. When centralised is the only ideology that works, I'm in favour.
Pick your centralising influence: amorphous Core team or Mike Hearn's self described "benevolent dictatorship". Benevolent in respect of who, exactly?
Can you explain why you believe a model with several competing implementations of the protocol wouldn't work? In fact, with the emergence of BitcoinXT it looks like it is beginning to work. The consensus critical code would of course need to be compatible between implementations; however, if a change was desired by the community (e.g., increasing the block size limit), each implementation could attempt to solve it "their own way" and then the community would decide the winner by switching to the implementation they favoured. Then, to retain some portion of their previous user base, the losing implementations would adopt the same change to the consensus code to prevent their clients from forking off from the longest proof-of-work chain when the change goes into effect (at some future time similar to BIP101). Is this a way to give the community more power in exercising their free choice?
|
|
|
|
jonald_fyookball
Legendary
Offline
Activity: 1302
Merit: 1008
Core dev leaves me neg feedback #abuse #political
|
 |
August 23, 2015, 04:17:38 PM |
|
The dev team is necessarily centralised.
Well, yes. A core dev team leads development... ...until they betray the wishes of the community, at which point other developers step in. That appears to be the current reality. I do think several implementations are healthy though, but you're probably right that changes need leadership.
|
|
|
|
knight22
Legendary
Offline
Activity: 1372
Merit: 1000
--------------->¿?
|
 |
August 23, 2015, 04:32:39 PM |
|
The dev team is necessarily centralised.
Well, Mike and Gavin just proved this to be wrong. When centralised is the only ideology that works, I'm in favour.
It actually doesn't. Otherwise XT would not have come into existance in the first place... XT is the results of the Core team ignoring a large part of the market that are asking for scalability faster than what they were projecting which IS a problem due to centralization.
|
|
|
|
pedrog
Legendary
Offline
Activity: 2786
Merit: 1031
|
 |
August 23, 2015, 05:41:05 PM |
|
The dev team is necessarily centralised. When centralised is the only ideology that works, I'm in favour.
Pick your centralising influence: amorphous Core team or Mike Hearn's self described "benevolent dictatorship". Benevolent in respect of who, exactly?
Linux operates under that model and now is, probably, the most used operating system in the world, if you count Android as being Linux...
|
|
|
|
knight22
Legendary
Offline
Activity: 1372
Merit: 1000
--------------->¿?
|
 |
August 23, 2015, 05:47:27 PM |
|
The dev team is necessarily centralised. When centralised is the only ideology that works, I'm in favour.
Pick your centralising influence: amorphous Core team or Mike Hearn's self described "benevolent dictatorship". Benevolent in respect of who, exactly?
Linux operates under that model and now is, probably, the most used operating system in the world, if you count Android as being Linux... Linux doens't need a consensus to prevent an potential colapse though...
|
|
|
|
pedrog
Legendary
Offline
Activity: 2786
Merit: 1031
|
 |
August 23, 2015, 05:51:05 PM |
|
The dev team is necessarily centralised. When centralised is the only ideology that works, I'm in favour.
Pick your centralising influence: amorphous Core team or Mike Hearn's self described "benevolent dictatorship". Benevolent in respect of who, exactly?
Linux operates under that model and now is, probably, the most used operating system in the world, if you count Android as being Linux... Linux doens't need a consensus to prevent an potential colapse though... Yap, the implications are quite different, there are a shitload of Linux forks and that's ok, the more the merrier. Bitcoin developing/governance model is a concrete problem, it's curious how it only became obvious by now.
|
|
|
|
CIYAM
Legendary
Offline
Activity: 1890
Merit: 1098
Ian Knowles - CIYAM Lead Developer
|
 |
August 23, 2015, 05:55:39 PM |
|
Bitcoin developing/governance model is a concrete problem, it's curious how it only became obvious by now.
Actually IMO the problem that is not being realised is that we don't need "one blockchain". Once people can get over that idea then true decentralisation can start to take place (and yes that is a hint at what the CIYAM project is about).
|
|
|
|
Zangelbert Bingledack
Legendary
Offline
Activity: 1036
Merit: 1000
|
 |
August 23, 2015, 06:28:57 PM |
|
The dev team is necessarily centralised. When centralised is the only ideology that works, I'm in favour.
Pick your centralising influence: amorphous Core team or Mike Hearn's self described "benevolent dictatorship". Benevolent in respect of who, exactly?
Can you explain why you believe a model with several competing implementations of the protocol wouldn't work? In fact, with the emergence of BitcoinXT it looks like it is beginning to work. The consensus critical code would of course need to be compatible between implementations; however, if a change was desired by the community (e.g., increasing the block size limit), each implementation could attempt to solve it "their own way" and then the community would decide the winner by switching to the implementation they favoured. Then, to retain some portion of their previous user base, the losing implementations would adopt the same change to the consensus code to prevent their clients from forking off from the longest proof-of-work chain when the change goes into effect (at some future time similar to BIP101). Is this a way to give the community more power in exercising their free choice? Of course it is. Competing implementations is the only way to make it a market choice. In some years we will wonder why this was ever not obvious.
|
|
|
|
meono
|
 |
August 23, 2015, 06:31:53 PM |
|
Bitcoin developing/governance model is a concrete problem, it's curious how it only became obvious by now.
Actually IMO the problem that is not being realised is that we don't need "one blockchain". Once people can get over that idea then true decentralisation can start to take place (and yes that is a hint at what the CIYAM project is about).You've been hinting this alot, can you stop it already? until you got something to show..
|
|
|
|
Peter R (OP)
Legendary
Offline
Activity: 1162
Merit: 1012
|
 |
August 23, 2015, 06:41:45 PM |
|
The dev team is necessarily centralised. When centralised is the only ideology that works, I'm in favour.
Pick your centralising influence: amorphous Core team or Mike Hearn's self described "benevolent dictatorship". Benevolent in respect of who, exactly?
Can you explain why you believe a model with several competing implementations of the protocol wouldn't work? In fact, with the emergence of BitcoinXT it looks like it is beginning to work. The consensus critical code would of course need to be compatible between implementations; however, if a change was desired by the community (e.g., increasing the block size limit), each implementation could attempt to solve it "their own way" and then the community would decide the winner by switching to the implementation they favoured. Then, to retain some portion of their previous user base, the losing implementations would adopt the same change to the consensus code to prevent their clients from forking off from the longest proof-of-work chain when the change goes into effect (at some future time similar to BIP101). Is this a way to give the community more power in exercising their free choice? Of course it is. Competing implementations is the only way to make it a market choice. In some years we will wonder why this was ever not obvious. I agree. In fact, I see this as the Bitcoin Consensus mechanism playing out exactly like it should. The Bitcoin white paper says that nodes express their acceptance of a block by building on top of it; the longest chain becomes the correct chain. Giving people the choice between competing implementations just makes it easier for them to express their acceptance of, for example, blocks larger than 1 MB. In hindsight, it will be seen as ironic that so many fought for centralized development in order to keep Bitcoin decentralized.
|
|
|
|
|