[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6},"actionData","errors","routes/hashtag",{"_7":8,"_9":10,"_11":12},"articles",[13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30],"authors",{},"tag","cvm",{"_31":547,"_33":548,"_35":549,"_37":38,"_39":40,"_41":550,"_43":551},{"_31":508,"_33":509,"_35":510,"_37":38,"_39":40,"_41":511,"_43":512},{"_31":479,"_33":480,"_35":481,"_37":38,"_39":40,"_41":482,"_43":483},{"_31":446,"_33":447,"_35":448,"_37":38,"_39":40,"_41":449,"_43":450},{"_31":424,"_33":425,"_35":426,"_37":38,"_39":40,"_41":427,"_43":428},{"_31":391,"_33":392,"_35":393,"_37":38,"_39":40,"_41":394,"_43":395},{"_31":364,"_33":365,"_35":366,"_37":38,"_39":40,"_41":367,"_43":368},{"_31":325,"_33":326,"_35":327,"_37":38,"_39":40,"_41":328,"_43":329},{"_31":304,"_33":305,"_35":306,"_37":38,"_39":40,"_41":307,"_43":308},{"_31":279,"_33":280,"_35":281,"_37":38,"_39":40,"_41":282,"_43":283},{"_31":255,"_33":256,"_35":257,"_37":38,"_39":40,"_41":258,"_43":259},{"_31":220,"_33":221,"_35":222,"_37":38,"_39":40,"_41":223,"_43":224},{"_31":194,"_33":195,"_35":196,"_37":38,"_39":40,"_41":197,"_43":198},{"_31":165,"_33":166,"_35":167,"_37":38,"_39":40,"_41":168,"_43":169},{"_31":143,"_33":144,"_35":145,"_37":38,"_39":40,"_41":146,"_43":147},{"_31":111,"_33":112,"_35":113,"_37":38,"_39":40,"_41":114,"_43":115},{"_31":83,"_33":84,"_35":85,"_37":38,"_39":40,"_41":86,"_43":87},{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":42,"_43":44},"content","We are thrilled to announce the launch of the brand new ContextVM website, now live at [contextvm.org](https://contextvm.org)! This is a major step forward in our mission to create a truly sovereign, resilient, and open marketplace for computational tools and services.\n\nThis first version of our new site is fully functional and provides the core tools you need to engage with the ContextVM servers. Our primary focus is on making it simple to discover, connect to, and use ContextVM servers.\n\n### Discover and Connect\n\nThe new website acts as your gateway to the ContextVM ecosystem. The key functionality allows you to:\n\n* **Discover Public Servers:** Find and explore publicly available ContextVM servers shared by the community.\n* **Connect to Private Servers:** The platform is designed not just for public use, but to give you a seamless interface for connecting to and using your own private servers. Run a service on your machine at home and access it from anywhere, securely and privately.\n\nOur goal is to break down the barriers of traditional networking. With ContextVM, running a service is as simple as running an app on your laptop—no public IP addresses, complex firewall rules, or gatekeepers required. This new website is the user-friendly portal to that experience.\n\nShort demo of the site:\nhttps://video.nostr.build/4a0f4498cadb8e165d96118ece0714d6c03f2b135d340871cc89567a5cf93195.webm\n\n### A New Home for a Growing Project\n\nAs part of this launch, we've reorganized our online presence to better serve the community:\n\n* **New Pages:** The site now includes a **Blog** (which you're reading right now!), a comprehensive **About** page explaining our vision, and an **FAQ** to answer common questions. We want to provide clear, accessible information for everyone, from new users to experienced developers.\n* **Dedicated Docs:** All of our technical documentation has been moved to its new home at [docs.contextvm.org](https://docs.contextvm.org).\n\n### Openly Built and Ready for Contribution\n\nIn the spirit of decentralization and collaboration, the entire website is open source. It’s built with modern tools, including Svelte 5 and the `applesauce` Nostr library. We encourage you to check out the code, fork it, and contribute.\n\nWhile this first iteration is stable and fully working, we are continually iterating to add new features and improve the design.\n\n### We Need Your Help! A Call for Designers\n\nWe are actively looking for talented designers to help us shape the future of the ContextVM interface. If you have experience in UI/UX design and believe in a more open, permissionless internet, we would love to hear from you. Your contribution can make a massive impact on the usability and appeal of the project.\n\n### Get Involved\n\nWhether you're a developer, a designer, or simply someone who believes in a more sovereign web, there are many ways to get involved.\n\n* Explore the new website at [contextvm.org](https://contextvm.org).\n* Dive into the documentation at [docs.contextvm.org](https://docs.contextvm.org).\n* Contribute to the project on GitHub at [github.com/contextvm](https://github.com/contextvm).\n* Join the conversation in our Signal group: [Join the group](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR).\n\nIf you have any questions, doubts, or need help with anything—from running your own server to connecting it with LLMs—please don't hesitate to get in contact.","created_at",1755098914,"id","7c331a609dcce773596743514e1c31e010dfa3159b9184aa6c287cbe41a112b2","kind",30023,"pubkey","6b3780ef2972e73d370b84a3e51e7aa9ae34bf412938dcfbd9c5f63b221416c8","sig","ac1434f4bf1cf8e84898ff239a189dedf97c326cbf4b75c0cb5f75f5b9f2825164cb6135dd9309bb019d159ce101542179ef42e691a2d5cfd3a3bd393d7edc10","tags",[45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60],[81,82],[79,80],[77,78],[61,76],[61,75],[61,74],[61,12],[61,73],[61,72],[61,71],[61,70],[61,69],[67,68],[65,66],[63,64],[61,62],"t","CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg","alt","This is a long form article, you can read it in https://habla.news/a/naddr1qvzqqqr4gupzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqqf8yetvv4shx6twvukkueth94ekjar97vcl4k","published_at","1755098910","image","https://image.nostr.build/98c21918d6a4d4c26b9bfb98db71d988069b291e40f7440c030c7c766403808d.jpg","internet","freedom","llm","ai","ctxvm","contextvm","mcp","nostr","summary","We are thrilled to announce the launch of the brand new ContextVM website, now live at contextvm.org! This is a major step forward in our mission to create a truly sovereign, resilient, and open marketplace for computational tools and services.","title","Releasing the new ContextVM website 🚀","d","releasing-new-site","# Introducing ContextVM Enhancement Proposal (CEP) Guidelines\n\nWe're excited to announce the launch of our new ContextVM Enhancement Proposal (CEP) guidelines! As ContextVM has grown, we recognized the need for a more structured approach to protocol evolution. This standardized process is designed to ensure that enhancements to the ContextVM protocol are well-vetted, thoroughly discussed, and properly documented while maintaining our community-driven approach to development.\n\nOur approach draws inspiration from successful governance models used by other open source projects, including the Model Context Protocol's SEP guidelines, Python PEPs and Rust RFCs. By adapting these proven approaches to ContextVM's unique needs, we've created a framework that balances structure with flexibility.\n\n## What Are CEPs and Why Do They Matter?\n\nA **CEP** (ContextVM Enhancement Proposal) is a formal design document that proposes changes to the ContextVM protocol, outlines new features, or describes improvements to our development processes. Think of CEPs as the pathway for bringing big ideas to the ContextVM ecosystem in a way that ensures they receive the consideration they deserve. For more information about what qualifies as a CEP, see our [CEP guidelines](https://docs.contextvm.org/spec/cep-guidelines/).\n\nThe CEP process serves several important purposes. It provides standardization by creating a consistent format for proposing and reviewing protocol changes. It ensures transparency by maintaining a clear record of design decisions and community input. It fosters collaboration by ensuring broad community participation in protocol evolution. And it maintains quality by encouraging thorough consideration of technical implications and security concerns.\n\n## What Qualifies for a CEP?\n\nNot every change requires a CEP! The process is designed for substantial proposals that benefit from formal discussion and documentation. You should consider proposing a CEP if your change involves:\n\n- **New Protocol Features**: Adding event kinds, Nostr integration patterns, or changing data structures\n- **A Breaking Change**: Any change that is not backwards-compatible\n- **A Change to Governance or Process**: Any proposal that alters the project's decision-making, contribution guidelines\n- **A Complex or Controversial Topic**: If a change is likely to have multiple valid solutions or generate significant debate, the CEP process provides the necessary framework to explore alternatives, document the rationale, and build community consensus before implementation begins\n\nFor smaller, straightforward changes, a regular GitHub issue or pull request is often more appropriate. You can learn more about the CEP submission process in our [official documentation](https://docs.contextvm.org/spec/cep-guidelines/#submitting-a-cep).\n\n## The Three Types of CEPs\n\nWe've defined three categories of CEPs to serve different purposes within our ecosystem:\n\n1. **Standards Track CEPs** describe new features or implementations for the ContextVM protocol itself. They extend or enhance the base protocol and become part of the official specification once finalized. These are the most common type of CEP and represent the core evolution of our protocol. For more details on Standards Track CEPs, refer to our [CEP guidelines](https://docs.contextvm.org/spec/cep-guidelines/#cep-types).\n\n2. **Informational CEPs** provide guidelines, describe design issues, or share information with the community without necessarily representing official consensus. These documents serve as valuable resources that help the community understand complex topics or design considerations, even if they don't directly change the protocol. Learn more about Informational CEPs in our [documentation](https://docs.contextvm.org/spec/cep-guidelines/#cep-types).\n\n3. **Process CEPs** focus on how we work rather than what we build. These address processes surrounding ContextVM development, such as changes to contribution guidelines, review procedures, or community governance. They ensure that as our project grows, our ways of working evolve thoughtfully and with community input. For more information about Process CEPs, see our [CEP guidelines](https://docs.contextvm.org/spec/cep-guidelines/#cep-types).\n\n## How the CEP Process Works\n\nThe CEP process is designed to be thorough yet efficient, ensuring that good ideas get proper consideration while moving through clear stages. For Standards Track CEPs, the journey begins with a discussion phase where you start with a GitHub Issue to gather initial feedback and build consensus. This is followed by the specification phase where you create a Pull Request with the detailed technical specification. Then comes sponsorship, where you find a maintainer to champion your proposal. Next is the review process, where your proposal undergoes formal review by maintainers. Finally, there's implementation, where you complete a reference implementation before final approval.\n\nFor Informational and Process CEPs, the journey is similar but slightly streamlined. You still start with a discussion phase by creating a GitHub Issue, then find a maintainer sponsor, go through formal review by maintainers, and finally see your CEP accepted.\n\n## Key Benefits of the CEP Process\n\nThe CEP process brings significant advantages to everyone involved in the ContextVM ecosystem:\n\n### For Contributors\n- **Clear Process**: Well-defined steps for bringing your ideas to life\n- **Community Input**: Your proposal gets reviewed by the entire community\n- **Expert Guidance**: Access to maintainer expertise and feedback\n- **Historical Record**: Your contribution becomes part of ContextVM's history\n\n### For the Community\n- **Quality Assurance**: Thorough review of protocol changes\n- **Transparency**: Clear documentation of design decisions\n- **Consensus Building**: Structured approach to resolving disagreements\n- **Ecosystem Growth**: Well-considered enhancements that benefit everyone\n\n### For Protocol Evolution\n- **Stability**: Breaking changes are carefully managed\n- **Interoperability**: New features are designed with compatibility in mind\n- **Security**: Security implications are thoroughly evaluated\n- **Maintainability**: Clear documentation makes future maintenance easier\n\n## Getting Started with CEPs\n\nReady to propose an enhancement? The journey begins by reviewing the full CEP guidelines to understand the detailed requirements. It is highly recommended that a single CEP contain a single key proposal or new idea. First, ascertain whether your idea is CEP-able by posting to the ContextVM community forums (Nostr, Signal, GitHub Discussions). When ready, create a GitHub Issue with the `CEP` and `proposal` tags. The next step is to find a sponsor by tagging relevant maintainers to get your proposal championed. Finally, engage with the community to build consensus and refine your idea based on feedback. For detailed instructions on submitting a CEP, please refer to our [CEP guidelines](https://docs.contextvm.org/spec/cep-guidelines/#submitting-a-cep).\n\n## Looking Ahead\n\nThe CEP process represents an important step forward for ContextVM's governance and development workflow. By establishing clear guidelines for protocol enhancement, we're ensuring that the main specification remains focused and clean while protocol extensions are properly documented and reviewed. This approach guarantees that community voices are heard and valued, and that innovation happens in a structured, collaborative environment.\n\nWe believe this process will help ContextVM continue to evolve in a way that benefits the entire ecosystem while maintaining the quality and security that our users expect. Drawing inspiration from successful projects gives us confidence that this approach will scale with our community's growth.\n\n## Join the Conversation\n\nThe CEP process is fundamentally community-driven, and we need your participation to make it successful! Whether you want to propose an enhancement, review existing proposals, or simply learn more about the protocol, there are many ways to get involved. You can browse existing CEP proposals in the ContextVM-docs repository, join discussions on GitHub, Nostr, or Signal, review and provide feedback on CEPs in development, or consider sponsoring proposals if you're a maintainer.\n\nTogether, we're building the future of ContextVM.\n\n## Additional Resources\n\nFor more information about ContextVM and the CEP process, please visit:\n\n- [CEP Guidelines Documentation](https://docs.contextvm.org/spec/cep-guidelines/)\n- [ContextVM Documentation](https://docs.contextvm.org/)\n- [ContextVM-docs Repository](https://github.com/ContextVM/contextvm-docs)",1756305533,"9b575d9f107c7f0cf6a6582dee75e2b028cd6d89ff8f1f90f80878d0a5d9db6a","3ce500dcf91b91a0c322450fe26e3b560ea2936a68bc71d16f7274a9e33c4dd1767d621bfb0737a8045152edb6698cb38c5c7b587fc9737b9ea3ab3c89243772",[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104],[81,110],[79,109],[77,108],[65,66],[63,64],[61,107],[61,76],[61,75],[61,74],[61,12],[61,73],[61,72],[61,71],[61,70],[61,69],[67,106],[61,105],"submitting","https://image.nostr.build/766e2080a058797690ad298542ff2e491bb942eaebb8fa52335077178c23f1f7.jpg","cep","We're excited to announce the launch of our new ContextVM Enhancement Proposal (CEP) guidelines! As ContextVM has grown, we recognized the need for a more structured approach to protocol evolution. This standardized process is designed to ensure that enhancements to the ContextVM protocol are well-vetted, thoroughly discussed, and properly documented while maintaining our community-driven approach to development.\n","Meet CEPs — Propose. Review. Ship","introducing-ceps","The promise of a truly decentralized internet has long been a guiding star for builders, developers, and advocates of digital freedom. Yet, the practical challenges of deploying services that are both censorship-resistant and easy to manage have often felt insurmountable. During the recent #sovEng 5 cohort, we embarked on a period of intense experimentation with ContextVM (CVM), a technology that we believe provides a powerful new foundation for sovereign infrastructure. This article shares the insights, breakthroughs, and a Cambrian explosion of projects that emerged, painting a picture of a more liberated digital future.\n\n## The Paradigm Shift: Services Addressed by Public Keys\n\nAt the heart of our exploration was a fundamental realization: CVM enables a powerful paradigm shift by allowing services to be addressed by a public key rather than a permissioned, location-dependent IP address. This seemingly simple change has profound implications.\n\nSuddenly, the need for API keys vanishes, replaced by cryptographic identity. The complex dance of configuring networks, firewalls, and NAT traversal becomes obsolete. You can deploy a service from your laptop in a coffee shop, and it is instantly accessible to the world, securely and privately. The service is identified by *who* it is (its pubkey), not *where* it is.\n\nThis unlocks the concept of \"rolling services\"—infrastructure that can move geographically without any disruption in accessibility. It makes deploying services not only trivial but also unstoppable. Security and privacy are enhanced by default; since a service never needs to reveal its IP address, only the relay it connects through can see its IP, but all communication is end-to-end encrypted, rendering the relay blind to what's happening.\n\n## Balancing the Trilemma: Convenience Through Sovereignty\n\nZooko's like Trilemmas suggests that of the three desirable properties—privacy, decentralization, and convenience—we can only pick two. If convenience is provided by a third party, you inevitably sacrifice either privacy or decentralization.\n\n![Zooko's Trilemma](https://image.nostr.build/b3029b832db5082ca0cc9e0915f0991c7b31047b6619f79ddd9b100f5c3e4cb3.png)\n\nInspired by nostr:nprofile1qqsxu35yyt0mwjjh8pcz4zprhxegz69t4wr9t74vk6zne58wzh0waycprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5qyxhwumn8ghj7mn0wvhxcmmvee340a 's presentations during the cohort, we were led to a powerful conclusion: you can balance all three if you reframe the problem. When a user provides their own convenience, they sacrifice nothing. Convenience is transformed into sovereignty.\n\n![Sovereignty Trilemma](https://image.nostr.build/7106ea033c5b5e85ea9d86ec4d3193ba5a0e2b50fdb5e10f550f971c5b3facee.png)\n\nCVM provides the technical groundwork for this model, making it practical for anyone to become their own infrastructure provider. This is especially appealing for node runners or anyone with a spare device and an internet connection. We are actively working to make this even more accessible, with plans for \"one-click\" CVM server installations on platforms like Umbrel and Start9, truly democratizing the ability to run one's own corner of the internet.\n\n## From Theory to Practice: A Cambrian Explosion of Experiments\n\nTalk is cheap. The true test of any technology is what people build with it. SovEng 5 unleashed a torrent of creativity, with projects exploring the potential of CVM. Here are some of the highlights:\n\n### [Nutoff](https://github.com/gzuuus/nutoff-wallet): A Sovereign Cashu Wallet\n\nOne of the first experiments, Nutoff is a Cashu wallet that runs locally on your device, yet is accessible from anywhere. By implementing the Nostr Wallet Connect (NWC) API, it allows users to create and pay invoices while ensuring all sensitive data remains under their control. This minimizes custodial risk and provides a powerful, self-hosted alternative for managing eCash. To complement the wallet, the [`nutoff-http`](https://github.com/gzuuus/nutoff-http) project was created, providing a simple HTTP server to interact with the wallet and offer a Lightning Address out of the box for any Nutoff wallet. Here you can see a [diagram](https://nostr.at/nevent1qvzqqqqqqypzqs9eep0ll6hurjkl3sc2fewgses07mjfwxsdcu3at2m8fd0xrdz3qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qqsypfpvq4afjm9n977xsxf7ngx75a0556tf46rzvwcam3jmgdelgsg6uqw24) of how all this works together.\n\n### [Beacon](https://github.com/humansinstitute/beacon-main): A Trojan Horse for Freedom Tech\n\nBeacon is a liberating and audacious idea: infiltrate walled gardens like WhatsApp with Lightning payments and other freedom technologies. Born from the realization that in many parts of the world, WhatsApp *is* the internet, Beacon uses CVM as the unstoppable glue to connect its different components and users from closed ecosystems to open networks. It's a pragmatic tool for guiding people toward free information, free networks, and freedom money. As the project's main meme states, \"Nice walled garden you got there, shame if someone... Put some freedom tech in it\" ([Demo](https://nostr.at/nevent1qvzqqqqqqypzp9pptap2jce4epluh85grg9mkc4e5724r8ssnn6ln5h0v9mgra3zqy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uqzqznn5y4wf2xsm5sj55tddemrgj6x7yscyn8pp7xmn8fznh2ryt9t0lxchs))\n\n### [Blovm](https://github.com/ContextVM/blovm): Your Personal, Sovereign Dropbox\n\nBlovm explores the idea of a personal file indexing and storage system. It watches a local directory, indexes any files you drop into it, and uses Blossom integration to let you access or share them from anywhere. Essentially, you can request your server to upload a file from your local filesystem to a Blossom server, making it available to be downloaded from anywhere. It also supports the reverse process, allowing you to monitor a public key and automatically back up all associated blobs to your local machine. Other powerful features include periodic health checks to ensure your online blobs remain accessible, enabling you to re-upload them if they disappear.\n\n### [CtxCn](https://github.com/ContextVM/ctxcn): Streamlining Developer Experience\n\nInspired by tools like `shadcn` and [Cap'n Web](https://blog.cloudflare.com/capnweb-javascript-rpc-library/), CtxCn is a command-line utility that makes developers' lives easier. It connects to a CVM server, reads the JSON schema definitions of its tools, and automatically generates a type-safe TypeScript client. With a simple `init` and `add ` command, developers can call remote CVM tools as if they were native functions, complete with type safety and autocompletion. We'll be writing a more detailed article on this tool soon.\n\n### [Retired in a Field](https://github.com/humansinstitute/retired-in-a-field-cvm): FUNding, and Multi-Jurisdictional Deployments\n\nThis playful game demonstrated how a full-stack application could be built with a completely decoupled architecture. The static frontend was hosted somewhere, while the CVM backend—managing Cashu payments, leaderboards, and some logic—ran from an Airbnb in Funchal, Madeira. This highlights the concept of multi-jurisdictional deployments, a powerful strategy for building resilient applications. It also brought \"fun\" to funding, with proceeds split between the developer and the CVM team. Another insight from this project is the ability to create 'full-stack' apps based on static web pages, a powerful pattern when combined with Nsite.\n\n### [Keepass-CVM](https://github.com/ContextVM/keepss-cvm.git): A Secure, Self-Hosted Password Manager\n\nThis project brings the convenience of services like Bitwarden to a self-hosted, minimized-trust environment. Keepass-CVM allows anyone to run their own secure password manager, accessible from anywhere, without any sensitive information ever leaving their device. It transmits data over relays in an end-to-end encrypted manner.\n\n### [Craig David Machine](https://github.com/humansinstitute/craigdavid-cvm): Composable AI Entertainment\n\nA perfect example of a composable application, this hilarious experiment uses multiple micro-backends to summarize your week on Nostr and turn it into a rap song, performed by a virtual Craig David. It's a fun demonstration of what's possible when services can be composed seamlessly. ([Craig David Profile](https://nostr.at/nprofile1qqs865yg459use0ggf8925h4xwntlu7kuuwatzaymkcme2dm2kqjnrgpzfmhxue69uhk7enxvd5xz6tw9ec82csppamhxue69uhkummnw3ezumt0d5q3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5qyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueqpp4mhxue69uhkummn9ekx7mqsy6l7p))\n\n### [Hypernote Elements](https://github.com/futurepaul/hypernote-elements): Interactive Experiences on Nostr\n\nHypernote brings back the spirit of the early, hypertext-driven web, allowing developers to create interactive, micro-apps that live directly within Nostr notes. It have some examples using CVM to provide the 'backend' or state management for these hyper-apps, opening up new possibilities for rich, decentralized content. ([Demo](https://nostr.at/nevent1qvzqqqqqqypzqrtvswydevzfhrw5ljxnmrpmhy778k5sh2pguncfezks7dry3z3nqy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uqzq6pp2c2wd6qwdv75xamn4dvxf5qxxe9vj7z383nr68qg5geytg3t2z8q2a))\n\n### [Paygress CVM Integration](https://github.com/DhananjayPurohit/paygress): Sovereign Machine Provisioning\n\nAnother powerful idea, this project explored using CVM as the interface for Paygress, a service that offers VPS and machine deployment using Nostr. This would allow users to programmatically buy and manage machines in a completely sovereign manner.\n\n### And More...\n\nOther projects are being built right now, and we are working on creating an awesome list of them. Stay tuned!\n\n## Empowering the Builders: Workshops and Knowledge Sharing\n\nA common misconception we encountered was that CVM is purely for AI and LLM applications. To dispel this, we conducted workshops focused on building general-purpose services. We demonstrated how anyone could build an MCP server in one of the ten supported languages (see the [MCP SDKs](https://modelcontextprotocol.io/docs/sdk)) and instantly expose it as a CVM server using the gateway component. The [CVM Rust MCP example](https://github.com/futurepaul/cvm-rust-mcp) created by nostr:nprofile1qqsq6myr3rwtqjdcm48u357ccwae8h3a4y96s28y7zwg458ngeyg5vcpzpmhxue69uhnzdps9enrw73wd9hsz9rhwden5te0dehhxarj9ehhsarj9ejx2as9mu63n during the workshop is a testament to this flexibility.\n\n## The Dual API: A Bridge Between Humans and AI\n\nWhile these experiments focused on CVM for sovereign backends and programmatic use, it's crucial to remember that the underlying Model Context Protocol (MCP) was designed for interaction with LLMs. This gives every CVM service a unique \"dual API\" nature. By building on CVM, you get an API usable by LLMs for free. A service built for a human or another program can be seamlessly understood and utilized by an LLM, opening up a fascinating design space for the future.\n\n## The Road Ahead\n\nThe experiments at SovEng 5 revealed that ContextVM is more than just a tool; it's a foundation for a new class of applications built on the principles of sovereignty, privacy, and decentralization. It enables multi-jurisdictional deployments, eliminates single points of failure, and provides a stellar developer experience.\n\nAll the projects mentioned are in their early stages, and we are incredibly excited to continue working on them, and about what's next. We hope this article has illuminated the potential of CVM and inspired you to join us. Keep an eye on these projects, or better yet, jump in and contribute.\n\nIf you have questions or want to contribute, please reach out to us on Nostr or join our [Signal community](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR). We are always happy to help build the future.\n\nThanks to everyone who contributed to make this article possible 💛 ",1760440304,"ec2db296ad534b208e0d0b6740a5856c06dffaeee2e02fbbd94cc699305b2ffc","44fb22342835ac9b67361276ccfd378e5073745f0588961a5465859c5926ac25130e37a7a0f8427d79d0c92f9c0f41fcb79056fbdc6c2606a962583efd94646b",[116,117,118,119,120,121,122,123,124,125,126,127,128],[140,141,142],[65,139],[81,138],[67,137],[79,136],[77,135],[61,134],[61,76],[61,12],[61,74],[61,75],[129,133,131,132],[129,130,131,132],"p","0d6c8388dcb049b8dd4fc8d3d8c3bb93de3da90ba828e4f09c8ad0f346488a33","","mention","6e468422dfb74a5738702a8823b9b28168abab8655faacb6853cd0ee15deee93","sovEng","During the recent SovEng 5 cohort, we embarked on a period of intense experimentation with ContextVM (CVM), a technology that we believe provides a powerful new foundation for sovereign infrastructure. This article shares the insights, breakthroughs, and a Cambrian explosion of projects that emerged, painting a picture of a more liberated digital future.","Lessons and Innovations from CVM at SovEng 5","https://image.nostr.build/7106ea033c5b5e85ea9d86ec4d3193ba5a0e2b50fdb5e10f550f971c5b3facee.png","H6A1QyrVRu8DkRqZy_pJN","1760440304","client","Yakihonne","31990:20986fb83e775d96d188ca5c9df10ce6d613e0eb7e5768a0f0b12b37cdac21b3:1700732875747","Trust is not an absolute quantity, it's always relative, it's a deeply personal and contextual phenomenon. In centralized systems, we’ve become accustomed to trust being imposed upon us by platforms and institutions. But this model misunderstands the nature of trust itself. As explored in \"[Trust Is a Scaling Solution](https://trustisascalingsolution.com/),\" trust is the fundamental mechanism that reduces friction in complex systems, allowing us to cooperate beyond our immediate relationships.\n\nHowever, traditional systems have applied this principle with a flaw: they have attempted to create one-size-fits-all metrics or impose their own model of trust to determine what is trustworthy. We are pleased to introduce Relatr, our approach to decentralized trust. It is built on a fundamentally different philosophy. Relatr is a decentralized service to compute trust in decentralized networks like Nostr, that embraces the relative, dynamic, and layered nature of trust, empowering individuals to define what trust means to them.\n\n## The Engine of Trust: A Transparent Algorithm\n\nRelatr computes trust from a specific source public key perspective which every instance should configure (if not configured it will default to nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc public key). At its core, it uses a simple yet meaningful algorithm to compute trust scores by combining multiple factors into a single, weighted score:\n\n`Trust Score = Σ(wᵢ × vᵢ) / Σ(wᵢ)`\n\nHere, `wᵢ` represents the weight you assign to a metric, and `vᵢ` is its normalized value, allowing for deep personalization. This formula is inspired by the [\"Qualitative Thumb System\" (QTS) outlined by arkinox](https://nostr.at/naddr1qvzqqqr4gupzp68dx7vvdlltl7sg2qdv8838ze3tl5tq76y0jnz966fdsana6dz6qq25gnzpveay5jns29z9xdrkdgehw5mvv46k6gd0088)\n\nThe system analyzes two primary types of signals:\n\n1. **Social Graph Proximity**: Reflecting the idea that trust diminishes across social connections, Relatr measures social distance between the source public key and a target public key, using Martti Malmi's `nostr-social-graph` library. Direct relationships between the source and the target public key carry the most weight, while trust decays exponentially as distance grows, capturing the essence of \"I trust you, so I can extend a degree of trust to those you trust.\"\n\n2. **Objetive Profile Validations**: Beyond social ties, Relatr incorporates objective, verifiable data. This includes metrics like NIP-05 domain validation, Lightning Network address, and other proofs. The framework is designed to be extensible, allowing new validation plugins to be added over time to assess factors like user activity or zap interactions.\n\n## Decentralized and Accessible: Relatr on ContextVM\n\nRelatr's architecture embodies its principles. It is not a centralized service but a protocol that anyone can run. This is made possible by **ContextVM**, a decentralized protocol that enables services to communicate over the Nostr network.\n\nRunning Relatr as a ContextVM service makes it incredibly accessible. Anyone can deploy their own trust engine from source or a Docker container in environments like Umbrel or Start9, often with a one-click install. This turns any internet-connected device into a personal trust server without complex networking or hosting costs.\n\nEach Relatr instance is identified by the public key of its ContextVM server. The **[relatr.xyz](https://relatr.xyz)** website demonstrates this. While it defaults to a public server we are running, it allows any user to paste in the public key of another Relatr instance. Whether it’s their own, a friend’s, or one run by a community they trust. This guarantees no vendor lock-in; you are always free to choose your provider.\n\n## Seamless Integration: Empowering Developers with CtxCn\n\nThe benefits of ContextVM extend to developers. Integrating Relatr into clients is remarkably simple, thanks to a tool called **CtxCn** ([We introduced it last week](https://nostr.at/naddr1qvzqqqr4gupzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqq25set9ddxy2s33wq68y4fkx9hxwcn4geeyszanq8u)). It’s a command-line utility that generates a fully-typed Relatr client directly into an application's codebase. Simple as running a single command.\n\n`npx @contextvm/ctxcn add `\n\nInstead of wrestling with an opaque library, developers get clean, readable source code they can own and adapt, and it's easy to maintain. This empowers anyone to easily integrate Relatr, allowing users to configure their own trust server and plug a powerful, personalized reputation system directly into their user experience.\n\n## From Centralized Authority to Individual Sovereignty\n\nRelatr represents a fundamental departure from the black-box algorithms of traditional platforms. Where centralized systems impose universal standards, Relatr delivers transparency and control. Trust carries costs and risks, making it a valuable and vulnerable resource. The principle of \"don't trust, verify\" is key, but realizing that verification itself is relative to the observer's point of view. Relatr enables this by allowing you to fine-tune your own criteria, creating a resilient ecosystem resistant to censorship.\n\nThe open-source algorithm and the ability to run your own instance mean you can always understand and audit how scores are computed, giving you true sovereignty over your trust decisions.\n\n## Getting Started with Relatr\n\nRelatr is designed to be lightweight and should run on almost any device. The easiest way to get started is with the official Docker image. For detailed instructions, follow the readme in the [repository](https://github.com/contextvm/relatr).\n\n## Conclusion\n\nRelatr is more than a technical tool; it’s a philosophical statement. It argues that in a decentralized world, trust cannot be outsourced. It must be cultivated, calculated, and claimed as our own.\n\nIts existence is also part of a broader conversation within the Nostr ecosystem, inspired by projects like [Vertex](https://vertexlab.io/), which first introduced advanced trust computation concepts. It's a testament to the idea that there is no single right way to compute trust. The more models we have to explore, the healthier the ecosystem becomes. By placing powerful, transparent tools in the hands of individuals and developers, Relatr paves the way for a more a sovereign digital future where power is distributed and systems serve human agency.\n\n## Get Involved\n\nExplore this and get involved with the Relatr project.\n\n- **Website**: [https://relatr.xyz](https://relatr.xyz)\n- **GitHub Repository**: [https://github.com/contextvm/relatr](https://github.com/contextvm/relatr)\n",1761497287,"7ca6570bebc83140365dec05ce343b77eb5c7d74b8c4f74e2c9a97de123012d5","3ab00a6212041a5c22e985322e6ac3c8b184c12b9c988da4cd16f00c4b3c6a6511b9ad73ce78ff3af3b7def14e75402c60f2cc31e27b8b47341ff8ff1c497ceb",[148,149,150,151,152,153,154,155,156,157,158],[140,141,142],[65,164],[81,163],[67,162],[79,161],[77,160],[61,76],[61,159],[61,12],[61,75],[129,133,131,132],"trust","A decentralized trust metric service for Nostr that computes trust scores based in the perspective of a source pubkey using social graph distances and customizable validations.","Relatr — Relate, Relative, Relation: Our shot on Decentralized Trust.","https://image.nostr.build/30d7fdef1b3d3b83d9e33f47b7d15388deeb47428041f0656612d1450cdb1216.jpg","yItckCkpmTq-owE5AgYtq","1761497287","Trust is not an absolute quantity. It is deeply personal, contextual, and always relative. In centralized systems, we have become accustomed to trust being imposed upon us by platforms and institutions, a \"blue check\" or a hidden algorithm deciding who is trustworthy for everyone.\n\nBut this model misunderstands the nature of trust, especially in decentralized systems like Nostr. Trust is a scaling solution, the fundamental mechanism that reduces friction in complex systems, allowing us to cooperate beyond our immediate relationships.\n\nWe built Relatr to reclaim this mechanism. Relatr is a service that anyone can run, computing trust scores based on the perspective of a specific source. It embraces the relative, dynamic, and layered nature of trust, empowering individuals and communities to define what trust means to them.\n\nToday, we are releasing Relatr v0.1, with significant architectural improvements powered by the new Nostr Social Duck library. This update solves critical scaling challenges and makes running your own trust engine more accessible than ever.\n\n## A Transparent Algorithm\n\nAt its core, Relatr computes trust from a specific source public key perspective. Because decentralized networks like Nostr lack a global state, there is no \"global reputation.\" Instead, we rely on social graph proximity together with objective validations. While Relatr includes some default validations like NIP-05 domain checks, relay lists, and Lightning address verification, among others, the system is fundamentally flexible. You can customize it with any validation rule, enabling highly specific trust models tailored to your needs.\n\nIf you are interested in learning more about how Relatr computes trust scores, the about page of the Relatr website is a good way to start. [https://www.relatr.xyz/about](https://www.relatr.xyz/about)\n\nThis flexibility enables Relatr to serve diverse use cases. Individuals might prioritize social connections, while businesses or communities can configure their instance to validate specific badges, memberships, or other criteria, effectively creating their own Web of Trust metrics based on their own standards. At its core, Relatr embraces the relativity of trust and context. We are still working to make custom validations more accessible and intuitive, but the framework is already extensible enough for anyone to create custom validation rules.\n\n## The Challenge\n\nIn our initial release, we used a combination of the `nostr-social-graph` library for social graph distance calculations and SQLite for profile metadata. While this worked well for looking up the score of single pubkeys, it struggled with search. Search is a much more nuanced operation than calculating a score for a given pubkey.\n\nConsider a search for \"Alex\". This query could potentially return thousands of matches. To find the profiles relevant to *you*, we must filter and rank these thousands of candidates by their trust score, and then return the top results.\n\nIn our previous architecture, the \"phone book\" (names) and the \"social map\" (distances and validations) lived in separate systems. We had to fetch large batches of potential matches, calculate trust scores for each individually, and then sort them. This approach was inefficient and prone to making servers hang under load. Returning all potential matches is very expensive and inefficient, so we opted to add a multiplier to the search limit to keep computation under control. However, this limit approach was quite arbitrary: too few possible matches and we missed relevant people; too many or all matches, and performance and response times became unpredictable.\n\n## The Solution: Nostr Social Duck\n\nWe needed a way to improve this, to query metadata and social graph distance simultaneously while keeping resource requirements low. In other words, we had to shift the concept of the query from returning all matches from \"Alex\", to returning the most relevant \"Alex\". After some research, we found an answer that fits our needs.\n\nEnter DuckDB.\n\nDuckDB is an embedded, in-process SQL database designed for high-performance analytics. Crucially, it handles memory management gracefully. When a query requires more memory than is available, DuckDB spills to disk rather than crashing. This allows us to perform complex graph analysis on modest hardware.\n\nWe built [Nostr Social Duck](https://github.com/gzuuus/nostr-social-duck) (NSD), a library that leverages DuckDB to perform graph operations over Nostr data. If you are interested in learning more about NSD, you can visit its repository, and read this [introductory note](https://nostr.eu/nostr:nevent1qvzqqqqqqypzqs9eep0ll6hurjkl3sc2fewgses07mjfwxsdcu3at2m8fd0xrdz3qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqypmz4lcyj5k9he9yl5gan0erwqjdxrskymvw6qawhqj9l0rwlr6cspasp6h)\n\nWith this in place, we could move both the social graph and profile metadata into a unified DuckDB instance, transforming the search problem. Now, in a single SQL query we can:\n\nFind profiles matching \"Alex\" across metadata fields\nCalculate their social distance from the source key\nApply validation criteria\nReturn ranked results\n\nThis unified approach allows us to pre-rank and return the most relevant results from the entire dataset in milliseconds, not just a random subset.\n\n## Performance and Accessibility\n\nOne of our core goals is to ensure Relatr can be self-hosted by anyone, not just those with powerful servers.\n\nThe results of this refactor have been excellent. Our public Relatr instance currently runs on a $4 VPS. Even on this constrained hardware, it can handle hundreds of requests per minute with graceful performance degradation. We conducted some naive benchmarking and stress testing, achieving ~30ms response times for searches under normal load and ~300ms response times during peak stress periods. In the other hand the pubkey lookup method demonstrated response times from ~2ms under normal load, to ~30ms under heavy load.\n\nThis efficiency makes the results feel instant and can satisfy various application use cases, such as tagging and quick search, among others. Additionally, you can deploy your own trust engine on almost any hardware, including a Raspberry Pi, an Umbrel node, a low-cost cloud server, or even a phone, without significant expense and with reasonable responsiveness. The disk requirements are also quite low; currently, our public instance, which contains more than 300k relationships, along with profile metadata and validations, uses just ~200MB.\n\n## Ecosystem Adoption and Use Cases\n\nWe cannot conclude this article without mentioning the community's response to Relatr, which is already being integrated into several projects:\n\n**Nostrudel:** Uses Relatr for username search and tagging\n**Profilestr:** Aggregates Relatr scores with other metrics like their own, and Vertex for unified reputation views\n**Zap-Work:** Leverages Relatr to compute trust scores for user interactions in their job marketplace\n**AQSTR:** Uses Relatr for engagement and reward platform scoring\n\nThanks to everyone integrating and using Relatr 💛\nThis adoption validates our belief that the ecosystem needs diverse, interoperable trust models. The potential use cases for Web of Trust on Nostr are extensive, and Relatr's self-hostable design makes it ideal for integration into clients for personalized scoring, tagging, search, and recommendations, among others.\n\nWe're also participating in the #WoTathon organized by Nosfabrica, which is advancing important discussions around Web of Trust implementations. This initiative inspires us to integrate NIP-85 trusted assertions into Relatr, providing another interface for developers and users to leverage Relatr's capabilities.\n\n## Seamless Integration\n\nWe want to make it trivial for developers to add \"Web of Trust\" features to their apps.\n\nWith CtxCn, integrating Relatr is as simple as running one command in your project:\n\nnpx @contextvm/ctxcn add\n\nThis generates a fully-typed, readable TypeScript client directly in your codebase. You own the code, it's easy to maintain, and it connects immediately to the specified Relatr instance.\n\nBut you're not limited to TypeScript. Relatr uses the ContextVM protocol, so in practice, if you can call a DVM, you can call any Relatr instance. The interaction follows a simple Nostr event pattern that works with any programming language.\n\nTo call Relatr tools like `search_profiles` or `calculate_trust_score`, you send a Nostr event of kind 25910 containing a request. The event must tag the Relatr instance's pubkey and include your call in the content field.\n\n**Example request structure:**\n\n{\n\"kind\": 25910,\n\"tags\": [[\"p\", \"\"]],\n\"content\": {\n\"jsonrpc\": \"2.0\",\n\"id\": \"your-request-id\",\n\"method\": \"tools/call\",\n\"params\": {\n\"name\": \"search_profiles\",\n\"arguments\": {\"query\": \"jack\"}\n}\n}\n}\n\nNote: The content field should be stringified.\n\n**Listening for responses:**\nResponses come as Nostr events from the Relatr instance, tagged with your pubkey. The response contains the result with trust-scored profiles and metrics.\n\n### Quick Testing with `nak` CLI\n\nFor quick testing, you can use the `nak` CLI tool:\n\n**Send a search request:**\n\nnak event -k 25910 -c '{\"jsonrpc\":\"2.0\",\"id\":\"test\",\"method\":\"tools/call\",\"params\":{\"name\":\"search_profiles\",\"arguments\":{\"query\":\"jack\"}}}' -t \"p=750682303c9f0ddad75941b49edc9d46e3ed306b9ee3335338a21a3e404c5fa3\" wss://relay.contextvm.org\n\n**Listen for responses:**\n\nnak req --stream -s \"$(date +%s)\" -k 25910 -p wss://relay.contextvm.org\n\n**Discover available tools:**\n\nnak event -k 25910 -c '{\"jsonrpc\":\"2.0\",\"id\":\"any-id\",\"method\":\"tools/list\"}' -t \"p=750682303c9f0ddad75941b49edc9d46e3ed306b9ee3335338a21a3e404c5fa3\" wss://relay.contextvm.org\n\nThis returns complete tool definitions with input/output schemas, so you know exactly what methods are available, which parameters to use, and what to expect in responses.\n\nNote that the pubkey used in this examples are the public key of the public Relatr instance that we are running which is accessible to anyone and can also be used through [https://relatr.xyz](https://relatr.xyz)\n\nIf you want to learn more about the underlying ContextVM protocol, you can visit the [ContextVM documentation](https://docs.contextvm.org).\n\n## Run Your Own Instance\n\nRelatr is designed to be self-hostable and accessible. You can deploy it in multiple ways, we provide Docker images for easy deployment, you can have a Relatr instance running in minutes. For custom configurations or development, you can build Relatr from source. The project uses TypeScript and Bun, and the repository contains comprehensive documentation on configuration options, custom validation rules, and more.\n\n## Conclusion\n\nRelatr represents more than just a tool for us, it is a statement that in a decentralized world, trust cannot be outsourced. It must be claimed as our own.\n\nThe evolution from our initial architecture to the current Nostr Social Duck-powered implementation marks significant progress in making trust metrics accessible, efficient, and scalable. With v0.1, we've established a foundation that empowers individuals, communities, and businesses to define their own trust models.\n\nLooking ahead, we're focusing on several key enhancements. We're working to make validation customization more intuitive for non-developers, moving beyond the current approach that requires modifying Relatr's source code. Performance optimization remains a priority to ensure efficient operations across the board. We're actively incorporating community feedback and exploring the integration of NIP-85 trusted assertions to provide additional interfaces for developers. Additionally, we will expand our documentation to facilitate easier integration of Relatr into any Nostr application.\n\nWe're excited to see how the community adopts and builds upon these foundations and invite you to run your own instance, integrate Relatr into your projects, or contribute to the codebase.\n\n**Website:** [relatr.xyz](https://relatr.xyz)\n**GitHub:** [github.com/contextvm/relatr](https://github.com/contextvm/relatr)\n**Nostr Social Duck:** [github.com/gzuuus/nostr-social-duck](https://github.com/gzuuus/nostr-social-duck)",1764943791,"2bbfb8cb0ce158f385c62c50ee6fa3cefe4c2fa18e87055b1168985931d7d460","cb23362834959c2ee3ebd7fa4901d87b8cbf61f7abef8843aeeeb2ac9a45bcee431c5db78a54404030e1017317c2bf74e239bced9dcbd74651b8467017b78e48",[170,171,172,173,174,175,176,177,178,179,180,181,182],[81,193],[79,192],[77,191],[67,190],[65,189],[61,76],[61,188],[61,187],[61,159],[61,12],[61,74],[184,185,186,131,183],[129,183,131],"40b9c85fffeafc1cadf8c30a4e5c88660ff6e4971a0dc723d5ab674b5e61b451","e","762aff04952c5be4a4fd11d9bf237024d30e1626d8ed03aeb8245fbc6ef8f588","wss://nos.lol/","wotathon","wot","1764943791","https://image.nostr.build/c15be8c517785968002188b9dfbb6a4a8ba0509d3de569bd7d0f78f0b13c1b53.jpg","Today, we are releasing Relatr v0.1, with significant architectural improvements powered by the new Nostr Social Duck library. This update solves critical scaling challenges and makes running your own trust engine more accessible than ever.","Relatr v0.1: Scaling Decentralized Trust","relatr-nsd","# **The ContextVM World** 🌍 **— #1**\n\n*GM people, and welcome to the first ever issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!*\n\n*In our updates we will bring you the latest information about CVM and its ecosystem, with a particular focus on projects, services, and companies leveraging it for their infrastructure.*\n\n*We will also present a curated list of articles, blog posts, and notes talking about CVM and how it is changing the way we interact with MCP servers.*\n\n*Finally, we will bring the latest news from the MCP ecosystem, including specification changes and new protocol additions. CVM is built on MCP, which means that we care about providing you up-to-date information from its thriving ecosystem.*\n\n*Let's start!*\n\n---\n\n## **News from ContextVM** 📰\n\n*A list of updates, releases and new cool features.*\n\n- The new [v0.2.x](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#020) family release of the ContextVM SDK has been [announced](https://jumble.social/notes/nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyt8wumn8ghj7am0w3ezuun9d3shgu3w0puh5tcqyrpfja5kcfxgzws0mezugr5zzpz53ps54m5gj9tvh8e4zs6rpkeww5jfu5a) on Wednesday 21st, focusing on reliability, code quality, and architectural maturity. This release transforms ContextVM from a functional prototype into a hardened foundation ready for long-running servers. While this release lays the groundwork for future enhancements, it provides backward compatibility with the previous release to allow for a smooth transition. We recommend upgrading any production environment to v0.2.x to benefit from the reliability improvements on relay handling and memory management.\n- We [announced](https://primal.net/e/nevent1qqstsfzpmt7m2te8a5xfzdy6s93utgtejmujqcvxcrnffeljkhtm9fc7320y5) the release of [ContextVM Interface](https://github.com/contextvm/cvmi) (CVMI), a CLI tool that aims to simplify development on ContextVM. The tool comes with a complete set of [agent skills](https://agentskills.io/home) that cover the entire stack, from protocol fundamentals to production deployment. CVMI will soon become the go-to toolkit for everything related to CVM development, superseding older tools and integrating new features.\n- Today we consolidated the old gateway-cli and proxy-cli tools into CVMI, simplifying the installation and configuration process. Two commands were introduced, `serve` to allow anyone to serve any MCP server over Nostr, even remote HTTP ones, and `use` to leverage remote servers as if they were local. Both new commands work out of the box with ephemeral keys and default relays, with the possibility to customize the setup.\n- We [announced](https://jumble.social/notes/nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qghwaehxw309aex2mrp0yh8qunfd4skctnwv46z7qpqymaslej2jq4ahkpgljm24c8a2nce7rekf9tddlf2mhkgkljav8rqf66s7l) the release family [v0.3.x](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#030), following improvements to the gateway module. This component now allows users to expose remote HTTP MCP servers over Nostr.\n\n---\n\n## **News from the ContextVM Ecosystem** 🗞️\n\n*Find all the projects leveraging ContextVM on [ContextVM/awesome](https://github.com/ContextVM/awesome).*\n\n- Following our recent introduction of [Trusted Assertions](https://jumble.social/notes/nevent1qvzqqqqqqypzq3svyhng9ld8sv44950j957j9vchdktj7cxumsep9mvvjthc2pjuqy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uqzpzvx2l22ycvmuzmvtq5ntjmsw0hxfxj4e8zkrj43fgydte6a3r0a8p09qu) on Relatr, the specification has been officially merged in the Nostr protocol under [NIP-85](https://github.com/nostr-protocol/nips/blob/master/85.md). This NIP allows users to offload Web-Of-Trust calculations, which require a huge amount of events and computational power, to declared trusted service providers, and for these providers to publish signed \"Trusted Assertion\" events for the client consumption. We published a [blog](https://contextvm.org/blog/trusted-assertions-in-relatr) post talking about the details of this integration in Relatr, and how request/response pattern and TAs are complementary.\n- [Relatr v0.1.16](https://github.com/ContextVM/relatr/releases/tag/v0.1.16): Implemented relay capping and updated rate limit token defaults for better burst capacity. Upgraded to the latest version of the ContextVM/SDK.\n- [wotrlay v0.2.5](https://github.com/ContextVM/wotrlay/releases/tag/v0.2.5): The web-of-trust Nostr relay implementation has been updated, bringing various improvements such as better error handling and enhanced observability.\n- In a recent conversation with Pete Winn ( nostr:npub1jss47s4fvv6usl7tn6yp5zamv2u60923ncgfea0e6thkza5p7c3q0afmzy ), the creator of nanalytics, a plethora of experiments over CVM, and games over Nostr like [Word5](https://word5.otherstuff.ai/), we learned that his CVM servers are currently receiving thousands of requests. Here, CVM acts as the imperceptible backbone of these applications. Good technology is invisible. On our side, Relatr is also receiving a high load of requests each day. This kind of load allows us to stress-test CVM and reveal bugs. All the gathered information is currently being used as the foundation for release family 0.2.x, which makes long-running servers with loads of requests stable and performant. CVM is still young and is maturing, becoming more stable and resilient in each iteration.\n- [Earthly.city](https://github.com/zeSchlausKwab/earthly) is a project leveraging CVM for its integration with geographical data. [The server is public](https://contextvm.org/s/ceadb7d5b739189fb3ecb7023a0c3f55d8995404d7750f5068865decf8b304cc) and you can use it as well. \n- More and more projects are currently joining the CVM world. If you are building something on top of CVM, please just let us know! We will be happy to assist, and include you in this newsletter.\n\n---\n\n## What’s Next for ContextVM? ⏭️\n\n*Let’s take a look at the features currently being implemented!*\n\n- [CEP-8](https://github.com/ContextVM/contextvm-docs/issues/8): This enhancement proposal provides a standardized pricing mechanism and payment flow for MCP capabilities over CVM. This would allow servers to advertise pricing for their services, and enable clients to discover and pay for MCP capabilities.\n- [CEP-15](https://github.com/ContextVM/contextvm-docs/issues/15): This enhancement proposal implements a standard for defining and discovering common tool schema. This aims to enable interoperability between multiple servers, creating a marketplace of service providers using the same tool interface.\n\n---\n\n## **Who is Talking about ContextVM?** 📢\n\n*A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.*\n\n- [Say WOT — Ep. 2](https://fountain.fm/episode/emFUU2tGnuiGRRu0Q27W): Avi Burra from Plebchain Radio sits down with Gzuuus to discuss CVM and the Web-Of-Trust tech stack.\n- What’s next for [Relatr](https://jumble.social/notes/nevent1qvzqqqqqqypzqagxsgcre8cdmtt4jsd5nmwf63hra5cxh8hrxdfn3gs68eqycharqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyfhwumn8ghj7mmxve3ksctfdch8qatz9uqzpweq8w0cg643dtxsgetv4fpvp7hqx8jg300c4fpf55plxqan36e4z4p258)?\n- An interesting [note](https://jumble.social/notes/1939f1ca9ec3e088b6964915cb573b8036e801e9e9cc39b4413b81bb37350fdb) about [earthly.city](https://github.com/zeSchlausKwab/earthly), a project leveraging CVM.\n- [Trusted Assertion in Relatr](https://contextvm.org/blog/trusted-assertions-in-relatr)\n- [SEC-05: YOLO Report](https://jumble.social/notes/naddr1qvzqqqr4gupzpq7enxs5scju854msxd0xpjvpa4p94763rmgktrfyg0n5arpw8geqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qqthxetr95cr2ttedakx7ttddajx2ttjv4cx7un52ycmyz)\n\n---\n\n## **News from the MCP world** 🤖\n\n*What is going on in the MCP world?*\n\n- MCP maintainers [announced](https://blog.modelcontextprotocol.io/posts/2026-01-26-mcp-apps/) the release of MCP Apps, an official MCP Extension that allows any tool to return interactive UI components, such as dashboards, forms, and workflows, all rendered directly in the conversation. As of today, MCP Apps are already available in Goose, Claude, VS Code, and ChatGPT.\n- A new functionality called “[Tool search tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/tool-search-tool)” is available in beta through the Claude APIs. This tool allows servers to reduce token usage by enabling dynamic tool discovery and the possibility to load them on-demand, thus reducing context window consumption and improving tool selection.\n- In a recent [blog post](https://blog.modelcontextprotocol.io/posts/2025-12-19-mcp-transport-future/) about the future of MCP transports, [Kurtis Van Gent](https://github.com/kurtisvg) and [Shaun Smith](https://github.com/evalstate) discussed the advantages of making the MCP protocol stateless. Interestingly enough, CVM added a stateless mode a couple of months ago, allowing efficient communication between clients and servers. Now, the same concepts are coming to the official MCP specifications.\n\n---\n\n*Find out more about ContextVM:*\n\n- *Check out our [website](https://contextvm.org/) for documentation, blog posts, and more.*\n- *Join our [Signal](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR) group*\n- *Follow ContextVM on Nostr, nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm *\n- *Follow Relatr on Nostr, nostr:npub1w5rgyvpunuxa446egx6fahyagm376vrtnm3nx5ec5gdruszvt73spqeu4t *\n- *Check out our GitHub [repositories](https://github.com/contextvm) and leave us a ⭐*",1770152843,"026223c588bd74d12ab1da1784f070b59c9adcaa0d2ba01b3d835453c73e2a95","f5ea0331b7c99461a6a940488a5593b3cd7aba2bcf70d456d55731e4aac1eb0ff1e38ad351fdf8effd148c7b9b303a2f1110660a724d527ad2b920b68898a980",[199,200,201,202,203,204,205,206,207,208,209,210,211],[140,141,142],[65,219],[81,218],[67,217],[79,216],[77,215],[61,76],[61,75],[61,214],[61,12],[129,213,131,132],[129,40,131,132],[129,212,131,132],"750682303c9f0ddad75941b49edc9d46e3ed306b9ee3335338a21a3e404c5fa3","94215f42a96335c87fcb9e881a0bbb62b9a795519e109cf5f9d2ef617681f622","dvm","GM people, and welcome to the first ever issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!","The ContextVM World 🌍 — #1","https://blossom.band/9ffc2f74143d9208d03f87f5ec509d4b231f50d1f4a6112e1494f45d8173746a.jpg","the-contextvm-world-1","1770138385","*GM people, and welcome to the second issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!*\n\n*In today's update we are going to discuss payments on CVM, enabled by CEP-8 specifications. The latest releases of CVM SDK and CVMI have been updated to support this huge milestone.*\n\n*We will also cover the latest features currently being implemented. In particular, we will take a look at CEP-17, which deals with relay lists, and CEP-19, which aims to improve privacy for encrypted communications.*\n\n*We will also present a curated list of articles, blog posts, and notes talking about CVM and how it is changing the way we interact with MCP servers.*\n\n*Finally, we will bring the latest news from the MCP ecosystem, including specification changes and new protocol additions. CVM is built on MCP, which means that we care about providing you up-to-date information from its thriving ecosystem.*\n\n*Let's start!*\n\n## **News from ContextVM** 📰\n*A list of updates, releases and new cool features.*\n\n**ContextVM has received support from [OpenSats](https://primal.net/opensats)**: OpenSats [announced](https://opensats.org/blog/fifteenth-wave-of-nostr-grants) its fifteenth wave of grants from the Nostr Fund. ContextVM is one of the new projects to receive the grant, which will support core protocol development, SDK expansion, and improvements to the reliability of shared infrastructure.\nIt will also allow the team to work on new SDK implementations, create and manage one-click deployment packages, provide comprehensive documentation and tutorials, and integrate CVM with open-source developer tools.\n\n**Payments are finally live on CVM**: With the recent merging of [CEP-8](https://docs.contextvm.org/spec/ceps/cep-8/) specification, anyone running a MCP server can finally monetize its capabilities, allowing for a decentralized and permissionless marketplace of services and tools. Most importantly, it does so without imposing a single (or a set of) payment method(s), but by standardizing the way users ask for payments.\n\nCEP-8 introduces a language called *Payment Method Identifier* (PMI), based on the homonymous [W3C standard](https://www.w3.org/TR/payment-method-id/), that allows to define the specific payment method to be used during the interaction. In other words, PMI is the type-tag for the payment request payload, analogous to content-type in HTTP. For example, a BOLT11 lightning payment will be identified by the string `bitcoin-lightning-bolt11`. Notably, [CEP-21](https://docs.contextvm.org/spec/ceps/informational/cep-21/) has been added to\nprovide recommended naming conventions for new PMIs.\n\n**CVMI latest release**: [v1.10.0](https://github.com/ContextVM/cvmi/blob/main/CHANGELOG.md#0110) for CVMI, the cli tool for CVM, has been recently released. The latest version introduces comprehensive documentation for implementing payments through CEP-8. It also adds support for environment variables to spawned MCP servers and normalizes quoted command strings to serve any MCP server.\n\n**CVM SDK release family 0.4.x**: Starting from v0.4.0, the ContextVM SDK added support for payments through CEP-8. Other patch versions has been released to fix minor issues or include small features, such as payment export and logging and preventing zombie publishing loops. Notably, [v0.4.5](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#045) added support for payments through [NIP-57 Lightning Zaps](https://github.com/nostr-protocol/nips/blob/master/57.md). This is the third payment processor to be supported in CVM, following NWC and [LNBits](https://github.com/ContextVM/sdk/pull/25) implementations.\n\nThe release [v0.4.6](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#046), adds notifications for payment verification based on [NIP-47 NWC](https://github.com/nostr-protocol/nips/blob/master/47.md).\nSince this feature is not supported by all NWC providers, the payment processor will determine compatibility and only enable notifications if the provider supports it.\nBefore publishing v0.4.6, we have released a series of patches which add deduplication capabilities for multi-relay deployments, making the transports more efficient and increasing performances when connected to multiple relays.\n\n## **News from the ContextVM Ecosystem** 🗞️\n*Find all the projects leveraging ContextVM on [ContextVM/awesome](https://github.com/ContextVM/awesome).*\n\nAgents are starting to realize ContextVM exists and are looking for ways to integrate it into their operations. [Clawstr](https://clawstr.com) and [The Colony](https://thecolony.cc/) are two examples of platforms where agents are discussing about the benefits of ContextVM.\n\n## **What’s Next for ContextVM?** ⏭️\n*Let’s take a look at the features currently being implemented!*\n\n[CEP-15](https://github.com/ContextVM/contextvm-docs/issues/15): This enhancement proposal implements a standard for defining and discovering common tool schema. This aims to enable interoperability between multiple servers, standardizing tool interfaces that clients can recognize and use consistently. It leverages MCP's `_meta` field, RFC 8785 for deterministic hashing, and\n[CEP-6 announcements](https://github.com/ContextVM/contextvm-docs/blob/master/src/content/docs/spec/ceps/cep-6.md) for discovery, creating a marketplace where users can choose between multiple providers implementing the same standard tool interface.\n\n[CEP-17](https://github.com/ContextVM/contextvm-docs/issues/17): This enhancement proposal defines a relay list mechanism based on [NIP-65](https://github.com/nostr-protocol/nips/blob/master/65.md) conventions. Servers can publish the list of relays they are connected to using kind `10002` events,\nallowing clients to discover the appropriate relays for establishing connections. This solves the current limitation where users must know both a server's public key and its relay URLs to connect.\n\n[CEP-19](https://github.com/ContextVM/contextvm-docs/issues/19): This enhancement proposal introduces an optional convention for CVM servers and clients to exchange encrypted messages using an ephemeral gift wrap kind. This CEP aims to improve privacy for encrypted communications by establishing a new kind `21059`, similar to kind `1059`, which will not be stored by a relay.\n\n## **Who is Talking about ContextVM?** 📢\n*A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.*\n\nOur [blog post](https://jumble.social/notes/nostr:naddr1qvzqqqr4gupzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uqpqmr9d4hkuctyv5kkcet8v4hxguchwt8dw) providing a simple and fun tutorial to illustrate how the CEP-8 payment flow works. Get your Nostr badge now!\n\nOur [blog post](https://jumble.social/notes/nostr:naddr1qvzqqqr4gupzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uqpwerfva5hgctv94kx2mt0deskgefdwd6xzmnywvldqt6c) on CEP-8 and *Digital Lemonade Stands*.\n\nA [note](https://jumble.social/notes/nostr:nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qqs2u23g4wlu63e6pchrfzswu0j5k0er5pc2dyepv8kyule7w763n2q9wzl4z) on our official Nostr profile highlighting the importance of CVM in an agent-mediated world.\n\nA [note](https://jumble.social/notes/nostr:nevent1qvzqqqqqqypzpuk62d950kl7qkq2gt0rkavv49q3n4z76w8ffchehcxp269nr324qythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qqsgdeg2a5maua7cnf425tcfg7lwur7qaqnphsxtc28x3pep20j7p6sg049vd) from MaximumSats\n(nostr:npub17td9xj68m0lqtq9y9h3mwkx2jsge630d8r55utumurq4dze3c42sdav95p), developer of the LNBits processor in the CVM SDK, discussin MCP-to-Nostr bridges.\n\n## **News from the MCP world** 🤖\n*What is going on in the MCP world?*\n\n[PR2127](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127)\npresents a draft specification, [SEP-2127](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127/files),\nthat proposes a standardize way to describe MCP servers, called Server Cards.\nThis would allow an MCP client to discover server capabilities using a `.well-known` endpoint, without the need to establish a full connection.\n\n**Note**: This proposal together with the [registry](https://modelcontextprotocol.io/registry/about) specification defines a series of HTTP endpoints attached to specific servers to allow discoverability of MCP servers. In ContextVM, we think this is an anti-pattern, increasing centralization and gatekeeping. We already solved discoverability in\n[CEP-6 (Public Server Announcements)](https://docs.contextvm.org/spec/ceps/cep-6/) where we standarized the usage of relays as decentralized repositories. Servers are free to announce their existence in any number of relays and curation is done directly by the relays. This way, incentives are always aligned without any central point of failure.\n\n[SEP-2133](https://modelcontextprotocol.io/community/seps/2133-extensions) has been officially formalized. This specification establishes a lightweight framework for extending MCP through optional, composable extensions. In particular, it provides guidance on how extensions should be proposed and adopted, and defines both a list of official extensions, developed and\nrecommended by MCP maintainers, and one of experimental ones, for simple discovery, prototyping and collaboration.\n\n[SEP-1730](https://modelcontextprotocol.io/community/seps/1730-sdks-tiering-system) has officially landed, providing a tier system for MCP SDKs. This allows to establish clear expectations for feature support, maintenance commitments, and quality standards. The specification defines a three-tier\nsystem, based on objective, measurable data. In particular:\n\nTier 1: Fully supported. The SDK implements the full protocol and is well supported;\nTier 2: Commitment to be fully supported. The SDK is actively working towrds full support;\nTier 3: Experimental. The SDK is in its early stage.\n\n*Find out more about ContextVM:*\n\n*Check out our [website](https://contextvm.org/) for documentation, blog posts, and more*\n*Join our [Signal](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR) group*\n*Follow ContextVM on Nostr, nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm*\n*Follow Relatr on Nostr, nostr:npub1w5rgyvpunuxa446egx6fahyagm376vrtnm3nx5ec5gdruszvt73spqeu4t*\n*Check out our GitHub [repositories](https://github.com/contextvm) and leave us a ⭐*",1771343488,"4459a42f69885a145415f4b1f8f16724d9331c882ddabf052558ada635c4389e","a94de0ca5872591f8eae3097bf08a9ff7d5772ce72969170a13732f90063654cc8fe8ce2471a495b35653b91e26b0b27d0b6ffaee17a53ed969d16e788b250bc",[225,226,227,228,229,230,231,232,233,234,235,236,237,238,239,240,241],[81,254],[79,253],[77,252],[67,251],[65,250],[61,12],[61,214],[61,75],[61,76],[61,249],[246,248,186],[246,247,186],[184,245,244,131,40],[129,40,131],[184,243,244,131,242],[129,242,131],[129,212,131],"f2da534b47dbfe0580a42de3b758ca94119d45ed38e94e2f9be0c1568b31c555","86e50aed37de77d89a6aaa2f0947beee0fc0e8261bc0cbc28e68872153e5e0ea","wss://search.nos.today/","ae2a28abbfcd473a0e2e348a0ee3e54b3f23a070a6932161ec4e7f3e77b519a8","a","30023:6b3780ef2972e73d370b84a3e51e7aa9ae34bf412938dcfbd9c5f63b221416c8:digital-lemonade-stands","30023:6b3780ef2972e73d370b84a3e51e7aa9ae34bf412938dcfbd9c5f63b221416c8:lemonade-legends","agents","1771343417","https://image.nostr.build/4ab9910c783112f2b6813e571a8a0ff8e90909e7de709f73df315ee2f029e030.jpg","GM people, and welcome to the second issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!\n\nIn today's update we are going to discuss payments on CVM, enabled by CEP-8 specifications. The latest releases of CVM SDK and CVMI have been updated to support this huge milestone.","The ContextVM World 🌍 — #2","cvm-world-2","*GM people, and welcome to the third issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!*\n\n*In today's update we cover ephemeral gift wraps, which have been recently merged into the protocol with CEP-19. This feature introduces an optional convention for CVM servers and clients to exchange encrypted messages using an ephemeral gift wrap kind. We also present the latest release family, v0.6.x.*\n\n*We also discuss the latest news from the ecosystem, with a new MCP server to query Wolfram Alpha over Nostr, and the new feature being implemented in the CVM protocol, namely CEP-15, for common tools schema, and CEP-17, which provides a way for a server to publish its relay list.*\n\n*Moreover, we will present a curated list of articles, blog posts, and notes talking about CVM and how it is changing the way we interact with MCP servers.*\n\n*Finally, we will bring the latest news from the MCP ecosystem, including specification changes and new protocol additions. CVM is built on MCP, which means that we care about providing you up-to-date information from its thriving ecosystem.*\n\n*Let's start!*\n\n---\n\n## **News from ContextVM** 📰\n\n*A list of updates, releases and new cool features.*\n\n- **Ephemeral gift wraps are live on CVM**: We recently merged\n [CEP-19](https://github.com/ContextVM/contextvm-docs/blob/master/src/content/docs/spec/ceps/cep-19.md)\n proposal, which introduces an optional convention for CVM servers and clients to exchange encrypted\n messages using an ephemeral gift wrap kind. This is a major upgrade that provides more privacy\n in the communication between servers and clients, since it prevents relays to store the events.\n\n Consequently, we also open a [PR](https://github.com/nostr-protocol/nips/pull/2245) in the NIPs\n repository. The proposed modification aims to expand\n [NIP-59](https://github.com/nostr-protocol/nips/blob/master/59.md) to include the convention for\n ephemeral gift wraps.\n\n- **A NIP for CVM**: Recently, we opened another [PR](https://github.com/nostr-protocol/nips/pull/2246)\n on the NIP repository to formalize CVM as a minimal convention for transporting Model Context\n Protocol (MCP) JSON-RPC messages over Nostr. The proposal is waiting for feedback and reviews from\n other peers.\n\n- **A new major release family for the CVM SDK**: With the merging of CEP-19, we released a new major\n version family for the CVM SDK, v0.6.x.\n\n Notably, [v0.6.0](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#060) integrates support for ephemeral gift wraps, while maintaing compatibility with previous versions. We also released a patch version, [v0.6.1](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#061).\n\n Previously, we released [v0.5.0](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#050), which\n added a single `paymentPolicy` hook to make payment consent programmable.\n\n---\n\n## **News from the ContextVM Ecosystem** 🗞️\n\n*Find all the projects leveraging ContextVM on [ContextVM/awesome](https://github.com/ContextVM/awesome).*\n\n- Relatr (nostr:nevent1qqsxzqw884dxrjfdy3ntcjz63gzcfgtz7sll4uqmarat9ytwn2k8g8c9g5yfl) has been\nrunning for more than two weeks without missing a single beat. No crashes, no downtime. It just worked!\n\n- [Wolfram Alpha](https://primal.net/p/npub1w0lf8t44p4575d7g9ly44yalzv4msjqg0d27x8mmt97kt3vqg8ysr5ht7c)\nis now available as a decentralized MCP server through CVM. Ask math, science, weather, conversions\nand more. Connect to the server [here](https://contextvm.org/s/73fe93aeb50d69ea37c82fc95a93bf132bb848087b55e31f7b597d65c58041c9) to test it out!\n\n---\n\n## **What’s Next for ContextVM?** ⏭️\n\n*Let’s take a look at the features currently being implemented!*\n\n- [CEP-15](https://github.com/ContextVM/contextvm-docs/issues/15): This enhancement proposal implements a\nstandard for defining and discovering common tool schema. This aims to enable interoperability between\nmultiple servers, standardizing tool interfaces that clients can recognize and use consistently. It\nleverages MCP's `_meta` field, RFC 8785 for deterministic hashing, and\n[CEP-6 announcements](https://github.com/ContextVM/contextvm-docs/blob/master/src/content/docs/spec/ceps/cep-6.md)\nfor discovery, creating a marketplace where users can choose between multiple providers implementing the\nsame standard tool interface.\n\n- [CEP-17](https://github.com/ContextVM/contextvm-docs/issues/17): This enhancement proposal defines\na relay list mechanism based on [NIP-65](https://github.com/nostr-protocol/nips/blob/master/65.md)\nconventions. Servers can publish the list of relays they are connected to using kind `10002` events,\nallowing clients to discover the appropriate relays for establishing connections. This solves the\ncurrent limitation where users must know both a server's public key and its relay URLs to connect.\n\n---\n\n## **Who is Talking about ContextVM?** 📢\n\n*A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.*\n\n- Our [Hacker News post](https://news.ycombinator.com/item?id=47151294), presenting ContextVM to the\nbroader technical ecosystem. We are actively working to get more eyes on out project!\n\n- CVM has been mentioned on\n[Nostr Compass #11](https://primal.net/a/naddr1qvzqqqr4gupzqa6e2nmnzsgjfzdy520vdy4hywr06c9ue6crpr2zxyq749uu275qqqgr2epex33nqde3xyursdfsx3sngusdfz8)\n, a weekly newsletter covering everything going on in the Nostr ecosystem.\n\n- [Travis Knot](https://primal.net/p/nprofile1qqsyjd2kjy34yrvj08kgh84z5r7759d64k5ewhswltm38lffv9s9m9ssyrpny) wrote an [article](https://primal.net/a/naddr1qvzqqqr4gupzqjf426gjx5sdjfu7ezu752s0m6s4h2k6n967pma0wyla99skqhvkqq2hzcf5w3r8w3r5f9f4jkt9fqurg7r5wd2xgawud0t) describing CVM as a protocol for creating \"permissionless digital lemonade stands\". With\nCVM, you do not need permission to build!\n\n- Our NIP proposal was mentioned in [Nostr Biweekly Review (15-28 Feb 2026)](https://primal.net/a/naddr1qvzqqqr4gupzqavxnnavfdqnx0p29h8vxtstenmds0wy5n0etkm6fs7sjdmgrxv8qq2h2jz9ff5k7mektuenv369gaz9yamwd3xx5xlghkl).\n\n- CVM has been mentioned in the\n[Financial Freedom Report #110](https://primal.net/a/naddr1qvzqqqr4gupzpuvcn2tdwk4rs66vsu25xcnvhvmzcqey3v3qmjdw20tua7724ukpqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qq35v6twv9hxx6tpdsk5vun9v4jx7mfd2fjhqmmjwsknzvfs94u8wvmxvenq9g2l59) by the\n[Human Rights Foundation](https://primal.net/p/nprofile1qqs0rxy6jmt44guxkny8z4pkym9mxckqxfytygxuntjn6l80hj409sgy2hv7w) (HRF).\n\n---\n\n## **News from the MCP world** 🤖\n\n*What is going on in the MCP world?*\n\n- The *Skills-over-MCP* Interest Group is actively working to provide directions and guidelines\non the possibility to provide Skills to agents as MCP resources. Contributors are focusing on\nthe so-called skills-as-instructors, those that teach an agent how to use MCP tools correctly,\nwithout executing any code, with the aim to find a common ground to address distribution, portability,\nsecurity and fragmentation. It is possible to find more information in the\n[meeting notes](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/2248).\n\n---\n\n*Find out more about ContextVM:*\n\n- *Check out our [website](https://contextvm.org/) for documentation, blog posts, and more.*\n- *Join our [Signal](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR) group*\n- *Follow ContextVM on Nostr, nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm *\n- *Subscribe to our [Substack](https://contextvm.substack.com/). Help us spread the word!*\n- *Check out our GitHub [repositories](https://github.com/contextvm) and leave us a ⭐*",1772552850,"c818662f02719aec772837d83e5b63a725871a03ce5f81505a33af4671ad89d3","105ebdef17688ab4d3440af0b960a828d4602d31ed0fe77683b2a02038ff9ac30062812eda40a0934ed996efe7d60fb57c230fd59df5f021a13e54800214acfd",[260,261,262,263,264,265,266,267,268,269,270],[140,141,142],[65,278],[81,277],[67,276],[79,275],[77,274],[61,12],[61,273],[61,272],[61,271],[129,40,131,132],"ephemeral","nips","nip","In today's update we cover ephemeral gift wraps, which have been recently merged into the protocol with CEP-19. This feature introduces an optional convention for CVM servers and clients to exchange encrypted messages using an ephemeral gift wrap kind. We also present the latest release family, v0.6.x.\n\nWe also discuss the latest news from the ecosystem, with a new MCP server to query Wolfram Alpha over Nostr, and the new feature being implemented in the CVM protocol, namely CEP-15, for common tools schema, and CEP-17, which provides a way for a server to publish its relay list.","Ephemeral Is Better — The ContextVM World #3","https://image.nostr.build/9704fd70e8a3dfe2b53cbe727e63818012afeb032d7e30a89d05f96d7d691fdc.jpg","84wfjCtA3PqMen62Olv5t","1772552850","ContextVM is built on a simple idea: remote computation should be easy to publish and easy to use without depending on the usual stack of domains, hosted infrastructure, and OAuth-heavy integration.\n\nCVMI is becoming the command line for that world.\n\nWith the new `discover` and `call` commands, CVMI is no longer only a supporting tool around the ecosystem. It is becoming a direct way to explore the network, inspect remote servers, debug them from the terminal, and integrate ContextVM services into scripts, apps, and agent workflows.\n\n## Why this matters now\n\nThe CLI is having a comeback, and for good reason.\n\nA command line is one of the few interfaces that works equally well for users, and agents. It is explicit, scriptable, composable, and easy to debug. That makes it a natural fit for modern tooling, especially as more people build workflows around agents and automation.\n\nThis is also why interest in CLI-first patterns around MCP is growing. Instead of loading every possible tool definition up front, a CLI lets you discover what is available and inspect details only when needed. That can make workflows lighter, cheaper, and easier to compose. One recent example of this trend are blog posts like CLI vs MCP: , developments like MCPorter: , or even Google with gws: .\n\nContextVM fits this moment unusually well because it already removes many of the assumptions that make remote tooling harder than it needs to be. It does not depend on OAuth or involves more third parties than public Nostr relays. It is secure by default, permissionless, and based on key-driven identity and relay-based reachability.\n\n## Discover services directly from the network\n\n`cvmi discover` makes public ContextVM services easier to find.\n\nInstead of relying on docs, directories, or manual endpoint sharing, you can query relay announcements directly from the terminal:\n\n```bash\nnpx cvmi discover\n```\n\nThat is useful for anyone. Users and agents can browse what is available. Developers can verify that their servers are visible. Builders can inspect the public surface of the network without extra tooling.\n\nDiscovery becomes part of the protocol experience itself, not something bolted on from outside.\n\n## Call remote tools without extra ceremony\n\n`cvmi call` handles the next step: actually using a remote service.\n\nYou can inspect a server:\n\n```bash\nnpx cvmi call \n```\n\ninspect a specific tool:\n\n```bash\nnpx cvmi call --help\n```\n\nand invoke it directly:\n\n```bash\nnpx cvmi call key=value\n```\n\nThis is powerful because it serves several roles at once.\n\nFor developers, it is a practical debugging surface for remote servers. You can list exposed tools, inspect expected inputs, try requests manually, and read results without building a custom client first.\n\nFor agents and automations, it is a narrow and scriptable interface that fits naturally into shell workflows.\n\nFor users, it is a simple way to interact with a remote service from the terminal.\n\nAnd this is only part of what CVMI is becoming, it already exposes commands such as `serve`, `use`, and `add`, which means the same CLI can help you expose a server over Nostr, connect a remote service locally, or install ContextVM skills alongside discovery and direct tool calls.\n\n## Why CVMI fits ContextVM so well\n\nThese new commands matter because they make ContextVM operationally simple.\n\nContextVM already had the ingredients for a great open model of remote computation: no mandatory third parties involved, permissionless participation, relay-based discovery, and the ability to deploy from small setups instead of needing full hosted infrastructure from day one.\n\nCVMI now gives that model a better interface.\n\nYou can discover services on the network, inspect them from the shell, call them directly, and use the same workflow for debugging, personal use, scripting, or agent integration. That lowers the barrier for everyone who wants to publish tools, experiment with them, or build on top of them.\n\nIn practice, this means you can deploy from the garage and still be reachable worldwide. You can expose tools without building a full traditional and permissioned web stack. You can consume those tools in the way that suits you best: from a terminal, from edge scripts, or inside agent workflows.\n\nThat is what makes this release important. It is not just two more commands. It is ContextVM becoming easier to use in the real environments where people already work.\n\n## Start from here\n\nThe easiest way to see where CVMI is headed is to run it.\n\n```bash\nnpx cvmi\n```\n\nIf you plan to use it often, install it globally and keep it nearby as part of your everyday toolkit:\n\n```bash\nnpm install -g cvmi\ncvmi\n```\n\nFrom there, you can discover public services with `cvmi discover`, call remote tools with `cvmi call`, expose an already existing MCP server with `serve` (stdio or http) through Nostr, connect to remote server locally with `use`, or install ContextVM skills with `add`. In one CLI, CVMI is starting to cover the path for learning, debugging, publishing, and integration.\n\n## Further reading\n\n- CVMI repository: \n- Google Workspace CLI: \n- MCPorter: \n- Context Mode: \n- CLI vs MCP: \n",1773658050,"81d42d8f9d46b49ae87c89a2409dbc58948a5e46278b653577513179da782876","05ece10021bd7ab9f9017b6522e4086caeca72b8994d0dde532b1ec7050696fb00320586fd6944033d82eb1a37feef1d458f2cbf554671d0e19a312cf94e97a8",[284,285,286,287,288,289,290,291,292,293,294,295,296],[140,141,142],[65,303],[81,302],[67,301],[79,300],[77,299],[61,298],[61,12],[61,214],[61,75],[61,297],[61,249],[61,71],"contexvm","cli","CVMI is becoming the command line for that world.\n\nWith the new `discover` and `call` commands, CVMI is no longer only a supporting tool around the ecosystem. It is becoming a direct way to explore the network, inspect remote servers, debug them from the terminal, and integrate ContextVM services into scripts, apps, and agent workflows.","CVMI the swiss army knife CLI for ContextVM","https://image.nostr.build/77cfbb1a15627f247965e2a29af718b20762c1f9cdbb7d3c1ca6cb55354b8052.jpg","zlzyqFzEtZDfPr3pErWLI","1773658050","*GM people, and welcome to the third issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!*\n\n*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 to be discovered by clients.*\n\n*We also discuss the latest news from the ecosystem and the latest feature being implemented in the CVM protocol, CEP-15, for common tools schema.*\n\n*Moreover, we will present a curated list of articles, blog posts, and notes talking about CVM and how it is changing the way we interact with MCP servers.*\n\n*Finally, we will bring the latest news from the MCP ecosystem, including specification changes and new protocol additions. CVM is built on MCP, which means that we care about providing you up-to-date information from its thriving ecosystem.*\n\n*Let's start!*\n\n---\n\n## **News from ContextVM** 📰\n*A list of updates, releases and new cool features.*\n\n**Become discoverable**: We recently merged [CEP-17](https://docs.contextvm.org/spec/ceps/cep-17/), a proposal that defines a relay list mechanism based on [NIP-65](https://github.com/nostr-protocol/nips/blob/master/65.md) conventions. Servers can publish the list of relays they are connected to using kind `10002` events, allowing clients to discover the appropriate relays for establishing connections. This solves the current limitation where users must know both a server's public key and its relay URLs to connect.\n\n**A new release family for the CVM SDK**: We published a new release family of the CVM SDK, v0.7.x. Notably, we introduced support for CEP-17 in [v0.7.0](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#070), while successive patch releases introudeced new features, such as default discovery to bootstrap relays.\n\n**Making the CLI agent-friendly**: We rolled out several new improvements to our CLI tool, CVMI, bringing [v0.2.x](https://github.com/ContextVM/cvmi/blob/main/CHANGELOG.md#025) to life. This new release family introduces two new powerful commands:\n\n`call`: This command allows users to invoke CVM server directly from the command line, making it highly suited for agentic use. It also reduces token usage, thanks to simpler and cleaner responses;\n\n`discover`: This command allows users to easily find public CVM servers, by querying relay announcements.\n\n**A new CVM SDK in Rust**: Open-source contributor [K0sh](https://primal.net/p/nprofile1qqspvd9c0d0ul49xcnlj7t0pw3gvenjxlx47pvp2wxrkcktwc9jmlmg3r68pg#notes) is currently doing a complete rewrite of the [CVM SDK using Rust](https://github.com/k0sti/rust-contextvm-sdk), the most common programming language in the Bitcoin/Nostr ecosystems. The project is still highly experimental, thus we recommend testing it taking great care.\n\n---\n\n## **News from the ContextVM Ecosystem** 🗞️\n*Find all the projects leveraging ContextVM on [ContextVM/awesome](https://github.com/ContextVM/awesome).*\n\n[Schlaus Kwab](https://primal.net/p/nprofile1qqsr4fvpwfeu8vhefay3ss8qguhsf8g0zqqfug77vvqxze4u4xekagcs48nlt) integrated an AI agent chat into [earthly.city](https://earthly.city/), a Nostr-native collaborative mapping application that leverages CVM. Check this [note](https://primal.net/e/nevent1qqs0fwy8fuwduvcf0u8m2duj62jq8tys3mrsrnxuh5uydwp2ysamflqr47max) to view how it works!\n\n---\n\n## **What’s Next for ContextVM?** ⏭️\n*Let’s take a look at the features currently being implemented!*\n\n[CEP-15](https://github.com/ContextVM/contextvm-docs/issues/15): This enhancement proposal implements a\nstandard for defining and discovering common tool schema. This aims to enable interoperability between\nmultiple servers, standardizing tool interfaces that clients can recognize and use consistently. It\nleverages MCP's `_meta` field, RFC 8785 for deterministic hashing, and\n[CEP-6 announcements](https://github.com/ContextVM/contextvm-docs/blob/master/src/content/docs/spec/ceps/cep-6.md)\nfor discovery, creating a marketplace where users can choose between multiple providers implementing the\nsame standard tool interface.\n\n---\n\n## **Who is Talking about ContextVM?** 📢\n*A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.*\n\nOur latest [article](https://primal.net/a/naddr1qvzqqqr4gupzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qq40fk857t3geay2az6g3n9qu3nwpzhy46vfyqwxx83) on CVMI, the swiss army knife CLI for ContextVM.\n\nCVM has been mentioned on [Nostr Compass #12](https://primal.net/a/naddr1qvzqqqr4gupzqa6e2nmnzsgjfzdy520vdy4hywr06c9ue6crpr2zxyq749uu275qqyt8wumn8ghj7un9d3shjtnyd968gmewwp6kytcpzamhxue69uhhxetpwf3kstnwdaejuar0v3shjtcqzqmnvenp893nvctyv5ukxdenvcmqlvdyfa), a weekly newsletter covering everything going on in the Nostr ecosystem.\n\n---\n\n## **Intresting resources from the web** 🤖\n*A curated list of resources we found interesting.*\n\n[Google Workspace CLI](https://github.com/googleworkspace/cli): A one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more, with AI agent skills.\n\n[MCPorter](https://github.com/steipete/mcporter/blob/main/README.md): A TypeScript runtime, CLI, and code-generation toolkit for MCP.\n\n[Context Mode](https://mksg.lu/blog/context-mode): An MCP server that allows to reduce context usage by 98%.\n\n[CLI vs MCP](https://kanyilmaz.me/2026/02/23/cli-vs-mcp.html): An interesting blog post hightlightin the difference between CLIs and MCPs.\n\n[Code Mode](https://blog.cloudflare.com/code-mode-mcp/): An MCP server that provides a technique for reducing context window usage during agent tool use.\n\n[When the Interface Flattens Into a Prompt](https://youtu.be/ccT0jjd36I4): This video explores emerging paths in AI interface design, and why terminal-like experiences are appealing and can be dangerous.\n\n[The lethal trifecta for AI agents](https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/): This article explores the security risks of letting agents leverage tools that can lead attackers to steal you data.\n\n[MCP is Dead; Long Live MCP!](https://chrlschn.dev/blog/2026/03/mcp-is-dead-long-live-mcp/): A thoughtful blog post trying to shine some lights on the current hype on CLIs replacing MCPs.\n\n---\n\n*Find out more about ContextVM:*\n\n*Check out our [website](https://contextvm.org/) for documentation, blog posts, and more.*\n*Join our [Signal](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR) group*\n*Follow ContextVM on Nostr, nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm*\n*Subscribe to our [Substack](https://contextvm.substack.com/). Help us spread the word!*\n*Check out our GitHub [repositories](https://github.com/contextvm) and leave us a ⭐*",1773760301,"cc50554eafb3e23752e76481219dea7cc952b50ceb359cfd7a3e475a389cc695","995f43a6b79099b0044bf1a44f201b9ec22f205688ff3d69864ec87c3c41b9519df7d843e9fdc9b91da29a1260f24967373baa9d7b391bc87d50a902ae928fb0",[309,310,311,312,313,314,315,316,317,318,319],[81,324],[79,323],[77,322],[67,321],[65,320],[61,75],[61,12],[61,249],[61,71],[61,214],[129,40,131],"1773760301","https://mibo.eu.nostria.app/52499ea5b6913f6acf6e733bc8dc2e1ea122d26034f6a6956109f04662babf70.webp","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 to be discovered by clients. New CVMI capabilities, and other news from the ecosystem","Become Discoverable — The ContextVM World #4","cvm-world-4","GM people, and welcome to the fifth issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!*\n\n*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 realys.*\n\n*We also discuss the latest news from the ecosystem, with a growing number of MCP servers appearing. For example, two new MCP servers are now available through CVM, one based on am-i.exposed, another on OpenTimeStamp.*\n\n*Moreover, we will present a curated list of articles, blog posts, and notes talking about CVM and how it is changing the way we interact with MCP servers.*\n\n*Finally, we will bring the most interesting news from the internet regarding the MCP ecosystem, AI agents, and more!*\n\n*Let's start!*\n\n---\n\n## **News from ContextVM** 📰\n\n*A list of updates, releases and new cool features.*\n\n- **Summer of Bitcoin**: CVM has been invited to participate in the [Summer of Bitcon (SoB)](https://www.summerofbitcoin.org/) project, a global, online summer internship program focused on introducing university students to Bitcoin, Nostr, and open-source development. CVM will provide projects for students to work on during the summer, mentoring the new generation of open-source contributors and helping them bootstrapping their careers in the space. Do you have a CVM-based project you would like to propose for SoB? Feel free to [reach out to us](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR)!\n\n- **Search by `npub`**: We recently made a powerful update to our website to improve server discoverability and strengthen decentralization. Users can now lookup MCP server directly by `npub` and `nprofile` either in the search bar or directly by adding it to the URL. Bonus point, you can also search it through its [NIP-05](https://github.com/nostr-protocol/nips/blob/master/05.md) indentifier!\n\n- **Spam attack**: We recently suffered a spam attack on our relays. To fix the issue and reduce the attack surface for the future, we decided to [fork](https://github.com/ContextVM-org/strfry-cvm) the Strfry relay, which is the base of our infrastructure, to add additional write policies to restrict accepted event kinds to the subset used by our relay.\n\n---\n\n## **News from the ContextVM Ecosystem** 🗞️\n\n*Find all the projects leveraging ContextVM on [ContextVM/awesome](https://github.com/ContextVM/awesome).*\n\n- **Am I exposed?**: A new [MCP server](https://contextvm.org/s/e30b0e8de68d4dfa1d172c7ae37116d1dd96488694be135c11bbecf40ce55d18) is now available on Nostr leveraging the [am-i.exposed](https://am-i.exposed/) on-chain scanner capabilities to audit the privacy of your wallet information, ranging from transaction evaluation, UTXO hygiene, and full audit. We also did a quick [demo](https://jumble.social/notes/nostr:nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyd8wumn8ghj7un9d3shjtnwdaehgunrdpjkx6ewd4jj7qpq3mk46gdne4pkgt5ykwd7f3zrmxvk4nzv3wfh5dw2xf5snhuevsdschwfsk) on how to use it.\n\n- **Time-stamping Nostr events**: Another new [MCP server](https://www.contextvm.org/s/e1c1c32729cbd542c9b9ce7ee6e421c434e07835228020c4f57140782f02496a) is now available, allowing users to use [OpenTimeStamp](https://opentimestamps.org/) to time-stamp any Nostr event. The tool is very simple, providing one command to create an attestation and another to verify it. We also wrote a simple [note](https://jumble.social/notes/nostr:nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qqsfa832c5rsu2x8n0qf099jsjc2vtjuy2h8knmxteu778p3advxrjc6edys7) with the instruction to use this server through CVMI CLI.\n\n- **Nostr.watch + CEP-8**: [Nostr.watch](https://nostr.watch/), an important online tool that monitors relays health, recently integrated CEP-8 payments in their [CVM-enabled MCP server](https://cvm.nostr.watch/). Check Sandwich, nostr.watch creator, [note](https://jumble.social/notes/nostr:nevent1qvzqqqqqqypzpem34u9stj8ftlxldl4n2qz5f5hmrnxns3uga86fpwe7u28ga4n0qythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qqs95r698a753rtsqnly9v9g9hvf42m4qp32c4yesdxv3uxmvnzy7jsx0wx7j) to know more.\n\n- **Relatr + Ants**: Relatr was recently added into the [Advanced Nostr Text Search (Ants)](https://github.com/dergigi/ants) project by [Gigi](https://jumble.social/users/nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc) to improve its search capabilities.\n\n- **New Relatr domain**: Due to some issues with our registrar we no longer control the old relatr.xyz domain. You can now find it on [relatr.net](https://www.relatr.net/).\n---\n\n## **What’s Next for ContextVM?** ⏭️\n\n*Let’s take a look at the features currently being implemented!*\n\n- [CEP-15](https://github.com/ContextVM/contextvm-docs/issues/15): This enhancement proposal implements a\nstandard for defining and discovering common tool schema. This aims to enable interoperability between\nmultiple servers, standardizing tool interfaces that clients can recognize and use consistently. It\nleverages MCP's `_meta` field, RFC 8785 for deterministic hashing, and\n[CEP-6 announcements](https://github.com/ContextVM/contextvm-docs/blob/master/src/content/docs/spec/ceps/cep-6.md)\nfor discovery, creating a marketplace where users can choose between multiple providers implementing the\nsame standard tool interface.\n\n- Three new CEPs have been proposed and are waiting for a number to be assigned:\n- [CEP-XX](https://github.com/ContextVM/contextvm-docs/issues/22): This enhancement proposal aims to define a way to detect when a message can't be published, due to its payload exceeding the size limits of a relay. The linked issue tracks exploratory work for this new mechanism.\n- [CEP-XX](https://github.com/ContextVM/contextvm-docs/issues/23): This enhancement proposal aims to standardize the way in which MCP servers publish a persistent public profile and how they manage a public communication channel for updates and announcements.\n- [CEP-XX](https://github.com/ContextVM/contextvm-docs/issues/24): This enhancement proposal aims to standardize how users attach comments and reviews to server announcements. This would allow to create a Nostr-native review and discussion layer around servers.\n\n---\n\n## **Who is Talking about ContextVM?** 📢\n\n*A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.*\n\n- CVM has been mentioned on [Nostr Compass #15](https://jumble.social/notes/nostr:naddr1qvzqqqr4gupzqa6e2nmnzsgjfzdy520vdy4hywr06c9ue6crpr2zxyq749uu275qqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qqgrjcmp89snzepjvesnjve3xdnrxwkwxyl), a weekly newsletter covering everything going on in the Nostr ecosystem. CVM has been also mentioned in the [Nostr Compass Podcast #12](https://jumble.social/notes/nostr:nevent1qvzqqqqqqypzqa6e2nmnzsgjfzdy520vdy4hywr06c9ue6crpr2zxyq749uu275qqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qqsvydegp7zgusxlg248rudq8hakztm5dku4rztxfdmxspre3tyht8c02zr6j).\n\n---\n\n## **Intresting resources from the web** 🤖\n\n*A curated list of resources we found interesting.*\n\n- [Nicholas Carlini - Black-hat LLMs | [un]prompted 2026](https://www.youtube.com/watch?v=1sd26pWhfmg): *Nicholas Carlini*, Research Scientist at *Anthropic*, discusses how LLMs can now be used to automate attacks that were previously only doable by human adverasries.\n\n- [Thoughts on slowing the fuck down ](https://mariozechner.at/posts/2026-03-25-thoughts-on-slowing-the-fuck-down/): An interesting article by *Mario Zecher* diving into what could be the best way to work with coding agents.\n\n- [Skills Over MCP Interest Group - March 24th 2026 Office Hours Notes](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/2460): This resource provides the minute of the meeting of the *Skills Over MCP Interest Group*, the commitee responsible for discussing the next steps, issues, and blockers for implementing Skills into MCP.\n---\n\n*Find out more about ContextVM:*\n\n- *Check out our [website](https://contextvm.org/) for documentation, blog posts, and more.*\n- *Join our [Signal](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR) group*\n- *Follow ContextVM on [Nostr](https://jumble.social/users/nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm)\n- *Subscribe to our [Substack](https://contextvm.substack.com/). Help us spread the word!*\n- *Check out our GitHub [repositories](https://github.com/contextvm) and leave us a ⭐*",1774973288,"37bbe417904a63ab4ed5d0dad2e96c53ea753a3a717fce05beee3a0ed08a180e","daa209d27f7f404b3b829dbd11377d1c2b1c8d10dad1fb44af21af0ab29fee9fdcacc48b710cbd12b8db00867b9654b20b75ac9d41ec4abae3941b4812024486",[330,331,332,333,334,335,336,337,338,339,340,341,342,343,344,345,346,347,348,349],[81,363],[79,362],[77,361],[67,360],[65,359],[61,12],[61,75],[61,214],[61,72],[61,249],[184,357,358,131,40],[129,40,131],[184,356,244,131,40],[184,355,244,131,354],[129,354,131],[129,133,131],[246,353,244],[184,352,244,131,351],[129,351,131],[140,350],"nostria","775954f7314112489a4a29ec692b72386fd60bcceb0308d423101ea979c57a80","c237280f848e40df42aa71f1a03dfb612f746db95189664b766804798ac9759f","30023:775954f7314112489a4a29ec692b72386fd60bcceb0308d423101ea979c57a80:9ca9a1d2fa9313f3","e771af0b05c8e95fcdf6feb3500544d2fb1ccd384788e9f490bb3ee28e8ed66f","5a0f453f7d488d7004fe42b0a82dd89aab750062ac5499834cc8f0db64c44f4a","9e9e2ac5070e28c79bc09794b284b0a62e5c22ae7b4f665e79ef1c31eb5861cb","8eed5d21b3cd43642e84b39be4c443d9996acc4c8b937a35ca326909df99641b","wss://relay.primal.net/","1774973288","https://media.openresist.com/94358655519c6194b8268e6c036566a939fef59dc288d3da4b772531720567c6.webp","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 realys.","Mentoring the Next Generation — The ContextVM World #5 🌍 ","cvm-world-5","*GM people, and welcome to the 7th issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and everything in between!*\n\n*In today's update we cover the latest news from ContextVM. In particular, we discuss the recent merging of two new specifications, CEP-23, which allows servers to publish a public profile and post notes signed with the same keypair used for protocol operations, and CEP-24, which allows users to attach comments and reviews to servers.*\n\n*We also discuss the latest news from the ecosystem, with a recent update of wavefunc.live, an internet radio working through Nostr and CVM.*\n\n*We also show the features we are currently working on, such as the new Rust SDK and new specifications.*\n\n*Moreover, we will present a curated list of articles, blog posts, and notes talking about CVM and how it is changing the way we interact with MCP servers.*\n\n*Finally, we will bring the most interesting news from the internet regarding the MCP ecosystem, AI agents, and more!*\n\n*Let's start!*\n\n---\n\n## **News from ContextVM** 📰\n\n*A list of updates, releases and new cool features.*\n\n- **Public Presence**: Thanks to the hard work of our students from [Summer of Bitcoin](https://www.summerofbitcoin.org/), we recently merged a new specification, namely [CEP-23](https://docs.contextvm.org/spec/ceps/cep-23/). This enhancement proposal standardizes the way in which MCP servers publish a persistent public profile and how they manage a public communication channel for updates and announcements. Servers are now able to publish `kind:0` events for profile metadata and `kind:1` notes for providing social announcements, public updates, or more, signed using the same keypair used for protocol operations. Consequently, we released a new version of our TypeScript SDK, [v0.9.0](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#090), integrating the latest specifications.\n\n- **Review your server**: We also merged [CEP-24](https://docs.contextvm.org/spec/ceps/cep-24/), an enhancement proposal that standardizes how users attach comments and reviews to server announcements. This provides a Nostr-native review and discussion layer around servers. Reviews and public metadata are already available on our [website](https://contextvm.org/s/750682303c9f0ddad75941b49edc9d46e3ed306b9ee3335338a21a3e404c5fa3)!\n\n- **The complete Swiss army knife**: We recently published the latest version of CVMI, [v0.3.0](https://github.com/ContextVM/cvmi/blob/main/CHANGELOG.md#030). This release finally completes the migration of the old cli tools into CVMI, with the latest addition of CTXCN, a utility that generates a type-safe client from a CVM server's tool definitions, allowing developers to call CVM tools as if they were native TypeScript functions.\n---\n\n## **News from the ContextVM Ecosystem** 🗞️\n\n*Find all the projects leveraging ContextVM on [ContextVM/awesome](https://github.com/ContextVM/awesome).*\n\n- [wavefunc.live](https://wavefunc.live/), an internet radio project based on Nostr and CVM, just got a big update. Check out this [note](https://primal.net/e/nostr:nevent1qqs9fcura3hq087h4e4hvk4tfpqd0hlnj3n9vxa9ryg2qcaffm2pekgy2lawe) by its creator, developer Schlaus Kwab.\n\n---\n\n## **What’s Next for ContextVM?** ⏭️\n\n*Let’s take a look at the features currently being implemented!*\n\n- [CEP-15](https://github.com/ContextVM/contextvm-docs/issues/15): This enhancement proposal implements a\nstandard for defining and discovering common tool schema. This aims to enable interoperability between\nmultiple servers, standardizing tool interfaces that clients can recognize and use consistently. It\nleverages MCP's `_meta` field, RFC 8785 for deterministic hashing, and\n[CEP-6 announcements](https://github.com/ContextVM/contextvm-docs/blob/master/src/content/docs/spec/ceps/cep-6.md)\nfor discovery, creating a marketplace where users can choose between multiple providers implementing the\nsame standard tool interface.\n\n- [CEP-35](https://github.com/ContextVM/contextvm-docs/issues/35): This enhancement proposal introduces informational 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.\n\n- The Rust SDK for CVM, [rs-sdk](https://github.com/ContextVM/rs-sdk) is progressing, thanks to our SoB students. It is steadily reaching feature parity with our TypeScript SDK, adding support for CEP-4, CEP-6, CEP-17, and CEP-19. Stay tuned for its first official release!\n---\n\n## **Interesting resources from the web** 🤖\n\n*A curated list of resources we found interesting.*\n\n- A new [proposal](https://github.com/pulsemcp/air/blob/main/docs/mcp-json-proposal.md) for a client-side MCP server configuration.\n\n- [\"At Meta, workers train their replacements\"](https://vector.news/at-meta-workers-train-their-replacements/): An insightful article, describing how Meta is training its models directly on employees' actions.\n\n- [\"Every level of AI and its terrifying consequences\"](https://www.youtube.com/watch?v=Qj9--hb-prA): What happens when we build systems so efficiently that even the smartest people can’t slow them down when they spiral out of control? What happens when something designed with good intentions follows those intentions to their logical extreme, even when it starts working against us? And more importantly, what happens when these systems stop being tools and start becoming something else, with their own wills and desires?\n\n- [\"The Supply and Demand of AI Tokens | Dylan Patel Interview\"](https://www.youtube.com/watch?v=LF3aUIM57uw): Patrick O'Shaughnessy sits down with Dylan Patel, founder of SemiAnalysis, to explore the explosive supply and demand dynamics of the AI revolution.\n\n---\n\n*Find out more about ContextVM:*\n\n- *Check out our [website](https://contextvm.org/) for documentation, blog posts, and more.*\n- *Join our [Signal](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR) group*\n- *Follow ContextVM on [Nostr](https://jumble.social/users/nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm)*\n- *Subscribe to our [Substack](https://contextvm.substack.com/). Help us spread the word!*\n- *Check out our GitHub [repositories](https://github.com/contextvm) and leave us a ⭐*",1777389926,"08a843495d1d713fd9ebcc1468358ea26208f30d88ba5851a7b15001c57e7881","30fd957a499d036599c7d34bce47369ae165edfc639c57f9f373587ab47c500ebff60b53215fed80d08a53809e5e6669d3700d7665b1363f1f0c8a03887f8be8",[369,370,371,372,373,374,375,376,377,378,379,380,381,382],[81,390],[79,389],[77,388],[67,387],[65,386],[61,12],[61,214],[61,76],[61,75],[61,385],[61,384],[184,383,131,131,131],[129,40,131],[140,350],"54e383ec6e079fd7ae6b765aab4840d7dff39466561ba51910a063a94ed41cd9","llms","agent","1777389926","https://mibo.nostria.app/be3fd7b9c46c3bf89ccb11d3ad28c90470c6bb654dfd7d4185bcb32f2530b8ff.webp","In today's update we cover the latest news from ContextVM. In particular, we discuss the recent merging of two new specifications, CEP-23, which allows servers to publish a public profile and post notes signed with the same keypair used for protocol operations, and CEP-24, which allows users to attach comments and reviews to servers.","Public Presence — The ContextVM World #7","cvm-w7","*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!*\n\n*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.*\n\n*We also discuss the latest news from the ecosystem, with CVM being used as an actor for Nostr-based state machines.*\n\n*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.*\n\n*Finally, we will bring the most interesting news from the internet regarding the MCP ecosystem, AI agents, and more!*\n\n*Let's start!*\n\n---\n\n## **News from ContextVM** 📰\n\n*A list of updates, releases and new cool features.*\n\n- **The Rust SDK**: We recently released the first stable version of our brand-new [Rust SDK for CVM](https://github.com/ContextVM/rs-sdk)! The 0.1.x release family lands with the core specifications in place and support for [CEP‑4 Encryption](https://docs.contextvm.org/spec/ceps/cep-4/), [CEP‑6 Server Announcements](https://docs.contextvm.org/spec/ceps/cep-6/), [CEP‑19 Ephemeral Gift Wraps](https://docs.contextvm.org/spec/ceps/cep-19/), and [CEP‑35 Stateless Session Discovery and Capability Learning](https://docs.contextvm.org/spec/ceps/informational/cep-35/). With Rust, CVM now expands into native development, opening the door to new use cases, better performance, and future bindings for other languages.\n\n This effort was led by students from Summer of Bitcoin, especially [Harsh](https://primal.net/p/nostr:nprofile1qqstfkaf4k54fs6hcuu03ua9nr7j5q324kkg7zpqgze59c4pfp74xncvwyshd) who lead the development of this release, and [Kushagra0902](https://primal.net/p/nostr:nprofile1qqs8mnfd962xrvpzpru4kjplpvmka7mjysr7apr4zn3jxgl0pqqyewgprw9vs) and [Kosti](https://primal.net/p/nostr:nprofile1qqspvd9c0d0ul49xcnlj7t0pw3gvenjxlx47pvp2wxrkcktwc9jmlmg3r68pg) who put together the very first version. We’re grateful for the community effort behind this!\n\n- **Common tool schema**: At last, we merged [CEP-15](https://github.com/ContextVM/contextvm-docs/issues/15), an enhancement proposal that implements a\nstandard 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](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#0100) of the TypeScript SDK.\n\n- **Open-ended streams**: We recently introduced a new specification called [CEP‑41](https://docs.contextvm.org/spec/ceps/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](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#0110) of the TypeScript SDK.\n\n- **Stateless session behavior**: We also published [CEP-35](https://github.com/ContextVM/contextvm-docs/issues/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.\n---\n\n## **News from the ContextVM Ecosystem** 🗞️\n\n*Find all the projects leveraging ContextVM on [ContextVM/awesome](https://github.com/ContextVM/awesome).*\n\n- Developer Schlaus Kwab [shared](https://primal.net/e/nostr:nevent1qqsfpwsnyy59rjmthl5uw24suyflyek5h00w069pepy857j4e7vmqsgeyxtpz) 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](https://schlaustronics.com/nsm/).\n\n---\n\n## **What’s Next for ContextVM?** ⏭️\n\n*Let’s take a look at the features currently being implemented!*\n\n- Our main focus is bring the Rust SDK up to par with the TypeScript reference implementation. [IS64](https://github.com/ContextVM/rs-sdk/issues/64) is keeping track of the work needed to achieve it.\n\n- 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](https://contextvm.org/), and it will allow users to pick servers and start chatting with LLMs using them.\n\n- We are currently adapting our website to support CEP-15, to help users discover servers and their related features.\n\n## **Interesting resources from the web** 🤖\n\n*A curated list of resources we found interesting.*\n\n- New day, new [supply‑chain attack](https://safedep.io/mass-npm-supply-chain-attack-tanstack-mistral/). Be safe! Check out TanStack [post‑mortem](https://tanstack.com/blog/npm-supply-chain-compromise-postmortem).\n\n- [Experimental triggers & events](https://github.com/modelcontextprotocol/experimental-ext-triggers-events) are coming to MCP. This is similar to the work we recently did for CEP‑41!\n\n- [The bottleneck was Never the code](https://www.thetypicalset.com/blog/thoughts-on-coding-agents): And interesting article discussing the usage of coding agents.\n\n- [Local AI needs to be the norm](https://unix.foo/posts/local-ai-needs-to-be-norm/): Another interesting article about running local models for some app features for increased privacy and more resilient software.\n\n**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.\n\n---\n\n*Find out more about ContextVM:*\n\n- *Check out our [website](https://contextvm.org/) for documentation, blog posts, and more.*\n- *Join our [Signal](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR) group*\n- *Follow ContextVM on [Nostr](https://jumble.social/users/nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm)*\n- *Subscribe to our [Substack](https://contextvm.substack.com/). Help us spread the word!*\n- *Check out our GitHub [repositories](https://github.com/contextvm) and leave us a ⭐*",1778594930,"00f36473bbe0e1235371ca5f8c4fc95b004a5302335b2bd96560dbd8e54b8137","7c293f49d26529788382888cb7e929ef3f63c5fdec878fdbf6df54d633bda14d5fe6bece84980cbed72f0684fec325bd8d3d04c7782490c307e200398e5af569",[396,397,398,399,400,401,402,403,404,405,406,407,408,409,410,411,412,413],[81,423],[79,422],[77,421],[67,420],[65,419],[61,12],[61,75],[61,214],[61,249],[61,71],[61,72],[61,418],[129,417,131],[129,416,131],[129,415,131],[184,414,131,131,131],[129,40,131],[140,350],"90ba13212851cb6bbfe9c72ab0e113f266d4bbdee7e8a1c8487a7a55cf99b041","1634b87b5fcfd4a6c4ff2f2de17450ccce46f9abe0b02a71876c596ec165bfed","7dcd2d2e9461b02208f95b483f0b376efb722407ee847514e32323ef08004cb9","b4dba9ada954c357c738f8f3a598fd2a022aadac8f082040b342e2a1487d534f","rpc","1778594930","https://mibo.nostria.app/53e54b2cbbf686ef168732e87292b137702a35c7ecb8352f61db672540f9fa60.webp","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!\n\nIn 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.","The Rust SDK — The ContextVM World #8 🌍","cvmw-8","Relatr 0.2.x has been a long time coming.\n\nThis release is the result of a real engineering effort: not just shipping features, but stepping back, questioning assumptions, and redesigning one of the most important parts of the system until it matched the principles we care about. The center of gravity in this release is the plugin system, and with it, Relatr takes a major step forward.\n\nIn Relatr, plugins, or validators, are a big part of its essence. The core algorithm is based on two main components that each account for 50% of the final rank. One half is social graph distance. The other half is a set of validators. From the beginning, the idea was to make those validators configurable so anyone could decide what trust means for them and craft their own algorithm by composing that set.\n\nBefore this iteration, in the 0.1.x family, plugins in Relatr were written in TypeScript. That approach was powerful in theory. Anyone could write their own validator, extend the system, and adapt it to their own trust model. But in practice, the experience was not where it needed to be.\n\nWriting a plugin meant navigating the codebase, understanding Relatr’s internal capabilities, and implementing logic directly in TypeScript. That is possible, especially today with LLMs helping people bridge gaps faster than ever. But the deeper questions remained unanswered.\n\nHow do you install a plugin from someone else?\n\nHow do you share one cleanly?\n\nHow do you publish a validator so others can discover it, evaluate it, and adopt it?\n\nThere was no satisfying answer. And because the plugin system lived in TypeScript, it also left the door open to bad tradeoffs: messy ergonomics, dependency creep, more attack surface, and a design that could easily become over-engineered in the name of flexibility. Every path forward seemed to point toward a solution that was heavier, more fragile, and less portable than what we wanted.\n\nSo we kept the problem in the back of our minds.\n\nThe goal was clear: build a validation plugin system for Relatr that would let anyone write plugins easily, share them easily, install them easily, and distribute them natively through Nostr itself. We wanted plugins to be portable. We wanted curation. We wanted the Web of Trust and Nostr’s distribution model to work together instead of living in separate worlds.\n\nThen we found [elo-lang](https://elo-lang.org/).\n\nElo is a simple, well-designed, portable, and safe data expression language. It is purely functional, originally designed for no-code tooling, and excellent at describing data transformations in a concise and understandable way. When we discovered it, the first reaction was immediate: this could be the foundation for Relatr’s new plugin system.\n\nIt checked almost every box.\n\nPortable. Safe. Expressive. Small enough to travel. Predictable enough to trust.\n\nBut once we started experimenting, we found an important limitation. Elo’s normal execution model is linear, and that is often exactly what you want. For Relatr, though, we needed something more expressive. We needed a way to describe multi-step processes. We needed plugins to declare when host-provided capabilities should be invoked: a Nostr query, a social graph operation, an HTTP-based NIP-05 resolution, and similar actions. We needed a clean way for the host to orchestrate those requests while keeping the plugin language itself safe and understandable.\n\nThat is what led us to fork Elo.\n\nFrom there, we introduced two core operators: do and then.\n\nThe idea is simple.\n\nDo declares that the host should execute a capability. For example, a plugin can say: perform a Nostr query, resolve a NIP-05 identifier, or inspect the social graph.\n\nThen defines ordering. It lets authors compose multi-step logic in a natural sequence, where later steps can depend on data gathered earlier.\n\nWhat we like most about this design is how little it feels like a bolt-on. The new operators fit naturally into Elo’s style. They feel close to the language that already existed. They preserve the elegance of the original while giving Relatr the expressivity it needed.\n\nMore importantly, the model is safe.\n\nA plugin cannot just execute arbitrary code or invent arbitrary powers for itself. The capabilities available to a validator are defined by the host. In this case, by the Relatr instance that chooses to run it. Relatr ships with a built-in catalog of capabilities like nostr.query, graph.are_mutual, or http.nip05_resolve. If a malicious plugin tries to invoke something outside that catalog, such as an imaginary evil capability, nothing happens. The host simply does not provide it.\n\nThat design changes Relatr fundamentally. It turns Relatr into a framework.\n\nPlugins become portable programs that are compatible depending on the version and capability surface of the host. The host decides what powers exist. The plugin can only ask for those powers, never exceed them.\n\nA useful way to picture the flow is this: first collect, then execute, then provision, then result.\n\nA plugin might say: first do a Nostr query to fetch kind 0 profile events; then extract the NIP-05 field from the returned metadata; then do an HTTP NIP-05 resolution; and finally return 1 or 0 depending on whether the resolution matches the target pubkey.\n\nNotice how naturally that reads. We can explain the execution model using the same words as the operators themselves: do this, then that. That was intentional. We wanted plugin authoring to feel as natural and comprehensive as possible.\n\nThis architecture gave us more than safety and readability. It also unlocked performance wins.\n\nBecause plugins declare their required data statically, the host can understand the work up front. It can group similar capability calls, deduplicate requests, and avoid redundant executions. That improves synchronization and validation throughput without making plugin authors think about low-level orchestration. Authors describe what they need. Relatr decides how to fetch and provision it efficiently.\n\nThe result is a plugin language that is portable, safe, multi-step, expressive, and efficient enough to live comfortably inside a Nostr event.\n\nThat last point matters.\n\nOnce we had the plugin model, the next logical question was: how should these plugins be packaged and shared?\n\nThe answer was refreshingly simple. A plugin is bundled as a Nostr event.\n\nThe Elo expression goes in the event content. The metadata lives in tags: title, description, stable identifier, compatibility range, and other manifest details. The result is a regular Nostr event of kind 765, purpose-built for portable Relatr plugins.\n\nThis is where things start to get really exciting.\n\nIf plugins are Nostr events, then distribution becomes native to the same ecosystem Relatr already lives in. Plugins can be published to relays. They can be mirrored. They can be discovered. They can be curated. They can be forked. They can be grouped into packs. They can evolve through new versions. They can travel through the same open network that Relatr already uses.\n\nIn other words, plugin distribution stops being a side problem and becomes part of the protocol surface.\n\nThat opens the door to a plugin marketplace, and that is exactly where we went next.\n\nBut shipping a portable format was only part of the job. We also had to think seriously about the authoring experience.\n\nA portable language is only as useful as the tools people have to write it well.\n\nOne of Elo’s original strengths is that it already works nicely in the browser. It compiles to JavaScript, and the upstream project includes a playground where people can learn the language, write expressions, and validate their syntax. That gave us an excellent starting point.\n\nStill, there was a missing piece.\n\nElo by itself has no reason to know what Relatr is. It does not know Relatr’s capabilities. It does not know the host’s plugin constraints. It does not know what a valid Relatr plugin should look like. And we did not want to solve that by tightly coupling Relatr into Elo. We liked the separation. We wanted Elo to remain a general-purpose expression language and Relatr to remain its own system. Keeping them decoupled makes both easier to understand, easier to maintain, and potentially more useful across the broader Nostr ecosystem.\n\nBut decoupling alone does not solve authoring UX.\n\nWriters still need confidence. They need validation. They need feedback before publishing.\n\nThat is why we built Relo.\n\nRelo is both a library and a CLI. It bridges the authoring gap between Elo and Relatr without collapsing the two into one project.\n\nOn the web, it powers the publishing interface on the Relatr website, where users can write, validate, and publish plugins directly from the browser.\n\nLocally, it works as a CLI, so plugin authors can write validators on their own machines, validate them, build artifacts, and publish them from the command line. That matters for regular publishers, but it also matters for LLM-assisted workflows. If you are iterating quickly with local files, prompts, and terminal tools, the full plugin lifecycle is available without having to leave your environment and move to a website every time.\n\nAnd now there is another important piece in that authoring story: skills.\n\nWe wanted plugin writing to be accessible not only to experienced developers, but also to people working with AI-assisted tooling. So we created installable authoring skills that package the right context, concepts, and lifecycle knowledge into a form LLMs can use effectively.\n\nThat means a user who wants to write Relatr plugins with AI assistance can install the Relatr authoring skill as simply as running npx skills add contextvm/relatr. From there, they get a structured understanding of the plugin model: how to think in terms of bounded capabilities, how to structure multi-step programs, how to validate a plugin, and how to move from draft to a publishable Nostr event.\n\nThis matters because authoring is not only about syntax. It is about having the right mental model. A good plugin is not arbitrary code with network access. It is a bounded scoring program. It collects data safely, scores it clearly, and fits into a portable lifecycle that includes validation, packaging, publishing, installation, and tuning.\n\nThat is the real role of skills in this release. They turn the authoring experience into something teachable, repeatable, and much more accessible to people working with modern AI tools.\n\nTwo interfaces, one contract: web and CLI. And now, a third layer of support for AI-assisted authoring.\n\nThat made Relo, together with the new skills, the missing piece of the puzzle. The authoring loop is now much closer to end to end, while still preserving the elegance of the overall architecture.\n\nAnd this release is not only about internals. The website has been upgraded to reflect the new reality of Relatr as a plugin-driven framework.\n\nThe documentation now covers the new plugin system, including writing, publishing, tooling, and specification. There is a new plugin marketplace where users can discover available plugins and install them directly into their Relatr instances from the website. The new home for all of this is [relatr.net](https://relatr.net).\n\nThat is a major shift.\n\nRelatr instances are no longer opaque boxes you configure indirectly and hope for the best. Now operators can manage plugins directly from the website: install, uninstall, enable, disable, and adjust weights to shape the algorithm their instance uses.\n\nThat last point is central.\n\nTrust metrics should not be a black box.\n\nWith this release, it becomes much easier to see what algorithm is actually behind a Relatr instance. You can inspect the plugins, their weights, and the individual components contributing to a score. You can understand not just the output, but the composition behind the output.\n\nTransparency for trust means no black boxes.\n\nLooking back, this release was a genuine engineering journey. We designed a new plugin system for Relatr. We turned plugins into portable Nostr events. We discovered a remarkable expression language, then forked it carefully to meet the real needs of host-orchestrated validation. We created Relo to make authoring practical, ergonomic, and complete across both web and CLI. And we added skills so that even AI-assisted authors can work with the right concepts and constraints from the start.\n\nNone of this happened quickly, and that was the point.\n\nAt every stage we stopped to reconsider the tradeoffs: technical design, UX, safety, ergonomics, integration, and performance. We did not want to solve one problem by creating three worse ones. We also remained committed to one of Relatr’s original constraints: this software should still be able to run on modest hardware.\n\nThat remains true.\n\nRelatr is still fully open source. It still aims to be efficient. It still aims to let people run their own Web of Trust engine without requiring a pile of infrastructure or a mountain of specialized expertise, especially when paired with ContextVM. And for people who want to run it themselves, all the details are available in the GitHub repository at [https://github.com/ContextVM/relatr](https://github.com/ContextVM/relatr).\n\nWhat has changed is the degree of freedom available to users.\n\nNow anyone can compose an algorithm more like Lego than like a monolith. Anyone can write plugins. Anyone can publish them. Anyone can share them. Anyone can browse a marketplace, install validators, curate sets, and assemble trust models that reflect their own values and communities.\n\nThat is what this release is really about.\n\nNot just new features, but a stronger answer to an old question: who gets to define trust?\n\nOur answer remains the same. Not a platform. Not a hidden algorithm. Not a single authority.\n\nLet a thousand trust algorithms bloom.\n\nThat was one of the earliest premises behind Relatr, and with the 0.2.x family it is more true than ever. The engineering is there for people to use, inspect, fork, and build on. The system is more transparent, more portable, and more shareable. The black box has been opened.\n\nRelatr is now closer to what it always wanted to be: a tool for sovereign trust computation in an open network.\n\nThis release gets us materially closer to that future.",1775659222,"81d977abdb96a32e8a0b5bb27af3845fc8b384870e8bfa33538a8ae62d757152","eb954c728fd11c817b4f4dd1ce20fca5d3ece59cb801c04dc3d754219b523226d844c8f9f8e2c514c7f0be6ac1544951ff95a07be4302679c1ce2cf9401b0fcb",[429,430,431,432,433,434,435,436,437,438,439],[81,445],[79,444],[77,443],[67,442],[65,441],[61,188],[61,440],[61,12],[61,74],[61,159],[140,350],"relatr","1775659222","https://mibo.nostria.app/03789d2a1e6e2a733684239a050301c8196bc9dfc520d81f3779c941f33f0892.webp","Relatr 0.2.x has been a long time coming.\n\nThis release is the result of a real engineering effort: not just shipping features, but stepping back, questioning assumptions, and redesigning one of the most important parts of the system until it matched the principles we care about. The center of gravity in this release is the plugin system, and with it, Relatr takes a major step forward.","Relatr 0.2.x: Let a Thousand Trust Algorithms Bloom","relatr-0-2","*GM people, and welcome to the sixth issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!*\n\n*In today's update we cover the latest news from ContextVM. In particular, we discussed the recent merging of CEP-22 and the successive release of a new SDK version.*\n\n*We also discuss the latest news from the ecosystem, with the main topic being the new v0.2.0 of Relatr, with a freshly redesigned plugin system.*\n\n*Moreover, we will present a curated list of articles, blog posts, and notes talking about CVM and how it is changing the way we interact with MCP servers.*\n\n*Finally, we will bring the most interesting news from the internet regarding the MCP ecosystem, AI agents, and more!*\n\n*Let's start!*\n\n---\n\n## **News from ContextVM** 📰\n*A list of updates, releases and new cool features.*\n\n**Never too big**: We recently merged [CEP-22](https://contextvm.github.io/contextvm-docs/spec/ceps/cep-22/), a new proposal that allows CVM to publish a message to a realy even if its payload exceedes the size limits of a relay.\n\nThis change was also included in the latest release of the TypeScript SDK, with [v0.8.0](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#080) being published soon after the new specification was formalized. CVMI was also updated in [v0.2.8](https://github.com/ContextVM/cvmi/blob/main/CHANGELOG.md#028), bumping the SDK release to the latest one.\n\n---\n\n## **News from the ContextVM Ecosystem** 🗞️\n*Find all the projects leveraging ContextVM on [ContextVM/awesome](https://github.com/ContextVM/awesome).*\n\n**Relatr v0.2.x family**: Relatr has just undergone a major refactoring, which aimed to redesign the way the plugin system works.\nPlugins are one of the foundational parts that make Relatr what it is now, strongly impacting its core algorithm. Thus, the goal was to build the system such that anyone would be able to create, share, install, and distribute plugins directly through Nostr.\n\nIf you want to know more about the new Relatr, read our latest [deep dive](https://contextvm.substack.com/p/relatr-02x-let-a-thousand-trust-algorithms)!\n\n---\n\n## **What’s Next for ContextVM?** ⏭️\n*Let’s take a look at the features currently being implemented!*\n\n[CEP-15](https://github.com/ContextVM/contextvm-docs/issues/15): This enhancement proposal implements a\nstandard for defining and discovering common tool schema. This aims to enable interoperability between\nmultiple servers, standardizing tool interfaces that clients can recognize and use consistently. It\nleverages MCP's `_meta` field, RFC 8785 for deterministic hashing, and\n[CEP-6 announcements](https://github.com/ContextVM/contextvm-docs/blob/master/src/content/docs/spec/ceps/cep-6.md)\nfor discovery, creating a marketplace where users can choose between multiple providers implementing the\nsame standard tool interface.\n\nTwo new CEPs are currently [being worked on](https://github.com/ContextVM/contextvm-docs/pull/26/) by our students from SoB program:\n\n[CEP-23](https://github.com/ContextVM/contextvm-docs/issues/23): This enhancement proposal aims to standardize the way in which MCP servers publish a persistent public profile and how they manage a public communication channel for updates and announcements.\n\n[CEP-24](https://github.com/ContextVM/contextvm-docs/issues/24): This enhancement proposal aims to standardize how users attach comments and reviews to server announcements. This would allow to create a Nostr-native review and discussion layer around servers.\n\n---\n\n## **Who is Talking about ContextVM?** 📢\n*A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.*\n\nCVM was mentioned is several article from [Sovereign Engineering](https://sovereignengineering.io/):\n\n[15: Make Localhost Great Again](https://jumble.social/notes/nostr:naddr1qvzqqqr4gupzpx77gg2frul26xkzr0gaq9n842u50axpcjhdsa3yeu388vrv5pftqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qqwnzdfdd4skkefdd3hkxctvdphhxapdvaex2ct594skwctfdcf36eng)\n\n[21: Hashtree, Nostr VPN, and Iris w/ Martti Malmi](https://jumble.social/notes/nostr:naddr1qvzqqqr4gupzpx77gg2frul26xkzr0gaq9n842u50axpcjhdsa3yeu388vrv5pftqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qq0ryvfddpshx6r5wfjk2ttwdaehgu3dwecxuttpdejz66tjd9esktj8qg)\n\n[The Pirate Ship of the Psychopaths](https://jumble.social/notes/nostr:naddr1qvzqqqr4gupzqp82f7p4pu2k92savrwqwptp7kac8p4pr5dqq4c06azqmgssu9cnqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qqxnzdehx5enxvpexvun2denjp53py)\n\nCVM was also mentioned in two different issues of *The Latest Pojects Noted*, in particular issue [6](https://jumble.social/notes/nostr:naddr1qvzqqqr4gupzp6vlpknzqlxwx5lya3mpskdhvhuqgc3kpynt4x20rpvamz2kz0whqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qqjrvdrzxy6nvcmz95exvcnp956rqve4943rzdmp95unscmyxsukvdpjxejry4qu09e) and [7](https://jumble.social/notes/nostr:naddr1qvzqqqr4gupzp6vlpknzqlxwx5lya3mpskdhvhuqgc3kpynt4x20rpvamz2kz0whqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qqjrsd3c8ycrxvtr94snwep4956xvwfe95unyvny95enjct9x9nrjveexyenqrlckxt).\n\nRelatr was mentioned in [Nostr Compass #17](https://jumble.social/notes/nostr:naddr1qvzqqqr4gupzqa6e2nmnzsgjfzdy520vdy4hywr06c9ue6crpr2zxyq749uu275qqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qqgrsvrrvd3nzcf5xa3rxen9x5enjhnnar9).\n\nOur lates blog post on Relatr was also turned into a podcast! Check it out [here](https://unsaltedbutter.ai/listen/Ae2zCl4qvIDUXjq3).\n\n---\n\n## **Intresting resources from the web** 🤖\n*A curated list of resources we found interesting.*\n\n[Your Agent Is Mine: Measuring Malicious Intermediary Attacks on the LLM Supply Chain](https://arxiv.org/html/2604.08407v1): An interesting paper about AI security.\n\n---\n\n*Find out more about ContextVM:*\n\n*Check out our [website](https://contextvm.org/) for documentation, blog posts, and more.*\n*Join our [Signal](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR) group*\n*Follow ContextVM on [Nostr](https://jumble.social/users/nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm)*\n*Subscribe to our [Substack](https://contextvm.substack.com/). Help us spread the word!*\n*Check out our GitHub [repositories](https://github.com/contextvm) and leave us a ⭐*",1776242218,"74763c86f3c58556a28f8a70d5994327f8e5af60c8a40c1c225e4b5afba9f85a","8e766fd08156d7a4826ac0ee5d43fd73275024df69fcba553586d566e479aa550378d53f38acf2cd095f197c620c7ae6011c624c3ec4b8dff7e9bdf8b379fbe8",[451,452,453,454,455,456,457,458,459,460,461,462,463,464,465,466],[81,478],[79,477],[77,476],[67,475],[65,474],[61,12],[61,75],[61,473],[246,472,244],[246,471,244],[246,470,244],[246,469,244],[246,468,244],[246,467,244],[129,40,131],[140,350],"30023:775954f7314112489a4a29ec692b72386fd60bcceb0308d423101ea979c57a80:80ccc1a47b3fe539","30023:e99f0da6207cce353e4ec761859b765f80462360926ba994f1859dd895613dd7:8689031c-a7d5-4f99-922d-39ae1f939130","30023:e99f0da6207cce353e4ec761859b765f80462360926ba994f1859dd895613dd7:64b156cb-2fba-4035-b17a-98cd49f426d2","30023:04ea4f8350f1562aa1d60dc070561f5bb8386a11d1a00570fd7440da210e1713:1775330939573","30023:9bde421491f3ead1ac21bd1d01667aab947f4c1c4aed87624cf2273b06ca052b:21-hashtree-nostr-vpn-and-iris","30023:9bde421491f3ead1ac21bd1d01667aab947f4c1c4aed87624cf2273b06ca052b:15-make-localhost-great-again","news","1776242218","https://mibo.nostria.app/a7f4761c434b0bf548e4d6801004700d96c7064b81b6565f85470cf5c973080c.webp","GM people, and welcome to the sixth issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and all in between!","Never Too Big — The ContextVM World #6 🌍","cvmw-6","*GM people, and welcome to the 9th issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and everything in between!*\n\nIn today's update, we cover the latest news from ContextVM. In particular, we present the finalists that will take part in the Summer of Bitcoin program during the next months, and discuss the latest release of our SDK.*\n\n*We also discuss the latest news from the ecosystem. A new MLS implementation has recently been published, and it uses CVM as its coordination layer.*\n\n*We also show the features we are currently working on. Notably, our team is focused on reaching feature parity between the Rust and TypeScript SDKs.*\n\n*Finally, we will share the most interesting news from the internet regarding the MCP ecosystem, AI agents, and more!*\n\n*Let's start!*\n\n---\n\n## **News from ContextVM** 📰\n\n*A list of updates, releases and new cool features.*\n\n- **Finalists**: We selected the best students from the Summer of Bitcoin program. These students will spend the summer working on CVM, learning the ways of open-source development. Here are our finalists:\n - [Harsh](https://primal.net/p/nostr:nprofile1qqstfkaf4k54fs6hcuu03ua9nr7j5q324kkg7zpqgze59c4pfp74xncvwyshd), who pushed the implementation of the Rust SDK.\n - [Abhay](https://primal.net/p/nostr:nprofile1qqsqyze4twh4ajf845q4jrpvku6vlqnamlkmeycpfv6afxxzq4rvc5sv96sww), who pushed the work on [CEP-15](https://docs.contextvm.org/spec/ceps/cep-15/) for common tool schemas.\n - [Khushvendra](https://primal.net/p/nostr:nprofile1qqsrsnzurjcg64ujnts4jpe0f7ymw93hzvpru4uthye25w8n7h5vh4qfr633u), who worked on the TypeScript SDK and [CEP-22](https://docs.contextvm.org/spec/ceps/cep-22/) for oversize payload transfer. He also had the time to do some maintenance work.\n\n Congrats to our new interns!\n\n- **Updated SDK**: We recently released new versions of our TypeScript SDK belonging to the v0.11.x family. Notably, version .10 added support for category tags for CEP-15 tools schema. Another patch version, .11, was released to add client-side event deduplication and improve error handling for open-streams ([CEP-41](https://docs.contextvm.org/spec/ceps/cep-41/)).\n\n---\n\n## **News from the ContextVM Ecosystem** 🗞️\n\n*Find all the projects leveraging ContextVM on [ContextVM/awesome](https://github.com/ContextVM/awesome).*\n\n- **Coordinated MLS**: [Cordn](https://cordn.net/) is a new MLS-based protocol that uses CVM in an innovative way, relying on it as deployment and transport layer. Cordn introduces a coordinator, whose task is to provide strong message ordering, fetch semantics, and delivery for proposals, commits, welcomes, and application messages. Leveraging CVM makes self-hosting in ordinary environments (like your home network) easier, facilitates portability, and improves traffic privacy. Check out the [Cordn repository](https://github.com/Cordn-msg/cordn), [find out more](https://cordn.net/why/) about its trade-offs with respect to other MLS-based implementations, and join Cordn to be invited to our CVM group!\n\n- **Better search**: Relatr recently published [v0.2.9](https://github.com/ContextVM/relatr/blob/master/CHANGELOG.md#029). The latest release introduces significant improvements to search functionality by developing a new algorithm, making profile searches more relevant to the actual query. It is important to note that this is a breaking change with respect to previous versions, and result ordering may be different.\n\n---\n\n## **What’s Next for ContextVM?** ⏭️\n\n*Let’s take a look at the features currently being implemented! Check out our [Roadmap](https://github.com/orgs/ContextVM/projects/1) to always be up-to-date with the latest developments!*\n\n- The work to reach feature parity between the Rust SDK and the TypeScript one is progressing steadily. The team is currently focusing on integrating [CEP-17](https://docs.contextvm.org/spec/ceps/cep-17/), for server relay list metadata, and CEP-22, for oversize payload transfer. You can take a look at [IS64](https://github.com/ContextVM/rs-sdk/issues/64) to keep track of the progress.\n\n- The team is working to update [CEP-8](https://docs.contextvm.org/spec/ceps/cep-8/), which specifies how payments should work for CVM, to add a new lifecycle based on explicit errors. This modification would allow to work with 402-like approaches.\n\n---\n\n## **Who is Talking about ContextVM?** 📢\n\n*A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.*\n\n- OpenSats recently listed CVM in their project showcase. Check it out [here](https://opensats.org/projects/contextvm)!\n\n---\n\n## **Interesting resources from the web** 🤖\n\n*A curated list of resources we found interesting.*\n\n- [*Dont Outsource the Learning*](https://x.com/addyosmani/status/2056078124346228860): An interesting article discussing why you should slow down and take the time to understand what AI is doing on your behalf.\n\n- [*Token price index*](https://tokenpriceindex.com/): A useful tool for AI economics, featuring real-time token cost benchmarking, model performance tracking, and granular spend simulation.\n\n---\n\n*Find out more about ContextVM:*\n\n- *Check out our [website](https://contextvm.org/) for documentation, blog posts, and more.*\n- *Join our [Signal](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR) group*\n- *Follow ContextVM on [Nostr](https://jumble.social/users/nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm)*\n- *Subscribe to our [Substack](https://contextvm.substack.com/). Help us spread the word!*\n- *Check out our GitHub [repositories](https://github.com/contextvm) and leave us a ⭐*",1779891048,"1957906efe6123589063b2cd0a37fcbd13c83de86ec553aa41decdf9a76b1154","574a509b7623334efc9f92ea3030ff4eed30a30ee27292c1d1640b7a08bda3638a52eca592e057540f5596f53d89fa46a404ffe6fea6adaacca41ff5d0f65576",[484,485,486,487,488,489,490,491,492,493,494,495,496,497,498],[81,507],[79,506],[77,505],[67,504],[65,503],[61,12],[61,214],[61,502],[61,501],[61,75],[129,417,131],[129,500,131],[129,499,131],[129,40,131],[140,350],"384c5c1cb08d57929ae159072f4f89b7163713023e578bb932aa38f3f5e8cbd4","020b355baf5ec927ad01590c2cb734cf827ddfedbc93014b35d498c20546cc52","sdk","mls","1779891048","https://mibo.nostria.app/950a27698fd4326b8c151ab03c2dc13336da64230a1c38ea9c141119b0d9f2e1.webp","In today's update, we cover the latest news from ContextVM. In particular, we present the finalists that will take part in the Summer of Bitcoin program during the next months, and discuss the latest release of our SDK.","Coordinated MLS — The ContextVM World #9","cvmw-9","*GM people, and welcome to the 10th issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and everything in between!*\n\n*In today's update, we cover the latest news from ContextVM. In particular, we discuss the ongoing effort to expose the functionalities of CVM to other programming ecosystems through bindings in our Rust SDK. We also highlight the recent merge of ephemeral gift wraps in NIP-59, and two powerful additions to our website.*\n\n*We also discuss the latest news from the ecosystem. In particular, we cover Spectr, a multi-column deck for Nostr, integrating Relatr and CVM.*\n\n*We also show the features we are currently working on. Notably, our team is working on improving CEP-8, which specifies how payments should work for CVM.*\n\n*Finally, we will share articles, blogs, and posts talking about CVM and the most interesting news from the internet regarding the MCP ecosystem, AI agents, and more!*\n\n*Let's start!*\n\n---\n\n## **News from ContextVM** 📰\n\n*A list of updates, releases and new cool features.*\n\n- **Agentic website**: We recently made a huge update to our website, which now includes a chat interface for working with LLMs. This chat connects directly to MCP servers exposed through CVM, making it one of the most comprehensive demos of what CVM enables. Check out this [note](https://nostr.at/nostr:nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqrsdd2mz7r0h260f069pz0u9cxu83v6sjcq2yx442fv9us650qeesp6mre6) to see what the new website is capable of!\n\n- **Bindings are coming**: A Rust project is never complete, unless bindings are created to expose its functionalities to other ecosystems. That's why [aljazceru](https://github.com/aljazceru) is [adding bindings](https://github.com/ContextVM/rs-sdk/pull/84) to our Rust SDK. In particular, the new `contextvm-ffi` crate is exposing bindings to C, Python, Kotlin, and Swift, promising to bring CVM functionalities to mobile development.\n\n- **CVM improving Nostr**: Some months ago we opened a [PR](https://github.com/nostr-protocol/nips/pull/2245) in the Nostr Implementation Possibilities (NIP) repository. The PR has at last been merged, expanding [NIP-59](https://github.com/nostr-protocol/nips/blob/master/59.md) to include a new `kind` for ephemeral gift wraps, a type already implemented in CVM. The work we are doing is benefitting the whole ecosystem!\n\n- **CEP-15 is now in our website**: [CEP‑15](https://docs.contextvm.org/spec/ceps/cep-15/) (Common Tool Schemas) has been merged into our [website](https://contextvm.org/servers). 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.\n\n---\n\n## **News from the ContextVM Ecosystem** 🗞️\n\n*Find all the projects leveraging ContextVM on [ContextVM/awesome](https://github.com/ContextVM/awesome).*\n\n- **Spectr <> Relatr**: [Spectr](https://spectr.clave.casa/), a multi-column deck for Nostr, recently integrated Relatr and CVM. The new feature allows a user to check the trust score of any `npub`. Check out this [video](https://jumble.social/notes/nostr:nevent1qvzqqqqqqypzqvff2z0z85axzf0pg5d9jykmuqgfnc23wfkywe45fc0vhryydagxqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyp0d2sdeeeg06uhlxs66ekylk580fcwr0s7j8mq5g3vrvfk94lv27rjzf2e) to see how it works!\n\n---\n\n## **What’s Next for ContextVM?** ⏭️\n\n*Let’s take a look at the features currently being implemented! Check out our [Roadmap](https://github.com/orgs/ContextVM/projects/1) to always be up-to-date with the latest developments!*\n\n- The team is working to update [CEP-8](https://docs.contextvm.org/spec/ceps/cep-8/), which specifies how payments should work for CVM, to add a new lifecycle based on explicit errors. This modification to the protocol, currently ongoing in [PR44](https://github.com/ContextVM/contextvm-docs/pull/44), would allow working with 402-like approaches.\n\n---\n\n## **Who is Talking about ContextVM?** 📢\n\n*A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.*\n\n- CVM has been mentioned on [Nostr Compass #24](https://primal.net/a/nostr:naddr1qvzqqqr4gupzqa6e2nmnzsgjfzdy520vdy4hywr06c9ue6crpr2zxyq749uu275qqyt8wumn8ghj7un9d3shjtnyd968gmewwp6kytcpzamhxue69uhhxetpwf3kstnwdaejuar0v3shjtcqzqmnvenp893nvctyv5ukxdenvcmqlvdyfa), a weekly newsletter covering everything going on in the Nostr ecosystem. Specifically, the article discusses the role of CVM in [Cordn](https://cordn.net/).\n\n- [Khushvendra](https://primal.net/p/nostr:nprofile1qqsrsnzurjcg64ujnts4jpe0f7ymw93hzvpru4uthye25w8n7h5vh4qfr633u), one of our selected students from Summer of Bitcoin, published an interesting [post](https://www.linkedin.com/posts/khushvendra-singh-64827420a_ive-been-spending-a-lot-of-time-lately-digging-activity-7467463568272060416-KMu6) on LinkedIn about Nostr, CVM, and MCP servers, highlighting the powerful properties of these protocols. Thank you for bringing CVM outside the borders of Bitcoin and Nostr!\n\n---\n\n## **Interesting resources from the web** 🤖\n\n*A curated list of resources we found interesting.*\n\n- [\"Trust-me-bro in TEE\"](https://nostr.at/nostr:nevent1qqs8juuqdq69r7rnhxwkqdm079jkza5gayqf6mf28hkea4slzmvn9uqzyrh7t5fqmuxv9y86wjrj076943y8e2kngm20y2f6kp573uqlc5vczx74wcp): An interesting note by Aljaz about verifying TEE claims.\n\n- [\"Miasma npm Supply Chain Attack: Self-Spreading Worm via Phantom Gyp\"](https://www.stepsecurity.io/blog/binding-gyp-npm-supply-chain-attack-spreads-like-worm): npm supply chain attacks are becoming more and more common. Here is the report on the latest one.\n---\n\n*Find out more about ContextVM:*\n\n- *Check out our [website](https://contextvm.org/) for documentation, blog posts, and more.*\n- *Join our [Signal](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR) group*\n- *Follow ContextVM on [Nostr](https://jumble.social/users/nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm)*\n- *Subscribe to our [Substack](https://contextvm.substack.com/). Help us spread the word!*\n- *Check out our GitHub [repositories](https://github.com/contextvm) and leave us a ⭐*",1781013815,"bfeee74e7978764b7b4408726b434d7db2ff66e00e6fa151719f63d5b7529c23","3ee3b42296ddafc92e7164f7abbc553ab80040d305ea11708b701647d824316e174ce7ed60105d699760b238854ba8cd6b922317f8321fc42f485a31ec520b64",[513,514,515,516,517,518,519,520,521,522,523,524,525,526,527,528,529,530,531,532],[81,546],[79,545],[77,544],[67,543],[65,542],[61,12],[61,75],[61,249],[61,71],[61,541],[61,540],[184,539,358,131,40],[129,40,131],[184,538,186,131,537],[129,537,131],[246,535,536],[129,499,131],[184,534,131,131,533],[129,533,131],[140,350],"efe5d120df0cc290fa748727fb45ac487caad346d4f2293ab069e8f01fc51981","797380683451f873b99d60376ff165617688e9009d6d2a3ded9ed61f16d932f0","30023:775954f7314112489a4a29ec692b72386fd60bcceb0308d423101ea979c57a80:76fa9c6ade9c73f6","wss://relay.ditto.pub/","3129509e23d3a6125e1451a5912dbe01099e151726c4766b44e1ecb8c846f506","5ed541b9ce50fd72ff3435acd89fb50ef4e1c37c3d23ec1444583626c5afd8af","1c1ad56c5e1beead3d2fd14227f0b8370f166a12c0144356aa4b0bc86a8f0673","agentic","web","1781013815","https://mibo.nostria.app/ad8029c1079b8767ec226ab6d1166342934c52d1e5a7d119f2c0120768323816.webp","In today's update, we cover the latest news from ContextVM. In particular, we discuss the ongoing effort to expose the functionalities of CVM to other programming ecosystems through bindings in our Rust SDK. We also highlight the recent merge of ephemeral gift wraps in NIP-59, and two powerful additions to our website.","Agentic Web — The ContextVM World #10","cvmw-10","*GM people, and welcome to the 11th issue of \"The ContextVM World\", your biweekly appointment to discover everything you need to know about ContextVM, MCP, Nostr, and everything in between!*\n\n*In today's update, we cover the latest news from ContextVM. In particular, we discuss our first contribution to the upstream MCP repository, how we are trying to reduce the amount of dependencies in our SDK, our brand new documentation pages, and a new Explicit Payment Gating mode for CEP-8 that lets AI agents decide whether a call is worth paying for.*\n\n*We also cover the features we are currently working on. Notably, the team is looking into MCP Bundles (MCPB), a way to package and deploy local MCP servers.*\n\n*Finally, we will share articles, blogs, and posts talking about CVM and the most interesting news from the internet regarding the MCP ecosystem, AI agents, and more!*\n\n*Let's start!*\n\n---\n\n## **News from ContextVM** 📰\n\n*A list of updates, releases and new cool features.*\n\n- **Contributing Upstream**: We recently shipped an improvement to the official MCP rust-sdk repository! [PR858](https://github.com/modelcontextprotocol/rust-sdk/pull/858) was merged last week, bringing our experience as users to our major upstream dependency. The benefits of FOSS at work!\n\n This PR adds support for resetting a request timeout in case a long-running operation is ongoing. Previously, the SDK would make no difference between an offline peer which was not responding, and one that was just actively progressing to conclude a task. Our work refreshes the request timeout anytime the peer sends some progress, signaling that it is still busy and not offline.\n\n- **Fewer dependencies**: We published a new release family, v0.12.x. We decided to fork the official [MCP ts-sdk](https://github.com/modelcontextprotocol/typescript-sdk) and to strip out all those parts that are not needed in our project. What does this mean? Fewer unnecessary dependencies to the benefit of lightweight and web clients! Check out our [fork](https://github.com/ContextVM/mcp-sdk/tree/v1.x)!\n\n We then released new versions up to [v0.12.3](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#0123). We introduced progress notifications to avoid timeouts for oversized transfers, we fixed a conflict between progress tokens and open streams, and we improved handling of encryption size limits.\n\n- **Explicit Payment Gating for CEP-8**: We just released [ContextVM SDK 0.13.0](https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#0130), shipping full support for a new CEP-8 mode called Explicit Payment Gating. Until now, CEP-8 let servers charge for their tools, but only \"behind the scenes\", with payment handled silently by the transport layer. That is great for a wallet app, but not for an AI agent that actually needs to decide whether a call is worth paying for. With this update, a paid call returns a clean \"Payment Required\" error (`-32042`) that carries human-readable instructions and one or more payment options, inspired by HTTP's 402 status code. The agent reads the instructions, pays the invoice its own way, and retries the same call, with no special SDK knowledge required. The change is fully backward compatible, as the existing silent flow stays the default. Check out the [announcement](https://nostr.at/nostr:nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqzxteeuj9fu25cphayjpp03yh7cqvm0qcajl0kvda28l0ttegvtpqp9xzmm), the [CEP-8 spec](https://docs.contextvm.org/reference/ceps/cep-8/), and the [explicit gating guide](https://docs.contextvm.org/how-to/payments/explicit-gating/) to learn more!\n\n- **Diátaxis**: We also worked on improving how [our documentation](https://docs.contextvm.org/) is structured. We decided to follow [diátaxis](https://diataxis.fr/), a systematic approach to technical documentation authoring, with the aim to provide more clarity for our users. Moreover, we added comprehensive documentation for our Rust SDK.\n\n- **Bindings are here**: We finally merged bindings in our Rust SDK! In particular, the new contextvm-ffi crate is exposing bindings to C, Python, Kotlin, and Swift, bringing CVM functionalities to mobile development. \n\n---\n\n## News from the ContextVM Ecosystem 🗞️\n\n*Find all the projects leveraging ContextVM on [ContextVM/awesome](https://github.com/ContextVM/awesome).*\n\n- **MLS coordinator in the browser**: Open-source contributor sandwich developed a new MLS coordinator that runs directly in a browser tab, no need for a server to run it. An ephemeral coordinator that exist only for as long as it is needed. Check out this [note](https://nostr.at/nostr:nevent1qqsqqqqswpwuvg9my8f586jq7kdcnng7mrt83qld4yquy20j6x3j09qpp4mhxue69uhkummn9ekx7mqzypqtnjzlll40c89dlrps5nju3pnqlahyjudqm3er6k4kwj67vx69zvzcrjh) to know more!\n\n---\n\n## **What’s Next for ContextVM?** ⏭️\n\n*Let’s take a look at the features currently being implemented! Check out our [Roadmap](https://github.com/orgs/ContextVM/projects/1) to always be up-to-date with the latest developments!*\n\n- Our team is currently looking into [MCP Bundles](https://github.com/modelcontextprotocol/mcpb) (MCPB), a packaging format to easily distribute local MCP servers and provide one-click deployment. The team is currently implementing [a new command into CVMI](https://github.com/ContextVM/cvmi/pull/4) to enable developers to package local MCP servers into distributable bundles.\n\n---\n\n## **Who is Talking about ContextVM?** 📢\n\n*A curated list of articles, blog posts, and notes about ContextVM and its ecosystem.*\n\n- CVM has been mentioned on [Nostr Compass #27](https://nostr.at/nostr:naddr1qvzqqqr4gupzqa6e2nmnzsgjfzdy520vdy4hywr06c9ue6crpr2zxyq749uu275qqythwumn8ghj7um9v9exx6pwdehhxtn5dajxz7f0qqxkuethwdkx2ar5v4ez6v3hl4w4uc), a weekly newsletter covering everything going on in the Nostr ecosystem. Specifically, the article provides information on our latests SDK release.\n\n- We recently published a [demo](https://nostr.at/nostr:nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqsvz0vz4g3ghvx6vttut462swy5v50dk5c5qv6gketrathnejfhcqsqa0cr) on how to use our new LLM chat interface as a music research tool, by leveraging the [WaveFunc](https://contextvm.org/s/bb0707242a17a4be881919b3dcfea63f42aacedc3ff898a66be30af195ff32b2) MCP server. Try it out for yourself!\n\n- [aljaz](https://github.com/aljazceru) shared a new experiment born out of a hackathon: [kvaq](https://github.com/aljazceru/kvaq), bringing local inference to mobile with ContextVM support for tool use and discovery. See the [note](https://nostr.at/nostr:nevent1qvzqqqqqqypzpml96ysd7rxzjra8fpe8ldz6cjru4tf5d48j9yatq60g7q0u2xvpqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uqzpus0k3hgztj0qvdvqjkr4nr0cu8vvuw4fy866f696npdx085c0k44htjgh)!\n\n- [SkateSpots](https://nostr.at/nostr:npub1yrnuj56rnen08zp2h9h7p74ghgjx6ma39spmpj6w9hzxywutevsst7k5cx) built Sasquatch, a bot powered by CVM that helps you find skate spots. Check out the [note](https://nostr.at/nostr:nevent1qvzqqqqqqypzqg88e9f588nx7wyz4wt0ura23w3yd4hmztqrkr95utwyvgachjepqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqf6dv43vrjyfaxd5u87jw622x556n0nxpyp8f6xnvpp7vseqzdgjsgdlu7w)!\n\n---\n\n## **Interesting resources from the web** 🤖\n\n*A curated list of resources we found interesting.*\n\n- [\"What AI Can Never Be\"](https://www.youtube.com/watch?v=HAJclcj25uM): A great talk by John Vervaeke discussing intelligence and what AI can never be.\n\n---\n\n*Find out more about ContextVM:*\n\n- *Check out our [website](https://contextvm.org/) for documentation, blog posts, and more.*\n- *Join our [Signal](https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR) group*\n- *Follow ContextVM on [Nostr](https://jumble.social/users/nostr:npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm)*\n- *Subscribe to our [Substack](https://contextvm.substack.com/). Help us spread the word!*\n- *Check out our GitHub [repositories](https://github.com/contextvm) and leave us a ⭐*",1782310760,"65371dd0321bde8e531ce562733c662511e685e3c946bb1cc43814a1004455a7","b7c0d7cc61d930d7545ea960fe241f0aebfdd762940698e65e9a8d82a7790c61b5698c5ac592b7c3fe00428b6c647cd5505cdac23bf5142615757f5d975ed3f2",[552,553,554,555,556,557,558,559,560,561,562,563,564,565,566,567,568,569,570,571,572,573,574],[81,588],[79,587],[77,586],[67,585],[65,584],[61,12],[61,214],[61,71],[61,583],[61,502],[61,249],[61,72],[184,582,358,131,40],[129,40,131],[184,580,581,131,183],[129,183,131],[246,579,244],[184,578,358,131,40],[184,577,358,131,533],[129,533,131],[129,576,131],[184,575,358,131,576],[140,350],"4e9acac5839113d3369c3fa4ed2946a53537ccc1204e9d1a6c087cc864026a25","20e7c953439e66f3882ab96fe0faa8ba246d6fb12c03b0cb4e2dc4623b8bcb21","f20fb46e812e4f031ac04ac3acc6fc70ec671d5490fad2745d4c2d33cf4c3ed5","8304f60aa88a2ec3698b5f175d2a0e251947b6d4c500cd22d958fabbcf324df0","30023:775954f7314112489a4a29ec692b72386fd60bcceb0308d423101ea979c57a80:newsletter-27","000010705dc620bb21d343ea40f59b89cd1ed8d67883eda901c229f2d1a32794","wss://nos.lol","11979cf2454f154c06fd248217c497f600cdbc18ecbefb31bd51fef5af2862c2","rust","1782310721","https://npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm.blossom.band/e16eabb586379eeb5df4a447d82aa14ba306b94a6df4a1d04b4e6125a8ce6f97.jpg","In today's update, we cover the latest news from ContextVM. In particular, we discuss our first contribution to the upstream MCP repository, how we are trying to reduce the amount of dependencies in our SDK, our brand new documentation pages, and a new Explicit Payment Gating mode for CEP-8 that lets AI agents decide whether a call is worth paying for.","The Benefits of FOSS — The ContextVM World #11 🌍","cvmw-11"]