Improve nonce handling

[whoabuddy]

While testing I managed to get myself in a stuck nonce situation, I suspect that the last nonce value ended up either overwriting some deploys I had or increased itself too quickly.

PR #76 introduced a slight change to how the nonce was incremented, might be a regression there but ultimately we can do better detection.

The minting script we used for the airdrop had a reliable method we could replicate, plus some other goodies regarding chained or dependent transactions. It used a websocket to connect to the API and watch for new blocks, then processed its own logic when each new block arrived.

Example of nonce gapped account

• last executed is 59
• pending are 67, 71-86

Also noting that a good blanket fix for this would be to submit a new TX with the fee bumped by 0.000001 in the correct nonce order, filling in the gaps and replacing the stuck transactions.

[biwasxyz]

This repository has been superseded by aibtc-mcp-server and skills. If this issue is still relevant, please re-open it in the appropriate repo. This repo will be archived soon.