If clients were designed to warn their users when a soft fork happens, then
it could be done reasonably safely. The reference client does this (or is
it just for high POW softforks?), but many SPV clients don't.
If there was a delay between version number changing and the rule
activation, at leas
On Fri, Feb 12, 2016 at 10:31:56PM +1100, gladoscc via bitcoin-dev wrote:
> Here's a method of fixing block withholding attacks with a soft fork:
So, while you're technique I believe works, it's not a soft-fork, at
least under the definition most of the Bitcoin dev/research community
have been usi
Here's a method of fixing block withholding attacks with a soft fork:
We require blocks to choose an arbitrary target, e.g. two bytes. We
redefine the block PoW target to be "less than the difficulty, with the
last two bytes being the target".
We require blocks to include a blinded hash of the ta
