Chris Beavers pfp
Chris Beavers
@cbeav
proof of crosswork: without an online verifier (server or a blockchain), is there a solution for “i signed this no earlier than X in a way you can validate”? any time someone finishes the MW with a crappy connection, it adds time. would be cool to solve this but smells intractable
4 replies
0 recast
5 reactions

Tony D’Addeo pfp
Tony D’Addeo
@deodad
intractable
1 reply
0 recast
1 reaction

Johns | johnsgresham.eth pfp
Johns | johnsgresham.eth
@johns
Could maybe use a new latest block or txn hash onchain that isn’t knowable before X time. Could hash it with the solution if you want to make sure they know the solution at the time
1 reply
0 recast
0 reaction

Ellie Davidson ☕️ pfp
Ellie Davidson ☕️
@ellied
Or, if the device supported this (not sure if any do at the moment) you could use the device's secure enclave to sign the timestamp. So long as you assume a user can't break the secure enclave (which is pretty reasonable in, say, iPhones) and you can attest to the version of code running, then this seems like a good solution, too. But I am not at all familiar with how much devs can access secure enclave features in mobile devices. But this is a good idea in theory.
0 reply
0 recast
2 reactions

Ellie Davidson ☕️ pfp
Ellie Davidson ☕️
@ellied
I'm thinking you could do something similar to 2FA codes, since they solve a similar problem. They don't require internet to do the initial signing, but then they do require internet to authenticate that signature is valid. However, they work best when you don't need much time granularity. I'm not sure how well they'd work if you need very accurate time (like down to milliseconds)--I suppose it depends on how accurate the personal device clock is compared to the server clock.
0 reply
0 recast
1 reaction