From: Tom Harding <tomh@thinlink•com>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] DS Deprecation Window
Date: Thu, 06 Nov 2014 15:50:53 -0800 [thread overview]
Message-ID: <545C095D.4010703@thinlink.com> (raw)
In-Reply-To: <544FD47F.6060900@thinlink.com>
Added a section "Confidence to include tx1" and subsection "Deliberate
delay attack"
https://github.com/dgenr8/out-there/blob/master/ds-dep-win.md
I found that under concerted attack, if miner excludes any transaction
first seen less than 30 seconds ago, or double-spent less than 30
seconds after first seen, he should expect 5 of 10000 nodes to delay his
block.
Hal Finney remarked that this idea would need "careful analysis." More
help is very welcome.
https://bitcointalk.org/index.php?topic=3441.msg48789#msg48789
Cheers!
On 10/28/2014 10:38 AM, Tom Harding wrote:
> So, I think it will be possible to quantify and target the risk of
> including tx1...
>
next prev parent reply other threads:[~2014-11-06 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 19:58 Tom Harding
2014-10-27 20:17 ` Matt Corallo
2014-10-28 2:26 ` Tom Harding
2014-10-28 2:36 ` Gregory Maxwell
2014-10-28 17:38 ` Tom Harding
2014-11-06 23:50 ` Tom Harding [this message]
2014-10-28 6:24 ` Thomas Zander
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=545C095D.4010703@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