Repository navigation
An option to change the LSP token after init #38
Description
Activity
Are you making the token to each individual based off some metadata? Or what is the use case here?
Specifically want to build a token with Apple DeviceCheck before giving out liquidity. That requires talking to a server for validation. In theory it could happen as the LSP token but it's a good bit simpler to talk to a server that generates smaller tokens.
Reacted by benthecarmanHmm, actually maybe it doesn't matter, I realize I was really hoping to use DeviceCheck for VSS, which we'll need at init one way or another. Maybe there's a world where we use VSS and allow reads/small writes but then require some async DeviceCheck proof after we're up and running but there's no real Orange integration required there, just vss-server. So at least for us this is probably low priority, but it would be nice.
We just pass the token to ldk node so this would it's responsibility
Reacted by Matt Corallo (Macbook)We just pass the token to ldk node so this would it's responsibility
There's a PR on ldk-node #792 that adds support for configuring multiple LSPs at both build time and runtime, which should cover this once it lands.
Some
WalletConfigoptions don't really need to be set up front and it would be nice to be able to change them after init. In my case I want to build the LSP token async and pass in after initialization (though before pulling the first invoice).