This is a cool idea.
If a cpub gets compromised, rather than publishing an event that invalidates it, could you publish an event that tells clients to redirect any use of it to a new cpub?
Login to reply
Replies (1)
That’s the general idea, but details need to be worked. I could also add a ‘not valid after’ timestamp. That would not prevent an attacker from publishing prior fake events, but would prevent anything published after.