Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Account Sequence Mismatch Error in OG Chain Testnet #116

Open
Josephtran102 opened this issue Feb 27, 2025 · 0 comments
Open

Account Sequence Mismatch Error in OG Chain Testnet #116

Josephtran102 opened this issue Feb 27, 2025 · 0 comments

Comments

@Josephtran102
Copy link

Issue Description:
I'm experiencing a persistent account sequence mismatch error on the OG Chain testnet (zgtendermint_16600-2) that prevents me from submitting any transactions from my validator account.

Error Details
When querying my account, the sequence number shows as 5160:

0gchaind q account $(0gchaind keys show josephtran -a) --node https://og-testnet-rpc.itrocket.net:443
'@type': /cosmos.auth.v1beta1.BaseAccount
account_number: "106"
address: 0g1arf2rfrsx4pu9kpzxj06ydces6ptn8jw0pxzyw
pub_key:
  '@type': /ethermint.crypto.v1.ethsecp256k1.PubKey
  key: AnEnfincjzPo4Rz4BXtpROVrNZuxjrvI8p9v2tOl49Iq
sequence: "5160"

However, when attempting to send a transaction with sequence 5160, I receive an error saying the expected sequence is 5175:

raw_log: 'account sequence mismatch, expected 5175, got 5160: incorrect account sequence'

This creates a deadlock where:

  • The network expects sequence 5175
  • My account says it's at sequence 5160
  • I can't send transactions with either sequence number

Steps I've Tried
1. Sending transaction with sequence 5160 (actual account sequence)

0gchaind tx staking edit-validator \
--identity "891BC6B7C0D28458" \
--website "www.j-node.net" \
--chain-id zgtendermint_16600-2 \
--commission-rate "0.1" \
--from josephtran \
--gas 300000 \
--fees 5ua0gi \
--sequence 5160 \
--node https://og-testnet-rpc.itrocket.net:443 \
-y

Result:

account sequence mismatch, expected 5175, got 5160: incorrect account sequence

2. Sending transaction with sequence 5175 (expected by network)

0gchaind tx staking edit-validator \
--identity "891BC6B7C0D28458" \
--website "www.j-node.net" \
--chain-id zgtendermint_16600-2 \
--commission-rate "0.1" \
--from josephtran \
--gas 250000 \
--fees 2ua0gi \
--sequence 5175 \
--node http://localhost:10657 \
-y

Result:

account sequence mismatch, expected 5175, got 5160: incorrect account sequence

3. Using offline mode with various sequences

0gchaind tx staking edit-validator \
--identity "891BC6B7C0D28458" \
--website "www.j-node.net" \
--chain-id zgtendermint_16600-2 \
--commission-rate "0.1" \
--from josephtran \
--gas 200000 \
--fees 1ua0gi \
--sequence 5160 \
--account-number 106 \
--offline \
--broadcast-mode async \
--node https://og-testnet-rpc.itrocket.net:443 \
-y

Result: Transaction accepted into mempool but not processed.

4. Increasing gas fees
Tried with fees ranging from 0.1ua0gi up to 5ua0gi with no success.
5. Using different RPC endpoints
Tried both public RPC endpoints and my local validator node's RPC endpoint.
6. Resetting my node's state
Performed 0gchaind tendermint unsafe-reset-all and resynced, but the issue persists.

Environment

  • OG Chain Testnet: zgtendermint_16600-2
  • Node Version: v0.5.0
  • Operating System: Linux
  • GLIBC Version: 2.35

Impact
This issue prevents me from updating my validator information, delegating, or performing any other on-chain actions with my account.

Questions

Is there a way to force reset my account's sequence number?
Could there be pending transactions in the mempool that the network is aware of but haven't been finalized?
Is this a known issue with the testnet?

Thank you for your assistance in resolving this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant