5 ms·
> the current bitcoin developers Rusty, I'd suggest to replace that with "a significant number of current bitcoin developers". There are Bitcoin Developers who
by jlrubin 9y ago
> the current bitcoin developers
Rusty, I'd suggest to replace that with "a significant number of current bitcoin developers". There are Bitcoin Developers who may support the 2MB fork. "The current bitcoin developers" don't really make any centralized decisions on what to support or not.
- nadaviv 9y agoThe sentiment in the global technical bitcoin community is definitely against segwit2x, very strongly so. There may be some very few outliers, but the big picture is quite clear. See: https://en.bitcoin.it/wiki/Segwit_support#Developers https://en.bitcoin.it/wiki/Segwit_support#Developers
- wmf 9y agoNotably, that page doesn't list Jeff Garzik.
- deleted 9y ago[deleted]
- nullc 9y agohttps://en.bitcoin.it/wiki/Segwit_support https://en.bitcoin.it/wiki/Segwit_support I'm also aware of no person with more than 5 years experience developing the Bitcoin protocol or it's implementations who have ever been in support of it. Lots of people are supportive of various capacity increase things without being supported by the reckless last minute backdoor dealing. More comments can be found here: https://www.reddit.com/r/Bitcoin/comments/6h612o/can_someone_explain_to_me_why_core_wont_endorse/divtc93/ https://www.reddit.com/r/Bitcoin/comments/6h612o/can_someone...
- toomim 9y agoYou are not aware Jeff Garzick is a developer? This is a haiku.
- kobeya 9y agoMaybe emeritus, but he hasn't been doing bitcoin reference client development since 2012.
- toomim 9y agoHe's currently the lead developer of the btc1 reference client: https://github.com/btc1/bitcoin/tree/segwit2x https://github.com/btc1/bitcoin/tree/segwit2x Here are his recent commits: https://github.com/btc1/bitcoin/commits/segwit2x https://github.com/btc1/bitcoin/commits/segwit2x