Show what a PENDING swap is waiting on - #179
Merged
Merged
Conversation
A claimed swap sat on a blank page for the whole source-chain confirmation window — no status line, and a timeline whose first row was 'Initiated —' because initiated_at only lands once the deposit is final (20–45 min on BTC). The page already had everything it needed: the SwapClaimed event's block time, the deposit hash, and the live reservation behind the row. - Status helper for PENDING (and EXPIRED): names the source chain, the confirmation depth validators wait for, and the typical wall-clock, from the blockSecs/confirmations das now serves on /chains. - Timeline opens with 'Deposit claimed' (SwapClaimed block time) and 'Initiated' is a live waiting row — what it awaits plus elapsed time — instead of a hardcoded done step. - Sends/Receives tx hashes link to their chain explorer next to the copy affordance, so the user can watch confirmations accrue. - Pair, amounts, miner and proven wallet backfill from the live reservation (same lookup the tracker rows use) when the claim-stage row is still empty. - EXPIRED counts as terminal; chain seed refreshed for the new fields.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A claimed BTC→SOL swap sat on an almost-empty transaction page for the whole source-confirmation window: no status line for PENDING, and a timeline whose first row read Initiated — because
initiated_atonly lands once the deposit is final (20–45 min on BTC). That is exactly the phase where the user most wants reassurance.The page already had what it needed — the
SwapClaimedevent block time, the deposit hash, the live reservation — it just didn't use any of it. No DB change; the das side landed yesterday in #119 (blockSecs/confirmationson/chains).What
SwapClaimedblock time); Initiated becomes a live waiting row — awaiting 2 Bitcoin confirmations · ~52m elapsed — instead of a hardcoded done step.useReservationLookupthe tracker rows use.EXPIREDnow counts as terminal inisTerminal(no more ticking counters on a dead row);ChainInfogainsblockSecs/confirmations; chain seed refreshed (which also pulls insolusdc, hence thellms.txtdelta).Verified
Rendered against test-api: PENDING #112 (btc→sol, sitting at 52m on a slow testnet4 block) and COMPLETED #111 (tao→sol).
tsc -bandeslintclean.