rowan |
12-23-2017 07:53 PM |
Quote:
Originally Posted by jscott
(Post 22131090)
Satoshi didnt assign a team, the core team is derived of anyone who can provide usable code, so they are active contributors to the bitcoin development.
|
Not quite. There was never really any formal structure at first, and technically there isn't now, but the current people with commit access (you could count them on one hand, maybe a couple of hands) are in complete control of both the source. There's no way to for the users of Bitcoin to decide whom they want to control the reference client, nor to democratically vote on which features to implement or abandon. You have a small team of people, many whom are employed by the same for-profit company, that decide where Bitcoin goes from here.
From https://blog.plan99.net/the-resoluti...nt-dabb30201f7 (I strongly recommend you read the entire article. It gets a little sensationalist and whiny but there's some good information in it.)
When Satoshi left, he handed over the reins of the program we now call Bitcoin Core to Gavin Andresen, an early contributor. Gavin is a solid and experienced leader who can see the big picture. His reliable technical judgement is one of the reasons I had the confidence to quit Google (where I had spent nearly 8 years) and work on Bitcoin full time. Only one tiny problem: Satoshi never actually asked Gavin if he wanted the job, and in fact he didn?t. So the first thing Gavin did was grant four other developers access to the code as well. These developers were chosen quickly in order to ensure the project could easily continue if anything happened to him. They were, essentially, whoever was around and making themselves useful at the time.
[...]
Complicating things further, Maxwell founded a company that then hired several other developers. Not surprisingly, their views then started to change to align with that of their new boss.
[...]
But it quickly became apparent that the Bitcoin Core developers were hopelessly at loggerheads. Maxwell and the developers he had hired refused to contemplate any increase in the limit whatsoever. They were barely even willing to talk about the issue. They insisted that nothing be done without ?consensus?. And the developer who was responsible for making the releases was so afraid of conflict that he decided any controversial topic in which one side might ?win? simply could not be touched at all, and refused to get involved.
Quote:
Originally Posted by jscott
(Post 22131090)
Speed/fees, wait for Lightning, check out the youtube videos that explain it easily to understand, big great and bright future for bitcoin :thumbsup
|
Problem is, how long are we expected to wait? Even once Lightning is (finally) released it will take some time for enough people to adopt it that it becomes "part" of every Bitcoin transaction. There's no point me being an early adopter of Lightning if only 3 of the 100 recipients I regularly send funds to support it - those other 97 will still need standard slow, high fee transactions.
Lightning is very complex so it's going to take some time before everyone is confident it works, which will slow adoption. Bitcoin is already a mindfuck for newbies. Many people will sit back and wait for the others to iron out all of the inevitable problems once it's actually in use. They're not going to want to try to figure out how to use something that doesn't yet work reliably. In the meantime... the Core team could relieve the current painful situation by raising the block size, but it seems that's never going to happen. I'm just concerned this continued stubbornness is going to end up losing a lot of loyal users.
One consequence of the current network clogging is that people are more likely to leave their funds as balances on an exchange. That's bad, m'kay.
|