lightning

1534 Commits

55 Branches

107 Tags

38 MiB

Tree: f61da7eb64

Commit Graph

Author	SHA1	Message	Date
Rusty Russell	8522a5ea64	struct bitcoin_tx: remove explicit lengths, use tal_len()/tal_count() They're always tal objects, so we can simply ask tal for the length, simplifying the API. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	8 years ago
Rusty Russell	d8af789bbb	channel: remove enum channel_side, rename htlc_side to side. We had enum channel_side (OURS, THEIRS) for which end of a channel we had, and htlc_side (LOCAL, REMOTE) for who proposed the HTLC. Combine these both into simply "enum side". Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	9 years ago
Rusty Russell	ec3344ce6e	daemon/output_to_htlc: routines to map outputs for HTLCs for a given commit_num. And use this to resolve old transactions by comparing outputs with HTLCs. Rather than remembering the output ordering for every one of their previous commitment transactions, we just remember the commitment number for each commitment txid, and when we see it, derive all the HTLC scriptpubkeys and the to-us and to-them scriptpubkeys, and figure out which is which. This avoids us having to save information on disk, except for the txid->commitment-number mapping (and the shachain). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>	9 years ago

Author

SHA1

Message

Date

Rusty Russell

8522a5ea64

struct bitcoin_tx: remove explicit lengths, use tal_len()/tal_count()

They're always tal objects, so we can simply ask tal for the length,
simplifying the API.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

8 years ago

Rusty Russell

d8af789bbb

channel: remove enum channel_side, rename htlc_side to side.

We had enum channel_side (OURS, THEIRS) for which end of a channel we
had, and htlc_side (LOCAL, REMOTE) for who proposed the HTLC.

Combine these both into simply "enum side".

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

9 years ago

Rusty Russell

ec3344ce6e

daemon/output_to_htlc: routines to map outputs for HTLCs for a given commit_num.

And use this to resolve old transactions by comparing outputs with
HTLCs.

Rather than remembering the output ordering for every one of their
previous commitment transactions, we just remember the commitment
number for each commitment txid, and when we see it, derive all the
HTLC scriptpubkeys and the to-us and to-them scriptpubkeys, and figure
out which is which.

This avoids us having to save information on disk, except for the
txid->commitment-number mapping (and the shachain).

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

9 years ago

3 Commits (f61da7eb64d9b8bfda4c9882c4f83bf173d1c29f)