public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: John Dillon <john.dillon892@googlemail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Jorge@vps7135.xlshosting.net
Subject: Re: [Bitcoin-development] libzerocoin released, what about a zerocoin-only alt-coin with either-or mining
Date: Sun, 14 Jul 2013 19:52:56 +0000	[thread overview]
Message-ID: <CAPaL=UWBj2vhGMMzGAxGcjq3T8aO8+wMravQ4UXbi0w9DUEtAQ@mail.gmail.com> (raw)
In-Reply-To: <20130714194205.GA27202@vps7135.xlshosting.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Jul 14, 2013 at 7:42 PM, Pieter Wuille <pieter.wuille@gmail.com> wrote:
> On Sun, Jul 14, 2013 at 07:33:06PM +0000, Luke-Jr wrote:
>> Invalid blocks are rejected by validating clients in all circumstances.
>
> I don't think that's what John means.
>
> If you have hash power for the parent chain, mining invalid blocks for the
> merge-mined chain costs you nothing. Yes, they will be invalid, but you've
> lost nothing.
>
> The basic assumption underlying mining security is that it is more profitable
> to collaborate with mining a chain (and profit from the block payout) than to
> attack it. In the case of merged mining, this assumption is not valid.

You said it better than I did.

Essentially I am worried about the chain being strangled at birth, merge-mining
makes doing so cost nothing for the attacker. With zerocoin this is a
particularly dangerous possibility due to those in the Bitcoin community who
would like to see Bitcoin continue to have poor privacy properties.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBCAAGBQJR4wF9AAoJEEWCsU4mNhiPtCgH/3QLvFer3QHNU7AP+nehwcgK
QS3xLv60lvm+pYLVAp9xFyJ5SCHVGTPvWRBmoldk8xxh9ORHlNEsnrcx9ZONTJ4F
ja4Alp9MLZK5S8dKk2juJNdKziyRkQci/nNwuqepX5JjCIRNZq1lcW4Be4W7InPt
Ltrvp7lA03uNuAXxtlYnko4mEY5l1NiBp4BvhGZ6+GRdCltPeIk2m0NwLDHWd31t
qFLnnPSw0/9FGVs7lOaWuxbMGwPzGrIu6TXm17dqgBsl+8JuP6zHFE1ccqIxKyb6
Tdf4yNvhsvE+qlTnmcQNxM9nMHL4uqBZqJR174fAKQzcNGzVLloqbmRqKzuw5o4=
=leUJ
-----END PGP SIGNATURE-----



  reply	other threads:[~2013-07-14 19:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 14:01 [Bitcoin-development] libzerocoin released, what about a zerocoin-only alt-coin with either-or mining Adam Back
2013-07-12 13:18 ` Peter Todd
2013-07-13  9:51   ` Jorge Timón
2013-07-13  9:53     ` Jorge Timón
2013-07-13 18:32       ` Peter Vessenes
2013-07-15  9:51         ` Peter Todd
2013-07-15 13:05           ` Jorge Timón
2013-07-15 20:29             ` Peter Todd
2013-07-16  3:54               ` Peter Vessenes
2013-07-13 18:42     ` Adam Back
2013-07-14 11:18       ` Jorge Timón
2013-07-14 19:22         ` John Dillon
2013-07-14 19:33           ` Luke-Jr
2013-07-14 19:42             ` Pieter Wuille
2013-07-14 19:52               ` John Dillon [this message]
2013-07-14 20:16               ` Luke-Jr
2013-07-15  0:12                 ` Peter Todd
2013-07-15  1:51                   ` Luke-Jr
2013-07-15  1:59                     ` Peter Todd
2013-07-14 19:48             ` John Dillon
2013-07-15  0:14           ` Adam Back
2013-07-15  0:29           ` Peter Todd

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='CAPaL=UWBj2vhGMMzGAxGcjq3T8aO8+wMravQ4UXbi0w9DUEtAQ@mail.gmail.com' \
    --to=john.dillon892@googlemail.com \
    --cc=Jorge@vps7135.xlshosting.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=pieter.wuille@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