pull down to refresh
0 sats \ 1 reply \ @nps OP 3h \ parent \ on: I'm Nick Slaney CEO and Co-Founder of moneydevkit, AMA AMA
See here about serverless. It is a very common industry term that does not mean there is no server.
mdk wraps ldk to make it able to run on a serverless platform. Underneath, your node is spinning up and down as needed and expected by this model. When you create a checkout your node creates an invoice. The keys are to your node.
None of this is exposed to the user, as we're optimizing for people who could care less about the technical detail and want payments. But it is important to me that the bitcoin community understands there's no funny business under the hood. You can go look at the code for our libraries if you want.
I'm well aware of the Lambda psyop, really its ephemeral servers with some form persistent storage/db and a reverse proxy to a container control plane. Fancy talk for docker on the fly basically.
When you create a checkout your node creates an invoice
How are customers getting the invoice from the users node? CLINK could disintermediate this, all it would add is a nostr secret to the users key ring.
people who could care less about the technical detail and want payments
Sure but those users would use a custodial processor and you wouldn't need to tout it as have it be this innovative thing to make it "self-custody".
If your users aren't supposed to care, then why the extra steps?
It's not unreasonable to ask if you call something self-custody how did you solve it? I can't lab every library that makes fantastic claims, so looking for some signal first. If I was convinced, mdk might be a useful bootstrapping back-end in my stuff... but you seem resistant to any level of scrutiny.
reply