[SDK] Getting error: 'nonce too high. allowed nonce range: 0 - 20'

[max-bytekerk]

Team or Project

No response

Select the SDK

Python

ZK chain

Era

Environment

Mainnet

Issue Description

Hi, I'm trying to broadcast a transaction using V,R,S values. This is my process:

1. I have constructed the transaction (a swap on Syncswap). It looks like this:

tx = {
'value': 0,
 'chainId': 324,
 'from': '0xc9BA4D71E7946eDC1A17C7f03928b7711aE6Ac7B',
 'nonce': 29,
 'gas': 1000000,
 'gasPrice': 90500000,
 'to': '0xC8A3d1d834617796cdd8c68709e9719f41cb472E',
 'data': '0x414bf3890000000000000000000000003355df6d4c9c3035724fd0e3914de96a5a83aaf40000000000000000000000000469d9d1de0ee58fa1153ef00836b9bbcb84c0b60000000000000000000000000000000000000000000000000000000000000001000000000000000000000000c9ba4d71e7946edc1a17c7f03928b7711ae6ac7b0000000000000000000000000000000000000000000000000000000067c073b8000000000000000000000000000000000000000000000000000000000000138800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
}

2. I sign this transaction using the private key of my EOA. I get a signature with V,R,S values.

3. I now specifically want to use these V,R,S values to broadcast the transaction. So I execute the following process:

# Create an unsigned Transaction
unsigned_tx = serializable_unsigned_transaction_from_dict(tx)

# Sign the transaction using V,R,S
signed_tx = encode_transaction(unsigned_tx, vrs=(V, R, S))

# Get raw transaction hex
raw_tx_hex = to_hex(signed_tx)

# Broadcast!
sdk = ZkSyncBuilder.build("https://mainnet.era.zksync.io")
tx_hash = sdk.zksync.send_raw_transaction(raw_tx_hex)

This process works successfully when I use the private key of my EOA in step 2. However, I'm now trying to do this using an MPC wallet. I use the exact same process, with the only difference that the V,R,S values in step 2 are now given to me by my MPC provider. I then do the exact same things as in step 3, but when I try to broadcast I get the following error:

Web3RPCError: {'code': 3, 'message': 'nonce too high. allowed nonce range: 0 - 20, actual: 29', 'data': '0x'}

What does this mean? The nonce of my MPC wallet actually is 29 (at time of writing). So this "nonce too high. allowed nonce range: 0 - 20" does not make sense to me.

How should I interpret this?

Any input highly appreciated!

Expected Behavior

No error, successful broadcasting of the tx, and receiving the tx_hash.

Code Example

Please see description.

Repo Link (Optional)

No response

[JackHamer09]

Thanks for the report, will look into the issue and let you know asap!

[JackHamer09]

@max-bytekerk, there are a few potential reasons why you’re encountering this issue:

1. Signature Mismatch

   • The MPC-generated V, R, S values might be computed with different parameters (e.g., chain ID, recovery ID, etc.), leading to an incorrect recovered address.
   • As a result, the network interprets the transaction as coming from an address with 0 transactions, hence the allowed nonce range of 0-20.
   • The value 0 is due to resolving to an address with a transaction count of 0, while 20 is the max queue length the server allows.

2. Nonce Discrepancy

   • The network verifies the on-chain nonce of the recovered address.
   • If it determines the allowed nonce range is 0–20, a transaction with a nonce of 29 gets rejected.
   • This suggests the transaction is being signed incorrectly, leading to a different recovered address.

3. Server Instability

   • Network congestion or a slowdown at the time of submission could cause delays in processing transactions.
   • If you attempt to submit multiple transactions simultaneously, the server may still see unprocessed transactions within the allowed nonce range.
   • This could result in the “nonce too high” error if earlier transactions haven’t been processed yet.

---

Suggested Next Steps:

• Verify the Recovered Address:
  • Use the V, R, S values to manually recover the sender address.
  • Compare it with your MPC wallet address. If they don’t match, the issue is with how the signature is being computed.
• Check MPC Signing Process:
  • Ensure the MPC provider is signing the transaction correctly with the intended parameters (chain ID, recovery ID, etc.).
  • You may need to adjust how you’re constructing or encoding the transaction before signing.
• Manually Fetch Nonce from Network:
  • Before broadcasting, check the current nonce for the MPC wallet by querying the network.
  • Compare this against the nonce you are using.

[JackHamer09]

Let me know if you experience any other issues on zksync side!