[dev-node] ShareRequest failed with -32603: "could not retrieve access structure: not found"

Embedded Wallets (Web3Auth)
1

Hi,

I am encountering an internal JSON-RPC error (-32603) while attempting authentication/share retrieval on the test environment.

Environment & Setup:

  • Network / Endpoint: [https://node-1.dev-node.web3auth.io/sss/teal/jrpc](https://node-1.dev-node.web3auth.io/sss/teal/jrpc)

  • Verifier Identifier: tkey-dev

  • Client Environment: Android WebView (Custom App Integration)

Error response:

{
“jsonrpc”: “2.0”,
“error”: {
“code”: -32603,
“message”: “Internal error”,
“data”: "share request could not retrieve keyIndexes: "
},
“id”: 10
}

(Also occasionally receiving: "could not retrieve access structure: not found")

cURL Request:

curl --url ‘https://node-1.dev-node.web3auth.io/sss/teal/jrpc’
-H ‘accept: /’
-H ‘content-type: application/json; charset=utf-8’
-H ‘origin: https://dapp-web.dev.uptn.io’
-H ‘referer: https://dapp-web.dev.uptn.io/’
-H ‘x-requested-with: io.uptn.wallet’
–data-raw ‘{“jsonrpc”:“2.0”,“method”:“ShareRequest”,“id”:10,“params”:{“encrypted”:“yes”,“item”:[{“verifier_id”:“b9e5fa36d2be90e32a1a8a487ef52ff7e7769d890fd6c6eb63c21f0054257868”,“idtoken”:“<ID_TOKEN>”,“nodesignatures”:[{“signature”:“6ff916ace413da36accd76f355e0d6a19cffe4c7c9134ba04285268d663879aa770df38832f5676c5658c56d9de83328576dc2830501b57476555c6b24dbadbc1c”,“data”:“mug00\u001cb681690f2b03ade438d7814c9e77f2fd9a2822cae1364e7331a000cf63490e70\u001c1e197e0b12ff692fee202f0011ee706ebc67abe9f03e0248a8bf62d5d47157fb\u001c9c67ab5da5027993f08431a7fc122afc08ded33b10b3c864d329b294a3217bbf\u001ctkey-dev\u001c1787621186”,“nodepubx”:“f74389b0a4c8d10d2a687ae575f69b20f412d41ab7f1fe6b358aa14871327247”,“nodepuby”:“54e3a73098ed9bced3ef8821736e9794f9264a1420c0c7ad15d2fa617ba35ef7”,“nodeindex”:“1”,“pub_key_x”:“”}],“verifieridentifier”:“tkey-dev”}]}}’

Observations & Questions:

  1. The error suggests that the account or access structure has not been initialized/assigned on the node (access structure: not found / keyIndexes: <nil>).

  2. Is this issue caused by the user account/key not being pre-registered, or is there an ongoing sync/indexing issue with the dev nodes?

  3. Could you verify if the verifier tkey-dev configuration on the network requires any additional parameters or if this indicates an uninitialized key state?

Any guidance on resolving this would be greatly appreciated. Thank you!

2

Hi could you please verify the following:

  1. Does tkey-dev exist and remain active on the dev SSS network?
  2. Does the supplied verifier identifier have an access structure and keyIndexes?
  3. Is that state present on node-1 and the other dev nodes?
  4. Was the key initialized using the same environment/verifier configuration?
  5. Is there currently a replication/indexing issue between dev nodes?
2 Likes
3

We ran tests across different wallet accounts in this exact setup/environment, and other accounts retrieved their shares/keys successfully.

However, only this single specific wallet address fails with the access structure: not found / keyIndexes: <nil> error:

  • Target Wallet Address: 0xdd9e9497a9a6b3e14871e672d33aa12e1e3ea4d7

  • Verifier: tkey-dev

  • Verifier ID: b9e5fa36d2be90e32a1a8a487ef52ff7e7769d890fd6c6eb63c21f0054257868

Could you please check your node/metadata database to see:

  1. Whether an entry/access structure for this specific address (0xdd9e9497a9a6b3e14871e672d33aa12e1e3ea4d7 / Verifier ID: b9e5fa36...) exists in the network DB?

  2. If it was corrupted or lost during state assignment?

Looking forward to your feedback. Thank you!

4

Thanks for sharing let me get back to you