Rusty Russell

I have merged the million-fixup-commits into one commit, and trivially rebased onto the updated #759. The last two commits are new: 1. Make spelling happy. 2. Add a method to...

> > What is the use of that? As far as I understand we could sue the person but this won't give us a cryptographic guarantee to get our money...

OK, trivial rebase to fixup, and also new commits: 1. signatures on offers are now optional. This makes them *much* smaller, particularly on mainnet where it's just "node_id", "description" and...

> @rustyrussell Is it possible to use a BOLT12 that's generated on the fly by the payer with just the payee's node pubkey? > Since the `signature` on Offers is...

OK, at @t-bast 's suggestion I removed recurrence for now. You're free to implement it, ofc, but don't assume wallets support it yet. I've also (trivially) rebased on the latest...

OK, I fixed the incorrect placement of the offers fields, rebased onto the latest #759 and squashed some fixup commits. It's still more than one commitment because I think it's...

> @rustyrussell Is it possible to use a BOLT12 that's generated on the fly by the payer with just the payee's node pubkey? Since the `signature` on Offers is optional,...

> I just finished reading up on stateless bolt11 invoices (#912), would there be a similar mechanism for bolt12 invoices? would it just be a matter of including the `payment_metadata`...

> Hey everyone, super pumped for BOLT12. First off, thanks for your spelling review! I applied almost all ("e.g." is used in the style guide, so I left that). >...

OK, rebased on latest #759 and folded into a single, neat "draft 5" commit. I've added one commit, which defines our first invoice feature (mpp). Feedback welcome!