Would it be possible to timelock the decryption of a message to a specific npub?

Reply to this note

Please Login to reply.

Discussion

Don't think it can. Who determines time?

Bitcoin has its own concept of time. Time is irrelevant to nostr.

Possibly hook in a block # for a rough time? Use the verified hash of a block and the timestamp?

how do you get the block hash before it's mined? and the timestamp can be manually input without something to enforce it's reference

Are you saying the timelock will influence the action to a specified npud

Or are you saying

A message to a specified npub can have a timelock?

Ideally a message to a specific npub would have a timelock...

BUT I'm also wondering if the owner of that npub could potentially forward that encrypted message to another npub before the timelock triggers - in a way that the original recipient would no longer be able to decrypt it, but the new recipient would.

Is there a difference in result from scheduling via shipyard?

Thats scheduled posts not encryption.

I get that. But if you don't send it can't be decrypted either 🤷‍♂️

Untrue. A message can sit locally on my drive awaiting decryption.

then `man crontab` 🤪

If you encrypt the message such that it can only be decrypted by a threshold of a group of people, and you tell that group not to decrypt it until a specific time, you could achieve similar behavior. Perhaps a Fedimint module could be written to do this.

The decrypted message that the threshold unwraps could, itself, be a NIP-4 message or something similar that can be shared and decrypted by the final recipient

I can imagine a scenario where something like this could be approximated through DLCs on-chain 🤔