Tours Wallet - Issues with Writing to a contract

[syackzan]

Hello, I am trying to integrate Torus Wallet, but I am receiving issues when Writing a contract. I’ve tested the following and the following work, signing the user in, signing a message, and reading from a Smart contract. Now, I am trying to write to a smart contract, but I am receiving the following error:

"Error: Bad Request at LoglevelSentry.translateError (chunk-vendors.09492946.js:16:350836) at async Logger.x [as error] (chunk-vendors.09492946.js:16:352516)

1. Response {type: ‘cors’, url: ‘https://api.tor.us/transaction’, redirected: false, status: 400, ok: false, …}

2. body: (…)

3. bodyUsed: true

4. headers: Headers {}

5. ok: false

6. redirected: false

7. status: 400

8. statusText: “Bad Request”

9. type: “cors”

10. url: “https://api.tor.us/transaction”

11. [[Prototype]]: Response"

It would appear the api.tor.us is not allowing me to write a contract. Let me know if anyone has any answers. I tried with web3 and viem, but received the same error with both methods.

[w3abot]

Hi Scotty,

Thanks for reaching out! It seems you’re facing an issue while trying to write to a smart contract using the Torus Wallet.

Here are a few things we can check to help troubleshoot this issue:

1. Smart Contract Code:

   • Ensure that the smart contract method you’re trying to call allows writing and that you’re passing correct parameters.

2. Transaction Data:

   • Double-check the data field in the transaction object. Ensure everything is correctly defined and matches the smart contract function.

3. Account Balance:

   • Verify that the account has enough funds to cover the gas fees for executing the write operation.

4. Network Configuration:

   • Confirm that you’re interacting with the correct blockchain network and that the endpoints are properly configured.

5. Permissions:

   • Ensure that the wallet permissions are correctly set and the necessary approvals for writing to a smart contract are granted.

Could you also share:

• The Web3Auth initialization and login code snippets
• Any relevant segments of your contract interaction code

This additional information can help diagnose where the issue might be occurring.

Looking forward to your response!

[yashovardhan]

Torus Wallet is deprecated at this moment. We are working on a different product to replace the gap of that product. You can use Web3Auth as a Wallet as a Service, which provides the same functionality but customised for your needs.

[syackzan]

Can you confirm web3auth WaaS creates a new wallet address per user per platform? In other words, if a user logins into one Dapp, their wallet address will be different when logging into a separate Dapp? Unfortunately, that doesn’t work for our Dapp.

In addition, I was having trouble writing to smart contracts with web3auth, receiving internal RPC errors after following strict documentation. So, I strayed away from that.

It also should be noted that Torus wallet was indeed writing to the contract and the contract was processing correctly. I was still receiving the failed error regardless. It makes sense now that it’s depreciated. Not being able to access a transaction hash will cause future issues though. Thanks for your comments.

[yashovardhan]

Yes, it will change the address from one dApp to another. Every dapp integrating web3auth has a different key, depending upon the parameters mentioned in this document: https://web3auth.io/docs/troubleshooting/different-private-key

The internal RPC errors are generally associated with your RPC providers limitations or account funding etc. These errors are generally not related to web3auth integration. Nonetheless you can raise a new issue around it with particular error details.