Regarding Opentimestamps: NIP-03 says: "The OpenTimestamps proof MUST prove the referenced e event id as its digest." Wouldn't it be preferable if the proof were to have a concatenation of the reference event's event_id and its signature as its digest? Also, I find it useful to tag the reference event's pubkey and signature in the OTS event. #nostrdev

Trying to understand #nsecbunker and nip-46. So I think that,in order to control the bunker, you have to have admin credentials for the bunker. And if these admin credentials get stolen, the thief then controls your private keys, i.e. the ones you deposited inside the bunker. Is that right, or am I missing something? I'm just trying to figure out what you have to keep secret when using nsecbunker.

Does vnak allow you to authenticate to a relay and then fetch events that satisfy the specified filter? On the req tab, I entered a privkey which should be able to authenticate on nostr.wine. However, when I click "send request" it says "subscribed to nostr.wine" and doesn't do anything (actually it freezes at that point). I also never figured out how to do this with the original nak. I believe I need to do something like "--auth", possibly in combination with "--sec"?

I made something that allows you to revoke a nostr key pair and replace it with a new one. You can use it when you have lost your private key or when your private key has been stolen. Or you can use it preemptively for periodic key rotation. #nostrdev