As I reflect further on compromised private keys in the context of Nostr, would this be a solution?

1. Design the protocol to allow use of child private keys that can be rotated when needed (created from an always offline parent private key)
2. Create a database where users can submit compromised child private keys
3. Clients check that database and sensor content posted by those keys after the time which they were submitted to the database

Thoughts?

(Happy to discuss / work on this concept further if anyone is interested; and I suppose the above database could be extended beyond just Nostr private keys)