[c-lightning] Development priorities for 0.6?

Rusty Russell rusty at rustcorp.com.au
Thu Mar 1 20:38:17 AEDT 2018

Christian Decker <decker.christian at gmail.com> writes:
> I think we are pretty close to feature complete already, but there are a
> few things we won't be able to change too much after a release:
>  - We should probably do another pass over the JSON-RPC and see that
>    it's future proof
>  - We definitely need to make DEVELOPER=0 the default config, so that
>    issues like `dev-setfees 0` don't happen
> As for specific issues, I think critical ones are:
>  - JSON parse chokes on escaped quotes in strings #387
>  - Track owned outputs when they are being spent on the blockchain #451
>  - Empty close transaction on very low value channels #632
>  - Implement DNS based node lookup and bootstrapping #246
>  - Ability to disconnect with a peer #812


> I was deferring the implementation of DNS lookups for seeds since we
> don't yet have async name resolution, but I saw that we do sync in some
> cases, so I could just rely on that as well for now.

Yes, just put in a FIXME and we can get smart later.

> My WIP PR #1117 should also get rid of the need for `dev-rescan-outputs`
> so we can keep that a developer-only call, and it fixes #451.
> Shall we go through the issues and just assign them to v0.6?

Please do, and also mark bugs.


More information about the c-lightning mailing list