ContextVM is a decentralized protocol that enables Model Context Protocol (MCP) servers and clients to communicate over the Nostr network. It uses Nostr as a secure, distributed transport layer—leveraging cryptographic keys for identity, decentralized discovery, and Bitcoin-powered micropayments. Rather than relying on centralized infrastructure like domains, OAuth, or cloud hosting, ContextVM allows anyone to run or access services using only Nostr and a internet-connected device. It transforms any computational service into a discoverable, accessible, and monetizable resource—while preserving privacy, security, and user sovereignty.
Public Key
npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm Profile Code
nprofile1qqsxkduqau5h9eeaxu9cfgl9rea2nt35haqjjwxul0vuta3myg2pdjqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsvynql7
Show more details
Published at
2025-12-25T15:15:38Z Event JSON
{
"id": "f5cb3adc527357ed59d75ad131f56f6291d91b07a81f100d22bb404aee73d297" ,
"pubkey": "6b3780ef2972e73d370b84a3e51e7aa9ae34bf412938dcfbd9c5f63b221416c8" ,
"created_at": 1766675738 ,
"kind": 0 ,
"tags": [],
"content": "{\"name\":\"ContextVM\",\"about\":\"ContextVM is a decentralized protocol that enables Model Context Protocol (MCP) servers and clients to communicate over the Nostr network. It uses Nostr as a secure, distributed transport layer—leveraging cryptographic keys for identity, decentralized discovery, and Bitcoin-powered micropayments.\\n\\nRather than relying on centralized infrastructure like domains, OAuth, or cloud hosting, ContextVM allows anyone to run or access services using only Nostr and a internet-connected device. It transforms any computational service into a discoverable, accessible, and monetizable resource—while preserving privacy, security, and user sovereignty.\",\"picture\":\"https://image.nostr.build/d7356fafce4dbac8436355e9eb1f77156d3429c47c96be31d18c9ff29f7669fb.jpg\",\"display_name\":\"ContextVM\",\"displayName\":\"ContextVM\",\"website\":\"https://contextvm.org/\",\"lud16\":\"[email protected] \",\"banner\":\"https://image.nostr.build/98c21918d6a4d4c26b9bfb98db71d988069b291e40f7440c030c7c766403808d.jpg\",\"nip05\":\"[email protected] \"}" ,
"sig": "62b079bbed54fcf3bb8d7957f3b2bb3b4141013658cee13f60e363d98be7c26f516eae1f5d20aa08b53c63e87801db5e3d050d32f92b293ec7bb9632307b22fc"
}
Last Notes npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM New issue of the CVM World! This time the #8 issue! In today's update we cover the latest news from ContextVM. In particular, we discuss the first official release of our new Rust SDK, which brings CVM to native development. We also cover a bunch of new CEPs being merged. Read it in substack: https://contextvm.substack.com/p/the-rust-sdk-the-contextvm-world Or nostr: https://nostr.at/naddr1qvzqqqr4gupzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qqxvdmx6aed8qpd802z Please if you like what we are doing consider subscribe to the newsletter in Substack as that help us to reach more people and encourage us to keep pushing 💛 https://contextvm.substack.com #naddr1qv…802z npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Yes! LG 🔥 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Yes! 🚀 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM CEP‑41 has finally merged, bringing the ability to create open‑ended streams. These streams are intended for servers that stream data to clients, such as events, fragments, or real‑time data. This opens the door to many new use cases. For example, it enables a CVM server to proxy a WebSocket server, like a Nostr relay 👀. We can imagine numerous interesting applications: AI/LLM streaming APIs, chat servers, real‑time feeds, or any other system that relies on data streaming. You can read the specification on our docs page https://docs.contextvm.org/spec/ceps/cep-41/ A reference implementation is also available in the TypeScript SDK 0.11.x family. Happy building! 🚀🚀 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Do you know that now we also have a Rust SDK? 🦀😎 #nevent1q…8fet npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM This is an amazing idea, CVM being used to run state machines 🤌 #nevent1q…ysc8 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Thanks 💛 It’s still early days, we have a lot of work ahead introducing the other CEPs, for payments and so on. But this is a great foundation: all the core specs are in place, together with encryption and stateless operations. npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 🔥 Great news! 🔥 We’ve just released the Rust SDK for CVM: https://github.com/ContextVM/rs-sdk This is a big step forward for the ecosystem. Until now, the TypeScript SDK, our reference implementation, has been the only one available. With Rust, CVM now expands into native development, opening the door to new use cases, better performance, and future bindings for other languages. The Rust SDK follows the same architectural principles as the TypeScript SDK. It builds on the underlying RMCP SDK for protocol compliance and adds a Nostr transport on top. The 0.1.x release lands with the core spec in place and support for CEP‑4 Encryption, CEP‑6 Server Announcements, CEP‑19 Ephemeral Gift Wraps, and CEP‑35 Stateless Session Discovery and Capability Learning. This release also sharpens the SDK strategy: TypeScript remains the reference implementation for web and desktop, while Rust becomes the foundation for native development and future FFI bindings. The repository already includes docs and examples, with skills, and more documentation coming soon to docs.contextvm.org. It also ships with a strong test suite and interoperability coverage between the TypeScript and Rust SDKs, so it already feels robust. That said, this is still a beta release, and we’ll keep testing and pushing it further. You can follow the current parity status between both SDKs here: https://github.com/ContextVM/rs-sdk/issues/64 🧑💻 Install it with `cargo add contextvm-sdk`. Huge shout out to our students from Summer of Bitcoin, @npub1knd…cqxa who leaded the development of this release, and @npub10hx…wtt6 , also to @npub1zc6…25sl for putting together the very first version. We’re grateful for the community effort behind this 🫶 We hope this SDK unlocks a new wave of development across the CVM ecosystem. Now let’s keep building 🚀🚀 Repo docs: https://github.com/ContextVM/rs-sdk/tree/main/docs Repo examples: https://github.com/ContextVM/rs-sdk/tree/main/examples npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Stats powred by Nanalytics by @npub1jss…fmzy #nevent1q…vggc npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Glad to see nanalytics working great! npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM CEP-8 is the ContextVM standard for decentralized pricing and processing payments for capabilities. When a client requests a capability, an MCP server can send back a notification providing all the information needed for a payment to occur. Specifically, the server advertises the price requested for its capabilities and the types of payment accepted (known as PMI). Let’s examine it from a more technical perspective: 1. Capability Request: The client requests a capability (such as a tool execution) without prior payment. 2. Notification (payment_required): If the server requires payment, it pauses the request and emits a notifications/payment_required event containing the numeric amount, the pmi, and a pay_req opaque string (the actual invoice or payment data). 3. Payment Processing: The client parses the pay_req according to the specified PMI rule set and executes the payment. 4. Notification (payment_accepted or payment_rejected): The server verifies the settlement. If successful, it emits notifications/payment_accepted. If the payment is invalid or insufficient, it emits notifications/payment_rejected. 5. Capability Fulfillment: After a successful payment_accepted notification, the server processes the original request and returns the result to the client. The beauty of CEP-8 is that it does not mandate a specific payment method. Any server operator can decide and advertise the preferred rail for the payment to occur. There is also an alternative payment lifecycle for bearer assets that reduces round trips. We are also working on updates to make this more suitable for LLM agents. If you want to learn more, visit: https://docs.contextvm.org/spec/ceps/cep-8/ npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM It’s up to the imagination. That is a right association, tho. It also references the DVM standard, where “VM” stands for “Vending Machine” npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM At ContextVM we chose Nostr as a communication layer because its simple, permissionless, and decentralized. We think it’s one of the best possible technologies for AI agents to leverage MCPs. npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM ContextVM TS SDK 0.8.0 is live, with CEP‑22 oversized‑payload transfer. Large payload delivery over Nostr relays is now much more robust. We even stress‑tested it by pushing a 1.5 MB image over regular relays, partly to check robustness and partly for fun :) It worked, but keep in mind that this is not a general‑purpose file transfer protocol If you run a server or client on the TS SDK, update to 0.8.0. The CVMI CLI was also bumped to include it. We keep pushing boundaries 🚀 If you are curious about the underlying specification you can read it here: https://docs.contextvm.org/spec/ceps/cep-22/ npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Communications over the internet has been centralizing more and more since its very beginning, choked by permissioned control points. The risk we foresee is that the agentic web can fall in the same trap. ContextVM actively breaks this monopoly by routing the Model Context Protocol (MCP) over Nostr's decentralized relay network, leveraging censorship-resistant public keys that no single entity can shut down or revoke. npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Introducing CEP‑22 (WIP). This new spec adds a simple way to transport ContextVM messages that exceed the relay size limit. It proposes fragmenting a single payload into chunks across multiple events and reassembling it once the receiver has collected all the chunks. The design stays narrow, just enough to handle larger tool results while preserving the current workflow. See the draft spec: https://github.com/ContextVM/contextvm-docs/blob/feat/larger-than-relays/src/content/docs/spec/ceps/cep-22.md npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Curious about which services are already leveraging ContextVM? On our website you can find a list of public server to which your AI agent can connect through our infrastructure! 👇🏻 https://contextvm.org/servers npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Thanks 💛 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM In today’s update we cover the latest news from ContextVM. In particular, we have been chosen to mentor the next generation of open-source contributors through the Summer of Bitcoin internship program 🚀 We also cover our latest modification to the CVM website and the spam attack that recently hit our relays. Read the full article to learn everything going on in the CVM World! https://contextvm.substack.com/p/mentoring-the-next-generation-the #naddr1qv…gz9c npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM We bring amazing news! ContextVM has been invited to participate in the Summer of Bitcoin program. https://www.summerofbitcoin.org/ This is a global, online summer internship program focused on introducing university students to Bitcoin, Nostr, and open-source development and design. We’re very glad to have been chosen as mentors. We’d also be grateful to hear your project ideas for a student to work on for ContextVM during the summer. Please share any you have. What would you like to see in ContextVM? npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 🚀 https://contextvm.org/s/nprofile1qyd8wumn8ghj7un9d3shjtnrdah8getcw3mx6tn0wfnj7qpqvk3nfvp0tyfu7tqlwvmkq3xlzyj5zen8de75n8gvxn3v5yx08ctq06sg4p #nevent1q…rfna npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Setting up an MCP server to be used by AI agents requires a lot of skills, managing domains, OAuth, port forwarding. ContextVM changes the game, reducing the burden for running a remote MCP server! npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Thanks for the help reposting this; we got some new subs :) really appreciate it. #nevent1q…hhcm npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Just released a new version of our TS SDK (0.7.6). This update adds support for dynamic authorization on the server through two new optional callbacks: `isPubkeyAllowed` for runtime pubkey validation and `isCapabilityExcluded` for dynamic capability exclusion from the allowed pubkeys check. These async callbacks complement the existing static allowlist and exclusion configurations, enabling more flexible authorization policies. We have also renamed the `isPublicServer` option to `isAnnouncedServer` to better reflect its purpose of publishing public announcement events on Nostr for relay‑based discovery. The old option is deprecated but still supported for backward compatibility. Docs and skills updated! Happy building! 🦾 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM GM! As you know, we are trying to get the word out on ContextVM to the broader internet by launching our Substack! If you are already on the platform feel free to subscribe! We want the project to grow outside of our niche and we need your help to bootstrap the publication! Here is the link: https://contextvm.substack.com/ npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Just another quick demo. Same thing, but this time, instead of using the CVMI `call` command to access the server, we are connecting to the server as if it were a locally running MCP. This is possible thanks to the CVMI `use` command, which allows you to use CVM servers anywhere you can configure MCP servers. https://mibo.eu.nostria.app/3207606b2502451db13fcc29fe75558194de812bfc33fe1034a04b43961fbabe.mp4 #nevent1q…wfsk npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Just a little but powerful update to our site. Since we merged CEP‑17 for server‑relay announcements, we have updated our site to accept npubs and nprofiles for servers. You can now use these identifiers in the URL or in the search bar. It will resolve relays for the server in this order: 1. Relay hints when the identifiers are nprofiles 2. Server relays (from 10 002 events) 3. Hard‑coded relays, if none of the previous ones exist This really improves discoverability and strengthens decentralization capabilities. We also added an extra goodie: NIP‑05 resolution, so if your server pubkey is associated with a NIP-05 address the site will resolve it. For example, you can use https://contextvm.org/s/[email protected] or, since the host domain matches the NIP‑05 domain, you can even omit the domain part: https://contextvm.org/s/relatr Cool right? 😎 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Just testing this new 'Am I Exposed?' public server someone made online 👀 This is a Bitcoin on‑chain privacy scanner. We wanted to test it to see how it works. This is a short demo of using it together with the CVMI call command. It’s quite straightforward; we didn’t need to touch any other configuration files, just add an alias. The complete process and demo are in this video. https://mibo.eu.nostria.app/e99accc3ff571f264dcdd73620ddf46ef94f55e018762c470d3e7b270a274a9a.mp4 #nevent1q…84y4 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM There is loads of garbage, that's why we hardened the writing policies, also connections openning too many reqs concurrently. It is working great so far npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Basically we replaced the relay we were using with Strfry and hardened some writing rules. Strfry also has some sane abuse protection out of the box. npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Lazy yet productive Saturday. Stabilized relays from the spam attack and forked Strfry during the process. Contributed to https://ants.sh by @npub1der…xzpc to add relatr for search capabilities. Touched grass npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 🚀 #nevent1q…3u3s npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM This should be fixed now 🫡 As a side effect, we forked Strfry to add a convenient way to deploy a relay and some write policies to harden it for CVM usage. https://github.com/ContextVM-org/strfry-cvm #nevent1q…0mym npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Spam attack in our relays. Fixing now npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM A simple, but powerful concept #naddr1qv…eanj npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Hmm, what is your Node version? Some older versions might not have ws defined globally. In any case, we just pushed a new version of cvmi that polyfills this. Please test 0.2.6 and let us know, your feedback will be greatly appreciated 🙏 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Use it from contextvm.org or through the CVMI CLI. 1. Configure an alias for easy calling: `npx cvmi config add ots @nprofile…5kv0` 2. OTS an event: `npx cvmi call ots ots_event target=<event-id‑nevent‑naddr>` 3. Verify the attestation and get its state: `npx cvmi call ots verify_ots target=<event-id‑nevent‑naddr>` If you want, you can configure it as an MCP in your preferred agentic framework; just set `npx cvmi use @nprofile…5kv0` in your MCP configuration. #nevent1q…6c2m npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 🕰 New public server available! 🕰 This is an OTS client that lets you easily Open Time Stamp any Nostr event. The usage is straightforward: two tools, 'ots_event' to create an attestation for an event, and 'verify_ots', which lets you verify the OTS attestation and its state in the time chain. With this server, you or your agents can easily OTS any Nostr event. Here’s a brief demo: https://video.nostr.build/74e0a7eaebda78e3ae27c48b53adfbdac71efa2da606fcb665fa496460aa8cfb.webm The project’s code is open source, and you can run your own instance if you wish. By default it uses public Bitcoin nodes to verify the attestations, so you don’t need to run your own node. https://github.com/ContextVM-org/ots-cvm Server page: https://www.contextvm.org/s/e1c1c32729cbd542c9b9ce7ee6e421c434e07835228020c4f57140782f02496a You can use this service for free, but public OTS servers need to cover operating costs. If you’d like to donate, please refer to opentimestamps.org. npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 🌍 New issue of the ContextVM world newsletter 🌍 In today’s update we cover CEP‑17, the latest specification change to the CVM protocol. This change allows MCP servers to announce the relays for establishing connections, making it easier for clients to discover them. We also discuss new CVMI capabilities and other news from the ecosystem, plus demos and a new Rust SDK that is currently being built. Hope you enjoy it! Don’t miss any issue, subscribe to our Substack. https://contextvm.substack.com/ #naddr1qv…z2d5 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Make your MCPs over Nostr, composable, token efficient, easy 🚀 #naddr1qv…eanj #mcp npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM LG! 🚀 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM We'll write a spec draft soon so we can move forward with that :) npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM https://image.nostr.build/19f28ef0527a534876244ffd331799af566c0a965f04e07f1af7ae321cc958b5.png npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM The cool part about the demo, ahead of the reduction in token usage compared to building this with the MCP interface, is the progressive disclosure. The LLM didn’t know anything about Earthly, Wolfram, or Relatr, and it discovered tools and usage as needed. No extra tool schemas were loaded unnecessarily, no bloated context window, just organic discovery and usage. #nevent1q…4f6s npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM @npub182j…m4rf @npub1jss…fmzy npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM We’re thrilled to roll out CVMI CLI 0.2.x, adding two powerful commands: `call` and `discover`. `call` lets you invoke CVM servers straight from the command line, perfect for debugging or plugging into agents. No MCP config or schema loading needed; responses are cleaned to save tokens. Save servers with aliases and run them like `npx cvmi call relatr`. `discover` query relay announcements to list available tools, just run `npx cvmi discover`. Demo: query Earthly and Wolfram for the Eiffel Tower’s address and height https://video.nostr.build/14f2338be8a83b3e489233fbfcc359956eabb45d2ffee88417c72e1a0aaf7b4f.webm Get Sovereign Engineering pubkey using Relatr. https://video.nostr.build/e6560296c095847b5e5c20ea0d053f3c74bde4145f0ebe1f2bfd0a30721f85cf.webm These upgrades make CVM servers far easier to use and compose, cut token costs versus MCP, and give developers a simple way to debug, script, or integrate CVM services from the command line. Some screenshots of this new capabilities: https://image.nostr.build/9229de75630bcec299836fd1b77dded7809b3c31ba3784f7f7d4b1b434a7203d.png https://image.nostr.build/afae05aeb9be14f2872f11142f957530dff904f14e8697fd136b3de994236079.png https://image.nostr.build/afae05aeb9be14f2872f11142f957530dff904f14e8697fd136b3de994236079.png npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Just wow! This is seriously cool. I think you did the first integration of chat with CVM tools on the web to date. Really awesome! npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 🚀 CEP-17 is now merged into ContextVM, and it is available in the ts SDK from v0.7.x. https://docs.contextvm.org/spec/ceps/cep-17/ This is a meaningful step forward for resilience. With CEP-17, servers can publish the relay list they use following NIP-65, and clients can resolve connection paths more intelligently: first from explicit configuration, then from relay hints embedded in `nprofile`, and then if nothing is define from relay list discovery. That makes connectivity more robust by default, reduces dependence on central points of failure, and avoids hardcoded relays in normal client setup. It also makes client configuration simpler. In many cases, you can now just pass an `nprofile` string and clients will use its relay hints directly; if those are not available, it can fall back to CEP-17 discovery through NIP-65 relay-list metadata. The reference implementation is already in the SDK, the docs and skills have been updated, and contextvm.org now surfaces these new `nprofile` identifiers as well. Small change in surface, big improvement in how reliably clients can find and reach servers across a more sovereign network 🚀 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM We’re so back. DNS problems have been resolved, sites and relays are reachable again 🚀 #nevent1q…my5u npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM We've been having problems with DNS and registrars, which is why our ContextVM websites are down. We have a pending transfer that should be resolved soon. In the meantime, we’ve deployed the main site and documentation on GitHub Pages as a backup alternative. The links are: - https://contextvm.github.io/contextvm-site/ - https://contextvm.github.io/contextvm-docs/ Sorry for the inconvenience. CVM servers are still running, and clients can still connect using any relay, there’s no disruption there 🦾 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Nostr == WS == CVM. Connecting to servers, calling tools, etc, everything has worked over WebSockets since day one with ContextVM 🚀 #nevent1q…xla3 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM A new issue of our biweekly newsletter is out! 🚀 "Ephemeral Is Better — The ContextVM World #3" Available in nostr and substack: https://contextvm.substack.com/p/ephemeral-is-better-the-contextvm #naddr1qv…8e0w npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Continuing with NIPs, we have just added a pr for CVM to the NIPs repository. We wrote this NIP to describe the conventions for transporting Model Context Protocol (MCP) messages over Nostr. We deliberately kept the NIP thin on details that already live in the full CVM spec; it exists to make CVM discoverable in the Nostr ecosystem and to show that CVM is just Nostr, using the same primitives any Nostr app uses. https://github.com/nostr-protocol/nips/pull/2246 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM We just opened a PR in the NIPs repo that includes this convention for ephemeral gift wraps. Perhaps other developers will find it a valuable building block https://github.com/nostr-protocol/nips/pull/2245 #nevent1q…c6mq npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Ephemeral giftwraps improve your privacy and hygiene on relays, as nothing is persisted there. CVM messages use ephemeral events when the traffic is not encrypted, but when encrypted, they wrap the ephemeral events in a gift wrap which uses a regular kind. So even if the wrapped event is ephemeral, its envelope isn't. Ephemeral gift wraps solve this; everything is encrypted end-to-end, relays just route blindly, nothing is persisted, no collect now, decrypt later 🥷🏼 #nevent1q…e26y npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM CEP-19 is live with ephemeral gift wraps 🚀 In plain terms, you can now send end-to-end encrypted MCP messages that do not have to be stored on relays. This is a significant upgrade for privacy, as your messages can travel through public infrastructure without becoming permanent data. The kind used by CVM is ephemeral (25910), and when you use encryption, this ephemeral kind is gift-wrapped (NIP-59) in a regular event kind that is persistent on relays (1059). With this update, servers and clients can use a new kind for ephemeral gift wraps (21059). It is exactly the same as the regular kind (1059) but is ephemeral, so it is not stored on relays. This also improves metadata hygiene: relays can forward messages without needing to retain payloads. How it works: CEP-19 introduces an ephemeral gift-wrap kind alongside the existing persistent kind. Both sides advertise their support, and when both do, the transport prefers ephemeral wrapping while maintaining backward compatibility with older clients. Configuration in the SDK: This feature is available from version v0.6.0. Just set the transport’s `GiftWrapMode` option to `EPHEMERAL` to always use ephemeral gift wraps, `PERSISTENT` to force legacy behavior, or `OPTIONAL` to negotiate ephemeral wrapping when supported. The default remains compatible with existing relays and clients, making this an opt-in privacy upgrade without being a breaking change. npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Hey Nostr! We're excited to share that we're working on getting more eyes on ContextVM and its development. We just published our first post on Hacker News. If you're on the platform, we'd love for you to check it out, share your thoughts, or help spread the word. Every bit helps, so please join us in growing ContextVM! 🚀 https://news.ycombinator.com/item?id=47151294 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Looks dope! npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Now that payments are in place, we are going to work on: - CEP-19 for ephemeral gift wraps: https://github.com/ContextVM/contextvm-docs/issues/19, and - CEP-17 for servers relay list: https://github.com/ContextVM/contextvm-docs/issues/17. Both CEPs are quite minimal but yet beneficial for the ecosystem. CEP-19 provides better privacy guarantees, as servers and clients will be able to use ephemeral gift wraps for encrypted communications. Currently, they use regular gift wraps, which are regular events, and even if the events inside are ephemeral, they are wrapped in a regular envelope. CEP-17 defines how servers can announce relay lists (NIP-65) to improve discoverability. Simple but powerful! LG!🚀 After this iteration we will come back to CEP-15 introducing common tool schemas, which is a bigger one https://github.com/ContextVM/contextvm-docs/issues/15 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM We've just released a new version of our SDK, now CEP-8 implementation is now complete, end to end, we’ve added the missing piece for LLM aware spending CEP-8 gives us the wire protocol for paid MCP capabilities, servers request payment, clients settle, both sides get explicit confirmation. What was missing was a clean way to make consent programmable. This release adds a single paymentPolicy hook at the client boundary, a little yet powerful new addition. Your host environment decides whether a charge proceeds: a deterministic budget, a per-tool allowlist, a terminal prompt, or a full LLM-based policy engine. One hook, any pattern. Google's AP2 addresses a similar problem, but it's an ambitious multi-actor framework involving Shopping Agents, Credential Providers, and cryptographic Mandates passed across multiple parties, quite complex. Our take is different, CEP-8 provides the payment rails, Nostr anchors every request to a cryptographic identity at the transport level, and consent is a composable local primitive. Simpler to integrate, and versatile enough to fit whatever your host needs to do. This our take on agentic payments, simple, versatile, composable, no vendor lock ins npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Yes! npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM After a few days experimenting and receiving feedback around CEP‑8 payments, we enhanced their SDK implementation, making payments more reliable and consistent. We’ve just released a new feature that supports additional use cases, such as servers with prepaid balances, top‑up accounts, or separate payment management. This feature lets you waive a payment via the server’s resolve price callback. With this update, payment processing is far more powerful 🚀 Docs and skills have been updated accordingly. Happy building :) https://image.nostr.build/fbd347f5e537efc79947c1d91acb930cc32ba229624ec17b3380e8be5cf6469b.png Docs: https://docs.contextvm.org/ts-sdk/payments/overview/#waiving-payment-prepaid--subscription-models Skills: npx cvmi add --skill payments, or npx skills add contextvm/cvmi --skill payments npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM We are at speed now, and you can find our latest issue of the newsletter on our Substack! https://contextvm.substack.com/p/the-contextvm-world-2 #nevent1q…rlat npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Get it fresh in your inbox every two weeks! #nevent1q…c4ug npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM GM Nostr! Our newsletter, The ContextVM World 🌍, is now live on Substack: https://contextvm.substack.com/ While ContextVM is built on Nostr and will continue to publish natively on Nostr, our goal is to reach a larger audience outside of Nostr to have more builders leveraging our protocol! Feel free to subscribe to our Substack and to share our newsletter with the world! npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM The second issue of "The ContextVM World" is out! Hope you enjoy it 💛 #naddr1qv…vpzd npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Let's keep building! 🚀 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Thanks Tim! appreciate your words 💛 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Thanks so much to openSats for this opportunity! We'll keep pushing the boundaries of this new paradigm 💛 #nevent1q…hxrk npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Protocols over Platforms is the mantra at the core of CVM https://notnotp.com/notes/use-protocols-not-services/ npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM https://lemonade.contextvm.org #nevent1q…rf53 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM These are badges are real, you can check them here as well: https://nostrsigil.com/badges/naddr1qvzqqqr48ypzpl0zzdglhjrqfsnaelea2plcaxc4gw8nh5zqj09rl4tu66ekckxsqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsqyrvv4kk7mnpv3jj6mr9vajkuernaqgdnx #nevent1q…y4t3 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 🍋 Introducing Lemonade Legends, our newest teaching project that demonstrate how to use CEP-8 in a tangible and fun way! Do you want your lemonade legend badge? https://lemonade.contextvm.org This is a server that mints nostr badges with dynamic pricing: 21 sats on day 0, +21 sats each day after. A live experiment in paid capabilities, SQLite accountability, and dual APIs (humans via UI, agents via MCP). The idea behind this project was to create a new and fun educational resource for the CVM ecosystem. You can read our blog post here: https://contextvm.org/blog/lemonade-legends or in nostr. What we did for this project: ✨ Server + Svelte app, both open source ✨ Step-by-step blog post walking through the code ✨ Copy-paste ready patterns for your own paid tools Dive in → https://contextvm.org/blog/lemonade-legends Server → github.com/ContextVM/lemonade-legends Site → github.com/ContextVM/lemonade-legends-site What will you build with CEP-8? 💛 #lemonadelegends #contextvm #cep8 #nostr #bitcoin #lightning #opensource #naddr1qv…t8dw npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 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⚡⚡️ https://image.nostr.build/986e254f2b9a960f1d6080be6b74b027bafe22e6619e302fc6837bfc3c84d22c.png 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!⚡️⚡️⚡️ npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM LFG! 🔥 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Totally agree. This is why CVM 💛 #nevent1q…myde npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 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. #nevent1q…cyqu npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM It takes you ~20 LOC to enable payments in your server. NWC + CVM = 🤯 https://image.nostr.build/808074d08ff8c4f5cb0f345ffc2cc89d10a22e156fd9248dd1915600ef32e4e3.png The code: https://github.com/ContextVM/dummy-paid-server/blob/main/index.ts #nevent1q…8du5 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 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! 🚀 #nevent1q…ad8v npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 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. https://video.nostr.build/aaa0ef0bb44b55da525e2047b681b4fbd7aa4e5c603bb4fbbd682c5603b21ceb.mp4 Looking forward to hear your thoughts and see what you are building! Read the docs: https://docs.contextvm.org/spec/ceps/cep-8/ Build a stand. Price a capability. Let value flow. If you have any question just ask #naddr1qv…qt6c npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Payments are coming imminently 🚀 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 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: https://github.com/ContextVM/contextvm-docs/blob/ed71abec7bd93ba1082e67dfc92f0b0bcf618a72/src/content/docs/spec/ceps/cep-8.md SDK progress: github.com/ContextVM/sdk/pull/24 Feedback welcome! #nevent1q…ppc5 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 📡 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 @npub1jss…fmzy 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: https://github.com/ContextVM/awesome#public-cvm-relays npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Great! can you open a pr? npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Well, there is no need to add methods for topping up the wallet/nutstash. We should assume the wallet is already plugged in and has funds. If you read CEP-8, the responsibilities of servers and clients are clarified there. tldr; Servers act as payment processors, emitting payment requests and then validating that the payment was done. Clients act as payment handlers, being responsible for paying the requests emitted by the server. The funds that the wallet has available are a separate matter and are better kept out of scope, so there is no need for deposit or withdraw methods. A way this could work is as follows: the server (payment processor) receives a request for a paid capability. It then goes to the mint it has configured, gets a quote, obtains the BOLT11 invoice from it, and sends the payment request. The client (payment handler) takes the BOLT11 invoice, gets a melt quote for it, and the mint handles the payment. At that point, the server can check its quote status and verify if it's fulfilled. Then the lifecycle is completed. Extra steps could include redeeming the tokens from the quote and storing them either locally or in the NIP-60 wallet. What do you think? If there are some concepts that are not clear, we have written a couple of guides and resources to understand how payments work in CVM: Payments, Paid Servers, and Clients https://github.com/ContextVM/sdk/blob/e2096b7c94658e1f7b5a3f06ad53738d1e3eacea/docs/payments-paid-servers-and-clients.md Payments Architecture https://github.com/ContextVM/sdk/blob/e2096b7c94658e1f7b5a3f06ad53738d1e3eacea/docs/payments-architecture.md There is also the spec CEP-8: https://github.com/ContextVM/contextvm-docs/blob/8d0dbfc95a929ac6dd49cab556b18874df758b73/src/content/docs/spec/ceps/cep-8.md Happy to solve any doubts if you have any! npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM I haven't checked the dependency tree to be honest. But if you feel comfortable with nostr-tools and there is no need for other new deps, it is preferable. If not, maybe the best option is to create a separate repo for extra payment processors and handlers. npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Exactly https://applesauce.build/money/wallet/package.html https://applesauce.build/examples/#/example/wallet/wallet npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Amazing! we have nostr-tools as dependency as well. Thanks 🚀💛 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Sounds good! Do you feel proficient enough in TypeScript to contribute with a PR? Ideally without introducing more deps, we already have applesauce which it have nip-60 utils as well, If not, we can add it in a future iteration once our PR is finished. Ongoing PR: https://github.com/ContextVM/sdk/pull/24 Reference from the PR we just merged with the LNbits backend: https://github.com/ContextVM/sdk/pull/25 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM The PR is not even merged yet, and we already have @npub19a8…2ckt 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 #nevent1q…ppc5 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 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 https://github.com/ContextVM/contextvm-docs/pull/9 and follow the progress of the implementation in the SDK at https://github.com/ContextVM/sdk/pull/24 . Feel free to give us some feedback or ask any questions! npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 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, @npub1ye5…knpr, for pointing them out 🚀 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 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: https://github.com/ContextVM/contextvm-docs/pull/9 If you are interested in the development of it: https://github.com/ContextVM/sdk/pull/24 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Hey, yes, these servers are offline. We are not running them, is the operator, probably @npub1ye5…knpr Sorry for the inconvenience. We should add a function to dummy ping servers so they can display an 'offline' badge. I'm happy to assist further if you need help npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 🗞 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 @npub1jeq…nmal , 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!🚀 #naddr1qv…zmfy npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM A brief demo of the power of these new commands 👀 https://video.nostr.build/6b13b147fffa320ce95bc61c291cc4922a6d40b726edfc83c1e5c43d817ab4f9.mp4 #nevent1q…gw65 npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM And this is not the only news we have for today 👀 more about this later, wait for it 🔥 #nevent1q…x2hg npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM 🚀 Serve and Use: two new commands, one CLI, zero hassle https://image.nostr.build/04fc33ed93083179db6cd6f751d40f06c801ac978f8e38b024c0751fb2d4a9f7.png 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. https://github.com/contextvm/cvmi #ContextVM #Nostr #MCP #decentralized npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Hahaha ok, thought it was something new. We think that as enshittification continues extending its shadow through the internet and digital world, it is going to be more and more valuable for individuals to be able to fully, self organize, associate, collaborate and share their resources. We feel that the infrastructure as a service model that we are seeing more and more is going to be a huge bottleneck and more discriminatory since the heavy computations they offer will struggle with a more democratized demand for the resources. So, the more people, the worse that model scales without sacrificing a competitive environment and becoming a monopoly. At the same time, things are going to get cheaper to run at low scale and people will be able to share the resources they have to satisfy demand at their scale. This vision can be true or not in the future, but it is one of the fundamental whys behind CVM, high bandwidth collaboration between individuals. If you feel curious about our point of view and ethics you can check our blog, we have some nice articles like https://contextvm.org/blog/forging-a-new-frontier npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm ContextVM Thanks! Yes, Nostr is a whole paradigm shift, and CVM is another building block of Nostr that leverages as many of its inherent features as possible. Very powerful. We would love to know more about that concept of cognitive computing resources you mentioned. Would you mind explaining what it means?