Ephemeral gift wraps have been merged into the nips repo! 🚀

GitHub

nips/59.md at master · nostr-protocol/nips

Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.

The implementation of CEP‑15 (Common Tool Schemas) has been merged into the https://contextvm.org website. This allows servers to define their categories and common tool hashes so they can be discovered and grouped accordingly. The result is a marketplace‑style UX where multiple servers can expose the same tools or use the same categories. Server operators can position their services within these common categories or tools, and users can navigate the marketplace to find the services that best suit their needs.

This is very cool. Very innovative way to use ContextVM and it's latest updates 👀 View quoted note →

We are proud to be part of the projects listed on the OpenSats website.

OpenSats

ContextVM - funded by OpenSats

A nostr-routed MCP protocol with SDKs, relays, and gateways for exposing services by public key.

💛

Yesterday, we finally chose the finalist students from Summer of Bitcoin. These people will spend the whole summer working on the different parts of ContextVM. Here is what they achieved so far: - @Harsh , pushed the implementation of the Rust SDK - @Abhay , who pushed the work on CEP-15** - @Khushvendra , who worked on the TS SDK, CEP-22, and had also the time to do some maintenance work Huge shotout to our interns!🎇🎇

This is an amazing idea, CVM being used to run state machines 🤌 View quoted note →

🔥 Great news! 🔥 We’ve just released the Rust SDK for CVM:

GitHub

GitHub - ContextVM/rs-sdk: Rust SDK for the ContextVM protocol

Rust SDK for the ContextVM protocol. Contribute to ContextVM/rs-sdk development by creating an account on GitHub.

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:

GitHub

SDK Compliance: CEP & Feature Parity with TS SDK · Issue #64 · ContextVM/rs-sdk

SDK Compliance Tracker Tracking feature parity between rs-sdk and the TS SDK implementation. Checked items are implemented and tested. Open items a...

🧑‍💻 Install it with `cargo add contextvm-sdk`. Huge shout out to our students from Summer of Bitcoin, @Harsh who leaded the development of this release, and @Kushagra , also to @k0sh 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:

GitHub

rs-sdk/docs at main · ContextVM/rs-sdk

Rust SDK for the ContextVM protocol. Contribute to ContextVM/rs-sdk development by creating an account on GitHub.

Repo examples:

GitHub

rs-sdk/examples at main · ContextVM/rs-sdk

Rust SDK for the ContextVM protocol. Contribute to ContextVM/rs-sdk development by creating an account on GitHub.

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 View article →

🚀 https://contextvm.org/s/nprofile1qyd8wumn8ghj7un9d3shjtnrdah8getcw3mx6tn0wfnj7qpqvk3nfvp0tyfu7tqlwvmkq3xlzyj5zen8de75n8gvxn3v5yx08ctq06sg4p View quoted note →

Lazy yet productive Saturday. Stabilized relays from the spam attack and forked Strfry during the process. Contributed to

ants

advanced nostr text search

by @Gigi to add relatr for search capabilities. Touched grass

🚀 View quoted note →

Thanks so much to openSats for this opportunity! We'll keep pushing the boundaries of this new paradigm 💛 View quoted note →

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 →

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 🚀

🗞 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 →

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