From: Tom Harding <tomh@thinlink•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Update to Double-Spend Deprecation Window Proposal
Date: Sun, 08 Feb 2015 19:38:55 -0800 [thread overview]
Message-ID: <54D82BCF.1090200@thinlink.com> (raw)
This update strengthens the incentive not to confirm double-spends after
time T (30 seconds). To grow and stabilize adoption, it is necessary to
influence the miner of the block after a deprecated block, who in turn
is concerned with the block after that. Accordingly, the disincentive is
changed from a simple delay to a temporary chain work penalty, which can
be negative. Hal Finney first suggested this in 2011.
The penalty is graduated in two steps based on the respend gap, for
reasons explained within. I believe it is the minimum required to
achieve the intended result.
Double-Spend Deprecation Window
https://github.com/dgenr8/out-there/blob/master/ds-dep-win.md
next reply other threads:[~2015-02-09 3:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 3:38 Tom Harding [this message]
2015-02-09 6:32 ` Peter Todd
2015-02-09 13:37 ` Tom Harding
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=54D82BCF.1090200@thinlink.com \
--to=tomh@thinlink$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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