pull down to refresh

Hey @nps! Congrats on the launch, I've been playing a bit with MDK in Vercel today and it's going great so far.
The only thing a bit confusing at first, at least to me, was the webhook. I wanted to test things locally first, but of course that didn't work because the node was not reachable on a public endpoint. Do you have any plans to simplify this first step, for example with a proxy between localhost and a temporary domain hosted by MDK?
Also am I correct in assuming that it's fine to run two instances at the same time with the same seed (one local, one deployment), since on payment reception the MDK infrastructure will just reach out to the deployed instance? But then how does the local instance knows the payment succeeded? I tried and it does notice the payment arrived.
Thanks!
this territory is moderated
100 sats \ 1 reply \ @nps OP 4h
Hey thanks for giving it a try!
Local testing is on our list for near term priorities, for a v1 we're thinking we'll add a button to mock the webhook so you can be sure everything else is set up right before you deploy.
We're working through multiple websites / locations as well. Your example with local / deployed should be fine. The state for the node is stored encrypted in remotely in VSS linked to your seed, so where the node spins up does not matter so much.
reply
0 sats \ 0 replies \ @fanis 2h
Thanks for your answer! VSS makes a lot of sense here, truly great stuff 🔥
reply