Re: [bitcoin-dev] How much is too much time between difficulty changes?

2018-12-10 Thread Zawy via bitcoin-dev
It's possible to let the difficulty linearly drop as the solvetime goes beyond some limit (credit AS). If the limit is greater than any delay in the past it could be backwards-compatible. A simple daily-rolling average DA like BCH is probably the best option if a faster DA is ever needed. As a

[bitcoin-dev] call for demos: Cryptocurrency Implementers' Workshop

2018-12-10 Thread Andrew Miller via bitcoin-dev
Hi all, I'm happy to announce the first Cryptocurrency Implementers' Workshop, cohosted with Financial Crypto. http://fc19.ifca.ai/ciw/ Now that the BITCOIN cryptocurrency research workshop has been folded into the main FC conference, it's time to try something new. The goal of this workshop

Re: [bitcoin-dev] Safer sighashes and more granular SIGHASH_NOINPUT

2018-12-10 Thread David A. Harding via bitcoin-dev
On Thu, Dec 06, 2018 at 11:57:09AM -0500, Russell O'Connor via bitcoin-dev wrote: > One more item to consider is "signature covers witness weight". > > While signing the witness weight doesn't completely eliminate witness > malleability (of the kind that can cause grief for compact blocks), it

Re: [bitcoin-dev] Safer sighashes and more granular SIGHASH_NOINPUT

2018-12-10 Thread Johnson Lau via bitcoin-dev
The current proposal is that a 64-byte signature will be used for the default “signing all” sighash, and 65-byte for other sighash types. The space saved will allow a few more txs in a block, so I think it worths doing. However, this also makes witness weight estimation more difficult in