From: John Dillon <john.dillon892@googlemail•com>
To: Luke-Jr <luke@dashjr•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] libzerocoin released, what about a zerocoin-only alt-coin with either-or mining
Date: Sun, 14 Jul 2013 19:48:45 +0000 [thread overview]
Message-ID: <CAPaL=UW2-W_dOmF=NDjEpE2fvPuzk-G-cmFKkj2dHdHoO6ygXg@mail.gmail.com> (raw)
In-Reply-To: <201307141933.13754.luke@dashjr.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Sun, Jul 14, 2013 at 7:33 PM, Luke-Jr <luke@dashjr•org> wrote:
>> Merge mining is very much mining a coin for free. Ask not what the total
>> reward is, ask that the marginal cost of merge mining an additional coin
>> is.
>
> But the total reward is what mining will tend toward equalizing in costs.
> In any case, the cryptocurrencies are neutral to cost of mining, or perhaps
> even benefit from it being as cheap as possible: if it's cheaper to mine, you
> can get an even higher difficulty/security out of it.
Again, you forget that there may exist miners for which the value of the coin
is negative.
Never mind that in practice you want there to exist a cost to encourage miners
to actually pay attention to what they mind and to encourage them to update
software when required and participate.
>> The issue is that unless there is a cost to mining a *invalid* block
>> the merge mined coin has little protection from miners who mine invalid
>> blocks, either maliciously or through negligence. If the coin isn't worth
>> much, either because it's market value is low or the worth is negative to
>> the malicious miner, your theories of value have nothing to do with the
>> issue.
>
> Invalid blocks are rejected by validating clients in all circumstances.
Validating clients, not SPV clients.
> I suspect you may mean a block that doesn't include transactions you want
> confirmed. In that case, you must not be paying sufficient fees for the miner
> to consider it worth their time, or must be doing something the miner
> considers fundamentally objectionable (in which case they won't be satisfied
> by any fee). But these miners, unless they are able to acquire over 50% of the
> hashrate (in which case the cryptocoin is compromised), are not the only ones
> mining blocks, and if another miner accepts your transactions there is no
> issue.
All those things simply change the amount of alt-coin the miner gets, which to
the miner may have no reward. You also have the issue that we may be talking
about a non-currency chain where reward is more nebulous.
In any case, regarding a zerocoin chain, Peter's observation that
proof-of-sacrifice allows a strong 51% attck defense is very clever and IMO is
significantly stronger than proof-of-work mining, merged or not, would provide.
It's essentially the ability to conjur up mining capacity on demand, but only
by those who have a stake in the crypto-coin. It does depend on the existance
of a proof-of-work chain, but we have a perfectly good one handy.
PS: good to see you signing you email!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBCAAGBQJR4wCFAAoJEEWCsU4mNhiPIcwH+gLYbUPDi/7ITK02wftqEV2E
FSlzZ0W8aw7z7sF7hqPm7jpmtqbXdvQRSSy+XRDgWUxvF72o5oRTwOpY7xN8KOct
9rMwF35nld8An9FOjOB6NR3sIQxmAg9q7xoilZrOHyRFcz/UT0BexSZ3x5DrKIAB
6S7qalrGT0NWZx8CI0PRAzY8Nx+WouaoofBaypRaXBVJxigFqJlWNxgUM1FuoCL+
C1wn0hlbWfO42Mh9jdnFZXhH2Omd5V3PzIS/t2cJGTjrwr7nT6VAJu+0hbNZHI/q
yg0TGbO/01pp4OVe7WdLz9OktMqqDdDZJd6HWLQk07zqHS3iRJ2cpRIO6k9UCk0=
=oicX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-07-14 19:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 14:01 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
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 [this message]
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=UW2-W_dOmF=NDjEpE2fvPuzk-G-cmFKkj2dHdHoO6ygXg@mail.gmail.com' \
--to=john.dillon892@googlemail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/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