lightning

107 Tags

38 MiB

Tree: a72dd8d9de

Author	SHA1	Message	Date
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	be7c7b9732	lightningd/handshake: rename WIRE_BAD_COMMAND to WIRE_HANDSHAKE_BAD_COMMAND So it doesn't clash with opening daemon, for example. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	b1403a764f	lightningd/opening: use peer_failed to send PKT_ERR on problems. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	5475666b7e	lightningd: simple wallet support. This allows us to add funds via the P2SH-wrapped Segwit Transactions. 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