Replies (1)

No overhaul needed. Relays don’t have to know anything about lineage. They already store opaque JSON and ignore tags they don’t understand. This fits inside NIP-01 as is. For clients that use WoT or auth features, nothing breaks. The root key doesn’t change. The epoch keys still verify back to the same identity using a signed lineage event. It’s additive, not a replacement. Clients can keep doing whatever they’re doing today and simply optionally follow the rotation chain if they want stronger key hygiene. It’s a client side improvement path, not a protocol rewrite. I’ll add a client integration guide to the GitHub repo later tonight.