public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] [RFC] Lightning invoice/payment format draft
Date: Thu, 1 Jun 2017 07:54:37 +0200	[thread overview]
Message-ID: <ogoa6o$o4s$1@blaine.gmane.org> (raw)
In-Reply-To: <874lw0h4y3.fsf@rustcorp.com.au>

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.
> 




      parent reply	other threads:[~2017-06-01  5:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01  1:28 [bitcoin-dev] [RFC] Lightning invoice/payment format draft Rusty Russell
2017-06-01  3:42 ` [bitcoin-dev] [Lightning-dev] " ZmnSCPxj
2017-06-01  3:48   ` ZmnSCPxj
2017-06-01  5:54 ` Andreas Schildbach [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ogoa6o$o4s$1@blaine.gmane.org' \
    --to=andreas@schildbach.de \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox