Did you know that https://nostr.watch has both a v2 rest API...

sandwich

npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx

hex

5a0f453f7d488d7004fe42b0a82dd89aab750062ac5499834cc8f0db64c44f4a

nevent

nevent1qqs95r698a753rtsqnly9v9g9hvf42m4qp32c4yesdxv3uxmvnzy7jsprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgswwud0pvzu362lehm0av6sq4zd97cue5uy0z8f7jgtk0hz368dvmc5jjmxw

Kind-1 (TextNote)

2026-03-27T12:04:36Z

Did you know that https://nostr.watch has both a v2 rest API with L402/P2PK payments and a CVM with CEP-8 payments? NIP-66 is always free of course, and can derive all of the data from these endpoints. Both have been live but unannounced for roughly ~5 months, running with payments enabled for about a month. The purpose of deploying these was to exercise the deployment of an end-to-end, self-managed payment solution that implements novel payment protocols.

https://image.nostr.build/2db46cac84e491fcf0873be6a2f25041e818cff66f26253dafa03a18e9b8569b.jpg

https://nostr.watch runs its own lightning node, with it's own liquidity management and a private mint for internal use.

Both the CVM and REST API run a @nostrwatch/rstate instance, a state machine derived from aggregate NIP-66 data.

USEFUL LINKS: https://status.nostr.watch https://cvm.nostr.watch
https://api.nostr.watch/v2/

CONTEXTVM SANDBOX: https://www.contextvm.org/s/65a334b02f5913cf2c1f73376044df11254166676e7d499d0c34e2ca10cf3e16

RSTATE SOURCE: https://github.com/sandwichfarm/nostr-watch/tree/next/apps/rstate

LMK if you have issues or feedback.

Disclaimer: Due to the complexity of testing P2PK payments, the stability of the implementation is unknown. However, when I shipped it, it worked beautifully.

Raw JSON

{
  "kind": 1,
  "id": "5a0f453f7d488d7004fe42b0a82dd89aab750062ac5499834cc8f0db64c44f4a",
  "pubkey": "e771af0b05c8e95fcdf6feb3500544d2fb1ccd384788e9f490bb3ee28e8ed66f",
  "created_at": 1774613076,
  "tags": [
    [
      "imeta",
      "url https://image.nostr.build/2db46cac84e491fcf0873be6a2f25041e818cff66f26253dafa03a18e9b8569b.jpg",
      "ox 2db46cac84e491fcf0873be6a2f25041e818cff66f26253dafa03a18e9b8569b",
      "x e653a32138ac9519b6090c13f61635350d4c7327d2a05112c309cefe28d7168c",
      "m image/jpeg",
      "dim 800x611",
      "bh L13IC%B=^QS$}s1d^6SN}q5,=ySh",
      "blurhash L13IC%B=^QS$}s1d^6SN}q5,=ySh",
      "thumb https://image.nostr.build/thumb/2db46cac84e491fcf0873be6a2f25041e818cff66f26253dafa03a18e9b8569b.jpg"
    ]
  ],
  "content": "Did you know that https://nostr.watch has both a v2 rest API with L402/P2PK payments and a CVM with CEP-8 payments? NIP-66 is always free of course, and can derive all of the data from these endpoints. Both have been live but unannounced for roughly ~5 months, running with payments enabled for about a month. The purpose of deploying these was to exercise the deployment of an end-to-end, self-managed payment solution that implements novel payment protocols. \n\nhttps://image.nostr.build/2db46cac84e491fcf0873be6a2f25041e818cff66f26253dafa03a18e9b8569b.jpg\n\nhttps://nostr.watch runs its own lightning node, with it's own liquidity management and a private mint for internal use.\n\nBoth the CVM and REST API run a @nostrwatch/rstate instance, a state machine derived from aggregate NIP-66 data. \n\nUSEFUL LINKS:\nhttps://status.nostr.watch\nhttps://cvm.nostr.watch  \nhttps://api.nostr.watch/v2/\n\nCONTEXTVM SANDBOX:\nhttps://www.contextvm.org/s/65a334b02f5913cf2c1f73376044df11254166676e7d499d0c34e2ca10cf3e16\n\nRSTATE SOURCE:\nhttps://github.com/sandwichfarm/nostr-watch/tree/next/apps/rstate\n\nLMK if you have issues or feedback.\n\nDisclaimer: Due to the complexity of testing P2PK payments, the stability of the implementation is unknown. However, when I shipped it, it worked beautifully.",
  "sig": "be514592a849d974ef6a4eefef4fe62754861dceeb8abedc48f80104d295bf66b5d70da0b75630c9d4174371337b880370420bab3a9e58d25a89470d71ae2be2"
}