Movement SDK: Unable to Sign and Send Transaction on Testnet (Movevent Token Deployment)

Help - Plug n Play PnP iOS SDK
, ,
1

IMG_8410
IMG_84101179×1819 498 KB

Hi Movement team,

I’m currently working on deploying and interacting with the Movement token contracts (MOVE) for our Movevent Network Movevent DAO and Movement Network Foundation project. We’re using the Movement SDK and facing an issue while trying to sign and send transactions on the testnet.

Issue Description:

While attempting to mint tokens or call a smart contract method using a connected wallet on the testnet, the SDK throws an error (Invalid Signature or fails silently). We suspect it might be related to gas estimation, incorrect setup, or a signing flow issue with the connected wallet.

Environment Details:

  • SDK Version: @movementlabs/sdk (latest as of June 2025)
  • Platform: Node.js backend + Ethers.js integration
  • Network: Movement Testnet
  • Wallet Used: MetaMask (connected to Movement Testnet)
  • Repo: https://github.com/cshein45-Movement
  • Project: Movevent DAO / Movement Network Foundation
  • Operating System: macOS + Ubuntu (tested both)

Steps to Reproduce:

  1. Set up Movement SDK and initialize connection with wallet
  2. Attempt to call a mint function or send tokens via smart contract
  3. Receive error during signing or nothing happens (pending state)

Expected Behavior:

Transaction should be signed and sent on-chain with confirmation receipt.

Actual Behavior:

Either:

  • Nothing happens
  • OR the SDK returns a vague error about the signature or gas

Additional Context / Logs:

  • MOVE Token: 0x3073f7aAA4DB83f95e9FFf17424F71D4751a3073
  • Test wallet: 0xb2cA1CAecd1D3e9bF84B9332cb4aB11961639a5c
  • Repo: cshein45-Movement GitHub
  • Smart Contract Setup already deployed and verified on testnet
  • Confirmed that balance and wallet connection is OK
2

Thank you for the detailed report! Here’s a summary of your issue and the details gathered for the Web3Auth support team:

Issue Summary

Problem:
Unable to sign and send transactions (e.g., mint tokens or interact with the MOVE contract) on Movement Testnet using the Movement SDK. The SDK either throws an “Invalid Signature” error or fails silently (transaction stays pending).

Integration & Environment Details

  • SDK: @movementlabs/sdk (latest as of June 2025)
  • Platform: Node.js backend with Ethers.js integration
  • Network: Movement Testnet
  • Wallet: MetaMask (connected to Movement Testnet)
  • OS: macOS & Ubuntu (both tested)
  • Smart Contract: MOVE Token (0x3073f7aAA4DB83f95e9FFf17424F71D4751a3073)
  • Test Wallet: 0xb2cA1CAecd1D3e9bF84B9332cb4aB11961639a5c
  • Repo: cshein45-Movement GitHub
  • Project: Movevent DAO / Movement Network Foundation

Steps to Reproduce

  1. Initialize Movement SDK and connect wallet
  2. Attempt to call a mint function or send tokens
  3. Error occurs during signing or transaction remains pending

Observed vs Expected Behavior

  • Expected: Transaction is signed and sent, with a confirmation receipt.
  • Actual:
    • No transaction sent (pending state), or
    • SDK returns a vague error (Invalid Signature/gas issue)

Additional Context

  • Smart contract is deployed and verified on testnet
  • Wallet connection and balance are confirmed as OK
  • Screenshot provided (please ensure the image is visible to the support team)

Next Steps & Suggestions

To Help Diagnose Further:

  • Could you please share:
    • The code snippet used for Web3Auth and Ethers.js provider initialization and transaction sending?
      (This will help us check for any issues in provider usage or signing flow.)
    • The exact error message (if any) from the browser/Node.js console or SDK logs.
    • If using a custom RPC or chain configuration, please share those details as well.

Potential Solution Areas:

  • Make sure you are using the correct provider instance for signing (i.e., the one from Web3Auth, not directly from MetaMask).
  • Double-check the chainId and network configuration in your SDK and Ethers.js setup.
  • If you are using Web3Auth’s EIP1193 provider, follow the Ethereum Integration Guide for correct setup.
  • For gas estimation issues, try manually specifying gasLimit and gasPrice in your transaction object.

Reference Documentation:

Once you provide the code snippet and any error logs, the support team can assist you further. Thank you for your patience and detailed report!

Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours

1 Like
3

Hey @MOVE
Does Movement SDK use Web3Auth under the hood?
Other than that I don’t know how to help you.