Commit Graph

252 Commits

Author SHA1 Message Date
lisa neigut 67703823c5 0.8.2 Changelog Update
0.8.2, we're doing it
2020-04-30 15:15:46 -05:00
lisa neigut f637b88932 v0.8.2rc3 changelog updates
We're doing an RC3 folks!
2020-04-28 15:08:46 -05:00
lisa neigut 10f47b41fa changelog: update to rc2
Changelog-None
2020-04-24 14:23:42 -05:00
lisa neigut 6b2f6612e2 changelog: use correct format for label 2020-04-20 13:48:11 -05:00
lisa neigut 8189e9a64d v0.8.2-rc1 Changelog updates
Changelog-None
2020-04-19 08:07:47 +09:30
Rusty Russell 7de03e990f CHANGELOG.md: 0.8.1: "Channel to the Moon"
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-02-17 19:07:09 +10:30
Rusty Russell 0b123a3cec CHANGELOG.md: 0.8.1rc3
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-02-15 09:04:50 +10:30
Rusty Russell 243078ac0c CHANGELOG.md: fix extra 'v' in version.
Breaks `tools/build-release.sh`

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-02-15 08:48:04 +10:30
Rusty Russell e7a1cf137a CHANGELOG.md: v0.8.1rc2
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-02-13 16:10:26 +10:30
Rusty Russell fc4d01cd9d db: put scids in forwards even if we didn't actually send.
If the peer is not connected, or other error which means we don't
actually create an outgoing HTLC, we don't record the
short_channel_id.  This is unhelpful!

Pass the scid down to the wallet code, and explicitly hand the
scid and amount down to the notification code rather than handing it
the htlc_out (which it doesn't need).

Changelog-Changed: JSON API: `listforwards` now shows `out_channel` even if we couldn't forward.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-02-12 22:27:57 -06:00
Rusty Russell ff968e7730 CHANGELOG.md: Update for 0.8.1-rc1.
Normalized lines; split some where we've deprecated something (needs a
line each in Deprecated section).

Also, removed unused [Unreleased] footnote in favor of [0.8.0] footnote.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-02-12 16:23:28 +10:30
Christian Decker c15169b463 release: Updating changelog to v0.8.0 final 2019-12-16 21:25:35 +01:00
Christian Decker eb2b225c9f changelog: Update the changelog for 0.8.0rc2 2019-12-13 22:46:30 +01:00
Michael Schmoock 727d6a0415 doc: correct wording in changelog 2019-12-12 13:56:16 +01:00
Christian Decker 9660549b0c changelog: Update changelog for the 0.7.4 release 2019-12-12 00:15:23 +01:00
Rusty Russell 6fa965c6b5 CHANGELOG.md: reset to Unreleased.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-10-30 12:59:16 -05:00
lisa neigut 5bc2de8997 update version to 0.7.3 2019-10-28 15:23:37 -05:00
lisa neigut 0cee553ed7 remove reverted feature desc 2019-10-28 15:23:37 -05:00
Rusty Russell 21d2cc663b lightningd: apply feerate changes correctly.
Feerate changes are asymmetric, as they can only be sent by the funder.

For FUNDER, the remote feerate is set when upon send of
commitment_signed, and the local feerate is set on receipt of
revoke_and_ack.

For non-funder, the local feerate is set on receipt of
commitment_signed, and the remote feerate set on send of
revoke_and_ack.  In our code, these two happen together.

channeld gets this right, but lightningd ignored the funder/fundee
distinction, and as a result, receipt of a commitment_signed by the
funder altered fees in the database.  If there was a reconnection
event or restart, then these (incorrect) values would be used, causing
us to complain about a 'Bad commit_sig signature' and close the
channel.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-10-28 13:07:41 -05:00
lisa neigut d5706b80c0 rc3 2019-10-21 15:29:43 +02:00
lisa neigut 6b1b99d7de release 0.7.3 2019-10-18 08:32:15 +02:00
lisa neigut f278416708 changelog: update to rc2 2019-10-15 22:38:34 +02:00
lisa neigut 422b4502d3 funding: add RPC arg to specify a 'close_to' address
Takes advantage of upfront-shutdown-script to permit users to
specify the close-to address for a channel at open, by adding
a `close_to` field to `fundchannel_start`.

Note that this only is in effect if `fundchannel_start` returns
with `close_to` set -- otherwise, peer doesn't
support `option_upfront_shutdown_script`.
2019-10-15 19:10:05 +02:00
Rusty Russell 1f0b86e575 lightningd: add checkmessage JSON command.
I wanted to call it verifymessage, but then I read the LND API for that
and wanted nothing to do with it!

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-10-14 18:58:44 -05:00
Rusty Russell fc9a2a5dba lightningd: add signmessage JSON command.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-10-14 18:58:44 -05:00
Rusty Russell ca53c1b699 gossipd: push our own gossip messages harder.
I had a report of a 0.7.2 user whose node hadn't appeared on 1ml.  Their
node_announcement wasn't visible to my node, either.

I suspect this is a consequence of recent version reducing the amount of
gossip they send, as well as large nodes increasingly turning off gossip
altogether from some peers (as we do).  We should ignore timestamp filters
for our own channels: the easiest way to do this is to push them out
directly from gossipd (other messages are sent via the store).

We change channeld to wrap the local channel_announcements: previously
we just handed it to gossipd as for any other gossip message we received
from our peer.  Now gossipd knows to push it out, as it's local.

This interferes with the logic in tests/test_misc.py::test_htlc_send_timeout
which expects the node_announcement message last, so we generalize
that too.

[ Thanks to @trueptolmy for bugfix! ]
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-10-14 15:00:37 -05:00
Saibato a96b4d8363 Tor CHANGELOG updates for 0.7.3
Signed-off-by: Saibato <saibato.naga@pm.me>
2019-10-14 21:08:03 +02:00
lisa neigut a91b454749 changelog updates for 0.7.3-rc1 2019-10-11 13:05:01 -05:00
darosior 541df1591e Add a changelog line about behavior change on gossip_queries response
Forgot to add it in f88fc3714c and d78d888c2d284660f05134c572f6251785e866f2..
2019-10-11 10:06:10 -05:00
Rusty Russell bd55f6d940
common/features: only support a single feature bitset.
This is mainly an internal-only change, especially since we don't
offer any globalfeatures.

However, LND (as of next release) will offer global features, and also
expect option_static_remotekey to be a *global* feature.  So we send
our (merged) feature bitset as both global and local in init, and fold
those bitsets together when we get an init msg.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-10-11 02:52:04 +00:00
darosior fac5faacc0 Document hsm_secret encryption 2019-10-09 22:00:38 -05:00
trueptolemy bb5aa774e2 CHANGELOG: Add the entry about `destination` in `close` 2019-10-09 21:04:16 -05:00
trueptolemy d59015d4ca CHANGELOG: Add the entries about the new parameter name `amount` 2019-10-09 16:51:42 -05:00
Rusty Russell 33c658ecfb gossipd: advertize all our features in node_announcement.
This preempts the acceptance of
https://github.com/lightningnetwork/lightning-rfc/pull/666 but it's
clear that feature bits are going to be distinct, so this is safe to
do anyway.

See https://github.com/lightningnetwork/lightning-rfc/pull/680

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-10-07 05:51:05 +00:00
Rusty Russell 15612d269a Make option_static_remotekey non-EXPERIMENTAL now it's in spec.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-30 01:50:44 +00:00
darosior 61c07bca45 doc: Document the changes to the 'plugin' command 2019-09-30 00:20:16 +00:00
Rusty Russell 4e8141aa36 features: remove INITIAL_ROUTING_SYNC.
It only had an effect if the peer didn't support option_gossip_queries, but
still, we don't want a gossip blast any more.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-25 04:01:56 +00:00
Rusty Russell 27790832a5 gossipd: gossip_queries_ex is not longer experimental.
The master spec has some typos which make it not parse, so I created
a PR and generated the CSV from that:

https://github.com/lightningnetwork/lightning-rfc/pull/673

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-22 01:17:11 +00:00
Rusty Russell fe66b53fb9 jsonrpc: add more fields to listfunds.
This avoids having to correlate with listpeers for the most pertinent
information.

This API predates plugins, otherwise we'd have listutxos and listpeers
and this would simply combine them appropriately.  Still, it exists so
there's little reason not to make it more friendly.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-19 01:03:09 +00:00
trueptolemy ece0ec8bb9 CHANGELOG: Add the entry about `pay` can exclude error nodes 2019-09-16 12:22:06 +08:00
trueptolemy 36852c36e6 CHANGELOG: Add the entry about `getroute` supports excluding nodes 2019-09-16 12:22:06 +08:00
lisa neigut 5c70890efa rpc: add 'utxos' parameter to txprepare + withdraw
Allow a user to select the utxo set that will be added to a
transaction, via the `utxos` parameter. Optional.

Format for utxos should be of the form ["txid:vout","..."]
2019-09-11 23:56:27 +00:00
lisa neigut b1f05795a8 rpc: have fundchannel_start also return scriptpubkey
Easier to pass it back than dig it out of the address, since we
have it. Needed for extracting fundchannel
2019-09-11 23:56:27 +00:00
trueptolemy 4c2bc91955 CHANGLOG: Add the CHANGLOG entry of extending `fundchannel_cancel` 2019-09-11 17:04:14 -05:00
Rusty Russell afbed94a6c gossipd: work around missing pwritev().
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-11 05:58:36 +00:00
trueptolemy 8df27a7bbb CHANGELOG: Add the entry for `sendpay_success` and `sendpay_failure` 2019-09-11 00:57:39 +00:00
darosior e52af0d1ea doc: Document the new dependency 2019-09-10 02:17:27 +00:00
darosior a7cbe93fb8 closingd: retransmit 'funding_locked' if we reconnect without any update
As per BOLT02 #message-retransmission :
if `next_commitment_number` is 1 in both the `channel_reestablish` it sent and received:
    - MUST retransmit `funding_locked`
2019-09-10 02:02:51 +00:00
Rusty Russell 077ba88b88 JSON: remove listpayments.
You either want listpays (high level) or listsendpays.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-06 14:19:14 +02:00
Rusty Russell 884f4fa6d0 JSON: Remove description fields.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-06 14:19:14 +02:00