Really interesting article and approach Dustin! Congratulations, I really believe there is something quite powerful in what you are describing and integrating DVMs as a source for function calls. But just one question that went through my mind while reading you. Have you thought of integrating this DVM calling by just using the MCP architecture/approach? The idea would be to create a MCP DVM server that makes it easy to discover and call dvms, being able to discover and list them as tools, and a MCP client used by the llms to interop with the server. What do you think of this? I'm just throwing my ideas out, I haven't thought them through
Discussion
I’d need to look into this a bit more to provide more detail. My quick understanding is that there is some overlap between what these solve. MCP seems to standardize calls with JSON, we get the same effect from DVMs because it’s the Nostr protocol.
MCP is also solving more problems than what I was proposing here, like managing the context window.
I’m not sure how easy MCP enables you to use tools that are not already running as part of your MCP setup. I suspect the automatic use of brand new DVMs is where it would differ.
The scope of MCP is bigger than what I’m talking about for most of the article (except maybe MCP could solve a lot of the Manager DVM part).
I assume MCP doesn’t do payments? DVMs are already less friction than using paid APIs because of this.