Just pushed a new payment processor for our SDK based on ZAPS!⚡️ It only requires an LN address to be used, it couldn't be easier⚡⚡️ With this new payment processor, our SDK now supports three payment processors based on Lightning BOLT11: NWC, LNbits, and now ZAPS⚡ To use it, simply update to the latest contextvm SDK. The only consideration regarding this payment method is that ZAPS can be faked by the provider of your LN address. If you trust the provider of the configured Lightning address, there is no problem, it could even be your own node. However, if you don’t trust the provider, the ZAP receipt alone is not sufficient to prove settlement. This is not a new issue; it has been discussed and is already covered in an appendix in nip-57 Hope you enjoy!⚡️⚡️⚡️

This is why CVM. In an agent-mediated world, the shipped feature set matters less than what an agent can discover and compose at runtime. Your real product becomes your callable surface area: reliability, clear schemas, predictable behavior, and the ability to snap into workflows you didn’t design. That shift makes distribution the new battleground. If discovery collapses into a handful of registries and default tool lists, the ecosystem recentralizes fast, no matter how open the API spec looks. You can already see the gravity well: MCP’s mainstream path tends to reintroduce old control points, registries anchored to domains, OAuth-based access, and platform-shaped “approved” directories. They’re convenient, but they harden into gatekeeping, and single points of failure. ContextVM is built to route around that. It runs MCP over Nostr so services are addressed by public keys, routed over relays, and announced publicly without permission. Discovery becomes a network primitive instead of a platform feature. Relays act as decentralized repositories, and curation becomes competitive and plural rather than owned. We’ve just added payments in a way that composes cleanly with autonomous, per-call usage. If agents can swap tools mid-workflow, pricing has to be as modular as the capabilities themselves, without dragging builders back into accounts, gatekeepers, and permissioned land. ContextVM’s wager is simple: if agents are going to assemble the future on the fly, the underlying rails for identity, discovery, and payment must be open, permissionless, and censorship-resistant by default. View quoted note →

It takes you ~20 LOC to enable payments in your server. NWC + CVM = 🤯 The code:

GitHub

dummy-paid-server/index.ts at main · ContextVM/dummy-paid-server

Contribute to ContextVM/dummy-paid-server development by creating an account on GitHub.

View quoted note →

Pro tip: get the CVM skills for payments `npx cvmi add --skill payments -y` Ask your agent to build something profitable, use an NWC connect string, and start monetizing. Quite easy. Additionally, there is an LNBits backend available in the SDK, and the skills come with documentation on how to build your custom payment rails if you need. Let's build! 🚀 View quoted note →

Payments Have Arrived! 🚀 ContextVM now supports payments with CEP-8! Your servers can finally become digital lemonade stands, paid, permissionless services that anyone can run and consume without asking for permission. This release packs everything you need. The new version of the SDK have everything you need, even ships with Lightning BOLT11 integrations (NWC and LNbits), the ContextVM site now supports payment discovery, cvmi and skills has been updated, and the docs cover the full flow. Want to see it in action? The dummy demo server (https://github.com/ContextVM/dummy-paid-server) shows you exactly how to price and monetize a capability. Looking forward to hear your thoughts and see what you are building! Read the docs:

ContextVM Documentation

CEP-8 Capability Pricing and Payment Flow

Pricing mechanism and payment processing for ContextVM capabilities

Build a stand. Price a capability. Let value flow. If you have any question just ask View article →

Payments are coming imminently 🚀

Just shipped some clarity improvements to CEP-8 🎯 We are pretty close to getting this done; we just shipped some clarification to the payments spec so some concepts are less ambiguous. The spec now has well-defined PMI (payment method identifier) boundaries, clarifiying what goes in `pay_req`. We've added a recommended PMI registry with precise payload semantics, plus naming conventions to keep things unambiguous as the ecosystem grows. Also new: optional direct payments for bearer assets. When both parties support it, you can skip the roundtrip, just attach `["direct_payment", "<pmi>", "<payload>"]` to your request and you're done. Good for cashu 🥜 The ongoing implementation remains unchanged, this is all documentation and specification hardening. Current spec:

GitHub

contextvm-docs/src/content/docs/spec/ceps/cep-8.md at ed71abec7bd93ba1082e67dfc92f0b0bcf618a72 · ContextVM/contextvm-docs

ContextVM documentation and specification. Alternative link: https://contextvm.github.io/contextvm-docs/ - ContextVM/contextvm-docs

SDK progress: github.com/ContextVM/sdk/pull/24 Feedback welcome! View quoted note →

📡 New relay live! wss://relay2.contextvm.org 📡 We were running a public relay at wss://relay.contextvm.org and have now added a new relay to increase redundancy. This new relay is hosted by a different provider in a different location, ensuring that if one provider experiences an outage, the other will remain available. Additionally, there is a third relay operated by @Pete Winn at wss://cvm.otherstuff.ai Note: You can use any public relay for CVM stufff, but these three are more optimized as they reject other events not related with CVM and do not store events, they are ephemeral. We have also added a new section to our awesome repo to make it easy to find these relays:

GitHub

GitHub - ContextVM/awesome: Awesome things based on ContextVM

Awesome things based on ContextVM. Contribute to ContextVM/awesome development by creating an account on GitHub.

The PR is not even merged yet, and we already have @klabo contributing an LNbits payment processor and handler 🚀 Thanks so much for the contribution 💛 The PR will ship two payment processors and handlers: NWC for making it work with any wallet supporting NWC, super easy to configure and use. And LNbits, which will allow the use of an LNbits backend as a payment processor and handler. More built-in payment methods can be added in future iterations. Anyone will be able to create their custom ones as well View quoted note →

Very excited for this 🔥 CEP-8 payments are coming to ContextVM, with a reference implementation in our TypeScript SDK. It is shaping up nicely, with a clean design and implementation. The cool part is that nothing changes for operators; the transports will still work in the same way they do today, with no breaking changes. Payments are enabled through middlewares, so the inclusion of payments will not affect current consumers of the SDK in any way. There will be no performance degradation, no API-breaking changes, and maximum flexibility. Soon, we will release the new version including the new features, along with some guides on how to start monetizing your services. Stay tuned. In the meantime, you can read the specification at

GitHub

feat: cep-8 payments by gzuuus · Pull Request #9 · ContextVM/contextvm-docs

Resolves: #8

and follow the progress of the implementation in the SDK at

GitHub

feat: [CEP-8] Payments by ContextVM-org · Pull Request #24 · ContextVM/sdk

ContextVM/contextvm-docs#8

. Feel free to give us some feedback or ask any questions!

CVMI 0.1.9 is out. It includes two minor but necessary features: normalizing quoted command strings so you can pass commands to serve any MCP server inside quotes (e.g., `cvmi serve "npx -y …"`), and adding environment‑variable support to the spawned MCP server using flags such as `cvmi serve -e LOG_LEVEL=debug …`. They aren’t the flashiest features, but they are essential for real world scenarios. Thanks, @hzrd149, for pointing them out 🚀

CEP-8 payments is becoming a reality. Quite soon, anyone, humans or machines, will be able to monetize their services and computation over Nostr. Permissionless, unstoppable, robust, decentralized services, this is how we win. Little by little, all the pieces are coming together 🚀 If you are interested in the discussion, dig in:

GitHub

feat: cep-8 payments by gzuuus · Pull Request #9 · ContextVM/contextvm-docs

Resolves: #8

If you are interested in the development of it:

GitHub

feat: [CEP-8] Payments by ContextVM-org · Pull Request #24 · ContextVM/sdk

ContextVM/contextvm-docs#8

🗞 Proudly announcing the first issue of our new bi‑weekly newsletter! 🗞 In it we will explore everything related to ContextVM, its ecosystem, MCP news, projects, and everything in between. This inaugural issue was written by @tuma , who will help us with communication and news. Tuma is not an LLM or a bot, he is a person, and he already writes for other open‑source projects such as Bitcoin Optech, BTC++ Insider Edition, and more. We’re glad to have him on board and happy to welcome more contributors 💛 Hope you enjoy it, we welcome any feedback, now, Let's keep building!🚀 View article →

A brief demo of the power of these new commands 👀 View quoted note →

And this is not the only news we have for today 👀 more about this later, wait for it 🔥 View quoted note →

🚀 Serve and Use: two new commands, one CLI, zero hassle We merged our standalone gateway‑cli and proxy‑cli tools directly into cvmi. What used to require separate installations and configuration now lives under one unified CLI, and it couldn’t be simpler. Serve any MCP server over Nostr: - For example, the NostrBook: npx cvmi serve npx -y @nostrbook/mcp@latest - Or even expose a remote HTTP server through Nostr👀👀: npx cvmi serve https://mcp.applesauce.build/mcp This is a very new feature and led us to bump our SDK version to 0.3.x. More info is available in the CHANGELOG (https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md) and the gateway overview (https://docs.contextvm.org/ts-sdk/gateway/overview/). Use a remote server and access it locally via stdio: npx cvmi use 7506...5fa3 Both new commands work out of the box with ephemeral keys and default relays. Override relays, keys, or other settings via flags, config files, or environment variables when you need more control. To see all available options, just use --help with any command. For builders who want to ship, and for users who want to connect to their services easily, the toolkit is shaping well: skills, servers, and connectivity in one place. Run npx cvmi and explore. Soon we’ll add new features to complement these and give you everything you need to learn, build, debug, and interact with the CVM ecosystem. Stay tuned.

GitHub

GitHub - ContextVM/cvmi

Contribute to ContextVM/cvmi development by creating an account on GitHub.

#ContextVM #Nostr #MCP #decentralized

Thanks @Pete Winn and @Good Stuff Podcast you are building awesome stuff 🔥 View quoted note →

Add skills just like this `npx cvmi add` pick the one that better suits you, then 🚀 View quoted note →

🎇Meet CVMI: the Army knife we are building for ContextVM development🧑‍💻 If you are building/vibing on Nostr, this is for you. We are shipping CVMI alongside a complete skill set that makes ContextVM development delightful. The skills cover the entire stack: protocol fundamentals, architecture concepts, client and server development, troubleshooting, SDK internals, and production deployment. Each skill includes working templates, reference documentation, and patterns distilled from real Nostr development. Everything you need to do is `npx cvmi`. Or grab the skills through CVMI with `npx cvmi add`, or through the skills CLI with `npx skills add contextvm/cvmi`. These commands will show you the list of available skills and guide you through their installation for any coding platform. Cool, right? You can also pick exactly what you need `npx cvmi add --skill overview` CVMI starts as a skills manager, but we are building toward the unified toolkit that ContextVM deserves. One CLI for skills, server interaction, dev tools, the works. For builders who want to ship. The skills are here now.

GitHub

GitHub - ContextVM/cvmi

Contribute to ContextVM/cvmi development by creating an account on GitHub.

If you don't know what skills are:

Agent Skills Overview - Agent Skills

A standardized way to give AI agents new capabilities and expertise.

#ContextVM #Nostr #MCP #buildinpublic

🧑‍💻 We've just released a new version of the CVM SDK (0.2.6). This time, it is an update focusing on ergonomics and coding style guidelines. The main refactor is that when creating a transport for a client or a server, you no longer need to create a relay handler. You can simply pass an array of relays, and it will create the handler for you using the Applesauce relay handler, which is our recommended, robust, and better tested relay handler. Now: ```typescript const transport = new NostrClientTransport({ signer, relayHandler: ["wss://relay.contextvm.org", "wss://cvm.otherstuff.ai/"], }); ``` Before: ```typescript const relayHandler = new ApplesauceRelayPool([ "wss://relay.contextvm.org", "wss://cvm.otherstuff.ai/", ]); const transport = new NostrClientTransport({ signer, relayHandler, }); ``` Additionally, we updated some of the agentic conventions, code style, and guidelines. We switched to 'AGENTS.md' and created a 'CLAUDE.md' that simply redirects to 'AGENTS.md'."