Contact the mint via nostr:nprofile1qqsxkduqau5h9eeaxu9cfgl9rea2nt35haqjjwxul0vuta3myg2pdjqpzemhxue69uhhyetvv9ujumn0wd68ytnwv46z7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz740vluv no need to reinvent the wheel
Discussion
It’s probably worth expanding…
The thought here is a that mints are basically just structured apis for the wallet to talk to.
They rely on dns because APIs generally do and that’s how we talk to remote things. (Pre relays)
Context vm gives you out of the box self describing api like behaviours via mcp protocol that are pubkey addressable, don’t need any dns and can be reached behind firewalls. You can run it on a pi in your cupboard and you dont have to touch your router.
Given its mcp it’s increasingly accessible by thousands of ai tools and clients.
Or you can write client and talk to it in about 90 seconds with ctxcn and you get all this for free because piggybacks on mcp and just uses nostr for the transport layer.
Plus your mint traffic will be indistinguishable from any other context vm call on the network and your traffic can be via ephemeral keys.
nostr:nprofile1qqsxkduqau5h9eeaxu9cfgl9rea2nt35haqjjwxul0vuta3myg2pdjqpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcppemhxue69uhkummn9ekx7mp0esad58 really is other stuff at its finest.