I've read all of these.
1. It is not needed to opentimestamp the revocation (migration) event.
2. It isn't even necessary to indicate what key is being migrated to with the revocation event.
Profile attesations (like PGP key signing) can tag both the new and old key, and this can help people follow their new key. The revocation event informs people the key can not be trusted and to seek alternatives (and for those attestation events).
3. There also isn't a need to whitelist keys. Confirmation of the profile can happen in any number of ways "out-of-band".
Braydon Fuller
npub1r0…7zzyc
2024-09-30 20:45:08
in reply to nevent1q…7d06
Author Public Key
npub1r0ulywwu593kzjdu9uluxdq80t54n65kql9vl9z7lrutkgnachssk7zzycPublished at
2024-09-30 20:45:08Event JSON
{
"id": "6625b28e3967717da926edefbe3a2c42f137bac2dadab5b5f56767113ca19ae9",
"pubkey": "1bf9f239dca1636149bc2f3fc334077ae959ea9607cacf945ef8f8bb227dc5e1",
"created_at": 1727729108,
"kind": 1,
"tags": [
[
"e",
"b185e48793babede14d336f6a51b1ad6aae60ae8f4dd1f476e812172ce1e8198",
"",
"root"
],
[
"e",
"0000f4e0f567ea50b71be555ea0ef8f2058706df6be1f640c0971d8a96394f55",
"",
"reply"
],
[
"p",
"1bf9f239dca1636149bc2f3fc334077ae959ea9607cacf945ef8f8bb227dc5e1"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
]
],
"content": "I've read all of these.\n\n1. It is not needed to opentimestamp the revocation (migration) event.\n2. It isn't even necessary to indicate what key is being migrated to with the revocation event.\n\nProfile attesations (like PGP key signing) can tag both the new and old key, and this can help people follow their new key. The revocation event informs people the key can not be trusted and to seek alternatives (and for those attestation events).\n\n3. There also isn't a need to whitelist keys. Confirmation of the profile can happen in any number of ways \"out-of-band\".",
"sig": "f634015b6274b78ddc5d7d6dc58dabfec67637679863f5ff928f34eeeaca0d2e48df7c358bc2ef010c983902d18ad30fd3e9fbb0aa2c5d15c2c739c02b69763d"
}