pull down to refresh
0 sats \ 6 replies \ @justin_shocknet 27 Feb freebie \ parent \ on: Have you connected an external wallet on SN? meta
What you've done though is exactly the opposite of you're stated objective.... you've now turned SN into a programmable wallet. The aligned pattern would be instead yielding to rules controlled by an independent wallet like ShockWallet.
Custodian labels is theater in this context tbf, it's a trusted budget and invoice transport no matter what you want to project it as- to regulators or otherwise. Getting trapped into narrative corners like that is no way to create better solutions.
The only standard way to withdraw on the fly afaik is a withdrawal link, which expires and therefore breaks after it's been connected. That's already standard you support that doesn't require all the overhead you just implemented to remain a trusted and centralized service
What you've done though is exactly the opposite of you're stated objective....
We're not done yet, this was just the first step of many to come
The only standard way to withdraw on the fly afaik is a withdrawal link, which expires and therefore breaks after it's been connected.
Ah sorry, I didn't mean withdrawal links. I meant you can create an invoice for a service and then let the SN node pay that invoice. It's currently not trivial how to do that without the frontend but it's possible. That's basically a withdrawal where expiration of withdrawal links don't matter and should align with what you're building with your wallet. I don't understand why you would need persistent withdrawal links.