You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We increasingly get user requests interested to use LDK Node, but based on a custom wallet implementation rather than on the baked-in BDK.
We should therefore explore whether it's feasible to modularize Wallet and offer the BDK wallet as a default implementation.
While a Wallet trait may be tempting, it's a bit unclear how/if this could be exposed in bindings. Possibly UniFFI callback interfaces could be used, but it might put several restrictions on our design, e.g., unclear whether we can inherit from upstream traits such as WalletSource, etc.
The text was updated successfully, but these errors were encountered:
We increasingly get user requests interested to use LDK Node, but based on a custom wallet implementation rather than on the baked-in BDK.
We should therefore explore whether it's feasible to modularize
Wallet
and offer the BDK wallet as a default implementation.While a
Wallet
trait may be tempting, it's a bit unclear how/if this could be exposed in bindings. Possibly UniFFI callback interfaces could be used, but it might put several restrictions on our design, e.g., unclear whether we can inherit from upstream traits such asWalletSource
, etc.The text was updated successfully, but these errors were encountered: