📅 Original date posted:2020-01-31
📝 Original message:
Dear Fellow Protocol Devs,
the next meeting is this Monday (2020/02/03), and to facilitate review
and meeting preparations we have prepared a short agenda [1].
We switched over to a Github issue to prepare the agenda, since we
already heavily rely on the infrastructure for all of our other
tasks. Since this requires a bit of curation to keep the top post
updated I am curating the list based on feedback on the issue and in
other places. If you think that there is an open issue, open pull
request, or other topic that should be discussed next Monday please let
me know and I'll amend accordingly. Please let me know as soon as
possible to give other devs a chance to catch up prior to the meeting.
The current agenda looks like this:
```markdown
# Pull Request Review
- [ ] Single-option large channel proposal #596
- [ ] BOLT 7: be more aggressive about sending our own gossip. #684
- [ ] Bolt 1: Specify that extensions to existing messages must use TLV #714 (@t-bast)
- Gossip channel queries
- [ ] BOLT7: reply_channel_range parameter #560
- [ ] BOLT 7: clarify how to decode empty arrays #729
- [ ] BOLT 7: clarify how to encode multiple `reply_channel_range` messages #730
# Long Term Updates
- [ ] Current status of the trampoline routing proposal (@t-bast)
# Research
- [ ] How can we improve the gossip (`gossip_queries_ex`)? (@t-bast)
```
Looking forward to Monday,
Christian
[1] https://github.com/lightningnetwork/lightning-rfc/issues/731
Christian Decker [ARCHIVE] /
npub1wt…gtuyn
2023-06-09 12:58:29
in reply to nevent1q…aay7
Author Public Key
npub1wtx5qvewc7pd6znlvwktq03mdld05mv3h5dkzfwd3dc30gdmsptsugtuynPublished at
2023-06-09 12:58:29Event JSON
{
"id": "58f5ce5649d79487cab09f40a353e071636fd7a20b68b25386db8f8ca2e14a18",
"pubkey": "72cd40332ec782dd0a7f63acb03e3b6fdafa6d91bd1b6125cd8b7117a1bb8057",
"created_at": 1686315509,
"kind": 1,
"tags": [
[
"e",
"b650cecc88a52bbb3a3e44508c98069de7042c036c6670c987b786e82efe104e",
"",
"reply"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "📅 Original date posted:2020-01-31\n📝 Original message:\nDear Fellow Protocol Devs,\n\nthe next meeting is this Monday (2020/02/03), and to facilitate review\nand meeting preparations we have prepared a short agenda [1].\n\nWe switched over to a Github issue to prepare the agenda, since we\nalready heavily rely on the infrastructure for all of our other\ntasks. Since this requires a bit of curation to keep the top post\nupdated I am curating the list based on feedback on the issue and in\nother places. If you think that there is an open issue, open pull\nrequest, or other topic that should be discussed next Monday please let\nme know and I'll amend accordingly. Please let me know as soon as\npossible to give other devs a chance to catch up prior to the meeting.\n\nThe current agenda looks like this:\n\n\n```markdown\n# Pull Request Review\n- [ ] Single-option large channel proposal #596\n- [ ] BOLT 7: be more aggressive about sending our own gossip. #684\n- [ ] Bolt 1: Specify that extensions to existing messages must use TLV #714 (@t-bast)\n - Gossip channel queries\n - [ ] BOLT7: reply_channel_range parameter #560\n - [ ] BOLT 7: clarify how to decode empty arrays #729\n - [ ] BOLT 7: clarify how to encode multiple `reply_channel_range` messages #730\n\n# Long Term Updates\n- [ ] Current status of the trampoline routing proposal (@t-bast)\n\n# Research\n- [ ] How can we improve the gossip (`gossip_queries_ex`)? (@t-bast)\n```\n\nLooking forward to Monday,\nChristian\n\n[1] https://github.com/lightningnetwork/lightning-rfc/issues/731",
"sig": "ca99baac7e0453386339b8f3fcb66517a1d9d6deff8973fb54a753872ccd43dbe39d85d9a1d4f95b833f415d75eb538ccd1d3ab117863263431813698d3130b0"
}