From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 486DA259 for ; Thu, 1 Jun 2017 05:54:56 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from blaine.gmane.org (unknown [195.159.176.226]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B82E5106 for ; Thu, 1 Jun 2017 05:54:54 +0000 (UTC) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dGJ4F-00070D-Ey for bitcoin-dev@lists.linuxfoundation.org; Thu, 01 Jun 2017 07:54:43 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: bitcoin-dev@lists.linuxfoundation.org From: Andreas Schildbach Date: Thu, 1 Jun 2017 07:54:37 +0200 Message-ID: References: <874lw0h4y3.fsf@rustcorp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@blaine.gmane.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 In-Reply-To: <874lw0h4y3.fsf@rustcorp.com.au> Content-Language: en-US X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL, RDNS_NONE autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] [RFC] Lightning invoice/payment format draft X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 05:54:56 -0000 In order for such messages to be dispatchable between apps, I suggest prepending with an URI scheme, similar to the already existing "bitcoin:" scheme. Also I suggest defining a MIME type, e.g. for usage in NFC NDEF messages or emails. What is the relation of this BIP to BIP21 and BIP70-72? Is there a reason for not extending BIP70? On 06/01/2017 03:28 AM, Rusty Russell via bitcoin-dev wrote: > Hi all, > > There's a pull request for a lightning payment format which I'd > love wider review on. It's bech32 encoded, with optional parts tagged: > > https://github.com/lightningnetwork/lightning-rfc/pull/183 > > There's an implementation with a less formal description here, too: > > https://github.com/rustyrussell/lightning-payencode > > Example: > Send 2500 microbitcoin using payment hash 00010203040506...0102 to me > @03e7156ae33b0a208d0744199163177e909e80176e55d97a2f221ede0f934dd9ad > within 1 minute from now (Tue 30 May 12:17:36 UTC 2017): > > lnbc2500u1qpvj6chqqqqsyqcyq5rqwzqfqqqsyqcyq5rqwzqfqqqsyqcyq5rqwzqfqypqdq5xysxxatsyp3k7enxv4jsxqz8slk6hqew9z5kzxyk33ast248j3ykmu3wncvgtgk0ewf5c6qnhen45vr43fmtzsh02j6ns096tcpfga0yfykc79e5uw3gh5ltr96q00zqppy6lfy > > Thanks! > Rusty. >