[Bitcoin-development] A statistical consensus rule for reducing 0-conf double-spend risk
Tom Harding
tomh at thinlink.com
Tue May 6 17:49:05 UTC 2014
Christophe Biocca wrote:
> it becomes trivial with a few tries to split the network into two
> halves: (tx1 before tx2, tx2 before tx1).
"before" implies T=0. That is a much too optimistic choice for T; 50%
of nodes would misidentify the respend.
> Tom Harding <tomh at thinlink.com> wrote:
>> - Eventually, node adds a consensus rule:
>> Do not accept blocks containing a transaction tx2 where
>> - tx2 respends an output spent by another locally accepted
>> transaction tx1, and
>> - timestamp(tx2) - timestamp(tx1) > T
More information about the bitcoin-dev
mailing list