{"type":"rich","version":"1.0","author_name":"npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p","author_url":"https://nostr.ae/npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2012-01-31\n📝 Original message:I also wonder whether the \"send to private address\" should be part of this\nBIP, or a future one.\n\nIMO (but your mileage may vary) this BIP should only define the bare-bones\nURL scheme, AND provide room for future extensions such\nas send-to-private-address, send-multiple-signers, and so on. These should\nbe forwards-compatible (as Luke-Jr says) in the sense that older clients\ncan detect schemes they don't understand and give the user an appropriate\nerror message.\n\nMaybe we need a send-type parameter to define the scheme?\n\nGood point on the version parameter. How are clients supposed to handle\nthis? Refuse to handle the request if their URL scheme parser version is\nolder than in the URL? This should be in the BIP.\n\nWladimir\n\nOn Tue, Jan 31, 2012 at 9:23 AM, Andreas Schildbach\n\u003candreas at schildbach.de\u003ewrote:\n\n\u003e Generally I prefer BIP 21 over BIP 20.\n\u003e\n\u003e I'm neutral on the 'send' parameter - present in both BIPs - which I\n\u003e don't understand. I think a practical usecase should be given in the BIP.\n\u003e\n\u003e Also, the 'version' parameter is unclear. What does it mean? Is an oder\n\u003e defined on versions (1.0b \u003e 1.0)? Why is it an \";\" parameter rather than\n\u003e a normal \"\u0026\" parameter?\n\u003e\n\u003e\n\u003e On 01/30/2012 12:55 AM, Amir Taaki wrote:\n\u003e \u003e Matt Corallo posted a modification of BIP 20 in an earlier email and I\n\u003e \u003e asked him if he wanted to become the champion of that BIP he submitted.\n\u003e \u003e\n\u003e \u003e It is a modification of BIP 20 sans the alternative non-decimal number\n\u003e \u003e stuff.\n\u003e \u003e\n\u003e \u003e https://en.bitcoin.it/wiki/BIP_0021\n\u003e \u003e\n\u003e \u003e Right now, I will ask the GUI client implementations like MultiBit or\n\u003e \u003e Bitcoin-Qt, not different codebases like BitCoinJ or libbitcoin if they\n\u003e \u003e support BIP 20 or BIP 21. Feel free to raise any objections.\n\u003e \u003e\n\u003e \u003e More weight will be given to GUIs with actual URI sche me\n\u003e \u003e implementations and it's good to have a general consensus.\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e\n\u003e ------------------------------------------------------------------------------\n\u003e \u003e Try before you buy = See our experts in action!\n\u003e \u003e The most comprehensive online learning library for Microsoft developers\n\u003e \u003e is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,\n\u003e \u003e Metro Style Apps, more. Free future releases when you subscribe now!\n\u003e \u003e http://p.sf.net/sfu/learndevnow-dev2\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e _______________________________________________\n\u003e \u003e Bitcoin-development mailing list\n\u003e \u003e Bitcoin-development at lists.sourceforge.net\n\u003e \u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Keep Your Developer Skills Current with LearnDevNow!\n\u003e The most comprehensive online learning library for Microsoft developers\n\u003e is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,\n\u003e Metro Style Apps, more. Free future releases when you subscribe now!\n\u003e http://p.sf.net/sfu/learndevnow-d2d\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-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20120131/8214b95c/attachment.html\u003e"}
