Conversation
377311f to
130441e
Compare
130441e to
030d400
Compare
1b78f04 to
c47df1e
Compare
c47df1e to
4e69aeb
Compare
|
|
||
| impl InMemorySigner { | ||
| pub fn generate_from_seed(params: &[u8]) -> Self { | ||
| impl InMemorySignerExt for InMemorySigner { |
There was a problem hiding this comment.
can we keep InMemorySigner in fiber-lib crate?
There was a problem hiding this comment.
it's stored in db by a type chain:
Type `InMemorySigner` is STORE-RELATED (reachable from KeyValue).
Defined in: /Users/yukang/code/fiber/crates/fiber-types/src/channel.rs
Dependency chain(s) from KeyValue:
KeyValue::ChannelActorState -> ChannelActorState -> ChannelActorData -> InMemorySigner
crates/fiber-types/Cargo.toml
Outdated
| molecule = { version = "0.8.0", default-features = false } | ||
|
|
||
| ckb-hash = "1" | ||
| bitcoin = { version = "0.32", features = ["serde"] } |
There was a problem hiding this comment.
we only use sha256 related fn with this crate , a minimal sha256 crate may be better.
There was a problem hiding this comment.
we only use bitcoin::hashes::sha256::Hash for type conversion (in primitives.rs and invoice.rs). This conversion is required for interoperability with lightning-invoice, which itself depends on Bitcoin. So even if we remove the direct dependency, it will still be brought in transitively via lightning-invoice?
There was a problem hiding this comment.
yeah, we can use minimal bitcoin::hashes::sha256.
There was a problem hiding this comment.
whether we should add a feature gate such as cch .
446fe66 to
5729184
Compare
f2e0cff to
1a6ef43
Compare
8a7f645 to
2cad1f3
Compare
98bab7e to
92fbd54
Compare
Separate types from fiber-lib.
ref to: fiber-types Crate Design