Join Nostr
2026-11-17 13:20:21 UTC
in reply to

Technical Debt on Nostr: Not relevant in this case. When you generate an inkan identity for production you do ...

Not relevant in this case. When you generate an inkan identity for production you do that in an airgapped system, sign the delegation offline and then only use the delegated nsec on a day by day basis.

So only the “hot” nsec would have been compromised in this case, and then he could have signed a revocation and delegated the “cold” nsec to another nsec similar to the initial setup.

Think of Cake mini running on an offline android phone holding the keys and signing a bitcoin transaction for you.

Again this could be solved in n different ways, but the problem at hand is that vanilla nostr requires your identity key to be stored in memory and accessible through an always online device, even if you use signers.