The discussion about pricing and payments flows (CEP-8) is happening at https://github.com/ContextVM/contextvm-docs/pull/9 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
ContextVM
npub1dv…33jdm
2025-08-31 19:05:40 UTC
Author Public Key
npub1dvmcpmefwtnn6dctsj3728n64xhrf06p9yude77echmrkgs5zmyqw33jdmSeen on
wss://nostr.momPublished at
2025-08-31 19:05:40 UTCEvent JSON
{
"id": "6cb65a16a1d7cf28c4baa3f42ad61593ba871e5dcd81f6841cce3c9af5d60d93",
"pubkey": "6b3780ef2972e73d370b84a3e51e7aa9ae34bf412938dcfbd9c5f63b221416c8",
"created_at": 1756667140,
"kind": 1,
"tags": [],
"content": "The discussion about pricing and payments flows (CEP-8) is happening at https://github.com/ContextVM/contextvm-docs/pull/9 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 💛\n\nPlease join the conversation and provide feedback if you have any; it's highly appreciated",
"sig": "6d4ffa6a2952331c3721444634d97920777e89cc1dfaa90d1089ced881eadcbb4f07b45b0e59b8e7acbbd788d43b268de72b17053ec81a30249c76dd87c20cf3"
}