You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
It is possible that the client machine's clock is behind the SEP-10 server machine's clock.
If this is the case, client applications calling readChallengeTx() may not be able to validate the challenge due to the challenge transaction's minimum timebound being greater than the client machine's current time.
Changes
readChallengeTx() or the equivalent function
Apply a 5-minute grace period to the minibum timebound check
i.e. the minimum timebound should be permitted to be at most 5 minutes in the future from the client machine's current time
Implementations
Both the JS and Go SDKs have been updated with these changes.
SEP-10: Apply grace period to
minTime
constraintIt is possible that the client machine's clock is behind the SEP-10 server machine's clock.
If this is the case, client applications calling
readChallengeTx()
may not be able to validate the challenge due to the challenge transaction's minimum timebound being greater than the client machine's current time.Changes
readChallengeTx()
or the equivalent functionImplementations
Both the JS and Go SDKs have been updated with these changes.
The text was updated successfully, but these errors were encountered: