Payout 387268 sent
419a432eae3635498f322fb8ec72adee3078a01fcb361288d8dcbc529b21bfe0
and confirmed
--
will test out the pool for couple of days. seems to be running good.
kano, i tried 2fa but it said invalid code
...
As it says on the web page, what matters is the accuracy of the time on your device.
You can actually see on every web if there is a problem:
Check the time on the web page in the bottom left tiny text - that will show you the time on the server - which will be correct ignoring the delay for the web page to be sent to you.
Your timezone doesn't matter, but if you look at the tiny text on the bottom right, that's what time your browser thinks it is.
They should have almost exactly the same MM:SS on the end.
(however if you are in a timezone with a 30minute offset, then the MM will differ by 30 minutes also)
If the time in your device is different by more than a couple of seconds, that's the problem.
The 2fa time limit value used is 30s.
I have thought about this since I implemented it and I may give people the option to increase that 30s accuracy in the future maybe up to a few minutes.
It also depends on if the apps can be told larger numbers for the 30s without having to manually intervene in the settings.
... added to my long TODO list