From: Tom Harding <tomh@thinlink.com>
To: Natanael <natanael.l@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP: Full Replace-by-Fee deployment schedule
Date: Mon, 29 Jun 2015 18:00:11 -0700 [thread overview]
Message-ID: <5591EA1B.1050709@thinlink.com> (raw)
In-Reply-To: <CAAt2M1_yiN8ouaTdiyx8n8CkaT=e-pdUqqtde-bC32enqLfHog@mail.gmail.com>
On 6/29/2015 5:51 PM, Natanael wrote:
> What you ask to see implemented will trivially fall to a sybil attack.
> It isn't securable. It is running on the honor system exclusively. It
> will be attacked, it will fail, losses will be had, the attackers will
> walk away with embarrassingly large sums.
Oh please. Checking that a node does relay something is not much
different than banning it for relaying garbage.
It just happens to require that you have two nodes and coordinate them
somehow. I didn't offer a complete design, don't claim magical
properties, and certainly didn't mean to imply that nodes passing a test
could be trusted (as you suggest with your "accountable parties").
next prev parent reply other threads:[~2015-06-30 1:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 5:07 [bitcoin-dev] BIP: Full Replace-by-Fee deployment schedule Peter Todd
2015-06-29 5:40 ` Luke Dashjr
2015-06-29 5:43 ` Gregory Maxwell
2015-06-29 5:51 ` Luke Dashjr
2015-06-29 5:56 ` Peter Todd
2015-06-29 5:53 ` Peter Todd
2015-06-29 6:00 ` Luke Dashjr
2015-06-29 6:16 ` sickpig
2015-06-30 0:21 ` Tom Harding
2015-06-30 0:51 ` Natanael
2015-06-30 1:00 ` Tom Harding [this message]
2015-06-30 1:10 ` Natanael
2015-06-30 1:18 ` Tom Harding
2015-06-30 1:37 ` Peter Todd
2015-06-30 13:12 ` Adam Back
2015-06-30 13:49 ` Chris Pacia
2015-06-30 14:53 ` Peter Todd
2015-06-30 14:02 ` David A. Harding
2015-06-30 16:05 ` Peter Todd
2015-06-30 18:23 ` Chris Pacia
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=5591EA1B.1050709@thinlink.com \
--to=tomh@thinlink.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=natanael.l@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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