From d4db7d545d51cde2f5a98426c1839e0fe0745efa Mon Sep 17 00:00:00 2001 From: Adam Soltys Date: Wed, 24 Jun 2026 23:48:53 -0700 Subject: Detect stuck low-fee txs and stop actively monitoring them MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A pending tx is judged 'stuck' once it has waited ~10 blocks (≈100 min) and its fee rate (fee/vsize) is below the mempool's current floor (minimumFee) — i.e. it's been purged and won't confirm without a bump. _txSummary now records vsize and a firstSeen timestamp (persisted in cache) to support this. Stuck txs are dropped from active monitoring: excluded from the watched-address set and from the fast-poll trigger, so they don't hold a socket slot or keep us in the 6s lane. The slow ~25s reconcile still catches one if the floor later drops and it confirms. History flags them (⚠ stuck) and the detail view explains it — pointing outgoing ones at the existing fee bump. Co-Authored-By: Claude Opus 4.8 (1M context) --- src/i18n.js | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'src/i18n.js') diff --git a/src/i18n.js b/src/i18n.js index d948917..ce0f94d 100644 --- a/src/i18n.js +++ b/src/i18n.js @@ -174,6 +174,10 @@ const STR = { received: 'Received', sent: 'Sent', pendingTag: '⏳ pending', + stuckTag: '⚠ stuck', + stuckNote: 'Fee too low — may not confirm', + stuckIncomingNote: '⚠ This payment’s fee is below the current network floor, so it may not confirm. Only the sender can speed it up (bump or re-send).', + stuckOutgoingNote: '⚠ This transaction’s fee is below the current network floor, so it may not confirm on its own. Bump the fee below to rebroadcast it at a higher rate.', liveTag: 'Live', pollingTag: 'Polling', awaitingConfirmation: 'awaiting confirmation', -- cgit v1.2.3