mirror of
https://github.com/lightningdevkit/rust-lightning.git
synced 2025-02-24 23:08:36 +01:00
Expose TxCreationKeys in LocalCommitmentTransaction via a method
This makes it obvious to signer implementers that the pre-derived keys are a local cache and should not be trusted in a validating signer.
This commit is contained in:
parent
d2e6f2ac18
commit
6f635c6bc3
1 changed files with 7 additions and 2 deletions
|
@ -540,8 +540,7 @@ pub struct LocalCommitmentTransaction {
|
|||
// Which order the signatures should go in when constructing the final commitment tx witness.
|
||||
// The user should be able to reconstruc this themselves, so we don't bother to expose it.
|
||||
our_sig_first: bool,
|
||||
/// The key derivation parameters for this commitment transaction
|
||||
pub local_keys: TxCreationKeys,
|
||||
pub(crate) local_keys: TxCreationKeys,
|
||||
/// The feerate paid per 1000-weight-unit in this commitment transaction. This value is
|
||||
/// controlled by the channel initiator.
|
||||
pub feerate_per_kw: u32,
|
||||
|
@ -606,6 +605,12 @@ impl LocalCommitmentTransaction {
|
|||
}
|
||||
}
|
||||
|
||||
/// The pre-calculated transaction creation public keys.
|
||||
/// An external validating signer should not trust these keys.
|
||||
pub fn trust_key_derivation(&self) -> &TxCreationKeys {
|
||||
&self.local_keys
|
||||
}
|
||||
|
||||
/// Get the txid of the local commitment transaction contained in this
|
||||
/// LocalCommitmentTransaction
|
||||
pub fn txid(&self) -> Txid {
|
||||
|
|
Loading…
Add table
Reference in a new issue