On 02/25/2017 08:10 AM, Ethan Heilman via bitcoin-dev wrote:
SHA1 is insecure because the SHA1 algorithm is insecure, not because
160bits isn't enough.
I would argue that 160-bits isn't enough for collision resistance.
Assuming RIPEMD-160(SHA-256(msg)) has no flaws (i.e. is a random
oracle),
On 12/18/2016 12:51 PM, Douglas Roark via bitcoin-dev wrote:
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
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
I think the next hard fork should require a safety rule for TX fees.
https://blockchain.info/tx/6fe69404e6c12b25b60fcd56cc6dc9fb169b24608943def6dbe1eb0a9388ed08
15 BTC TX fee for < 7 BTC of outputs.
Probably either a typo or client bug.
My guess is the user was using a client that does not
