From decker.christian at gmail.com Tue May 9 08:22:41 2017 From: decker.christian at gmail.com (Christian Decker) Date: Tue, 9 May 2017 10:22:41 +0200 Subject: [Lightning-dev] [RFC] Lightning payment format In-Reply-To: <87y3u624kn.fsf@rustcorp.com.au> References: <87h918ghdv.fsf@rustcorp.com.au> <87h90yeieo.fsf@rustcorp.com.au> <20170508112529.GA28181@nex> <87y3u624kn.fsf@rustcorp.com.au> Message-ID: <20170509082241.GA21968@nex> On Tue, May 09, 2017 at 11:07:28AM +0930, Rusty Russell wrote: > Hey, invoices are totally human readable, for some humans :) > I know Pieter can decode bech32 on the fly :-) > But a good point. So let's use BTC with m (milli), u (micro), n (nano) > and p (pico). In theory we could allow . in that part, but I think it's > too distracting. > > At $1600/BTC: > > 0.01c = 62500p > 1c = 6250n > $1 = 625u > $1000 = 625m Perfect, even though your price is already outdated, and it currently is $1700/BTC. I mention the conversion confusion because I often run into that problem myself (and keep typing 0s until the client complains). > > Other than that, I really like the proposal, it's clean and > > extensible, and it supports testnet ;-) I also like using bech32 as a > > serialization format, if people also support the DNS bootstrapping and > > node lookup they can simply reuse that dependency, and it is a bit > > shorter than hex. We might consider also supporting a different, human > > readable, encoding though (without changing the signature > > serialization). And finally we could directly derive a URI scheme from > > the bech32 encoded string by replacing the '1' with a ':', but we can > > spin that discussion off in another thread ^^ > > OK, if people like this change, I think we can move start turning this > into BOLT 10? Oops, I think I did what Luke hates, and sort of self assigned a proposal number... I can of course assign the DNS bootstrap BOLT another number. Cheers, Christian