{"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: Bitcoin proposals for aliases have limitations, including centralization, reliance on HTTPS and CA, and limited domain name usage. Namecoin integration is complex but effective.\n📝 Original message:The number of proposals \u003chttps://en.bitcoin.it/wiki/BIP_0015\u003e is not\ninfinite, here are their problems :\n\n- FirstBits : centralized\n- DNS TXT Records : DNSSEC is required to have a minimum of security,\nlimits usage to engineers, limits usage to some domain names (i won't be\nable to use a gmail address for example, because i don't control the\ngmail.com domain)\n- Server Service (DNS + a daemon) : Same as DNS TXT records\n- HTTPS Web service : relies on HTTPS and CA, bitcoin needs to be able\nto check the full certificate chain and access a list of up-to-date\ncertificate authorities (installed on the OS or provided with bitcoin).\nAnd don't forget the CA model is not 100% reliable (several CA hacked\nthis year + possible government control...).\n- IP Transactions : /This proposal seeks to enable DNS lookups for IP\ntransactions/ =\u003e same as above\n\nI know that providing a namecoin daemon with bitcoin is not the lighter\nsolution, but, if a better one existed i guess it would have already\nbeen integrated into bitcoin... (see in what state is my first attempt\nwith the HTTPS proposal : Send payments to emails, urls and domains in\nGUI \u003chttps://github.com/bitcoin/bitcoin/pull/174\u003e - /khalahan opened\nthis pull request April 20, 2011/)\n\nSo, what's next ?\n\nLe 16/12/2011 20:54, slush a écrit :\n\u003e Khalahan, honestly, using namecoin for aliases is (for me) clean\n\u003e example of over-engineering. I mean - it will definitely work if\n\u003e implemented properly. I played with a namecoin a bit (as my pool was\n\u003e the first 'big' pool supporting merged mining), but I think there's\n\u003e really long way to provide such alias system in namecoin and *cleanly\n\u003e integrate it with bitcoin*. Don't forget that people who want to do\n\u003e lookup need to maintain also namecoin blockchain with their bitcoin\n\u003e client. It goes against my instinct of keeping stuff easy.\n\u003e\n\u003e For example, yesterday I implemented HTTPS lookup for addresses into\n\u003e my fork of Electrum client. I did it in 15 minutes, it works as\n\u003e expected, it does the job and the implementation is really\n\u003e transparent, becuase implementation is 20 lines of code. There's no\n\u003e magic transformation, no forced \"?handle=\" parameters or whatever. And\n\u003e I don't care if somebody provide URL\n\u003e https://some.strange.domain/name-of-my-dog?myhandle=5678iop\u0026anything_else=True\n\u003e \u003chttps://some.strange.domain/name-of-my-dog?myhandle=5678iop\u0026anything_else=True\u003e\n\u003e\n\u003e And everybody can do the same in their clients, in their merchant\n\u003e solutions, websites or whatever. Everybody can do HTTPS lookup. But\n\u003e try to explain DNS, Namecoin, IIBAN, email aliases to other programmers...\n\u003e\n\u003e Those IIBAN - well, why not. At least I see the potential in PR. So\n\u003e far I understand it as some teoretic concept which is not supported by\n\u003e anything else right now. Give it few years until it matures and then\n\u003e add IIBAN alias to Bitcoin client too.\n\u003e\n\u003e Maybe I'm repeating myself already, but the way to go is to make\n\u003e aliases as easy as possible, so everybody can implement it in their\n\u003e own solution and thus practially remove the need of using standard\n\u003e bitcoin addresses for normal users. Using some superior technology,\n\u003e which is hard to implement or even understand won't solve the\n\u003e situation, because it will ends up with some reference implementation\n\u003e in standard client only and nobody else will use it.\n\u003e\n\u003e slush\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/cb3fc4b4/attachment.html\u003e"}