public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Chris <ctpacia@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] On the security of softforks
Date: Fri, 18 Dec 2015 20:36:21 -0500	[thread overview]
Message-ID: <5674B495.10903@gmail.com> (raw)
In-Reply-To: <E76D5BF9-41BF-4AF5-BBAC-06F4EF574EBE@toom.im>

[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]

On Dec 18, 2015, at 10:30 AM, Pieter Wuille via bitcoin-dev 
<bitcoin-dev@lists.linuxfoundation.org 
<mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
> 2) The risk of an old full node wallet accepting a transaction whose
> coins passed through a script that depends on the softforked rules.
>
There's that, but there's also a case where an attacker creates a 
majority chain that follows the old rules but not the new ones. 
Non-upgraded nodes would accept a transaction on what they believe to be 
the consensus chain only to find that when they try to spend those coins 
no one accepts them because they were part of an invalid chain.

This has the effect of dropping non upgraded nodes to a form of spv 
security without their consent.

This is in contrast to a hard fork where a full node operator could 
explicitly set their node to accept higher version blocks that it can't 
validate. They get the soft fork functionality back but they have at 
least consented to it rather than have it forced on them. Doing forks 
that way would also have the benefit of notifying the user they are 
accepting unvalidated coins, whereas they wont know that in a soft fork.

[-- Attachment #2: Type: text/html, Size: 3213 bytes --]

  parent reply	other threads:[~2015-12-19  1:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18  2:30 [bitcoin-dev] On the security of softforks Pieter Wuille
2015-12-18  2:47 ` Jonathan Toomim
2015-12-18  3:02   ` Eric Lombrozo
2015-12-18 12:18     ` Peter Todd
2015-12-19 15:48       ` Bryan Bishop
2015-12-18  3:10   ` jl2012
2015-12-18  5:32     ` Jorge Timón
2015-12-18  6:12   ` Anthony Towns
2015-12-19  1:36   ` Chris [this message]
2015-12-19 17:46   ` Andrew
2015-12-20  4:14   ` Rusty Russell
2015-12-20 19:16     ` jl2012

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=5674B495.10903@gmail.com \
    --to=ctpacia@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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