Thanks nostr:nprofile1qqs9h8p23u023zwkxu55y094vupw89m23ljfzrw8kgn308ypevss40spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsypzr72 ! Let me chew over this. I think it can be done. Some sort of secure locker that can only be sprung open after a certain time (blockheight). I already have private storage implemented (undocumented), so I will give some thought on how it could be timelocked.
Hi nostr:npub1q6mcr8tlr3l4gus3sfnw6772s7zae6hqncmw5wj27ejud5wcxf7q0nx7d5 - I hope you don't mind me mentioning you.
Given your cool work on the nostr safebox, I thought you might have valuable feedback/opinion on the idea mentioned in my previous note (obviously not the same as the nostr safebox, but still somehow related). Cheers!
Discussion
Thanks for the quick response nostr:npub1q6mcr8tlr3l4gus3sfnw6772s7zae6hqncmw5wj27ejud5wcxf7q0nx7d5 !
I was not necessarily talking about doing it with nostr safebox. I also thought about block height as a time lock mechanism, but I would also like the thing to handle cases where the message owner is kind of reported missing after some time (e.g. he passed away...).
Maybe this could be achieved by checking if some data (e.g. some signature by the message owner) is present in the latest N blocks. But then still, how does that enable the receiver to unlock/decrypt the message after that condition is met? Also, requiring the message owner to pay for transaction fees for as long as he is alive (even if only every few thousand blocks) is not great.
Those are the reasons why I thought a solution involving a third-party (i.e. a traditional web service) could be acceptable.