Add Fee Bump Workflow with Mempool.space Accelerator Integration

[jamespepper81]

Problem

During network congestion, Bitcoin transactions with low fees get stuck in the mempool. While services like mempool.space Accelerator (https://mempool.space/accelerator) allow users to pay additional fees after broadcast to speed up confirmations, BitSleuth Analyzer currently lacks built-in functionality for this flow.

Proposal

Integrate a fee-bump workflow similar to mempool accelerators that allows users to:

• Check which transactions are eligible for acceleration (e.g., unconfirmed, not already RBF/CPFP bumped, not double-spent, valid for the external service’s criteria).
• Access the mempool.space Accelerator via API or direct deep-link to submit their stuck transaction.
• Estimate the fee/premium required for prioritized confirmation and show the estimated confirmation time.
• Display accelerator service results, notify users of success/failure, and update mempool status in real time.

Requirements

• Detect stuck transactions that meet the accelerator’s eligibility rules.
• Integrate with the mempool.space Accelerator API, or if unavailable, provide deep-linking and clear UI/CLI/API to guide the user through the process.
• Robust error messaging for unsupported tx types, exhausted accelerator slots, or other remote errors.
• Metrics: log all attempted bumps, outcomes (accepted, rejected, error), and any associated transaction IDs.

Considerations

• Security: Clearly communicate that submission will send the transaction ID to a third-party (mempool.space) for acceleration.
• User Experience: Seamless UI/CLI flow, confirmation dialogs, and updates as acceleration status changes.
• Document supported wallets/backends (e.g., Bitcoin Core, Electrum, third-party wallet compatibility).

Acceptance criteria

• Users can identify and select eligible transactions for acceleration.
• The system displays up-to-date guidance and acceleration options (in-app or via external link).
• Accelerator results (accepted, rejected) are surfaced in the UI/logs.
• All actions are auditable and logged.

---

Related resource: Mempool.space Accelerator