No, your existing keys won't become rotatable.

Raw JSON

{
  "kind": 1,
  "id": "ecee4739b9f8494bb3a6647de766a8ae7d66443dd1753a44945334d90616de24",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1773872410,
  "tags": [
    [
      "e",
      "dbe68638908a66bb601f681b5a92a41d9fd9683fb97330a1f6e7f8fe687b4277",
      "wss://relay.primal.net",
      "root",
      "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
    ],
    [
      "e",
      "84f229f8e0504a63745c0bf443883ccf45334a30adcce80002fb281ac105ad92",
      "wss://relay.damus.io/",
      "reply",
      "21b5a9c73d53c546547300441d780682b66cf4ee666bcbd5923eb1d839a545b6"
    ],
    [
      "p",
      "21b5a9c73d53c546547300441d780682b66cf4ee666bcbd5923eb1d839a545b6"
    ]
  ],
  "content": "No, your existing keys won't become rotatable.\n\nCreating a rotatable identity involves a bit of ceremony. You'd have to use the \"Inkan Management Utility\" to create a master key pair and a chain of delegation. This should be done on an airgapped system to keep the identity secure. I personally like using Tails ( https://tails.net/ ) with networking and persistent storage disabled. Creating the identity also requires a bit of Ether.\n\nBefore creating your own identity, it's a good idea to get a sense of how Inkan works. The best way to do this is to get on the allow list for accessing the identity features of the client. This will allow you to observe the existing permanent identities and the delegation / timestamp backup data that supports these identies.\n\nIt's a prototype, but I've been using it for several months and it works ok for me so far. If you're interested in taking a look at the identity features, let me know and I can put your pubkey on the allow list.",
  "sig": "aa016747e23afa23444946acec5dc14855af713f0c52341958be6146424dd56b7a231d967d36e3d186a046000173d71c2c7afdb95e2b12df4a000bfd72c2922d"
}