From: Tom Harding <tomh@thinlink•com>
To: Christophe Biocca <christophe.biocca@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] A statistical consensus rule for reducing 0-conf double-spend risk
Date: Tue, 06 May 2014 10:49:05 -0700 [thread overview]
Message-ID: <53692091.5040003@thinlink.com> (raw)
In-Reply-To: <CANOOu=_tpqz8wdDGj9x_xT5QcT=CHRbr+5Cewj5xuZyJ+ZurNw@mail.gmail.com>
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@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
next prev parent reply other threads:[~2014-05-06 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 0:29 Tom Harding
2014-05-04 2:54 ` Christophe Biocca
2014-05-06 17:49 ` Tom Harding [this message]
2014-05-12 4:41 ` Tom Harding
2014-05-12 13:04 ` 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=53692091.5040003@thinlink.com \
--to=tomh@thinlink$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=christophe.biocca@gmail$(echo .)com \
/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