lightning

107 Tags

38 MiB

Tree: 1ecd687eec

Author	SHA1	Message	Date
Rusty Russell	4bfaaef408	keyset: abstraction over what keys we need for a specific commitment. onchaind will need to do similar logic to channeld, so this allows them to share much more code. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	b99c5620ef	struct secret: use everywhere. We alternated between using a sha256 and using a privkey, but there are numerous places where we have a random 32 bytes which are neither. This fixes many of them (plus, struct privkey is now defined in terms of struct secret). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	ccff3ac437	lightningd/funding_tx: fill in scriptsigs for p2sh UTXOs. This is a bit tricky: for our signing code, we don't want scriptsigs, but to calculate the txid, we need them. For most transactions in lightning, they're pure segwit so it doesn't matter, but funding transactions can have P2SH-wrapped P2WPKH inputs. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	dc3b27e1d3	key_derive: key derivation from basepoints as specified in BOLT 3 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago