From: Devrandom <c1.devrandom@niftybox.net>
Date: Fri, 9 Apr 2021 09:18:45 +0000 (+0200)
Subject: Move Writeable from BaseSign to Sign
X-Git-Tag: v0.0.14~33^2~1
X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=commitdiff_plain;h=14e094adc12017cf8b5ad54bdaa1e35141928caf;p=rust-lightning

Move Writeable from BaseSign to Sign
---

diff --git a/lightning/src/chain/keysinterface.rs b/lightning/src/chain/keysinterface.rs
index 31b309652..a1fef4dea 100644
--- a/lightning/src/chain/keysinterface.rs
+++ b/lightning/src/chain/keysinterface.rs
@@ -226,7 +226,7 @@ impl Readable for SpendableOutputDescriptor {
 /// of LN security model, orthogonal of key management issues.
 // TODO: We should remove Clone by instead requesting a new Sign copy when we create
 // ChannelMonitors instead of expecting to clone the one out of the Channel into the monitors.
-pub trait BaseSign : Send + Writeable {
+pub trait BaseSign : Send {
 	/// Gets the per-commitment point for a specific commitment number
 	///
 	/// Note that the commitment number starts at (1 << 48) - 1 and counts backwards.
@@ -349,7 +349,7 @@ pub trait BaseSign : Send + Writeable {
 /// Although we require signers to be cloneable, it may be useful for developers to be able to use
 /// signers in an un-sized way, for example as `dyn BaseSign`. Therefore we separate the Clone trait,
 /// which implies Sized, into this derived trait.
-pub trait Sign: BaseSign + Clone {
+pub trait Sign: BaseSign + Writeable + Clone {
 }
 
 /// A trait to describe an object which can get user secrets and key material.