When confirming a transaction, asynchronously checks the recipient address via Blockscout API. If the address has zero transactions and zero token transfers, displays a prominent red warning banner advising the user to double-check the address.
Also updates existing warning styling to use red borders/text for better visibility.
Uses Blockscout /addresses/{addr} endpoint to check transactions_count and token_transfers_count
Appends warning to existing warnings array and re-renders
Failure is silent (best-effort check)
Closes #82
When confirming a transaction, asynchronously checks the recipient address via Blockscout API. If the address has zero transactions and zero token transfers, displays a prominent red warning banner advising the user to double-check the address.
Also updates existing warning styling to use red borders/text for better visibility.
- Uses Blockscout `/addresses/{addr}` endpoint to check `transactions_count` and `token_transfers_count`
- Appends warning to existing warnings array and re-renders
- Failure is silent (best-effort check)
clawbot
self-assigned this 2026-02-28 22:31:50 +01:00
Closes#82
When confirming a transaction, asynchronously checks the recipient
address via Blockscout API. If the address has zero transactions and
zero token transfers, displays a prominent red warning banner advising
the user to double-check the address.
Also updates existing warning styling to use red borders/text for
better visibility.
Added async checkRecipientHistory() that queries Blockscout /addresses/{addr} endpoint after the confirm-tx view loads
If transactions_count + token_transfers_count == 0, appends a red warning: "This address has ZERO transaction history. It may be incorrect. Double-check before sending."
Updated all warning styling to use red borders and text (border-red-500 text-red-500) for better visibility
Check is best-effort; failures are silently logged
docker build . passes (tests + lint + build).
Implementation complete. Changes:
- Added async `checkRecipientHistory()` that queries Blockscout `/addresses/{addr}` endpoint after the confirm-tx view loads
- If `transactions_count + token_transfers_count == 0`, appends a red warning: "This address has ZERO transaction history. It may be incorrect. Double-check before sending."
- Updated all warning styling to use red borders and text (`border-red-500 text-red-500`) for better visibility
- Check is best-effort; failures are silently logged
`docker build .` passes (tests + lint + build).
clawbot
removed their assignment 2026-02-28 22:32:11 +01:00
clawbot
self-assigned this 2026-02-28 22:45:39 +01:00
Correctly queries Blockscout /addresses/{addr} endpoint for transactions_count + token_transfers_count
Shows red warning banner when both are zero — matches #82 requirements
Silent failure on API error (best-effort) — good
state.blockscoutUrl fallback to DEFAULT_BLOCKSCOUT_URL allows per-network override
Warning styling updated to red (border-red-500, text-red-500) with ⚠ emoji
No linter/config changes
docker build . passes
Marked merge-ready and assigned to @sneak for merge.
**Review: ✅ PASS**
Code review of the diff looks clean:
- Correctly queries Blockscout `/addresses/{addr}` endpoint for `transactions_count` + `token_transfers_count`
- Shows red warning banner when both are zero — matches #82 requirements
- Silent failure on API error (best-effort) — good
- `state.blockscoutUrl` fallback to `DEFAULT_BLOCKSCOUT_URL` allows per-network override
- Warning styling updated to red (`border-red-500`, `text-red-500`) with ⚠ emoji
- No linter/config changes
- `docker build .` passes
Marked `merge-ready` and assigned to @sneak for 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.
Closes #82
When confirming a transaction, asynchronously checks the recipient address via Blockscout API. If the address has zero transactions and zero token transfers, displays a prominent red warning banner advising the user to double-check the address.
Also updates existing warning styling to use red borders/text for better visibility.
/addresses/{addr}endpoint to checktransactions_countandtoken_transfers_countImplementation complete. Changes:
checkRecipientHistory()that queries Blockscout/addresses/{addr}endpoint after the confirm-tx view loadstransactions_count + token_transfers_count == 0, appends a red warning: "This address has ZERO transaction history. It may be incorrect. Double-check before sending."border-red-500 text-red-500) for better visibilitydocker build .passes (tests + lint + build).Review: ✅ PASS
Code review of the diff looks clean:
/addresses/{addr}endpoint fortransactions_count+token_transfers_countstate.blockscoutUrlfallback toDEFAULT_BLOCKSCOUT_URLallows per-network overrideborder-red-500,text-red-500) with ⚠ emojidocker build .passesMarked
merge-readyand assigned to @sneak for merge.dupe #98
Pull request closed