Wallet service plugin send eth on Sepolia is always 0?

[leonwork919]

• SDK Version:
  @web3auth/single-factor-auth 9.0.0
  @web3auth/wallet-services-plugin 9.1.0
• Platform:
  web
• Browser Console Screenshots:
  none
• If the issue is related to Custom Authentication, please include the following information (optional):
  • Verifier Name: tma-wizzwoods-demo
  • JWKS Endpoint: https://tma-test.wizzwoods.com/_web3auth/jwks.json
  • Sample idToken (JWT):
    const tokenInfo: TokenData = {
    isRefresh: false,
    username: ‘496568435’,
    userId: 496568435,
    sub: ‘496568435’,
    name: ‘496568435’,
    email: wizz_496568435@web3auth.io,
    aud: ‘urn:my-resource-server’,
    iss: ‘https://ttest.wizzwoods.com’,
    iat: Math.floor(Date.now() / 1000),
    exp: Math.floor(Date.now() / 1000) + 60 * 60,
    };

my wallet address: 0x88F931EcD8e67032c724A7Ca50EE8665236EE22E

When I use the wallet service plugin to send a tx on the Sepolia ,I want send 0.001ETH and the pluin show data is correct,but when I view the tx on the etherscan ,the send value always is zero?
pls help me,thanks.

screenshots:

[w3abot]

Hi LeonCool!

Thank you for providing detailed information about the issue you’re encountering. Here’s a quick summary and some questions to clarify your situation:

Issue Summary:

• SDK Details: Single Factor Auth Web SDK
• SDK Versions:
  • @web3auth/single-factor-auth: 9.0.0
  • @web3auth/wallet-services-plugin: 9.1.0
• Platform: Web
• Issue: When sending a transaction on Sepolia using the wallet service plugin, the transaction value shows as 0 on Etherscan, despite the plugin indicating the correct amount (0.001 ETH).
• Custom Authentication:
  • Verifier Name: tma-wizzwoods-demo
  • JWKS Endpoint: https://tma-test.wizzwoods.com/_web3auth/jwks.json
  • Sample idToken (JWT): Provided.
• Wallet Address: 0x88F931EcD8e67032c724A7Ca50EE8665236EE22E
• Screenshots: Attached (not fully visible here, but appreciated.)

To help the support team assist you better, could you please provide the following additional details:

1. Initialization and Login Code Snippets: This will help us verify if the wallet service plugin is correctly integrated.
2. Specific Code for Sending Transaction: This snippet will help us see how you’re invoking the transaction using the wallet service plugin.

Feel free to reply with the additional details if it’s possible, and the support team will get on it right away. Thank you for your patience and understanding.

This response was generated by the Web3Auth Bot and a person from the Web3Auth team will come and give answer to your query as well.

[maharshi]

Hey @leonwork919,

Nice to meet you again! Could you share the chainConfig you’re using for ethSepolia and the Web3Auth initialization snippet as well? Also, I remember you were testing this on Bera Testnet before—does it work fine there, or are you encountering the same issue as before?

Looking forward to hearing from you!

[leonwork919]

hello,@maharshi,thanks for your help.
Now I use the config copyed from the demo.

static CHAIN_CONFIG = {
chainId: ‘0xaa36a7’,
displayName: ‘Ethereum Sepolia Testnet’,
chainNamespace: ‘eip155’,
tickerName: ‘Ethereum’,
ticker: ‘ETH’,
decimals: 18,
rpcTarget: ‘https://rpc.ankr.com/eth_sepolia’,
blockExplorerUrl: ‘https://sepolia.etherscan.io’,
logo: ‘https://cryptologos.cc/logos/polygon-matic-logo.png’,
};

And I use the SDK that like this

ant the tx request like this
url:
api-wallet.web3auth.io/transaction

payload:
{
“created_at”: “2024-09-25T06:34:20.940Z”,
“from”: “0x88f931ecd8e67032c724a7ca50ee8665236ee22e”,
“to”: “0xbd3c86f22f97b580389d8e0598529662ec047f26”,
“total_amount”: “0.005”,
“currency_amount”: “13.05325”,
“selected_currency”: “usd”,
“chain_id”: “0xaa36a7”,
“transaction_hash”:“0x94134ac84a3312f886480c0a6a13ae4e2124eca7325484338120b9a8bf78c68c”,
“transaction_category”: “sentEther”,
“gas”: “0x5208”,
“gasPrice”: “0x3fbac7e2f3”,
“nonce”: “0x4”,
“type”: “eth”,
“type_name”: “eth”,
“type_image_link”: “n/a”,
“symbol”: “eth”,
“status”: “submitted”,
“is_cancel”: false
}

I saw the payload total_amount is correct.Today I also test the diffurent SDK Version and berachain, all failed.

I have no idea about this problem.

The init code blow:

[leonwork919]

Dear @maharshi .

I find the problem, When I use SDK Version on 8, the operate work well done.

Now I use the SDK version is blow:

I think maybe have some details not dealt well on the version 9 update.

Blow is the new test result:

[maharshi]

Thanks for reporting, @leonwork919
We are looking into this issue, I’ll inform you when I have some news for you.