- Dec 16, 2015
- 2,806
- 6,088
The amount of very talented programmers, scientists etc. willing to spend their effort without scrutinizing the aims of their employers has always been high enough to sustain various oppressive uses of technology.
A benchmark figure taken from statements of a Blockstream subcontractor puts that level at around $0.5M / yr for an expert programmer.
To put that in perspective, the back taxes by the EU on Apple over the past 24 years are roughly around $0.5B / yr (this will of course be fought), but that would pay for 1000 such expert salaries per annum. And that's just the back taxes of a single multinational.
Co-opting (corrupting) developers is easy as pie.
[doublepost=1472563803][/doublepost]@satoshis_sockpuppet : I just put it to you that by making a fork depend on SegWit activation, we would introduce a dependency on Blockstream. How long would we be willing to wait to trigger the fork? We're forking primarly because blocks are full and Bitcoin is unable to grow, not because Blockstream loves overengineered soft forks which, if unchallenged, would guarantee their continued dominance (although that's a huge part of the problem).
I just think that by binding ourselves to a soft-fork which is not in sight of main-net release, we are hamstringing ourselves unnecessarily. Plus, we'd be stringing along their damn SegWit code for basically no good reason, or taking loads of effort and risk on ourselves to remove it safely.
I would support a "SegWit activation OR block-X" condition, since at least that's not open ended.
A benchmark figure taken from statements of a Blockstream subcontractor puts that level at around $0.5M / yr for an expert programmer.
To put that in perspective, the back taxes by the EU on Apple over the past 24 years are roughly around $0.5B / yr (this will of course be fought), but that would pay for 1000 such expert salaries per annum. And that's just the back taxes of a single multinational.
Co-opting (corrupting) developers is easy as pie.
[doublepost=1472563803][/doublepost]@satoshis_sockpuppet : I just put it to you that by making a fork depend on SegWit activation, we would introduce a dependency on Blockstream. How long would we be willing to wait to trigger the fork? We're forking primarly because blocks are full and Bitcoin is unable to grow, not because Blockstream loves overengineered soft forks which, if unchallenged, would guarantee their continued dominance (although that's a huge part of the problem).
I just think that by binding ourselves to a soft-fork which is not in sight of main-net release, we are hamstringing ourselves unnecessarily. Plus, we'd be stringing along their damn SegWit code for basically no good reason, or taking loads of effort and risk on ourselves to remove it safely.
I would support a "SegWit activation OR block-X" condition, since at least that's not open ended.
Last edited: