Dear Doris,
We are using a custom implementation, which is more or less a copy of the Proof Explorer code. However, when the code works with the Crypto X wallet, there’s no reason it shouldn’t also work with the Browser wallet - or do we need to handle this per wallet type?
Best regards, Niels
If the request is correct and the front-end handles the two wallet connections/requests correctly, then the proof generation should work for the browser wallet and the Crypto X wallet.
I suggest, for example, that you try out different IDPs indexes and see if the browser wallet reacts to any of them or can you give us additional information what request you sent to the wallet?
We’ve already tried switching around the IDP IDs and encountered the same result. It works on Crypto X with the correct IDP. We are sending the same request as mentioned above. Could you please check if your Proof Explorer functions properly on the mainnet for both Crypto X and Browser wallets when processing a requesting company’s commitments
We tested the front-end https://web3id-proof-explorer.testnet.concordium.com/ with a global finreg identity issued on mainnet by selecting the Digital Trust Solutions TestNet (IDP:3 to simulate the correct mainnet IDP) and the browser wallet version 1.7.1 popped up to generate a proof.
Currently, we are still not sure what could cause your behavior.
Okay - let me some more testing later and get back.
Dear Doris,
Following your update to the mainnet verifier, everything seems to be working fine now. We conducted some additional testing, and it’s all functioning as expected.
Please feel free to close this issue, and thank you for your assistance!