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
Step 1: Alice has received the public key from her mnemonic phrase and wants to find out her account: ed25519:3fJb5T7zAB7eysUoUyXnhA5cALdQ2GF8vuYZwmiMp16u
Bob sees that the key exists, but cannot explain to Alice why she cannot get the account name using the public key using the service and assumes that there is an error in the service.
The text was updated successfully, but these errors were encountered:
As a consumer of indexer DB replicas, Contract Helper relies on those upstream databases being up to date. When those databases fall behind, Contract Helper continues to serve old data with no way to indicate its age.
One potential workaround would be to determine the most recent block height from the data available to Contract Helper. If this height is insufficiently recent, the veracity of data returned from Contract Helper endpoints could be challenged. This opens up some potential implementations, if viable:
upon receiving empty data, query a new Contract Helper endpoint for its indexer replica block height and determine whether it is recent enough
query Contract Helper with a minimum block height, returning an error (rather than empty data) if the indexer replicas are behind it
Step 1: Alice has received the public key from her mnemonic phrase and wants to find out her account:
ed25519:3fJb5T7zAB7eysUoUyXnhA5cALdQ2GF8vuYZwmiMp16u
Step 2: Alice uses the helper to get her account:
Receives the answer:
Not found
Omniscient Bob knows Alice's account and can verify that the public key exists:
got:
Bob sees that the key exists, but cannot explain to Alice why she cannot get the account name using the public key using the service and assumes that there is an error in the service.
The text was updated successfully, but these errors were encountered: