Yes, I have mentioned exactly this previously. Amethyst assu...

Dikaios1517

npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhe

hex

7f176250894a9c6ebaa012cb32f77168f5618fef1bca55c015e7d51b722b5f04

nevent

nevent1qqs879mz2zy548rwh2sp9jej7ack3atp3lh3hjj4cq2704gmwg447pqprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgstwf6d9r37nqalwgxmfd9p9gclt3l0yc3jp5zuyhkfqjy6extz3jc0angyy

Kind-1 (TextNote)

2026-09-03T00:31:23Z

↳ 回复 事件不存在

2786e2879c793e112ba5550002072d9c6b4f91f8e484a65223a8363736bf7e11...

Yes, I have mentioned exactly this previously. Amethyst assumes that all relay lists other than inbox/outbox (kind 10002) should be private lists, and therefore encrypted. However, this is the LEAST compatible with other Nostr clients, and users have no way to choose not to have those lists encrypted.

Nevertheless, ALL Nostr clients should expect that lists can contain encrypted content, and support reading that content if they support those lists. This is detailed in NIP-51 (Lists), which says, "Lists can contain references to anything, and these references can be public or private... private items are specified in a JSON array that mimics the structure of the event tags array, but stringified and encrypted using the same scheme from NIP-44 (the shared key is computed using the author's public and private key) and stored in the .content."

原始 JSON

{
  "kind": 1,
  "id": "7f176250894a9c6ebaa012cb32f77168f5618fef1bca55c015e7d51b722b5f04",
  "pubkey": "b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb",
  "created_at": 1788395483,
  "tags": [
    [
      "e",
      "e50a08aab39fb21204e28481424a46f467e56e3436776d9687f42ec405a83467",
      "wss://theforest.nostr1.com/",
      "root",
      "f6900e6b42a83a6d66589714de49ac86919c6464857d9e164b953bcf9c7e939d"
    ],
    [
      "e",
      "2786e2879c793e112ba5550002072d9c6b4f91f8e484a65223a8363736bf7e11",
      "wss://spatia-arcana.com/inbox",
      "reply",
      "c230edd34ca5c8318bf4592ac056cde37519d395c0904c37ea1c650b8ad4a712"
    ],
    [
      "p",
      "f6900e6b42a83a6d66589714de49ac86919c6464857d9e164b953bcf9c7e939d"
    ],
    [
      "p",
      "bc02e0a6c0f01ad9cb57a2b0f8ef8241bc5ff979ce4452ce9e243de457756725"
    ],
    [
      "p",
      "c230edd34ca5c8318bf4592ac056cde37519d395c0904c37ea1c650b8ad4a712"
    ],
    [
      "client",
      "JANK"
    ]
  ],
  "content": "Yes, I have mentioned exactly this previously. Amethyst assumes that all relay lists other than inbox/outbox (kind 10002) should be private lists, and therefore encrypted. However, this is the LEAST compatible with other Nostr clients, and users have no way to choose not to have those lists encrypted.\n\nNevertheless, ALL Nostr clients should expect that lists can contain encrypted content, and support reading that content if they support those lists. This is detailed in NIP-51 (Lists), which says, \"Lists can contain references to anything, and these references can be public or private... private items are specified in a JSON array that mimics the structure of the event tags array, but stringified and encrypted using the same scheme from NIP-44 (the shared key is computed using the author's public and private key) and stored in the .content.\"",
  "sig": "e400e45a698bab49b43d8c68381cc9d94f0e13af4b7cefb3d5744906baf50a6fd1b0a984d44ee35abb470261c0e4192bf3590f5912d737e9864cce517877a6cf"
}