GM people, and welcome to the 8th issue of "The ContextVM World", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and everything in between!
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.
We also discuss the latest news from the ecosystem, with CVM being used as an actor for Nostr-based state machines.
We also show the features we are currently working on. Our focus is now directed to bringing the Rust SDK in par with the TypeScript implementation.
Finally, we will bring the most interesting news from the internet regarding the MCP ecosystem, AI agents, and more!
Let's start!
News from ContextVM 📰#
A list of updates, releases and new cool features.
The Rust SDK: We recently released the first stable version of our brand-new Rust SDK for CVM! The 0.1.x release family lands with the core specifications 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. With Rust, CVM now expands into native development, opening the door to new use cases, better performance, and future bindings for other languages.
This effort was led by students from Summer of Bitcoin, especially Harsh who lead the development of this release, and Kushagra0902 and Kosti who put together the very first version. We’re grateful for the community effort behind this!
Common tool schema: At last, we merged CEP-15, an enhancement proposal that implements a standard for defining and discovering common tool schema. The goal is to create a simple way for servers to tell each other what tools they have, so they can be grouped together as in a marketplace. Thus, any user would be able to see the different servers providing the same feature, allowing them to choose the best option for their needs. This feature is available starting from the v0.10.x family of the TypeScript SDK.
Open-ended streams: We recently introduced a new specification called CEP‑41, which proposes a method for defining open‑ended streams. This is especially useful for services that need to provide partial results, such as token‑by‑token generation, progressive computation output, subscriptions, and event feeds. This feature is available starting from the v0.11.x family of the TypeScript SDK.
Stateless session behavior: We also published CEP-35, and informational specificaiton that introduces guidelines for stateless session behavior, providing a single behavioral source of truth for session-scoped discovery exchange and capability learning. This has already been implmented in our SDK, and the CEP formalizes it.
News from the ContextVM Ecosystem 🗞️#
Find all the projects leveraging ContextVM on ContextVM/awesome.
- Developer Schlaus Kwab shared a proof-of-concept to run state machines over Nostr for coordination between parties. Some of the features proposed leverage CVM servers as one of the actors involved. You can play around with the p0c here.
What’s Next for ContextVM? ⏭️#
Let’s take a look at the features currently being implemented!
Our main focus is bring the Rust SDK up to par with the TypeScript reference implementation. IS64 is keeping track of the work needed to achieve it.
We are actively working to bring you a new playground, where users can try to use CVM with their favorite LLM. It will be part of our website, and it will allow users to pick servers and start chatting with LLMs using them.
We are currently adapting our website to support CEP-15, to help users discover servers and their related features.
Interesting resources from the web 🤖#
A curated list of resources we found interesting.
New day, new supply‑chain attack. Be safe! Check out TanStack post‑mortem.
Experimental triggers & events are coming to MCP. This is similar to the work we recently did for CEP‑41!
The bottleneck was Never the code: And interesting article discussing the usage of coding agents.
Local AI needs to be the norm: Another interesting article about running local models for some app features for increased privacy and more resilient software.
CVM Team Note: In CVM we like the new paradigm of coding agents and remote execution, but we stay vigilant and critical about how these are being developed and the side effects they may cause. That is the only way we can truly build systems that fit real‑world necessities rather than merely chasing the latest shiny thing.
Find out more about ContextVM:
- Check out our website for documentation, blog posts, and more.
- Join our Signal group
- Follow ContextVM on Nostr
- Subscribe to our Substack. Help us spread the word!
- Check out our GitHub repositories and leave us a ⭐
Comments
No comments yet. Start the conversation.