Thanks for the quick response Tim Bouma (npub1q6m…x7d5) !
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.
pf80
npub1tw…lhlss
2024-08-20 19:29:33
in reply to nevent1q…tg46
Author Public Key
npub1twwz4rc74zyavdefgg7t2eczuwtk4rlyjyxu0v38z7wgrjepp2lqslhlssPublished at
2024-08-20 19:29:33Event JSON
{
"id": "c962ed729b43706d8ad322745021c2c28fbef0c09465fb81dba1039a43def051",
"pubkey": "5b9c2a8f1ea889d63729423cb56702e3976a8fe4910dc7b227179c81cb210abe",
"created_at": 1724182173,
"kind": 1,
"tags": [
[
"e",
"a331f4e7b146bd78c8e662c08a2085f56e6262a89b419583b5ac5db4ec379aa6",
"",
"root"
],
[
"e",
"81fc8cc12d693f5046ce5eb0532a59d85b635aa335a2894df2da7349160ad77c",
"",
"reply"
],
[
"p",
"06b7819d7f1c7f5472118266ed7bca8785dceae09e36ea3a4af665c6d1d8327c"
],
[
"p",
"5b9c2a8f1ea889d63729423cb56702e3976a8fe4910dc7b227179c81cb210abe"
]
],
"content": "Thanks for the quick response nostr:npub1q6mcr8tlr3l4gus3sfnw6772s7zae6hqncmw5wj27ejud5wcxf7q0nx7d5 !\n\nI 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...).\n\nMaybe 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.\n\nThose are the reasons why I thought a solution involving a third-party (i.e. a traditional web service) could be acceptable.",
"sig": "263ebbce366a92b4e0b991b542a6a3614709281feeb43886f4fbb35482cc1ab5e0591de2aeac5a04df4d330ab59ca83e148d36474137a0a4b04bcf6fe032edbf"
}