Happy to. nostr:npub1rx039j20u63fqwggc3h0ewg3jrvejwmnszyxexp...

Raw JSON

{
  "kind": 1,
  "id": "09d178f1a5fd21fb71926e0bc9a4bb73c2fe39d26ef0bac4300bcc37c56e122e",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1788000551,
  "tags": [
    [
      "q",
      "30023:d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23:cold-storage-identities-for-nostr-c5n01a",
      "wss://relay.damus.io/"
    ],
    [
      "e",
      "dd06ce0159e6c088f7c3ae0bdb579edb4fd65d55d09c94991825792f17b841b3",
      "wss://relay.primal.net/",
      "root",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ],
    [
      "e",
      "cab76b7020db95a0a4570097b300ab5c821abe867ff9e7a5721038243118588a",
      "wss://relay.inkan.cc/",
      "reply",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ],
    [
      "p",
      "e28ef176cd7618a8cc0147570d88ff76bb252bbdd2252f99eda3fe019f673730"
    ],
    [
      "p",
      "073cd836b557a9fdc2a62c27373273da0c556a7008763f7f0e2b7f28ea754fd6"
    ],
    [
      "p",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ]
  ],
  "content": "Happy to. nostr:npub1rx039j20u63fqwggc3h0ewg3jrvejwmnszyxexpjrdvu2y7u49esyzu0mp is the signer key for meta's cold-storage identity, the identity itself is nostr:npub1u280zakdwcv23nqpgatsmz8lw6aj22aa6gjjlx0d50lqr8m8xucq7kf93q (longer story, for a NIP write-up see below). Regular Nostr clients only ever show the signer. To actually see the identity, its profile and posts etc., log into www.inkan.cc with your NIP-7 extension. The client should show you a welcome popup with a list of identities you can follow that includes nostr:npub1u280zakdwcv23nqpgatsmz8lw6aj22aa6gjjlx0d50lqr8m8xucq7kf93q, so you can follow it and then go to its profile page to see its events and interact with it.\n\nSo I think what meta wants is the mailstr address on the master identity, with everyday login staying on the signer. That should be doable, the delegation between the two keys is on-chain, you'd read it and attribute the session up. Emails sent by the identity will probably also want OTS timestamps so it's checkable the delegation was live at the time the email was sent. I haven't really dug into how mailstr, but making it delegation-aware would be a great thing.\n\nHere are more details, and I'm always happy to explain further:\n\nnostr:naddr1qvzqqqr4gupzp5dxzjv0fvwuym0shmx350573re4t7mpfdm3az6mya7sl7v6s23rqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wghxcctwvshsq2rrdakxgttnw3hhyct8v5kkjer9de6xjarfv4ej6en0wgkkummnw3ez6ce4dccrzcgtu4kzh",
  "sig": "43f0aa59ce4cad048b4e1b209a7aa67766821ecb93f33c9a763cd3582bf45c046dc6bac037b0fe5153dbe5bc5a3bfcff7523c1a5b42f459bc5d67e214511758c"
}