[j0ntz]

Description

Asana task

On a plain send with Stealth off, the send scene showed a Stealth reason line under the toggle even though no swap was involved. A CELO or RBTC send read "Stealth routing is not available when sending CELO to itself", and a small ETH send read the private-route minimum.

The line rendered whenever Stealth was off. With no recipient asset picked, the destination defaults to the source asset. The scene then treated a plain send as a same-asset Stealth route and explained why that route was unavailable.

Changes:

• The reason line under the toggle now renders only when a different recipient asset is picked (a swap is already involved), or after a failed Stealth quote turned the toggle back off.
• Tapping the toggle on a plain send still toasts the reason. For an asset the Stealth provider does not serve at all (CELO, Fantom), the toast now reads "Stealth routing is not available for CELO." instead of the "to itself" wording.
• The below-minimum line follows the same rule.

Tests: three new cases in SendScene2.recipientNetwork.ui.test.tsx cover an unserved asset's plain send, the minimum line before and after picking a recipient asset, and the line kept after a failed Stealth quote. The harness gains a fake swap plugin that refuses every quote.

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

• Yes
• No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

• Tested on iOS device
• Tested on Android device
• Tested on small-screen device (iPod Touch)
• Tested on large-screen device (tablet)

---

Note

Low Risk
Send-scene UI and copy only; toggle behavior on tap is unchanged aside from clearer unsupported-asset toasts.

Overview
Fixes misleading Stealth Send copy on plain sends (same asset, no recipient swap picked). The blocked-reason line under the toggle no longer appears just because Stealth is off; it only shows when a cross-asset recipient is already chosen or after a failed Stealth quote turns the toggle off. Tapping the toggle on a plain send still toasts the reason.

When Stealth cannot serve an asset at all, blocked messaging uses a new stealth_asset_unsupported_1s string instead of the “send to itself” wording. Tests cover plain-send notes, minimum-amount visibility before/after picking a recipient asset, and persistence after quote failure (with a fake Houdini plugin that refuses quotes).

^{Reviewed by Cursor Bugbot for commit 35a95f1. Bugbot is set up for automated code reviews on this repo. Configure here.}

Test evidence

7ab5d7e Hide Stealth reason on a plain send 2026-10-16 🪓 forced every private Stealth quote to refuse (temporary edit in the quote fetch, reverted)	1. celo plain send no note	2. celo toggle toast	3. eth 5usd plain send no note
	4. eth to btc swap shows minimum	5. 🪓 failed quote line

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-10-16T23:03:06.507124Z	7ab5d7e	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.