{"type":"rich","version":"1.0","author_name":"npub1euw92v2lmlflea24tgns69r4gxwfknh3ufj0ata70hrk7jxkhgws0l06dn","author_url":"https://nostr.ae/npub1euw92v2lmlflea24tgns69r4gxwfknh3ufj0ata70hrk7jxkhgws0l06dn","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2011-12-16\n🗒️ Summary of this message: Namecoin is a decentralized system designed to map names to other things, such as public bitcoin addresses or URLs, and is not limited to .bit usage. It is proven technology, has no single point of failure, and is easily connectable to bitcoin.\n📝 Original message:Namecoin is a peer-to-peer generic name/value datastore system.\nDon't forget it's not limited to .bit usage ! So, directly mapping\nthings to .bit url would not be the optimal way of using namecoin.\n\nNamecoin is *specificaly designed to map things to names* in a fully\ndecentralized way. So, it's the perfect starting point to map names to\nother things (a public bitcoin address, an url, etc)\nYou won't have all the advantages of namecoin when using other systems\nlike DNS and HTTP(S) as the first entry point.\n\nWhat is namecoin ?\n\n* proven technology :\n- do not mix the namecoin technology and the dot-bit namespace with .bit\ndomains (dot-bit domains needs dot-bit compatible dns servers or proxies\n+ namecoin and have a small visibility due to the nature of\ntop-to-bottom domain name system controlled by ICANN, namecoin needs\nonly namecoin to store data !)\n- as proven and secure as bitcoin\n- merged mining provides a secure network\n\n* decentralized :\n- a lot of nodes, and you can have your own node\n- everybody can register his own name, by itself with the namecoin\nsoftware (bitcoin could even allow registration directly from it,\neasily) or by using a name provider\n- everybody can become a name provider (register for your friends and\nresell names).\n\n* no single point of failure :\n- DNS and HTTPS have several limitations (Man in the Middle attacks, no\nreliable authority of certifications, domain seizure, ...)\n\n* designed for that :\n- namecoin uses a system of namespaces to separate each usages :\nhttp://dot-bit.org/Main_Page#Namespaces.\nFor example, the \"personal namespace\" draft\n(http://dot-bit.org/Personal_Namespace) could be extended to support\nmapping to a bitcoin address, or a dedicated namespace can be used if\nprefered (the \"bitcoin/\" or \"alias/\" or \"map/\" prefixes for example).\n\n* easily connectable to bitcoin\n- they both use RPC and json to exchange informations, so connecting one\nto the other is really easy\n- bitcoin could even allow registration of names by sending an RPC\nrequest to namecoin\n\n* extensible and not limited :\n- you are not forced to store a bitcoin address directly in namecoin,\nyou can also store an url or a domain name\n- allows additional security : add a certificate fingerprint combined\nwith an https url (so, using DNS or HTTP(S) is not a major problem\nanymore if the first point of entry is really secure and configurable\n[and you use and self-signed certificate])\n- really easy to update\n- simple for simple cases\n- possibility to use a nick, an email address or a domain as name\n- other methods to get bitcoins addresses can be added later, protocol\nis extensible\n\n\nExamples of possible registered names in namecoin with the \"personal\nnamespace\" (with the \"p/\" prefix) :\n\n* An individual person with well known public addresses :\n\"p/*khal*\":\n{\n    \"email\": \"khal at dot-bit.org\",\n    \"bitcoin\": \"1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T\",\n    \"namecoin\": \"N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9\"\n}\n\n* Another individual person with well known public addresses :\n\"p/*khal at dot-bit.org*\":\n{\n    \"bitcoin\": \"1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T\",\n    \"namecoin\": \"N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9\"\n}\n\n* A merchant accepting payments in bitcoin, namecoin, paypal or\nothercoin (to show you how the whole namespace could be used) :\n\"p/*mymerchant.com*\":\n{\n    \"bitcoin\": {\n        \"url\": \"https://payto.mymerchant.com/bitcoin/\",\n        \"fpr\": \"54FFA829023FC4DEF26B9339E07F7A743DF9F926\"\n        \"cert\": \"https://payto.mymerchant.com/certificate.pem\",\n    },\n    \"namecoin\": {\n        \"url\": \"https://payto.mymerchant.com/namecoin/\",\n        \"fpr\": \"54FFA829023FC4DEF26B9339E07F7A743DF9F926\"\n    },\n    \"paypal\": \"xxxxxx at yyyyyyyyy.zzz\",\n    \"othercoin\": \"oxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\"\n}\n\n* A merchant with a public address, an url to generate custom addresses\nand a domain name (not sure if this case is really usefull, maybe as\nfallback)\n\"p/*mymerchant2*\":\n{\n    \"bitcoin\": {\n        \"url\": \"https://payto.mymerchant.com/bitcoin/\",\n        \"fpr\": \"54FFA829023FC4DEF26B9339E07F7A743DF9F926\",\n        \"dns\": \"_bitcoin.payto.mymerchant.com\",\n        \"address\": \"1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T\",\n    }\n}\n\n\n* How to use it in bitcoin ?\n\nSeveral possibilities of address syntax :\n- khal, khal at dot-bit.org, mymerchant.com, mymerchant2 : no syntax limit\n- mymerchant2 at bitcoin : will conflict with names already containing a @\n- mymerchant2 at namecoin : same\n- namecoin:mymerchant2 : strange syntax, confusing with the \"uri scheme\"\n- namecoin://mymerchant2 : same\n- other ?\n\n\nHere is how things would be processed when people put an address to pay\nto in the bitcoin client :\n\n* address : khal\n-\u003e RPC to namecoin for \"p/khal\"\n-\u003e json processing for \"p/khal-\u003ebitcoin\"\n-\u003e result : 1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T\n\n* address : khal at dot-bit.org\n-\u003e RPC to namecoin for \"p/khal at dot-bit.org\"\n-\u003e json processing for \"p/khal at dot-bit.org-\u003ebitcoin\"\n-\u003e result : 1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T\n\n* address : mymerchant.com\n-\u003e RPC to namecoin for \"p/mymerchant.com\"\n-\u003e json processing for \"p/mymerchant.com-\u003ebitcoin\"\n-\u003e json processing for \"p/mymerchant.com-\u003ebitcoin-\u003eurl\" and\n\"p/mymerchant.com-\u003ebitcoin-\u003efpr\"\n-\u003e https request to \"https://payto.mymerchant.com/bitcoin/\"\n-\u003e result : 1xyxyxyxyxyxyxyxyxyxyxyxyxyxy\n\n* address : mymerchant2\n-\u003e RPC to namecoin for \"p/mymerchant2\"\n-\u003e json processing for \"p/mymerchant2-\u003ebitcoin\"\n-\u003e json processing for \"p/mymerchant2-\u003ebitcoin-\u003eurl\" and\n\"p/mymerchant2-\u003ebitcoin-\u003efpr\"\n-\u003e https request to \"https://payto.mymerchant.com/bitcoin/\"\n-\u003e result : error (website unavailable, page not found, timeout, etc)\n-\u003e json processing for \"p/mymerchant2-\u003ebitcoin-\u003edns\"\n-\u003e dns request for \"_bitcoin.payto.mymerchant.com\"\n-\u003e result : 1xyxyxyxyxyxyxyxyxyxyxyxyxyxy\n\n\nLe 15/12/2011 20:59, theymos a écrit :\n\u003e Bitcoin already has code and a protocol for transactions to IP\n\u003e addresses. Why not reuse that for dynamic address lookup? Just a few\n\u003e changes are necessary to enable complete user at server.com handling:\n\u003e - Extend the protocol so that \"reply\" messages can be signed by a fixed\n\u003e   public key\n\u003e - Extend \"checkorder\" messages so they can specify an account to\n\u003e   send BTC to. Or standardize on how to put the account into the\n\u003e   message field.\n\u003e - Enable DNS lookups for IP transactions. The DNS-only proposals could\n\u003e   also be used here to avoid having to use the IP transaction protocol\n\u003e   sometimes. The public key for signing \"reply\" messages can be gotten\n\u003e   from TXT records. This will be safe with DNSSEC and Namecoin. With\n\u003e   plain DNS Bitcoin could take a SSH-like approach and ask the user to\n\u003e   verify the public key the first time it is used, remembering it later.\n\u003e\n\u003e DoS attacks are already handled by the IP transactions code: the same IP\n\u003e address is always given the same bitcoin address until it pays to that\n\u003e bitcoin address.\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e 10 Tips for Better Server Consolidation\n\u003e Server virtualization is being driven by many needs.  \n\u003e But none more important than the need to reduce IT complexity \n\u003e while improving strategic productivity.  Learn More! \n\u003e http://www.accelacomm.com/jaw/sdnl/114/51507609/\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\n\n-- \nBest Regards,\nKhalahan\nhttp://dot-bit.org/\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111216/e4feca94/attachment.html\u003e"}