From: Gregory Maxwell <gmaxwell@gmail•com>
To: timo.hanke@web•de
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Blockchain as root CA for payment protocol
Date: Mon, 11 Feb 2013 11:21:25 -0800 [thread overview]
Message-ID: <CAAS2fgST69zZAWPbkuLGPCY36SNOiNFVjSmp-HRVRHF+wcZqYg@mail.gmail.com> (raw)
In-Reply-To: <20130211191259.GA22257@crunch>
On Mon, Feb 11, 2013 at 11:12 AM, Timo Hanke <timo.hanke@web•de> wrote:
> It's not about technical differences, but about the different use or
> purpose, which can result in different security demands. I argue that
> DNS has a lower demand in this respect than payment ids have. So DNS
> data can be in a chain with a hashrate lower than bitcoin's hashrate but
> payment ids _for_ bitcoin have to be in a chain with equal hashrate.
It seems you're not very well informed about what namecoin does— it's
a multiple namespace key-value store. And, as Peter pointed out— a
non-parasitic system can have exactly the same POW hashpower. Namecoin
chose a model which made it so that namecoin could survive even if
Bitcoin failed, but you don't have to.
I strongly recommend you listen to Peter and Luke— externalizing the
costs of your services onto people who do not care about them is not
going to produce good results for anyone. It's possible to accomplish
what you want to accomplish without taking resources from the users of
the Bitcoin currency without their consent— and you have people here
who are willing to help you figure out how.
next prev parent reply other threads:[~2013-02-11 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 10:03 Timo Hanke
2013-02-08 11:01 ` Peter Todd
2013-02-09 14:33 ` Timo Hanke
2013-02-09 19:01 ` Luke-Jr
2013-02-11 19:12 ` Timo Hanke
2013-02-11 19:21 ` Gregory Maxwell [this message]
2013-02-11 11:21 ` Peter Todd
2013-02-11 19:39 ` Rick Wesson
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=CAAS2fgST69zZAWPbkuLGPCY36SNOiNFVjSmp-HRVRHF+wcZqYg@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=timo.hanke@web$(echo .)de \
/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