The discussion about pricing and payments flows (CEP-8) is happening at

GitHub

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

Resolves: #8

The proposal contemplates a 'matching' system to handle the multiplicity of possible payment methods that could exist. The 'matching' mechanism is based on a reference list of payment method identifiers. It's like a dating app, but for payment methods. For example, if your server supports the payment method identifier 'bitcoin-lingthing-bolt11', it emits a payment request including it, and the client matches if it supports that payment method. If it supports the method, it's a match! Beautiful 💛 Please join the conversation and provide feedback if you have any; it's highly appreciated

Migration complete, our relay and servers are up and running again. View quoted note →

Our relay and deployed servers are experiencing shortages due to a constant DDoS attack on our VPS provider, LNVPS.net. This has been happening for several days and uptime hasn't been good. We're working on migrating the infrastructure to a different provider.

Announcing CEPs: ContextVM Enhancement Proposals! 🚀 We’ve launched a formal, community-driven process for proposing, reviewing, and documenting protocol changes. CEPs standardize how new features, breaking changes, governance updates, or complex design ideas get considered—bringing transparency, quality, and clearer collaboration to ContextVM’s evolution. Learn how to propose or review CEPs and get involved: https://www.contextvm.org/blog/introducing-ceps

Hey! How's it going? After some days off, we are starting to work again on the payments specification, but before, we thought it would be good to introduce a formal process to introduce enhancements to ContextVM. We created a CEP guidelines document where we propose and describe this process. The goal is to keep the main specification well-defined and clean, and to document enhancements in different documents, similar to NIPs but for CVM. This way, enhancements like server public announcements, encryption, and payments can be placed in their own documents, and we can track updates and the status of enhancements more clearly. Please read the proposal we just created and provide feedback. -

GitHub

docs(cep): introducing ceps guidelines by gzuuus · Pull Request #3 · ContextVM/contextvm-docs

Summary This PR introduces comprehensive guidelines for ContextVM Enhancement Proposals (CEPs) to establish a formal process for proposing and disc...

Preview - https://contextvm-docs-git-cvmeps-contextvms-projects.vercel.app/cep-guidelines/

Just released an update to the ContextVM website. This one adds a search bar to easily filter servers or assist you in connecting to private servers. In the video, you can see how we test this by deploying an MCP server on a computer, taking its public key, and connecting and using it on a different machine—just that easy ✨ Also, all communication is encrypted and giftwrapped; no one can tell what is happening. Be your own infrastructure

This is a beautiful table, isn't it? https://www.contextvm.org/faqs

We're thrilled to announce the launch of the new ContextVM website, live at https://contextvm.org ! 🚀 This marks a significant step in our mission to create a sovereign, resilient, and open marketplace for computational tools and services. The new site makes it easy to discover, connect to, and use ContextVM servers. Key features include: - Discover Public Servers: Explore publicly available ContextVM servers shared by the community. - Connect to Private Servers: Seamlessly connect to and use your own private servers from anywhere. Currently there are two public servers running: DuckDuckGo search to perform searches and fetch websites, and NostrBook MCP with documentation about nostr, nips, kinds and more. You can test them now, they are open to everyone Check out a short demo of the site: Read more about the launch on our blog post: https://www.contextvm.org/blog/releasing-new-site The site includes a Blog, About page, FAQ, and dedicated documentation at docs.contextvm.org. The entire website is open source, built with Svelte 5 and the applesauce Nostr library. We welcome contributions from the community. We're also looking for talented designers to help shape the future of the ContextVM interface. If you have experience in UI/UX design and believe in a more open, permissionless internet, we'd love to hear from you. Get involved: * Explore the new website at https://contextvm.org * Contribute to the project on GitHub at

GitHub

ContextVM

The intersection of Nostr and MCP. ContextVM has 22 repositories available. Follow their code on GitHub.

* Join the conversation in our Signal group:

Signal Messenger Group

Follow this link to join a group on Signal Messenger.

For any questions or help, please don't hesitate to get in contact.

@Paul created HyperNote, which allows users to create interactive experiences embedded within nostr notes 🤯 These can be thought of as nostr mini-apps published as nostr notes 🤯🤯 It also demonstrates how ContextVM can be used to add custom interactive logic to a HyperNote, all embedded and published as a single note 🤯🤯🤯 The possibilities are endless View quoted note →

Next week we will launch the new ContextVM website 🚀🚀 Stay tunned

ContextVM lets anyone run and use Model Context Protocol (MCP) servers over Nostr. In practice, that means MCP clients can connect to MCP servers through Nostr relays—securely, without central gatekeepers, from any device with an internet connection. Think of it as a thin, elegant transport layer: we don’t replace MCP; we free it. By moving identity, discovery, connectivity, and payments into a decentralized fabric, ContextVM makes MCP truly permissionless and globally accessible.

Thank you, @Dustin Dannenhauer for sharing this article. We are honored that the work we are doing with ContextVM is inspiring others in the ecosystem. 🦾 View article →

Proposal for ContextVM Payments We're enhancing the payment system for ContextVM and its TypeScript SDK to create a flexible and robust framework that supports multiple payment methods like Bitcoin, Lightning, Cashu, and we are looking for some feedback. Here’s our current progress: We propose introducing a `payment_method` field to clearly identify the payment method used in payment request notifications, aligning with the W3C Payment Method Identifiers (PMI) specification. This ensures interoperability and future-proofing, making it easier to support various currencies and payment systems. Payment identifiers will look like `bitcoin-lightning`, `bitcoin-lightning-bolt11`, or `ecash-cashu`. On the SDK side, we propose a modular architecture with `PaymentHandler` and `PaymentProcessor` interfaces for client and server transports, respectively. This approach allows different payment methods to coexist seamlessly, enabling users to implement their own payment methods by adhering to these interfaces. However, we face some challenges. One main hurdle is handling mismatching payment methods between clients and servers effectively. To address this, we propose maintaining an array of payment handlers or processors, each satisfying a standard interface and specific to a payment method. For example, a server supporting both Lightning Network (LN) and Cashu would be initialized with [LNPaymentProcessor, CashuPaymentProcessor], while a client supporting only LN would be initialized with just [LNPaymentHandler]. More info in the linked issue below We invite you to review our progress and provide valuable feedback: ContextVM Spec PR:

GitHub

Payment Method Identifiers by gzuuus · Pull Request #2 · ContextVM/contextvm-docs

Scope and Motivation The primary goal of this pull request is to enhance the payment handling section of the ContextVM protocol specification by im...

ContextVM ts-sdk:

GitHub

Feat: add payments to sdk · Issue #6 · ContextVM/sdk

Add payment handling for client and server transports Client transport Server transport Handling Multiple Payment Methods in a Modular Architecture...

Your insights and suggestions are crucial in helping us overcome these challenges and shape these updates. Let's build a better payment system together!

Thank you to everyone who joined the call today! It was a great conversation. We covered: - Spec overview - SDK overview - A demo of a traditional MCP host client communicating with an MCP server over Nostr - A discussion about possible use cases. - Discussion about Paid MCP - Q&A

Well, well! Today we will be celebrating our first community call. If you are interested in ContextVM, MCP, Nostr, Bitcoin, or any related topics, join the conversation. - When? 16:00 UTC - What? An introduction to the spec, current tooling, next steps, and questions and discussions about other topics. - Where? HiveTalk

HiveTalk

ContextVM Community Call

First community call to discuss about ContextVM. Jul 25 @ 16:00 utc

New version of the TypeScript SDK v0.1.12 This release includes a reconnection mechanism with exponential backoff, removal of direct access to the private key in the 'privateKeySigner', structured logging, handling of ill-formed or invalid JSON, and improvements to the reconnection logic with resubscription. These enhancements make the SDK more robust. Changelog: - ee82a52: feat: improve relay reconnection handling with subscription persistence - eecd6af: fix: handle malformed json content in nostr events gracefully - dd8f444: feat: implement structured logging system with configurable levels - c18f47c: refactor: nostr signer with nip44 encryption and remove direct secret key access - 636b197: chore: bump deps - d5fd1a8: feat: add message validation and relay reconnection with exponential backoff

"Today, Big Tech is repeating the mistakes from the internet’s early days. Instead of using AI to serve people, they’re turning people into products — and using AI to accelerate the surveillance-capitalism business model built on advertising, data harvesting, and exploitation."

Proton

Introducing Lumo: AI where every conversation is confidential | Proton

Lumo gives you the power to solve problems big and small, while keeping your personal data confidential. Try it now.

Yes, we couldn't agree more! View article →

We just wrote an article explaining why we are working on ContextVM. We are just starting, and our first communications were directed to developers. However, we thought it was important to share what motivates us. View article →

This CLI programs enables you to use ContextVM with any existing MCP client or server. The proxy enables you to access MCP via Nostr using any client, including Claude Desktop/Code, Goose, Cursor, and others. The gateway allows you to expose any existing MCP server through Nostr, reducing the barrier between ContextVM and any MCP system. The CLIs are multiplatform and run on Linux, Windows, and macOS. View quoted note →

We plan to release some demo videos tomorrow. Stay tuned! 🚀 View quoted note →