I think there's an inconsistency (or a least a jarring tensi...

原始 JSON

{
  "kind": 1,
  "id": "4db0930a2c2520e29a12a3e486d6a8b7176622f706a08c675849d4a614f9e303",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1788950223,
  "tags": [
    [
      "e",
      "3aec1cd219bede90b0706e590bb2cae9ff3b14a472019d6d6fb312cb175679db",
      "wss://relay.primal.net/",
      "root",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ],
    [
      "e",
      "a21296b66e2358465e301104f29e0e7fe181767d0dda65afba045214cd77c729",
      "wss://relay.primal.net/",
      "reply",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ],
    [
      "p",
      "61bf790b2094afb03495c9e136acf615be0fccc2cb95b5acfb5f6ccefe18b062"
    ],
    [
      "p",
      "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd"
    ]
  ],
  "content": "I think there's an inconsistency (or a least a jarring tension) between these two statements:\n\n\"it does not change all that much\"\n\n\"So allowing a (main)key to remain in cold storage is a great risk reducer\"\n\nThe risk reduction that results from the ability to hold keys in cold storage is *enormous*. Without it, for example, cryptocurrencies would not really be practicable.\n\nI'm not sure how my system makes the main key's getting compromised \"worse.\" I guess you're uncomfortable with the fact that, having greater confidence in the security of their key, people may invest more seriously in building their identity on that key, so the loss of that investment would be greater. The discomfort one feels with  putting all one's eggs in one basket.\n\nNow currently it's a prototype and I wouldn't want people to be over-confident in in the nitty-gritty details of this particular implementation. But as far as I'm aware, there's no reason to think that the details can't be hardened into something robust, or who knows it may turn out that the current implementation is already robust. This is not different from any other Nostr app. Sensitive parts need to be diligently and continuously audited.\n\n\"it works under the assumption that your system gets normalized.\" While it would be great for it to get normalized quickly, it's actually functional *without* other clients adopting it. The key I'm using right now is the signer key for my Inkan master identity, and I can use it as a regular Nostr key that is fully compatible with normal Nostr clients. So there's nothing that prevents me from using normal Nostr and Inkan at the same time with the same key. Inkan does not interfere with or break the usual protocol. It can basically just be used on top of the regular protocol.\n\n\"there's a reason i point people towards your stuff\". Thanks, and what you get back in return from me is a bunch of critical comments, no good deed goes unpunished ...",
  "sig": "a60d1c81331805c4eb7db540d474bf26177a191054948d02756b2284ee57b3870d8c6ab61a042bc5d87ab6af9a9326d8bcc425ee118a433e5c0fad7d9e310ec5"
}