relay-diagnostic

Recover a stuck sponsored transaction by diagnosing the sponsor relay nonce health and automating recovery via RBF or gap-fill. The tool fetches nonce state from the Hiro API and uses an unlocked wallet or sponsor API key to restore nonce progression.

Sponsor relay nonce desync occurs when pending transactions drop or reorder in the mempool, creating a gap. Running a health check surfaces this mempool desync by fetching the current nonce state from the Hiro API to detect inconsistencies.

Check sponsor relay health on mainnet and testnet by running the check-health subcommand. It verifies nonce state, surfaces potential issues, and identifies nonce gaps or mempool desync to maintain sponsor reliability and nonce integrity.

Yes, automating nonce gap recovery requires an unlocked wallet or a sponsor API key. The recover subcommand uses these credentials to execute RBF or gap-fill transactions that unstick sponsor transactions and restore proper nonce progression.

The best way to unstick a sponsor transaction using RBF is to run an automated recovery command after a health check detects the stuck nonce. This replaces the original transaction with a higher fee to restore relay nonce progression.

Use gap-fill instead of RBF when a nonce gap exists but the original transaction is not easily replaceable. The recovery tool automates gap-fill to fill the missing nonce, allowing subsequent sponsored transactions to process and restoring relay nonce progression.