lightning

107 Tags

38 MiB

Tree: 9eeb76e185

Author	SHA1	Message	Date
Rusty Russell	7419fde9a0	Update to new spec: differentiate channel_id and short_channel_id. The spec 4af8e1841151f0c6e8151979d6c89d11839b2f65 uses a 32-byte 'channel-id' field, not to be confused with the 8-byte short ID used by gossip. Rename appropriately, and update to the new handshake protocol. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	6cf8a19881	lightningd/opening: receive details for remote config acceptance, not min/max. The requirements for accepting the remote config are more complex than a simple min/max value, as various parameters are related. It turns out that with a few assumptions, we can boil this down to: 1. The valid feerate range. 2. The minimum effective HTLC throughput we want 3. The a maximum delay we'll accept for us to redeem. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	a8b9177e9e	lightningd/opening: seed is a privkey not an sha256. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	065f11b42a	lightningd/opening: opening daemon. This conducts the conversation up until we have the txid to wait for (or broadcast). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago