vincenzopalazzo
/
rgb-cln
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity
rgb-cln/closingd/closing_wire.csv

43 lines
1.6 KiB
Plaintext
Raw Normal View History

common: move some files out of lightningd/ Basically all files shared by different daemons. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-08-28 17:05:01 +01:00
#include <common/cryptomsg.h>
#include <common/htlc_wire.h>
common/per_per_state: generalize lightningd/peer_comm Part 1 Encapsulating the peer state was a win for lightningd; not surprisingly, it's even more of a win for the other daemons, especially as we want to add a little gossip information. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-06-03 19:11:25 +01:00
#include <common/per_peer_state.h>
lightningd/closing: subdaemon for closing negotiation. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-07-04 01:49:43 +01:00
# Begin! (passes peer fd, gossipd-client fd)
Make all internal message numbers unique. We were sending a channeld message to onchaind, which was v. confusing due to overlap. We make all the numbers distinct, which means we can also add an assert() that it's valid for that daemon, which catches such errors immediately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-09-26 22:02:48 +01:00
closing_init,2001
common/per_per_state: generalize lightningd/peer_comm Part 1 Encapsulating the peer state was a win for lightningd; not surprisingly, it's even more of a win for the other daemons, especially as we want to add a little gossip information. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-06-03 19:11:25 +01:00
closing_init,,pps,struct per_peer_state
bitcoin: create new wrapper type bitcoin_txid, log backward endianness. It's just a sha256_double, but importantly when we convert it to a string (in type_to_string, which is used in logging) we use bitcoin_txid_to_hex() so it's reversed as people expect. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-12-18 06:41:52 +00:00
closing_init,,funding_txid,struct bitcoin_txid
lightningd/closing: subdaemon for closing negotiation. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-07-04 01:49:43 +01:00
closing_init,,funding_txout,u16
daemons: use amount_msat/amount_sat in all internal wire transfers. As a side-effect of using amount_msat in gossipd/routing.c, we explicitly handle overflows and don't need to pre-prune ridiculous-fee channels. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-02-21 03:45:55 +00:00
closing_init,,funding_satoshi,struct amount_sat
closingd: use hsmfd to get signatures, don't use seed. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-07-23 03:23:03 +01:00
closing_init,,local_fundingkey,struct pubkey
lightningd/closing: subdaemon for closing negotiation. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-07-04 01:49:43 +01:00
closing_init,,remote_fundingkey,struct pubkey
closing_init,,funder,enum side
daemons: use amount_msat/amount_sat in all internal wire transfers. As a side-effect of using amount_msat in gossipd/routing.c, we explicitly handle overflows and don't need to pre-prune ridiculous-fee channels. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-02-21 03:45:55 +00:00
closing_init,,local_sat,struct amount_sat
closing_init,,remote_sat,struct amount_sat
closing_init,,our_dust_limit,struct amount_sat
closing_init,,min_fee_satoshi,struct amount_sat
closing_init,,fee_limit_satoshi,struct amount_sat
closing_init,,initial_fee_satoshi,struct amount_sat
lightningd/closing: subdaemon for closing negotiation. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-07-04 01:49:43 +01:00
closing_init,,local_scriptpubkey_len,u16
closing_init,,local_scriptpubkey,local_scriptpubkey_len*u8
closing_init,,remote_scriptpubkey_len,u16
closing_init,,remote_scriptpubkey,remote_scriptpubkey_len*u8
lightningd: handle reconnect during shutdown and closing. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-07-05 06:33:28 +01:00
closing_init,,reconnected,bool
closing_init,,next_index_local,u64
closing_init,,next_index_remote,u64
closing_init,,revocations_received,u64
lightningd: re-allow closing negotiation when CLOSINGD_COMPLETE d822ba1ee accidentally removed this case, which is important: if the other side didn't get our final matching closing_signed, it will reconnect and try again. We consider the channel no longer "active" and thus ignore it, and get upset when it send the `channel_reestablish` message. We could just consider CLOSINGD_COMPLETE to be active, but then we'd have to wait for the closing transaction to be mined before we'd allow another connection. We can't special case it when the peer reconnects, because there could be (in theory) multiple channels for that peer in CLOSINGD_COMPLETE, and we don't know which one to reestablish. So, we need to catch this when they send the reestablish, and hand that msg to closingd to do negotiation again. We already have code to note that we're in CLOSINGD_COMPLETE and thus ignore any result it gives us. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-04-23 11:08:02 +01:00
closing_init,,channel_reestablish_len,u16
closing_init,,channel_reestablish,channel_reestablish_len*u8
closingd: retransmit `shutdown` on reconnect. The spec says so, and it's right: with the right pattern of packet loss (thanks Travis!) the other end can still be in channeld, waiting for our `shutdown` message. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-10-29 03:37:11 +00:00
closing_init,,final_scriptpubkey_len,u16
closing_init,,final_scriptpubkey,final_scriptpubkey_len*u8
closingd: send option_dataloss_protect fields when reestablishing. Travis caught an error where this happened: when closingd reconnects it was sending the reestablish message without the option_dataloss_protect fields. That causes the peer to fail the channel! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-04-08 02:35:13 +01:00
closing_init,,last_remote_secret,struct secret
lightningd/closing: subdaemon for closing negotiation. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-07-04 01:49:43 +01:00
# We received an offer, save signature.
Make all internal message numbers unique. We were sending a channeld message to onchaind, which was v. confusing due to overlap. We make all the numbers distinct, which means we can also add an assert() that it's valid for that daemon, which catches such errors immediately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-09-26 22:02:48 +01:00
closing_received_signature,2002
signature: wrap almost all signatures in struct bitcoin_signature. This is prep work for when we sign htlc txs with SIGHASH_SINGLE|SIGHASH_ANYONECANPAY. We still deal with raw signatures for the htlc txs at the moment, since we send them like that across the wire, and changing that was simply too painful (for the moment?). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-12-02 23:15:06 +00:00
closing_received_signature,,signature,struct bitcoin_signature
closingd: send the tx to master as we negotiate. We can derive fees from this, and also broadcast at any time without having to reconstruct it. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-08-18 05:43:52 +01:00
closing_received_signature,,tx,struct bitcoin_tx
lightningd/closing: subdaemon for closing negotiation. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-07-04 01:49:43 +01:00
Make all internal message numbers unique. We were sending a channeld message to onchaind, which was v. confusing due to overlap. We make all the numbers distinct, which means we can also add an assert() that it's valid for that daemon, which catches such errors immediately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-09-26 22:02:48 +01:00
closing_received_signature_reply,2102
closing: add message to billboard when closing txn is broadcast make it a bit easier to track mutual channel closures by adding broadcast txid to the listpeers billboard. since lightningd manages the 'identity' of the closing tx we need to send it back to closingd so it can update the billboard appropriately.
2019-04-10 22:58:01 +01:00
closing_received_signature_reply,,closing_txid,struct bitcoin_txid
lightningd/closing: subdaemon for closing negotiation. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-07-04 01:49:43 +01:00
# Negotiations complete, we're exiting.
Make all internal message numbers unique. We were sending a channeld message to onchaind, which was v. confusing due to overlap. We make all the numbers distinct, which means we can also add an assert() that it's valid for that daemon, which catches such errors immediately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-09-26 22:02:48 +01:00
closing_complete,2004