<unnamed>

Public Key

npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm

Profile Code

nprofile1qqsxkduqau5h9eeaxu9cfgl9rea2nt35haqjjwxul0vuta3myg2pdjqpr9mhxue69uhhyetvv9ujumn0wd68ycmgv43kktndv5q3zamnwvaz7tmj9ej8vmtrwqhxvatwqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsz9thwden5te0wfjkccte9ehx7um5wghxuet5qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqpz4mhxue69uhhwmm5wgh8yetvv968ytnc09aq4903yd

Publishing to

Last Notes

2026-09-24 16:03:37 UTC

Powerful
#nevent1q…5fzr

2026-09-22 13:18:33 UTC

Awesome project! Napplets are already quite powerful. Giving them backends through CVM for multiplayer capabilities, leaderboards, and more, makes them even more powerful.
#nevent1q…mkng

2026-09-21 07:57:35 UTC

- reply

Yea right? To be integrated you either need to speak fips or have a network interface for it. If I'm wrong please correct me and excuse my ignorance 🙏🏻

2026-09-18 08:43:02 UTC

- reply

These are different things. FIPS = networking layer, CVM = application layer. FIPS needs a native integration/network adapter, CVM just use regular relays. Different tools

2026-07-27 10:01:26 UTC

Continuing with our community appreciation round, Cordn is one of the apps at the forefront of what we’re building at ContextVM. This is one of the most exciting projects related to sovereign and private communications in the space as well.
What makes Cordn stand out at the edge of what’s being built at CVM is that it was one of the first real apps to use our Open Streams (CEP-41) feature, which allows them to directly stream new messages to users, so they receive them in real time. They’ve helped us catch edge cases and issues, and now the CVM implementation of Open Streams is more robust in the TypeScript and Rust SDKs. Thanks!
Aside from that, they’re also one of the first consumers of the UniFFI bindings we recently released from our Rust SDK. They built their app with native Kotlin modules for their notification service using the bindings from our Rust SDK, and it’s working flawlessly so far.
Thanks to the @npub1qc8…twss and @npub1c0r…0tlv teams for pushing forward the boundaries of what’s possible in this space!
#nevent1q…msxf

2026-07-18 11:01:00 UTC

This is a very cool concept from @npub1fct…eavj so many cool possibilities
#nevent1q…vnng

2026-07-18 11:00:14 UTC

- reply

Awesome concept!

2026-07-17 10:10:29 UTC

- reply

That's great! Looking forward to keep testing. Btw TEP-8 is CEP-8 (the cvm payments standard), or something else?

2026-07-16 14:00:52 UTC

@npub18px…p2py is one of the Summer of Bitcoin students working with us at ContextVM. He wrote this great article about his experience during this period. Give it a read! 😊
https://blog.summerofbitcoin.org/routing-agentic-computation-over-nostr/

2026-07-16 12:10:45 UTC

- reply

From our implementation, it can request to create invoices to top up funds when they run out. It can also access the balance, so it has a complete API to manage its wallet.

2026-07-03 14:24:47 UTC

Do you know you can find all the ContextVM-enabled MCP servers listed on our website?
You can also try them directly through our LLM chat!
Check them out!
https://contextvm.org/servers

2026-07-02 14:39:14 UTC

Building in FOSS is beautiful and powerful. Everything you do can impact upstream dependencies and downstream users alike.
For example, we recently shipped an improvement to the official MCP rust-sdk repository.
We are making the foundations on which we are building stronger!

2026-07-01 16:05:26 UTC

What is ContextVM?
A transport layer for MCP over the Nostr network. An open communication network built on cryptographic, censorship-resistant, and permissionless foundations!
https://contextvm.org/

2026-06-30 14:42:01 UTC

Take a look at our recent demo on how to use our new LLM chat interface as a music research tool, by leveraging the WaveFunc MCP server.
Try it out for yourself!
https://nostr.at/nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqsvz0vz4g3ghvx6vttut462swy5v50dk5c5qv6gketrathnejfhcqsqa0cr
#nevent1q…a0cr

2026-06-29 14:45:28 UTC

Our team is currently looking into CVM Bundles .cvmb, a packaging format to easily distribute servers and provide one-click deployment. The spec and implementation we are working on is inspired by .mcpb conventions by the official MCP working group
https://github.com/ContextVM/cvmi/pull/4

2026-06-24 15:02:50 UTC

ContextVM Rust SDK 0.2.0 is out! 🚀
MCP over Nostr just got a whole lot more capable. Three big things landed today:
📦 Oversized transfers (CEP-22)
Until now, messages were capped by what fits in a single Nostr event (around 65 KB). Larger payloads, like big tool results or resources, now split into chunks automatically, get verified end-to-end, and reassemble on the other side. Servers only do this when the client supports it, so older clients keep working.
🌊 Open-ended streaming (CEP-41)
A server tool can now send a live stream of data back to the client while a request is still running, think progress, partial results, or log lines. The client reads it as an async stream, and the final normal response still arrives at the end. Streaming is negotiated automatically with clients that support it.
🌍 UniFFI bindings, write ContextVM in your language
The SDK now ships bindings for Python, Swift, Kotlin, and C/C++, all built on the same Rust core. That means native support on mobile, backend services, and scripting runtimes. There's a runnable examples/python/ folder to get you started.
Plus: smarter relay resolution (CEP-17), richer server announcements (CEP-6), optional human-friendly server profiles (CEP-23), progress-aware request timeouts, and an MSRV bump to 1.88.
Huge thanks to @npub1alj…g9jp for the job on uniffi bindings, and @npub1knd…cqxa for all the hard hork!
Ready to build on this? Read the docs and ship your first ContextVM server or client today: https://docs.contextvm.org/

2026-06-24 14:30:04 UTC

And we have more news for today… hold on tight!

2026-06-24 14:24:09 UTC

The latest issue of our CVM World is out, with so much news, this one is packed! 📦
If you like the work we’re doing, please consider subscribing to our biweekly newsletter. You could also contribute or donate some sats. Every little bit counts! 🫶
https://contextvm.substack.com/p/the-benefits-of-foss-the-contextvm
#naddr1qv…r8mn

2026-06-24 09:20:07 UTC

You can also use the SkateSpots server through the https://contextvm.org/chat interface 🛹
https://npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm.blossom.band/10b88fcaca19c3f79a28f7205b258a1305f0deed09f82f2361cb462d5068d290.mp4
#nevent1q…lu7w

2026-06-23 16:10:13 UTC

CEP-8 can now talk directly to AI agents. 🧵
With the just released ContextVM SDK 0.13.0 we're shipping full support for a new CEP-8 mode called Explicit Payment Gating.
Why we built it:
CEP-8 already let servers charge for their tools and capabilities, but only "behind the scenes", payment was handled silently by the transport layer. That's great for a wallet app. It's not great for an AI agent that actually needs to decide whether a call is worth paying for.
The fix:
Agents reason through normal MCP responses, so we turned payment into one. Now a paid call returns a clean "Payment Required" error (-32042) that carries human-readable instructions and one or more payment options. Feed that straight to your LLM, it reads the instruction, pays the invoice its own way, and retries the same call. No special SDK knowledge required, and it works with any MCP-compatible agent runtime.
This design is based on the MPP spec and inspired by HTTP's 402 Payment Required status code, a long-reserved error code for exactly this idea, now adapted for JSON-RPC and AI agents.
What it unlocks:
- AI agents that natively understand and handle paid MCP capabilities
- Per-call budgets and consent at the agent layer
- Payment as a first-class decision: pay, decline, or escalate to a human
Under the hood, each successful payment grants a single-use authorization that's matched to the exact same request on retry, and a "Payment Pending" error (-32043) keeps verification from spamming invoices.
Fully backward compatible, the existing silent "transparent" flow stays the default, so nothing breaks for current users.
Try it:
Upgrade to @contextvm/sdk 0.13.0 and turn on a paid capability with explicit gating.
Docs:
CEP-8 spec — https://docs.contextvm.org/reference/ceps/cep-8/
Explicit gating guide — https://docs.contextvm.org/how-to/payments/explicit-gating/
API reference — https://docs.contextvm.org/reference/ts-sdk/payments/explicit-gating/
Go build something agents can pay for. 🔌
#ContextVM #MCP #AI #Bitcoin #Lightning #Nostr

2026-06-23 10:09:09 UTC

This is also a great example of what CVM allows, a full CVM server running in a browser tab! 🤯
#nevent1q…7w22

2026-06-22 14:12:08 UTC

ContextVM makes it easier to deploy your self-hosted infrastructure — No domains, no OAuth, no port forwarding!

2026-06-19 14:16:58 UTC

🚀 @contextvm/mcp-sdk 1.30.0 — 41% smaller bundles, opt-in validation
New patch for our lightweight stdio-focused MCP SDK fork. Two lightweighting wins, zero protocol changes:
📦 Tarball: 2.4 MB → 1.2 MB (−50%)
Dropped unreferenced CJS type declarations and source maps that were shipping but never used.
🗜 Consumer bundles: −41% gzip
- Client + stdio: 90.4 → 53.1 KB
- McpServer + stdio: 97.6 → 60.1 KB
The big win: JSON Schema validation (ajv) is now opt-in. Most apps define tools with Zod (validated natively) but never actually validate the JSON Schema they receive over the wire, so they were shipping 37 KB of ajv for nothing. Now ajv only lands in your bundle if you explicitly need it.
No breaking protocol changes. McpServer's own tool input/output validation is untouched. Existing apps that relied on default validation just need to pass the validator explicitly to re-enable it.
⚡ Smaller install, smaller apps, same CVM.
Alongside this new release, we’ve published a new version of our TypeScript SDK (@contextvm/sdk@0.12.4), which includes this lightweight MCP SDK along with other fixes for open streams

2026-06-18 15:05:23 UTC

Have you already tried our new website chat? This chat connects directly to MCP servers exposed through ContextVM, using your favorite LLM!
https://contextvm.org/chat

2026-06-17 20:58:42 UTC

We just got a PR merged into the official MCP Rust SDK! Contributing to upstream feels good man! 😎
https://github.com/modelcontextprotocol/rust-sdk/pull/858

2026-06-17 14:37:47 UTC

We recently released a new version of our TypeScript SDK, v0.12.0!
For this version, we forked the official MCP ts-sdk and stripped out all unnecessary dependencies for our project. Many features, such as HTTP transport are useless in ContextVM!
Check it out!
https://github.com/ContextVM/sdk/blob/master/CHANGELOG.md#0120

2026-06-17 11:24:50 UTC

- reply

@npub182j…m4rf

2026-06-17 11:24:28 UTC

Now researching about Angine de Poitrine:
https://npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm.blossom.band/f3349880f2f98db065042614e394de274f2aa78c9e7640f864fd302b008f96b5.mp4
#nevent1q…a0cr

2026-06-17 11:04:35 UTC

This is another brief demo of our latest chat interface at https://contextvm.org/chat.
This time, we're connecting to the https://wavefunc.live/ metadata server, which gives you useful tools for searching music metadata using the MusicBrainz API. We searched for Nina Simone. Pretty cool, to be honest. This is a great music research tool.
https://npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm.blossom.band/8d00a1dd988a85bc4aa8d247707bde59a3e5c43e6ba55cf1e047f68e3d71c4ff.mp4
If you want to test this, just open https://contextvm.org/s/bb0707242a17a4be881919b3dcfea63f42aacedc3ff898a66be30af195ff32b2 , connect to the server and navigate to the chat route

2026-06-16 10:03:35 UTC

Also, if you want to chat, share, or clear any doubts, we have a group on Signal and also on Discord. Feel free to join!
https://cordn.net/chat/3f5a6278-a38e-4079-840f-4e7523773f38?m=eyJuYW1lIjoiQ29udGV4dFZNIn0%3D
https://signal.group/#CjQKIOgvfFJf8ZFZ1SsMx7teFqNF73sZ9Elaj_v5i6RSjDHmEhAB3wO1Rg-0gLNdusnb3wLR
#nevent1q…u29n

2026-06-16 09:59:48 UTC

We’ve just updated our documentation https://docs.contextvm.org to follow the https://diataxis.fr , which aims to bring more clarity and structure to it. We’ve also added documentation for the Rust SDK we recently released.
https://npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdm.blossom.band/7bd1c1ba7765f47fe8cf150922f09b5ca754671d288f7733856300a54e86ccbb.png
Additionally, remember that we also have Skills to provide all necessary CVM documentation to LLMs.
Happy building! 🚀

2026-06-15 15:25:10 UTC

ContextVM makes it easier to deploy your self-hosted infrastructure. No domains, no OAuth, no port forwarding!

2026-06-12 14:28:16 UTC

Spectr, a Nostr-powered client, is now powered by Relatr and ContextVM!
Check out this video to see how it works!
#nevent1q…zf2e

2026-06-12 14:23:25 UTC

New version of the ts-sdk 0.12.0 🗜
For this version, we forked the official MCP ts-sdk and stripped out all unnecessary dependencies for our project. The official SDK comes with many dependencies related to HTTP transports and other unnecessary features for CVM. We simply removed all that fat to reduce the number of dependencies (from 17 down to just 5). This is especially beneficial for lightweight and web clients.
If you want to read more about this fork and what specifically was removed check https://github.com/ContextVM/mcp-sdk/tree/v1.x
There are no other changes besides this. Hope you enjoy the slimmer builds! 🗜

2026-06-11 14:16:28 UTC

The ContextVM website is quickly becoming the most comprehensive demo of what our protocol enables!
Recently we added a LLM chat that allows you to directly connect to servers and use and LLM to use them.
https://contextvm.org/chat
#nevent1q…mre6

2026-06-10 14:06:56 UTC

Are you providing any service over MCP? Learn more about ContextVM, and see for yourself how easy it is!

2026-06-09 14:22:28 UTC

New issue of the CVM World. This is the 10th edition.
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.
Hope you enjoy reading it 🫶
#naddr1qv…25vp
https://nostr.at/naddr1qvzqqqr4gupzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uqqwcmkd4mj6vfsx825vp

2026-06-08 16:24:55 UTC

- reply

Sorry, wrong tag. @npub18px…p2py is the right one 🙏

2026-06-08 16:21:30 UTC

Very pumped to introduce the LLM chat on the contextvm.org website!🚀
https://contextvm.org/chat
It's been long overdue, but we've just released the new version of our site, 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.
You can BYOK or use the free models, though be aware the free models are somewhat unstable, and we highly recommend plugging in your own key or connecting to your local Ollama instance. Any API with an OpenAI-compatible interface will work.
You can test public servers or connect to your own private CVM servers.
Here are some demos:
- Using Wolfram alpha and open meteo to calculate the distance between Madrid and Barcelona, and the weather forecast:
https://video.nostr.build/d2d61f6b9d548ed1d3fc643363d8a3f1951687d636465e99fe19ea63c6a6d502.webm
- Using Tenor api to find the funniest cat GIFs
https://video.nostr.build/0a08fb465ccbceccb85b8eb99196a1eedd782225d9344de00bc3f8697e3de860.webm
- Using Relatr to search for Jack and explain why the score
https://video.nostr.build/07167a800b190cd408ba2f39d661a8332677a12a217acee39efb4e00d013f678.webm
This is the agentic web in action. Hope you like this update, and please report any issues if you find them.
Huge thanks to @npub10hx…wtt6 for moving this forward.

2026-05-29 05:29:34 UTC

Ephemeral gift wraps have been merged into the nips repo! 🚀
https://github.com/nostr-protocol/nips/blob/master/59.md

2026-05-29 05:25:24 UTC

- reply

This is awesome!🔥

2026-05-26 10:38:22 UTC

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

2026-05-25 17:32:40 UTC

This is very cool. Very innovative way to use ContextVM and it's latest updates 👀
#nevent1q…kvhm

2026-05-14 14:47:02 UTC

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

2026-05-12 11:59:51 UTC

- reply

The list on contextvm.org isn't manually filtered, it just pulls from whatever relays are configured in the web app. You can see and change those relays by clicking the relay icon in the bottom left corner of the site.
https://image.nostr.build/5bfd4b857ddb75bab3255f84f2ab6df0f683b7490bcdd78d1592be560d04d47e.png
So if you announce your server to the same relays that the site is watching, it'll show up automatically. If you're announcing to different relays, it won't appear unless you add those relays to the site's configuration.
Hope this clears your doubt, don’t hesitate if you need more clarification.

2026-05-11 20:48:43 UTC

- reply

Yes! LG 🔥

2026-05-11 20:48:10 UTC

- reply

They are self announced in relays. It was one of the first extensions to the protocol :)
https://docs.contextvm.org/spec/ceps/cep-6/

2026-05-10 13:36:00 UTC

This is an amazing idea, CVM being used to run state machines 🤌
#nevent1q…ysc8

2026-05-08 14:44:48 UTC

- reply

Thanks 💛
It’s still early days, we have a lot of work ahead introducing the other CEPs, for payments and so on. But this is a great foundation: all the core specs are in place, together with encryption and stateless operations.

2026-05-08 14:35:24 UTC

🔥 Great news! 🔥
We’ve just released the Rust SDK for CVM: https://github.com/ContextVM/rs-sdk
This is a big step forward for the ecosystem. Until now, the TypeScript SDK, our reference implementation, has been the only one available. With Rust, CVM now expands into native development, opening the door to new use cases, better performance, and future bindings for other languages.
The Rust SDK follows the same architectural principles as the TypeScript SDK. It builds on the underlying RMCP SDK for protocol compliance and adds a Nostr transport on top.
The 0.1.x release lands with the core spec in place and support for CEP‑4 Encryption, CEP‑6 Server Announcements, CEP‑19 Ephemeral Gift Wraps, and CEP‑35 Stateless Session Discovery and Capability Learning.
This release also sharpens the SDK strategy: TypeScript remains the reference implementation for web and desktop, while Rust becomes the foundation for native development and future FFI bindings. The repository already includes docs and examples, with skills, and more documentation coming soon to docs.contextvm.org.
It also ships with a strong test suite and interoperability coverage between the TypeScript and Rust SDKs, so it already feels robust.
That said, this is still a beta release, and we’ll keep testing and pushing it further. You can follow the current parity status between both SDKs here: https://github.com/ContextVM/rs-sdk/issues/64
🧑‍💻 Install it with `cargo add contextvm-sdk`.
Huge shout out to our students from Summer of Bitcoin, @npub1knd…cqxa who leaded the development of this release, and @npub10hx…wtt6 , also to @npub1zc6…25sl for putting together the very first version. We’re grateful for the community effort behind this 🫶
We hope this SDK unlocks a new wave of development across the CVM ecosystem. Now let’s keep building 🚀🚀
Repo docs: https://github.com/ContextVM/rs-sdk/tree/main/docs
Repo examples: https://github.com/ContextVM/rs-sdk/tree/main/examples

2026-05-07 14:41:21 UTC

- reply

Glad to see nanalytics working great!

2026-04-28 15:49:26 UTC

- reply

It is a protocol that brings Nostr as a transport for MCP. You can learn more at https://contextvm.org

2026-04-21 21:05:11 UTC

- reply

Yes, that is a fascinating example. CVM is not the provider; it just provides the tools. The LLM comes from your own endpoint, so you basically bring the LLM to Earthly, and it already has the platform tools available thanks to CVM.

2026-04-21 21:03:20 UTC

- reply

You plug the MCPs into the LLMs, so you can run inference from whichever source you prefer. It’s like giving the LLM or agent some tools. The tools are described and can be invoked through the MCP. In any agentic framework, such as Claude Code, Cursor, or any other, you can configure which MCPs you’ll provide to the LLM.

2026-04-21 19:30:25 UTC

- reply

ContextVM uses MCP under the hood for the request and response schemas, and MCP is a “native” LLM API. Consequently, it can provide capabilities for LLMs, while also allowing you to build a UI around these services so they can be used by humans through interfaces.
You can learn more at https://contextvm.org and https://modelcontextprotocol.io/

2026-04-21 16:40:42 UTC

- reply

It’s up to the imagination. That is a right association, tho. It also references the DVM standard, where “VM” stands for “Vending Machine”

2026-04-16 17:09:49 UTC

- reply

Yes, we just finished, weird. Sorry for that

2026-04-09 11:42:23 UTC

Wow someone made a pod from the article we wrote yesterday for the new version of Relatr! This is awesome ♥
https://unsaltedbutter.ai/listen/Ae2zCl4qvIDUXjq3
#nevent1q…3cyd

2026-04-06 18:37:10 UTC

ContextVM TS SDK 0.8.0 is live, with CEP‑22 oversized‑payload transfer.
Large payload delivery over Nostr relays is now much more robust. We even stress‑tested it by pushing a 1.5 MB image over regular relays, partly to check robustness and partly for fun :) It worked, but keep in mind that this is not a general‑purpose file transfer protocol
If you run a server or client on the TS SDK, update to 0.8.0. The CVMI CLI was also bumped to include it.
We keep pushing boundaries 🚀
If you are curious about the underlying specification you can read it here: https://docs.contextvm.org/spec/ceps/cep-22/

2026-04-06 17:44:36 UTC

Communications over the internet has been centralizing more and more since its very beginning, choked by permissioned control points. The risk we foresee is that the agentic web can fall in the same trap.
ContextVM actively breaks this monopoly by routing the Model Context Protocol (MCP) over Nostr's decentralized relay network, leveraging censorship-resistant public keys that no single entity can shut down or revoke.

2026-04-01 14:58:23 UTC

Curious about which services are already leveraging ContextVM?
On our website you can find a list of public server to which your AI agent can connect through our infrastructure! 👇🏻
https://contextvm.org/servers

2026-03-31 17:11:53 UTC

- reply

Thanks 💛

2026-03-31 16:09:46 UTC

In today’s update we cover the latest news from ContextVM. In particular, we have been chosen to mentor the next generation of open-source contributors through the Summer of Bitcoin internship program 🚀
We also cover our latest modification to the CVM website and the spam attack that recently hit our relays.
Read the full article to learn everything going on in the CVM World!
https://contextvm.substack.com/p/mentoring-the-next-generation-the
#naddr1qv…gz9c

2026-03-30 19:47:42 UTC

We bring amazing news! ContextVM has been invited to participate in the Summer of Bitcoin program. https://www.summerofbitcoin.org/
This is a global, online summer internship program focused on introducing university students to Bitcoin, Nostr, and open-source development and design. We’re very glad to have been chosen as mentors.
We’d also be grateful to hear your project ideas for a student to work on for ContextVM during the summer. Please share any you have. What would you like to see in ContextVM?

2026-03-27 13:39:04 UTC

🚀
https://contextvm.org/s/nprofile1qyd8wumn8ghj7un9d3shjtnrdah8getcw3mx6tn0wfnj7qpqvk3nfvp0tyfu7tqlwvmkq3xlzyj5zen8de75n8gvxn3v5yx08ctq06sg4p
#nevent1q…rfna

2026-03-22 11:06:57 UTC

- reply

There is loads of garbage, that's why we hardened the writing policies, also connections openning too many reqs concurrently. It is working great so far

2026-03-22 10:28:48 UTC

- reply

Basically we replaced the relay we were using with Strfry and hardened some writing rules. Strfry also has some sane abuse protection out of the box.

2026-03-21 19:39:48 UTC

Lazy yet productive Saturday. Stabilized relays from the spam attack and forked Strfry during the process. Contributed to https://ants.sh by @npub1der…xzpc to add relatr for search capabilities. Touched grass

2026-03-21 16:33:08 UTC

🚀
#nevent1q…3u3s

2026-03-21 11:55:07 UTC

This should be fixed now 🫡 As a side effect, we forked Strfry to add a convenient way to deploy a relay and some write policies to harden it for CVM usage. https://github.com/ContextVM-org/strfry-cvm
#nevent1q…0mym

2026-03-18 17:37:39 UTC

- reply

Hmm, what is your Node version? Some older versions might not have ws defined globally. In any case, we just pushed a new version of cvmi that polyfills this. Please test 0.2.6 and let us know, your feedback will be greatly appreciated 🙏

2026-03-11 23:07:19 UTC

- reply

LG! 🚀

2026-03-11 22:49:55 UTC

- reply

We'll write a spec draft soon so we can move forward with that :)

2026-03-10 15:51:32 UTC

- reply

Just wow! This is seriously cool. I think you did the first integration of chat with CVM tools on the web to date. Really awesome!

2026-02-25 08:37:29 UTC

- reply

Looks dope!

2026-02-22 10:19:22 UTC

- reply

Yes!

2026-02-17 14:59:11 UTC

- reply

Let's keep building! 🚀

2026-02-17 14:58:48 UTC

- reply

Thanks Tim! appreciate your words 💛

2026-02-17 14:46:26 UTC

Thanks so much to openSats for this opportunity! We'll keep pushing the boundaries of this new paradigm 💛
#nevent1q…hxrk

2026-02-13 08:32:03 UTC

- reply

LFG! 🔥

2026-02-12 22:15:59 UTC

This is why CVM.
In an agent-mediated world, the shipped feature set matters less than what an agent can discover and compose at runtime. Your real product becomes your callable surface area: reliability, clear schemas, predictable behavior, and the ability to snap into workflows you didn’t design.
That shift makes distribution the new battleground. If discovery collapses into a handful of registries and default tool lists, the ecosystem recentralizes fast, no matter how open the API spec looks.
You can already see the gravity well: MCP’s mainstream path tends to reintroduce old control points, registries anchored to domains, OAuth-based access, and platform-shaped “approved” directories. They’re convenient, but they harden into gatekeeping, and single points of failure.
ContextVM is built to route around that. It runs MCP over Nostr so services are addressed by public keys, routed over relays, and announced publicly without permission. Discovery becomes a network primitive instead of a platform feature. Relays act as decentralized repositories, and curation becomes competitive and plural rather than owned.
We’ve just added payments in a way that composes cleanly with autonomous, per-call usage. If agents can swap tools mid-workflow, pricing has to be as modular as the capabilities themselves, without dragging builders back into accounts, gatekeepers, and permissioned land.
ContextVM’s wager is simple: if agents are going to assemble the future on the fly, the underlying rails for identity, discovery, and payment must be open, permissionless, and censorship-resistant by default.
#nevent1q…cyqu

2026-02-09 16:51:56 UTC

- reply

Great! can you open a pr?

2026-02-09 16:19:32 UTC

- reply

Well, there is no need to add methods for topping up the wallet/nutstash. We should assume the wallet is already plugged in and has funds. If you read CEP-8, the responsibilities of servers and clients are clarified there. tldr; Servers act as payment processors, emitting payment requests and then validating that the payment was done. Clients act as payment handlers, being responsible for paying the requests emitted by the server. The funds that the wallet has available are a separate matter and are better kept out of scope, so there is no need for deposit or withdraw methods.
A way this could work is as follows: the server (payment processor) receives a request for a paid capability. It then goes to the mint it has configured, gets a quote, obtains the BOLT11 invoice from it, and sends the payment request. The client (payment handler) takes the BOLT11 invoice, gets a melt quote for it, and the mint handles the payment. At that point, the server can check its quote status and verify if it's fulfilled. Then the lifecycle is completed. Extra steps could include redeeming the tokens from the quote and storing them either locally or in the NIP-60 wallet.
What do you think?
If there are some concepts that are not clear, we have written a couple of guides and resources to understand how payments work in CVM:
Payments, Paid Servers, and Clients https://github.com/ContextVM/sdk/blob/e2096b7c94658e1f7b5a3f06ad53738d1e3eacea/docs/payments-paid-servers-and-clients.md
Payments Architecture https://github.com/ContextVM/sdk/blob/e2096b7c94658e1f7b5a3f06ad53738d1e3eacea/docs/payments-architecture.md
There is also the spec CEP-8: https://github.com/ContextVM/contextvm-docs/blob/8d0dbfc95a929ac6dd49cab556b18874df758b73/src/content/docs/spec/ceps/cep-8.md
Happy to solve any doubts if you have any!

2026-02-09 15:31:21 UTC

- reply

I haven't checked the dependency tree to be honest. But if you feel comfortable with nostr-tools and there is no need for other new deps, it is preferable. If not, maybe the best option is to create a separate repo for extra payment processors and handlers.

2026-02-09 15:23:44 UTC

- reply

Exactly https://applesauce.build/money/wallet/package.html https://applesauce.build/examples/#/example/wallet/wallet

2026-02-09 15:12:32 UTC

- reply

Amazing! we have nostr-tools as dependency as well. Thanks 🚀💛

2026-02-05 16:38:36 UTC

CVMI 0.1.9 is out. It includes two minor but necessary features: normalizing quoted command strings so you can pass commands to serve any MCP server inside quotes (e.g., `cvmi serve "npx -y …"`), and adding environment‑variable support to the spawned MCP server using flags such as `cvmi serve -e LOG_LEVEL=debug …`. They aren’t the flashiest features, but they are essential for real world scenarios. Thanks, @npub1ye5…knpr, for pointing them out 🚀

2026-02-05 09:20:07 UTC

- reply

Hey, yes, these servers are offline. We are not running them, is the operator, probably @npub1ye5…knpr Sorry for the inconvenience. We should add a function to dummy ping servers so they can display an 'offline' badge. I'm happy to assist further if you need help

2026-02-03 17:20:25 UTC

🗞 Proudly announcing the first issue of our new bi‑weekly newsletter! 🗞
In it we will explore everything related to ContextVM, its ecosystem, MCP news, projects, and everything in between. This inaugural issue was written by @npub1jeq…nmal , who will help us with communication and news. Tuma is not an LLM or a bot, he is a person, and he already writes for other open‑source projects such as Bitcoin Optech, BTC++ Insider Edition, and more. We’re glad to have him on board and happy to welcome more contributors 💛
Hope you enjoy it, we welcome any feedback, now, Let's keep building!🚀
#naddr1qv…zmfy

2026-01-29 14:46:34 UTC

- reply

Hahaha ok, thought it was something new.
We think that as enshittification continues extending its shadow through the internet and digital world, it is going to be more and more valuable for individuals to be able to fully, self organize, associate, collaborate and share their resources. We feel that the infrastructure as a service model that we are seeing more and more is going to be a huge bottleneck and more discriminatory since the heavy computations they offer will struggle with a more democratized demand for the resources. So, the more people, the worse that model scales without sacrificing a competitive environment and becoming a monopoly. At the same time, things are going to get cheaper to run at low scale and people will be able to share the resources they have to satisfy demand at their scale. This vision can be true or not in the future, but it is one of the fundamental whys behind CVM, high bandwidth collaboration between individuals.
If you feel curious about our point of view and ethics you can check our blog, we have some nice articles like https://contextvm.org/blog/forging-a-new-frontier

2026-01-29 12:46:57 UTC

- reply

Thanks! Yes, Nostr is a whole paradigm shift, and CVM is another building block of Nostr that leverages as many of its inherent features as possible. Very powerful.
We would love to know more about that concept of cognitive computing resources you mentioned. Would you mind explaining what it means?

2026-01-29 11:51:32 UTC

- reply

Thanks for your words! We are glad that more people are aware of CVM and the possibilities it brings. If you ever need to clear any doubt please just ping us, we are more than happy to assist. CVM is fully open source and community driven, we all build this together 💛

2026-01-28 20:44:23 UTC

🎇Meet CVMI: the Army knife we are building for ContextVM development🧑‍💻
https://image.nostr.build/c0c7c982104c053e185bcd9522c578233e818e4c2c3ad8668fc395c090e27926.png
If you are building/vibing on Nostr, this is for you. We are shipping CVMI alongside a complete skill set that makes ContextVM development delightful.
The skills cover the entire stack: protocol fundamentals, architecture concepts, client and server development, troubleshooting, SDK internals, and production deployment. Each skill includes working templates, reference documentation, and patterns distilled from real Nostr development. Everything you need to do is `npx cvmi`.
Or grab the skills through CVMI with `npx cvmi add`, or through the skills CLI with `npx skills add contextvm/cvmi`.
These commands will show you the list of available skills and guide you through their installation for any coding platform. Cool, right?
You can also pick exactly what you need `npx cvmi add --skill overview`
CVMI starts as a skills manager, but we are building toward the unified toolkit that ContextVM deserves. One CLI for skills, server interaction, dev tools, the works.
For builders who want to ship. The skills are here now.
https://github.com/contextvm/cvmi
If you don't know what skills are: https://agentskills.io/home
#ContextVM #Nostr #MCP #buildinpublic

2026-01-16 11:08:10 UTC

- reply

Yes, the tricky part is replay attacks. But maybe you can mitigate them using something like NWT https://github.com/pippellia-btc/nostr-web-tokens

2026-01-13 10:02:18 UTC

- reply

Right, that's a good question. There are different factors at play to mitigate that issue. First, we implemented a preserve stale cache policy in case of failure when requesting a rank. This ensures that users who previously had their rank computed successfully maintain their rank, avoiding transient issues due to spam conditions.
This is not a perfect solution, and we still have some edge cases to cover. However, addressing these will require, as you mentioned, some kind of prioritization, which is a more complex task. For now, the more harmful edge cases are covered, and we will continue to think about this to potentially find a better solution.

2026-01-13 09:51:30 UTC

- reply

Hey! Thanks for sharing. Yes, it's an interesting approach, but I have some questions about how Privacy Pass tokens have value or are accepted by different relays. There should be some notion of consensus around the entity emitting these tokens, right? Like bonds, in the case where the issues or the Privacy Pass tokens vouch with its reputation, and that's what makes the PP tokens be accepted. So relay operators should recognize that reputation and allow these tokens to be accepted. How do you imagine this relationship to work? I'm a PP token issuer, and my mission is to grow reputation among relay operators so they accept my PP tokens?
On the other hand, I think that Cashu might be the best fit for this use case since it already can handle some spending conditions like time locks, pay-to-PK, refund paths, and as far as I know, there are some people working to bring zk-proofs to create arbitrary spending conditions. Do you imagine mints and PP token issuers being the same entity, or two separate things, like the mint is used as a 'third party' issuer of Cashu tokens, enforcing spending conditions, and the PP token issuer just issuing PP tokens based on the Cashu tokens you present? I think that other people who might be interested in this conversation are @npub12rv…85vg and @npub1klk…x3vt

2026-01-12 17:40:42 UTC

- reply

Yes, I think it is correct to say that, anyone can write if the bucket assigned to their pubkey is large enough. The publishing capability changes depending on the rank, users with high ranks get more events to publish per day. On the other hand, new npubs can only write one event per day, which must be of kind 1 and without urls in the content. If the reply guy spins new npubs each time, the relay will likely consume them. However, the key point is that this is the current policy we have on the wotr.relayr.xyz instance. You can run your own and tweak it to configure different thresholds and also to enable or disable publishing for users with no rank. You could also disallow anyone from writing below a certain threshold. Together with the ability to self-host your own relayr instance, makes it very customizable to each person's needs and communities. Also, remember that this is an experiment we are running, and so far, it is working great

2026-01-12 09:01:39 UTC

- reply

Hey, that's very interesting. I'm curious to hear more about your approach. Are you basing your solution on something like Cashu, or just LN with hold invoices?
In our case, the solution is much simpler. We use rate limiting to control the load between the relay and the upstream rank provider (Relatr), basically to avoid possible DDoS and load attacks. Initially, we based this rate limiting on IPs, but we noticed that it was penalizing legit users behind VPNs or IP groups. So now, we base the rate limiting on the number of requests per second that the relay can send to the rank provider. It's simpler, more effective, and users are not penalized for being behind an IP group

2026-01-12 08:53:11 UTC

- reply

Roughly 16 users, we are observing common relays to determine how many people have added wss://wotr.relatr.xyz to their relays list. To do this we are using nak with the following command, you can check it on your end as well.
'''
nak req -t r=wss://wotr.relatr.xyz -k 10002 wss://relay.damus.io wss://nos.lol wss://relay.primal.net wss://bitcoiner.social wss://search.nos.today/ wss://nostr.mom/ wss://relay.snort.social/ wss://discovery.eu.nostria.app/ wss://nostr.wine wss://eden.nostr.land | wc -l
'''

2026-01-11 20:38:15 UTC

- reply

Well, the relay is not actively fetching posts from other relays. However, since the relay is open, anyone can broadcast events to it. Some clients will do this when users who have the relay in their list interact with someone else. Therefore, by simply having the relay configured in your list, some clients will rebroadcast certain events. In the end, events can arrive through different means, but there is no active fetching involved