mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-01-09 23:27:17 +01:00
4a161b710d
When adding their HTLCs, it needs all the information. When failing, it needs the id as key and the failure reason. When fulfilling, it needs the id and payment preimage. It also needs to know when we have received an revoke_and_ack or a commitment_signed, to place in the database. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
4.6 KiB
4.6 KiB
1 | # Shouldn't happen |
---|---|
2 | channel_bad_command,0x8000 |
3 | # Also shouldn't happen |
4 | channel_hsm_failed,0x8001 |
5 | channel_crypto_failed,0x8002 |
6 | channel_internal_error,0x8003 |
7 | channel_gossip_bad_message,0x8004 |
8 | # These are due to peer. |
9 | channel_peer_write_failed,0x8010 |
10 | channel_peer_read_failed,0x8011 |
11 | channel_peer_bad_message,0x8012 |
12 | # Received and sent funding_locked |
13 | channel_normal_operation,1001 |
14 | #include <lightningd/cryptomsg.h> |
15 | #include <lightningd/channel_config.h> |
16 | # Begin! You're still waiting for the tx to be buried though (passes |
17 | # gossipd-client fd) |
18 | channel_init,1 |
19 | channel_init,,funding_txid,struct sha256_double |
20 | channel_init,,funding_txout,2 |
21 | channel_init,,our_config,struct channel_config |
22 | channel_init,,their_config,struct channel_config |
23 | channel_init,,first_commit_sig,secp256k1_ecdsa_signature |
24 | channel_init,,crypto_state,struct crypto_state |
25 | channel_init,,remote_fundingkey,33 |
26 | channel_init,,revocation_basepoint,33 |
27 | channel_init,,payment_basepoint,33 |
28 | channel_init,,delayed_payment_basepoint,33 |
29 | channel_init,,their_per_commit_point,33 |
30 | channel_init,,am_funder,bool |
31 | channel_init,,fee_base,4 |
32 | channel_init,,fee_proportional,4 |
33 | channel_init,,funding_satoshi,8 |
34 | channel_init,,push_msat,8 |
35 | channel_init,,seed,struct privkey |
36 | channel_init,,local_node_id,struct pubkey |
37 | channel_init,,remote_node_id,struct pubkey |
38 | channel_init,,commit_msec,4 |
39 | channel_init,,cltv_delta,u16 |
40 | channel_init,,init_peer_pkt_len,u16 |
41 | channel_init,,init_peer_pkt,init_peer_pkt_len*u8 |
42 | # Tx is deep enough, go! |
43 | channel_funding_locked,2 |
44 | channel_funding_locked,,short_channel_id,struct short_channel_id |
45 | # Tell the channel that we may announce the channel's existence |
46 | channel_funding_announce_depth,3 |
47 | # Tell channel to offer this htlc |
48 | channel_offer_htlc,4 |
49 | channel_offer_htlc,,amount_msat,8 |
50 | channel_offer_htlc,,cltv_expiry,4 |
51 | channel_offer_htlc,,payment_hash,32 |
52 | channel_offer_htlc,,onion_routing_packet,1366*u8 |
53 | # Reply; synchronous since IDs have to increment. |
54 | channel_offer_htlc_reply,104 |
55 | channel_offer_htlc_reply,,id,8 |
56 | # Zero failure code means success. |
57 | channel_offer_htlc_reply,,failure_code,2 |
58 | channel_offer_htlc_reply,,failurestrlen,2 |
59 | channel_offer_htlc_reply,,failurestr,failurestrlen*u8 |
60 | # Main daemon found out the preimage for an htlc |
61 | #include <bitcoin/preimage.h> |
62 | channel_fulfill_htlc,5 |
63 | channel_fulfill_htlc,,id,8 |
64 | channel_fulfill_htlc,,payment_preimage,struct preimage |
65 | # Main daemon says HTLC failed |
66 | channel_fail_htlc,6 |
67 | channel_fail_htlc,,id,8 |
68 | channel_fail_htlc,,len,2 |
69 | channel_fail_htlc,,error_pkt,len*u8 |
70 | # Ping/pong test. |
71 | channel_ping,11 |
72 | channel_ping,,num_pong_bytes,u16 |
73 | channel_ping,,len,u16 |
74 | channel_ping_reply,111 |
75 | channel_ping_reply,,totlen,u16 |
76 | # Channeld tells the master that the channel has been announced |
77 | channel_announced,12 |
78 | # When we send a commitment_signed message, tell master. |
79 | channel_sending_commitsig,20 |
80 | channel_sending_commitsig,,commitnum,u64 |
81 | # SENT_ADD_COMMIT, SENT_REMOVE_ACK_COMMIT, SENT_ADD_ACK_COMMIT, SENT_REMOVE_COMMIT |
82 | channel_sending_commitsig,,num_changed,u16 |
83 | channel_sending_commitsig,,changed,num_changed*struct changed_htlc |
84 | # Wait for reply, to make sure it's on disk before we send commit. |
85 | channel_sending_commitsig_reply,120 |
86 | # When we have a commitment_signed message, tell master to remember. |
87 | channel_got_commitsig,21 |
88 | channel_got_commitsig,,commitnum,u64 |
89 | channel_got_commitsig,,signature,secp256k1_ecdsa_signature |
90 | channel_got_commitsig,,num_htlcs,u16 |
91 | channel_got_commitsig,,htlc_signature,num_htlcs*secp256k1_ecdsa_signature |
92 | # RCVD_ADD_COMMIT: we're now committed to their new offered HTLCs. |
93 | channel_got_commitsig,,num_added,u16 |
94 | channel_got_commitsig,,added,num_added*struct added_htlc |
95 | # RCVD_REMOVE_COMMIT: we're now no longer committed to these HTLCs. |
96 | channel_got_commitsig,,num_fulfilled,u16 |
97 | channel_got_commitsig,,fulfilled,num_fulfilled*struct fulfilled_htlc |
98 | channel_got_commitsig,,num_failed,u16 |
99 | channel_got_commitsig,,failed,num_failed*struct failed_htlc |
100 | # RCVD_ADD_ACK_COMMIT, RCVD_REMOVE_ACK_COMMIT |
101 | channel_got_commitsig,,num_changed,u16 |
102 | channel_got_commitsig,,changed,num_changed*struct changed_htlc |
103 | # Wait for reply, to make sure it's on disk before we send revocation. |
104 | channel_got_commitsig_reply,121 |
105 | #include <lightningd/htlc_wire.h> |
106 | channel_got_revoke,22 |
107 | channel_got_revoke,,revokenum,u64 |
108 | channel_got_revoke,,per_commitment_secret,struct sha256 |
109 | # RCVD_ADD_ACK_REVOCATION |
110 | channel_got_revoke,,num_added,u16 |
111 | channel_got_revoke,,added_ids,num_added*u64 |
112 | channel_got_revoke,,shared_secret,num_added*struct secret |
113 | # RCVD_REMOVE_ACK_REVOCATION, RCVD_ADD_REVOCATION, RCVD_REMOVE_REVOCATION |
114 | channel_got_revoke,,num_changed,u16 |
115 | channel_got_revoke,,changed,num_changed*struct changed_htlc |
116 | # Wait for reply, to make sure it's on disk before we continue |
117 | # (eg. if we sent another commitment_signed, that would implicitly ack). |
118 | channel_got_revoke_reply,122 |