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
We noticed, that Indy VDR performs a state proof verification for each response of a read request to the ledger, but it seems there's no indication if the verification was successful or failed (except a trace message).
Did I miss anything here?
The text was updated successfully, but these errors were encountered:
This is by design, and consistent with the behaviour in indy-sdk. IIRC the state proof verification may fail when generated for a different epoch (which changes every 5 minutes) due to clock skew or delays in receiving the response from the server. I don't think every response type supports a state proof either. But a consensus response from the verifier nodes is also considered acceptable, this is generally n / 3 + 1 identical responses where n is the number of verifier nodes.
We noticed, that Indy VDR performs a state proof verification for each response of a read request to the ledger, but it seems there's no indication if the verification was successful or failed (except a trace message).
Did I miss anything here?
The text was updated successfully, but these errors were encountered: