Agenda for 2019-02-04

[rustyrussell]

At @cdecker suggestion, create a label (and an issue) for things people want to discuss in meeting.

[rustyrussell]

1. I would like to tag 1.0 at this meeting. There are more tweaks, but there always are... Perhaps after we approve the pending clarification fixes: https://github.com/lightningnetwork/lightning-rfc/labels/spelling and option_data_loss_protect: concretely define my_current_per_commitment_point #550
2. I would like to discuss more formalized unit tests. I've started such a thing here: https://github.com/rustyrussell/lightning-rfc/tree/guilt/tests
3. Would like decision on simplified_commitment_tx; should the feerate minimum be a separate feature, to avoid relying on change in bitcoind relay policy?
4. Would like to discuss feature bits; combine "routing" vs "peer" or expand node_announcement to have two bitmaps?
5. Would like to start assigning feature bits, for easier experimentation with interoperability.

[cdecker]

• I'm currently working on the multi-hop onion implementation I mentioned here multi: implement WIP extra onion blob encoding scheme as prep for AMP and beyond  lightningnetwork/lightning-onion#31 (comment). And I'm wondering whether we should rename the hops to frames since the payload frames are no longer related to physical hops. It'd make the idea much cleaner, since we can talk about multiple 65 byte frames making up a variable sized per hop payload.