If I’m reading the code correctly, this uses the duration of your “time lock” as the duration for how long it will perform scrypt operations on the key derivation.

In other words, if you say you want to “lock” the secret for 5 days, the code will perform scrypt to generate the key for 5 days!!! Then it expects you to remember the iteration count to decrypt it.

I don’t see any use case where that’s a useful mechanism. Especially since it ignores other computers are likely faster at scrypt then yours is.

Am I the only one who can’t think of a time DNS has caused a production outage on a platform I worked on?

Lots of other problems over the years, but never DNS.

If you’re in the USA I would suggest using Amica for your insurance. They are great, and I’ve never seen an advertisement for them!