From: Tier Nolan <tier.nolan@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Soft fork fix for block withholding attacks
Date: Fri, 12 Feb 2016 16:09:01 +0000 [thread overview]
Message-ID: <CAE-z3OWAbu=02=90-MUgccV-VoC-R3qSv_Q5TpJFKmarFAudXw@mail.gmail.com> (raw)
In-Reply-To: <20160212153453.GA4976@savin.petertodd.org>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
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 least nodes would get a warning recommending that they
update.
* At each difficulty interval, if 950 of the last 1000 blocks have the new
version number, reject the old version blocks from then on.
* Start new target at 255, the least significant byte must be less than or
equal to the target
* Update target at each difficulty re-targetting
T = ((T << 3) - T) >> 3
This increases the difficulty by around 12.5% per fortnight. After 64
weeks, the target would reach 0 and stay there meaning that the difficulty
would be 256 times higher than what is given in the header.
An attacker with 2% of the network power could create 5 blocks for every
block produced by the rest of the network.
[-- Attachment #2: Type: text/html, Size: 1231 bytes --]
prev parent reply other threads:[~2016-02-12 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL7-sS0NdZ4E7qwSs9TQdvsyqrzY0q847oM2cnwEYA3ciXCs4g@mail.gmail.com>
[not found] ` <CAL7-sS3QFGg_uj0UN+vPSE1Y3-XTj3HeCaPxERznpMfhvaj28A@mail.gmail.com>
[not found] ` <CAL7-sS2DqPF0Y7+UT7qGp==MJBmHmbQW5em+XFY8ZkVPuzCPcQ@mail.gmail.com>
[not found] ` <CAL7-sS2TMUg1KTPgitzMq61-4+ppzpZ7E_aEsbLXOuBYqU_q-g@mail.gmail.com>
[not found] ` <CAL7-sS1JhXAJ_hjUpLvnPWiwsf2hOwsaZdrq9negDPZiGs4nmg@mail.gmail.com>
2016-02-12 11:31 ` gladoscc
2016-02-12 15:34 ` Peter Todd
2016-02-12 16:09 ` Tier Nolan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE-z3OWAbu=02=90-MUgccV-VoC-R3qSv_Q5TpJFKmarFAudXw@mail.gmail.com' \
--to=tier.nolan@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox