Timeline for HTLCs and commitment transactions
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 19, 2019 at 17:09 | history | edited | Ugam Kamat | CC BY-SA 4.0 |
added 264 characters in body
|
| Jun 19, 2019 at 17:01 | vote | accept | spacemonkey | ||
| Jun 19, 2019 at 16:56 | comment | added | Ugam Kamat | @spacemonkey not necessarily; the keys can be calculated from a compact representation. For key generation, you just generate a seed, and then use an index to bit flip and hash the result. For storage, only one secret for each unique prefix need be saved; in effect, the number of trailing 0s is counted, and this determines where in the storage array the secret is stored. You can read more key storage in BOLT #3 here: github.com/lightningnetwork/lightning-rfc/blob/master/… | |
| Jun 19, 2019 at 16:13 | comment | added | spacemonkey |
But if I understand correctly the revocationprivkey would also have to be stored for every transaction, since per_commitment_secret would have to be regenerated for every new transaction?
|
|
| Jun 19, 2019 at 15:12 | history | answered | Ugam Kamat | CC BY-SA 4.0 |