I mostly agree, but I get stuck on this sometimes:

publishing a DVM event, listening for a reply, paying the invoice, and then publishing the result is slower than a traditional API.

It's a tradeoff in that an API requires setup, login, credit card info in order to have "faster" calls.

Reply to this note

Please Login to reply.

Discussion

This process will get better, for example some DVMs will be paid with a subscription and you always get a result without having to “pick one” first. There will be other, better payment schemes as well.

For speed, I’m curious how much faster we can make it over relays, with some relays designed specifically for DVM use. I don’t believe we have a DVM specific relay…. Yet 😉