ContextVM on Nostr: Just shipped some clarity improvements to CEP-8 🎯 We are pretty close to getting ...
Just shipped some clarity improvements to CEP-8 🎯
We are pretty close to getting this done; we just shipped some clarification to the payments spec so some concepts are less ambiguous. The spec now has well-defined PMI (payment method identifier) boundaries, clarifiying what goes in `pay_req`. We've added a recommended PMI registry with precise payload semantics, plus naming conventions to keep things unambiguous as the ecosystem grows.
Also new: optional direct payments for bearer assets. When both parties support it, you can skip the roundtrip, just attach `["direct_payment", "<pmi>", "<payload>"]` to your request and you're done. Good for cashu 🥜
The ongoing implementation remains unchanged, this is all documentation and specification hardening.
Current spec:
https://github.com/ContextVM/contextvm-docs/blob/ed71abec7bd93ba1082e67dfc92f0b0bcf618a72/src/content/docs/spec/ceps/cep-8.mdSDK progress: github.com/ContextVM/sdk/pull/24
Feedback welcome!
Very excited for this 🔥 CEP-8 payments are coming to ContextVM, with a reference implementation in our TypeScript SDK. It is shaping up nicely, with a clean design and implementation. The cool part is that nothing changes for operators; the transports will still work in the same way they do today, with no breaking changes. Payments are enabled through middlewares, so the inclusion of payments will not affect current consumers of the SDK in any way. There will be no performance degradation, no API-breaking changes, and maximum flexibility.
Soon, we will release the new version including the new features, along with some guides on how to start monetizing your services. Stay tuned.
In the meantime, you can read the specification at https://github.com/ContextVM/contextvm-docs/pull/9 and follow the progress of the implementation in the SDK at https://github.com/ContextVM/sdk/pull/24 .
Feel free to give us some feedback or ask any questions!
Published at
2026-02-10 16:31:34 CETEvent JSON
{
"id": "e6e707a0ff7cd78224165bde4a1eb58394ae1a1646be90f5bcffd60a018021da",
"pubkey": "6b3780ef2972e73d370b84a3e51e7aa9ae34bf412938dcfbd9c5f63b221416c8",
"created_at": 1770737494,
"kind": 1,
"tags": [
[
"q",
"040d147825f6a518173896da10e1d3137d24d5a88f28adf93102e9b518637d99",
"wss://relay.primal.net/",
"6b3780ef2972e73d370b84a3e51e7aa9ae34bf412938dcfbd9c5f63b221416c8"
]
],
"content": "Just shipped some clarity improvements to CEP-8 🎯\n\nWe are pretty close to getting this done; we just shipped some clarification to the payments spec so some concepts are less ambiguous. The spec now has well-defined PMI (payment method identifier) boundaries, clarifiying what goes in `pay_req`. We've added a recommended PMI registry with precise payload semantics, plus naming conventions to keep things unambiguous as the ecosystem grows.\n\nAlso new: optional direct payments for bearer assets. When both parties support it, you can skip the roundtrip, just attach `[\"direct_payment\", \"\u003cpmi\u003e\", \"\u003cpayload\u003e\"]` to your request and you're done. Good for cashu 🥜\n\nThe ongoing implementation remains unchanged, this is all documentation and specification hardening.\n\nCurrent spec: https://github.com/ContextVM/contextvm-docs/blob/ed71abec7bd93ba1082e67dfc92f0b0bcf618a72/src/content/docs/spec/ceps/cep-8.md\nSDK progress: github.com/ContextVM/sdk/pull/24\n\nFeedback welcome!\n\nnostr:nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqqsx3g7p976j3s9ecjmdppcwnzd7jf4dg3u52m7f3qt5m2xrr0kvscjppc5",
"sig": "774b5e2ee98c90e2aa54ac6b882ce3579d384e78dff62198b0f677420fc95f3d26049e6659825811851bf78e65d83d2b10b1e937a97b57368527213404c3374f"
}
