{"type":"rich","version":"1.0","author_name":"npub12tjaqer27049ejmvf0f3yd7kq6p93gg6ecavgrczge4rlzf59y5q2pye9h","author_url":"https://nostr.ae/npub12tjaqer27049ejmvf0f3yd7kq6p93gg6ecavgrczge4rlzf59y5q2pye9h","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2016-06-21\n📝 Original message:Thanks for starting this discussion, Erik.\n\n\n\u003e Should this be a new BIP?  I know netki's BIP75 is out there - but I think\n\u003e it's too specific and too reliant on the domain name system.\n\u003e\n\nThis is not quite accurate. BIP75 is designed to be independent of any name\nresolution system. You could use it with a static URL that you share, for\nexample, or even use it to implement a mesh-network payment system over\nbluetooth. Netki's wallet names do use DNS, but that isn't related to this\ndiscussion.\n\nWhat BIP75 *does* do is provide a way for a client to get a new payment\naddress for every payment. I personally think it is better than BIP47 for\nthe uses you mentioned (subscriptions, etc).\n\nI'm glad you brought up identity methods other than x509. At breadwallet we\nare thinking about how to establish the most universal system, and letting\nusers identify themselves with any of a selection of identity systems is\nideal. I think the pki_data slot should be constantly expanded to allow new\nidentity types, but they should be explained/standardized in the BIPs that\nadd them and use universal names. \"netki://\" wouldn't be appropriate, for\nexample, if their method is open sourced and possibly used by others--it\nshould instead be given a product name like \"dnswallet://\" or something\nmore clever.\n\nJames\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160621/316a6995/attachment.html\u003e"}