[c-lightning] Development priorities for 0.6?
jajomojo at gmail.com
Mon Apr 30 19:31:59 AEST 2018
Good morning ZmnSCPxj!
בתאריך שבת, 28 באפר' 2018, 23:25, מאת ZmnSCPxj <ZmnSCPxj at protonmail.com>:
> Good morning Jan,
> #1394 API change: `close` command accept channel ID
> was added to the 0.6 target, and will require a change in `close`
Sure. Thanks for info. I'm keeping an eye and have read what's there so
far. Here's how I understand it:
A parameter is being added to 'close' command, which until now cared only
about the peer, but after the change there can be multiple channels to one
peer (with different globally unique IDs so that once we have channelID,
the peerID is not needed). So after the change it will be something like
close [ <peer_id> | <channel_id> ]
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On April 27, 2018 6:24 PM, Ján Sáreník <jajomojo at gmail.com> wrote:
> Hi there!
> ZmnSCPxj <ZmnSCPxj at protonmail.com> wote:
>> Good morning c-lightningers,
>> There remain only 2 issues that are tagged with 0.6:
>> #551 onchaind: restart in case of reorg
>> Basic analysis suggests we already actually closed this, but neglected to
>> actually update the issue.
>> #546 HTLC expiry etc. must be checked against config.
>> Basic analysis suggests most config items are already being checked (just
>> not near the line shown), but I still need to check in more detail.
>> Are there any particular issues or changes we still want to make for 0.6
>> or can we start preparing for 0.6 release?
> Please let me know if there's any new documentation connected to the
> changes for 0.6 that specifically needs proofreading or formatting. I'll be
> happy to help with that.
> Have a nice weekend!
> Best regards, Ján
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the c-lightning