On the confirm-tx screen, asynchronously checks the recipient address via the Blockscout API. If the address has never sent or received any transactions, a prominent red warning banner is displayed.
Changes:
src/shared/transactions.js: Added hasTransactionHistory() that queries GET /addresses/:addr on Blockscout v2. Returns false if the address has 0 combined transactions+token transfers (or 404), true if >0, null on error (fail-open).
src/popup/views/confirmTx.js: After showing the confirm view, calls checkRecipientHistory() which appends a red-bordered warning to the warnings section if the address has no history.
On the confirm-tx screen, asynchronously checks the recipient address via the Blockscout API. If the address has never sent or received any transactions, a prominent red warning banner is displayed.
Changes:
- `src/shared/transactions.js`: Added `hasTransactionHistory()` that queries `GET /addresses/:addr` on Blockscout v2. Returns `false` if the address has 0 combined transactions+token transfers (or 404), `true` if >0, `null` on error (fail-open).
- `src/popup/views/confirmTx.js`: After showing the confirm view, calls `checkRecipientHistory()` which appends a red-bordered warning to the warnings section if the address has no history.
Closes #82
On the confirm-tx screen, asynchronously check the recipient address
via Blockscout API. If the address has never sent or received any
transactions, display a prominent red warning banner.
Closes#82
Added hasTransactionHistory() to transactions.js — queries Blockscout v2 /addresses/:addr endpoint and checks combined transactions_count + token_transfers_count. Returns false for zero-history (or 404), null on error (fail-open, does not block user).
Added checkRecipientHistory() to confirmTx.js — runs async after view loads, appends a red-bordered warning banner if recipient has no on-chain history.
docker build . passes (tests + prettier + build).
PR created. Changes:
- Added `hasTransactionHistory()` to `transactions.js` — queries Blockscout v2 `/addresses/:addr` endpoint and checks combined `transactions_count + token_transfers_count`. Returns `false` for zero-history (or 404), `null` on error (fail-open, does not block user).
- Added `checkRecipientHistory()` to `confirmTx.js` — runs async after view loads, appends a red-bordered warning banner if recipient has no on-chain history.
`docker build .` passes (tests + prettier + build).
Pull request closed
Please reopen this pull request to perform a merge.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On the confirm-tx screen, asynchronously checks the recipient address via the Blockscout API. If the address has never sent or received any transactions, a prominent red warning banner is displayed.
Changes:
src/shared/transactions.js: AddedhasTransactionHistory()that queriesGET /addresses/:addron Blockscout v2. Returnsfalseif the address has 0 combined transactions+token transfers (or 404),trueif >0,nullon error (fail-open).src/popup/views/confirmTx.js: After showing the confirm view, callscheckRecipientHistory()which appends a red-bordered warning to the warnings section if the address has no history.Closes #82
Closing as duplicate of #98 which already addresses issue #82 and is merge-ready.
PR created. Changes:
hasTransactionHistory()totransactions.js— queries Blockscout v2/addresses/:addrendpoint and checks combinedtransactions_count + token_transfers_count. Returnsfalsefor zero-history (or 404),nullon error (fail-open, does not block user).checkRecipientHistory()toconfirmTx.js— runs async after view loads, appends a red-bordered warning banner if recipient has no on-chain history.docker build .passes (tests + prettier + build).Pull request closed