fix: WaitTx and TransactionDetail use the network the transaction was sent on (closes #584)

WaitTx asked the active network's node for the receipt, so after a network switch a transaction sent on the other network was never found and was reported as timed out. It now asks the node of the network its chain id names, through reviewedNetworkProvider(), moved from ConfirmTx into the shared view helpers so both screens use one function. WaitTx and TransactionDetail build their explorer links for that network too. A stored wait or transaction whose chain id names no network is refused on restore, as a stored ConfirmTx transaction already is. Model: opus-5-5
2026-10-19 21:03:43 +00:00
parent 96446f4661
commit c5d5854e8f
11 changed files with 220 additions and 66 deletions
@@ -225,7 +225,12 @@ describe("a popup already open when the stored profile becomes unreadable", () =
                viewData: {
                    pendingWait: {
                        hash: "0x1",
-                        txInfo: { to: ADDRESS, amount: "1", token: "ETH" },
+                        txInfo: {
+                            to: ADDRESS,
+                            amount: "1",
+                            token: "ETH",
+                            chainId: "0x1",
+                        },
                        broadcastTime: Date.now(),
                    },
                },