The point of Inkan is to give users a key that secures their identity and that can be kept entirely offline (that's what I'm calling the "master key"). This seems like a desirable thing to have, so I wouldn't characterize it as "forcing" people to have something.
I'm not sure if I understand your proposal to "use Blockchain to rotate the master key," if by "rotation" you mean replacement with a different key. Shouldn't the master key be permanent, so that it can permanently secure the identity? Users may have a large following attached to the master key, so they wouldn't want the key replaced with something else.
Maybe we are using the term "master key" in different senses? In Inkan, the "master key" is the unchangeable cryptographic object that anchors the identity, as opposed to the "signer" key which can be replaced.
On your proposal, what is the exact object that anchors the identity?
(It's possible that I don't know enough about DNS, or what role it is supposed to play in your proposal. Your proposal seems to involve an "authoritative server." What must this server be trusted to do?)
inkan
npub16x…56z6l
2026-06-01 11:41:50 UTC
in reply to nevent1q…lfw0
Author Public Key
npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6lPublished at
2026-06-01 11:41:50 UTCEvent JSON
{
"id": "5e21a7954bfa1449a5d82a0fe1b306c090db9b1519b4bada475c73cd0d8b1019",
"pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
"created_at": 1780314110,
"kind": 1,
"tags": [
[
"e",
"15fde76baeb9bac55815115d43bc4be5a67cfb611a78f718d0c599dc9b40b7e9",
"wss://relay.primal.net/",
"root",
"930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9"
],
[
"e",
"5e23b5c86db5abab6d90aa2d8c24772a21beb9be8cb433d435657ecd2f597a08",
"wss://relay.primal.net/",
"reply",
"930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9"
],
[
"p",
"930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9"
]
],
"content": "The point of Inkan is to give users a key that secures their identity and that can be kept entirely offline (that's what I'm calling the \"master key\"). This seems like a desirable thing to have, so I wouldn't characterize it as \"forcing\" people to have something.\n\nI'm not sure if I understand your proposal to \"use Blockchain to rotate the master key,\" if by \"rotation\" you mean replacement with a different key. Shouldn't the master key be permanent, so that it can permanently secure the identity? Users may have a large following attached to the master key, so they wouldn't want the key replaced with something else.\n\nMaybe we are using the term \"master key\" in different senses? In Inkan, the \"master key\" is the unchangeable cryptographic object that anchors the identity, as opposed to the \"signer\" key which can be replaced.\n\nOn your proposal, what is the exact object that anchors the identity?\n\n(It's possible that I don't know enough about DNS, or what role it is supposed to play in your proposal. Your proposal seems to involve an \"authoritative server.\" What must this server be trusted to do?)",
"sig": "7a350be04d465173cbf7cb96e80b395b007e2acb78e20e47315cb7a65a755903fc81001e42fb1eeaf4f09aa8412535084e45e32387daca6d5b03058da9af0a7c"
}