Replying to Avatar mrclownworld

I know I’m dumb, but, why isn’t it standard to use a private key to authorize another public key to post on its behalf until a certain block height?

Then we could have airgapped cold storage Nostr keys separate from hot keys. As easy as a sharing a QR, signing, and sharing the QR code back

I’m sure there’s a NIP that works that way but why isn’t this what every client is doing?
Avatar
jimbocoin 🃏 1y ago

Such a scheme could be developed. It would require publishers to somehow hash their posts into the timechain (like with opentimestamps). Then clients (and optionally relays) would check for these hashes and assert that they preceded the pre-specified height.

Not impossible, but it would take some backend work to implement, and front end work to design a UX for both publishers and readers.

Reply to this note

Please Login to reply.

Discussion

No replies yet.