On Mon, Feb 11, 2013 at 11:12 AM, Timo Hanke <timo.ha...@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. ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
