I don't know if it's the best, but Twilio works: https://www.twilio.com/

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.

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!

I am considering building a service for sharing time locked messages and would be curious to hear your thoughts and recommendations.

My main motivation is that I would need something like this for myself, but could not find the right tool for my needs (please point me to any similar service you may know, I have certainly missed some).

The goal is to provide a user friendly (non-tech savvy) way to transmit and to claim a message after a given date or after a certain period of inactivity by the message sender. Could be used for inheritance planning obviously, but it would not have any legal authority.

I know the concept of timelock exists in Bitcoin, and also services like Casa or Nunchuk provide inheritance planning capabilities. But I am after something possibly simpler to transmit possibly less sensitive data/information. It would be used to transmit text, with whatever message you want. This doesn't mean security should not be a concern, so here are some of my thoughts at this stage, to possibly build something practical and secure enough:

* The service is a third-party that will store the encrypted message, i.e. you rely on the third party to retrieve the message or be notified when unlocked, but that third-party never knows the content of the message (i.e. encryption/decryption on the client side)

* Open source project so anyone can review the code (and for example validate that unencrypted message are indeed never sent to the third-party)

* Different workflows can be imagined, e.g. unlock message after a given date or unlock message after a certain period of inactivity by the author

* The message recipient is expected to have the key to decrypt the message the day it becomes available

* The message author can cancel the message with his key or with his email address (e.g. in case he lost the private key, he can still cancel the message but cannot view it)

I imagine pretty much anyone on Nostr will rightly say that relying on a third-party is not ideal, but it seems to me that it is acceptable in this case, mainly because the the third-party actually never sees the unencrypted message.

Anyway, I am curious to collect some thoughts about this. Thank you in advance for your feedback.

#timelock #inhertiance

I am in Mozambique at the moment. Was impossible to find cash (Meticals) before entering the country. Not many ATMs. When you find one, there are chances it is out of order or empty. When it works you can have long queues. And when you can finally withdraw money, you cannot withdraw much (something like the equivalent of 80 USD).

Bitcoin and Lightning definitely have potential here (and probably in many other countries in Africa).

npub1twwz4rc74zyavdefgg7t2eczuwtk4rlyjyxu0v38z7wgrjepp2lqslhlss