From: jl2012 <jl2012@xbt•hk>
To: Jonathan Toomim <j@toom•im>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] On the security of softforks
Date: Thu, 17 Dec 2015 22:10:02 -0500 [thread overview]
Message-ID: <6bc6451f3d9cfb5e5a1ba15356c229bc@xbt.hk> (raw)
In-Reply-To: <E76D5BF9-41BF-4AF5-BBAC-06F4EF574EBE@toom.im>
Jonathan Toomim via bitcoin-dev 於 2015-12-17 21:47 寫到:
> Mallory wants to defraud Bob with a 1 BTC payment for some beer. Bob
> runs the old rules. Bob creates a p2pkh address for Mallory to use.
> Mallory takes 1 BTC, and creates an invalid SegWit transaction that
> Bob cannot properly validate and that pays into one of Mallory's
> wallets. Mallory then immediately spends the unconfirmed transaction
> into Bob's address. Bob sees what appears to be a valid transaction
> chain which is not actually valid.
>
> Clueless Carol is one of the 4.9% of miners who forgot to upgrade her
> mining node. Carol sees that Mallory included an enormous fee in his
> transactions, so Carol makes sure to include both transactions in her
> block.
>
> Mallory gets free beer.
>
> Anything I'm missing?
You miss the fact that 0-conf is not safe, neither 1-conf. What you are
suggesting is just a variation of Finney attack.
next prev parent reply other threads:[~2015-12-18 3:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 2:30 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 [this message]
2015-12-18 5:32 ` Jorge Timón
2015-12-18 6:12 ` Anthony Towns
2015-12-19 1:36 ` Chris
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=6bc6451f3d9cfb5e5a1ba15356c229bc@xbt.hk \
--to=jl2012@xbt$(echo .)hk \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=j@toom$(echo .)im \
/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