5 Commits

Include renames

Author	SHA1	Message	Date
sneak	e9dc1fdccd	fix: the wallet's own send shows its amount to four decimal places (closes #522) ... ConfirmTx and the wait, success and error screens printed the text from Send's amount field as typed or as Max filled it in: `0.5 ETH`, `.5 ETH`, or `1.234147890123456789 ETH` after Max, where TxApproval shows a site's send as `0.5000 ETH`. ConfirmTx now writes the amount as TxApproval does: parsed at the scale it is encoded with, written back as plain decimal text, and cut by truncateAmountNeverZero(). It hands the status screens a copy carrying that text. The transaction is still signed for the exact amount, which stays on the pending transaction, and the USD value is priced from it. A saved confirmation screen whose amount is not text is no longer redrawn. Model: opus-5-5	2026-10-19 13:51:04 +00:00
clawbot	5e4b8ff3b0	fix: the confirmation screen reads its balance on the network it is drawn for (closes #558) ... ConfirmTx showed and checked the balance Send handed it, so a screen the popup reopened onto stated the balance as Send knew it, not as it is on the network the screen is drawn for. Each time it is shown, ConfirmTx now reads the From address's ETH balance, and for a token send its token balance, from the node reviewedNetworkProvider() picks for the network the transaction was reviewed for, the node the fee estimate and recipient checks ask. The fee estimate starts once the read returns. Until then the balance line says "Loading..." and Sign & Send stays disabled; a failed read is stated as unknown. Each message the read can bring has a box reserved from the first paint, so nothing moves when it returns. Model: opus-5-5	2026-10-19 09:54:09 +02:00
clawbot	e2e1c5d40e	fix: the recipient warning says what it checked and skips addresses that have received ETH (closes #528) ... The transaction count the node reports is what an address has sent, so an address that only receives, such as a savings address, got the "ZERO transaction history" box on every send. The check now also asks the node for the recipient's balance and warns only when both are zero. The box says the address has never sent a transaction and holds no ETH, naming the active network's native token as the contract warning does. Model: opus-5-5	2026-10-19 02:34:13 +02:00
clawbot	ff05bd50f7	fix: only the user switches the wallet's network (closes #408) ... A connected site's wallet_switchEthereumChain request for the other supported network now opens a prompt in its own window, through the existing approval machinery, naming the site and both networks. The network, endpoints, balances and caches change, and chainChanged is sent, only when the user approves it; rejecting or closing the prompt answers 4001. One such prompt per site at a time; a request for the active network needs none. The approval window no longer shows the connection prompt while it waits for the approval's description, since both prompts answer on the same port. Model: opus-5-5	2026-10-08 07:30:16 +02:00
clawbot	e3790c5da4	chore: the native token's label follows the network (closes #372) ... networks.js gives each network a nativeCurrency (ETH, SepoliaETH) and nothing read it: every screen wrote ETH. The wallet's balances and the Send and confirmation screens now use the active network's. A transaction's figures use the network its chain id names, through nativeCurrencyByChainId(): the approval value and fee, the wait, success and error screens, history entries, the detail screen and the fee-limit refusal, so a site switching networks cannot make one read as another network's coin. The "ETH" that selectedToken and txInfo.token hold is the native token's id and is unchanged. A token reporting any network's nativeCurrency is a spoof, and the detail screen calls an entry a token transfer when it has a token contract. Model: opus-5-5	2026-10-05 01:26:04 +02:00