RemoteSigner Implementation #10
Conversation
ksedgwic
force-pushed
the
remote-signer2
branch
from
4e71964 to
d9902c2
Compare
ksedgwic
force-pushed
the
remote-signer2
branch
5 times, most recently
from
34c6cd7 to
878ab0a
Compare
ksedgwic
force-pushed
the
remote-signer2
branch
3 times, most recently
from
4e5856b to
57d3258
Compare
ksedgwic
force-pushed
the
context-signer
branch
from
ba985cb to
0270c45
Compare
ksedgwic
force-pushed
the
remote-signer2
branch
4 times, most recently
from
7e316ae to
4c92f7d
Compare
ksedgwic
force-pushed
the
remote-signer2
branch
3 times, most recently
from
3127de4 to
33381c0
Compare
ksedgwic
force-pushed
the
remote-signer2
branch
from
33381c0 to
e5bb2e2
Compare
ksedgwic
force-pushed
the
remote-signer2
branch
2 times, most recently
from
4ce7e62 to
8120dcc
Compare
… remotesigner API now.
…ript" to "redeemScript".
ksedgwic
force-pushed
the
remote-signer2
branch
from
a17ad86 to
1da0fd1
Compare
|
What happened to lnd support? It seems that the current remote signing API in lnd is quite different from what rust-lightning-signer implements. |
|
We were having trouble adapting the internal lnd signing abstractions to our API, which are needed to support fully validating signing. We'd love to support lnd, but need advice/assistance on how to adapt lnd's internal signing abstractions. We're finding c-lightning and LDK have more compatible abstractions. |
|
There is some background here: lightningnetwork#6006 (comment) LND's interface is on a lower level which probably has its pros and cons. I am relatively new to this area in lightning implementations, but I can imagine that going from high to low level is possible but the other way around not so much? |
|
Yes, that is a good summary of many individual issues ... |
No description provided.