Outcome: Create a message with a count down timer. Once a top level password is entered, a countdown timer starts. Once timer expires, the message is decrypted.
Known methods: Proof of work. User has to use computing power to decrypt the message.
Problem: The computer power will change in the future. I want relatively accurate time lock, now & years from now.
Are these possible solutions…?
Proof of work time lock tied to Bitcoin difficulty: Bitcoin has a reactive difficulty parameter that will reflect current state of processing technology.
Is there anyway to use the Bitcoin difficulty parameter as to make a time locking message with a relatively accurate time lock time, now & in the future?
Smart contract based: A smart contract, that once a first layer password is input, a count down timer starts, based on a time now oracle of some kind. Once expired, the second layer message is decrypted.
A) Are any of these possible?
B) Are there any other existing solutions that would get the desired outcome currently?
**Removing serial hashing burden, but still getting the same benefit: ** When top level password is entered, BTC current block is noted. When BTC block reaches current block + X, 2nd layer message is decrypted.