This image is slightly outdated, but it’s still a good repre...

iefan 🕊️

npub1cmmswlckn82se7f2jeftl6ll4szlc6zzh8hrjyyfm9vm3t2afr7svqlr6f

hex

5e35888b36e80f7fd8d75cf0ea164cbfcdb2c52d693463b3d8aa469a3bd41c5b

nevent

nevent1qqs9udvg3vmwsrmlmrt4eu82zextlndjc5kkjdrrk0v25356802pckcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsvdac80utfn4gvly4fv54la0l6cp0udpptnm3ezzyajkdc44w53lg5k53a2

Kind-1 (TextNote)

2026-08-30T12:02:35Z

↳ 回复 事件不存在

6d25be23c41d0ec773640b5dd59c9c11c43f893b98858d8e838dee42b84d411c...

This image is slightly outdated, but it’s still a good representation of how our payment verification works, including built-in splits and referrals.

Think of it like signing a contract with our tiny backend before paying for an event. It attests what you’re purchasing and sends back a signed contract. After payment, you provide proof that the token was spent. We cross-check that against the contract, and if everything matches, you get the decryption key.

We’re also experimenting with open web-of-trust systems, particularly those being built by the Nostr community. We’re open to letting authors decide which mints they trust, and our system can adapt around that.

There’s also a key recovery mechanism if a key gets leaked. It’s still being developed, but it already works. Key derivation itself is deterministic based on the event, its author, and a specialized tag, while our backend only holds half of the secret.

Eventually, we want to expose all of this through an API so paid content can be integrated across applications. And what if that API could be self-hosted on a $2.50 ESP32?

We know we’ll make mistakes and there will be trade-offs along the way, but we’ll do our best. Feel free to ask me anything about it. https://cdn.nostrcheck.me/65c18dc63fc62f60e70c2441c5d0d6f9c5c93c7ed6f6d7300320082d5b6298e4.jpeg

原始 JSON

{
  "kind": 1,
  "id": "5e35888b36e80f7fd8d75cf0ea164cbfcdb2c52d693463b3d8aa469a3bd41c5b",
  "pubkey": "c6f7077f1699d50cf92a9652bfebffac05fc6842b9ee391089d959b8ad5d48fd",
  "created_at": 1788091355,
  "tags": [
    [
      "e",
      "5df56d0a2c87d97941ef5acc86a0049a70a8e791620d39d1e795d0769176128f",
      "wss://nos.lol/",
      "root",
      "c6f7077f1699d50cf92a9652bfebffac05fc6842b9ee391089d959b8ad5d48fd"
    ],
    [
      "e",
      "6d25be23c41d0ec773640b5dd59c9c11c43f893b98858d8e838dee42b84d411c",
      "wss://relay.primal.net/",
      "reply",
      "a6c47f0627c04e542e7d9cd9af53dab2d4f425b3a2b932817465f63186363313"
    ],
    [
      "p",
      "c6f7077f1699d50cf92a9652bfebffac05fc6842b9ee391089d959b8ad5d48fd",
      "wss://relay.snort.social/"
    ],
    [
      "p",
      "a6c47f0627c04e542e7d9cd9af53dab2d4f425b3a2b932817465f63186363313",
      "wss://relay.satlantis.io/"
    ],
    [
      "r",
      "https://cdn.nostrcheck.me/65c18dc63fc62f60e70c2441c5d0d6f9c5c93c7ed6f6d7300320082d5b6298e4.jpeg"
    ],
    [
      "imeta",
      "url https://cdn.nostrcheck.me/65c18dc63fc62f60e70c2441c5d0d6f9c5c93c7ed6f6d7300320082d5b6298e4.jpeg",
      "x 65c18dc63fc62f60e70c2441c5d0d6f9c5c93c7ed6f6d7300320082d5b6298e4",
      "size 72826",
      "m image/jpeg",
      "dim 824x1280",
      "blurhash ^04_tiRj00WB~qRjt7%M-;IUIURjxuxuayWBxuof%Mt7_3ay00IUWBxu~qD%9FM{?b9Fxu_3IUM{xu%MRjM{t7t7xut7xuayj[M{?b4nxu_3M{WB",
      "ox 65c18dc63fc62f60e70c2441c5d0d6f9c5c93c7ed6f6d7300320082d5b6298e4"
    ],
    [
      "client",
      "Amethyst"
    ]
  ],
  "content": "This image is slightly outdated, but it’s still a good representation of how our payment verification works, including built-in splits and referrals.\n\nThink of it like signing a contract with our tiny backend before paying for an event. It attests what you’re purchasing and sends back a signed contract. After payment, you provide proof that the token was spent. We cross-check that against the contract, and if everything matches, you get the decryption key.\n\nWe’re also experimenting with open web-of-trust systems, particularly those being built by the Nostr community. We’re open to letting authors decide which mints they trust, and our system can adapt around that.\n\nThere’s also a key recovery mechanism if a key gets leaked. It’s still being developed, but it already works. Key derivation itself is deterministic based on the event, its author, and a specialized tag, while our backend only holds half of the secret.\n\nEventually, we want to expose all of this through an API so paid content can be integrated across applications. And what if that API could be self-hosted on a $2.50 ESP32?\n\nWe know we’ll make mistakes and there will be trade-offs along the way, but we’ll do our best. Feel free to ask me anything about it. https://cdn.nostrcheck.me/65c18dc63fc62f60e70c2441c5d0d6f9c5c93c7ed6f6d7300320082d5b6298e4.jpeg",
  "sig": "528f1e36c679880b667982329883443fb4f0200bda8b71a1c72e9ccb5534f3c95e2ff560c04ee323b1352478e536c486c468841766484ded7289cf952d1a167f"
}