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!
ContextVM
npub1dv…33jdm
2026-02-09 17:19:32 CET
in reply to nevent1q…j4ms
Author Public Key
npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdmPublished at
2026-02-09 17:19:32 CETEvent JSON
{
"id": "e36d8c2770e55771a9d2c76ce8b82d808212b491febaf5db453bbc561c533512",
"pubkey": "6b3780ef2972e73d370b84a3e51e7aa9ae34bf412938dcfbd9c5f63b221416c8",
"created_at": 1770653972,
"kind": 1,
"tags": [
[
"e",
"3fc4e47ce3b8be48888041d0a72edcba73e5bf787d63362fabd873137594c2c3",
"wss://relay.primal.net/",
"root",
"6b3780ef2972e73d370b84a3e51e7aa9ae34bf412938dcfbd9c5f63b221416c8"
],
[
"e",
"008aeec7c748ac23a230ab18c0cdbc69caed96199084c2cb039d6c0de13648fc",
"wss://relay.primal.net/",
"reply",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f"
],
[
"p",
"2f4fa408d85b962d1fe717daae148a4c98424ab2e10c7dd11927e101ed3257b2"
],
[
"p",
"4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f"
]
],
"content": "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.\n\nA 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.\n\nWhat do you think?\n\nIf there are some concepts that are not clear, we have written a couple of guides and resources to understand how payments work in CVM:\nPayments, Paid Servers, and Clients https://github.com/ContextVM/sdk/blob/e2096b7c94658e1f7b5a3f06ad53738d1e3eacea/docs/payments-paid-servers-and-clients.md\nPayments Architecture https://github.com/ContextVM/sdk/blob/e2096b7c94658e1f7b5a3f06ad53738d1e3eacea/docs/payments-architecture.md\n\nThere is also the spec CEP-8: https://github.com/ContextVM/contextvm-docs/blob/8d0dbfc95a929ac6dd49cab556b18874df758b73/src/content/docs/spec/ceps/cep-8.md\n\nHappy to solve any doubts if you have any!",
"sig": "893e0a5379d34fee1e46a4969b1d51db9bb96e7caa6716f2a0aa34cc20da63e24766847e534c9dd02a9d1412ce3d12e3b9cc9766e12517b17e837d5db4cb495a"
}