We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The meeting will take place on Monday 2022/07/04 at 8pm UTC (5:30am Adelaide time) on Libera Chat IRC #lightning-dev. It is open to the public.
A video link is available for higher bandwidth communication: https://meet.jit.si/Lightning-Spec-Meeting
max_dust_htlc_exposure_msat
update_fee
shutdown
update_*
gossip_timestamp_filter
channel_reestablish
The following are topics that we should discuss at some point, so if we have time to discuss them great, otherwise they slip to the next meeting.
The text was updated successfully, but these errors were encountered:
I'll be on holidays and will miss the next two (!!) spec meetings, have fun and don't hesitate to merge my PRs while I'm away 😉
Sorry, something went wrong.
Note that today is a holiday in the US as well. I'll be out, dunno about the rest of the LDK team, may be a skeleton crew today.
No branches or pull requests
The meeting will take place on Monday 2022/07/04 at 8pm UTC (5:30am Adelaide time) on Libera Chat IRC #lightning-dev. It is open to the public.
A video link is available for higher bandwidth communication: https://meet.jit.si/Lightning-Spec-Meeting
Pull Request Review
max_dust_htlc_exposure_msat
#919Waiting for interop
update_fee
duringshutdown
BOLT 2: forget the check aboutupdate_*
messages, and check what must not happens duringshutdown
#972gossip_timestamp_filter
Inconsistent behavior around graph dump ongossip_timestamp_filter
. #980channel_reestablish
Nodes shouldn't publish their commitment when receiving outdatedchannel_reestablish
#934Long Term Updates
Backlog
The following are topics that we should discuss at some point, so if we have time to discuss them great, otherwise they slip to the next meeting.
The text was updated successfully, but these errors were encountered: