You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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:
However, when attempting to send a transaction with sequence 5160, I receive an error saying the expected sequence is 5175:
This creates a deadlock where:
Steps I've Tried
1. Sending transaction with sequence 5160 (actual account sequence)
Result:
2. Sending transaction with sequence 5175 (expected by network)
Result:
3. Using offline mode with various sequences
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
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.
The text was updated successfully, but these errors were encountered: