Maybe something trivial like lack of Python 3 dependency on older CentOS
builds?
On Mon, Dec 19, 2016 at 2:22 AM, Matt Corallo via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Please do report bugs to https://github.com/bitcoin/bitcoin . If you
> never report them of course they
Please do report bugs to https://github.com/bitcoin/bitcoin . If you never
report them of course they won't get fixed. I'm not aware of test suite
failures and know a bunch of folks who use CentOS, though not sure how many
develop on it.
On December 18, 2016 12:07:36 PM PST, Alice Wonder via bi
James,
I share your conviction that miners are the natural gatekeepers of the
maximum block size.
The trouble I see with Block75 is that linear growth won't work forever.
Also, by reading actual and not miners' preferred max blocksize, this
proposal is sensitive to randomness in block timing and
Hi All,
I'm coming late to the party. I like the Block75 proposal.
Multiple people have said miners would/could stuff blocks with insincere
transactions to increase the block size, but it was never adequately
explained what they would gain from this. If there aren't enough legitimate
transactions
I agree that finding the right line is difficult and purposefully crippling
(too strong a term?) the software is not necessarily the best way to
encourage long term adoption.
For example, I ran version 0.3.x from July/August 2010 for several years on
a miner without upgrading to anything higher th
On 2016/12/18 12:07, Alice Wonder via bitcoin-dev wrote:
> I almost did not update to 0.13.0 because the test suite was failing due
> to python errors. How to fix them was posted on bitcointalk.
>
> 0.13.1 came with new python errors in the test suite. So I just said
> fuck it.
>
> When the test
On 12/14/2016 07:38 PM, Juan Garavaglia via bitcoin-dev wrote:
For reasons I am unable to determine a significant number of node
operators do not upgrade their clients.
I almost did not update to 0.13.0 because the test suite was failing due
to python errors. How to fix them was posted on bi
One thing which hasn't been addressed yet in this thread is developer
centralization. Unlike other applications we want to ensure that it's not only
possible for users to refuse an upgrade, but easy. While this by no means
lessens the retirement that users run up to date software for security re
