feat: add USDT0 launch banner and promo sheet to Home

[CassioMG]

TL;DR

Adds a dismissible "USDT0 is live on Stellar" promo banner to the Home screen, between the action buttons and the account tabs. Tapping it slides up a fullscreen sheet with the USDT0 launch details and three actions: "Swap to USDT0" opens sushi.com's Stellar swap in a new tab, "Receive USDT0" routes to the account QR code screen, and "Transfer to Stellar" opens the usdt0.to bridge in a new tab. The banner's X persists dismissal, reusing the storage/message plumbing of the old "Introducing Freighter Mobile" promo (removed in #2962) renamed to "USDT0 Launch Banner" throughout.

Designs: Home banner · Launch sheet

usdt0-launch.mov

Implementation details (for agents)

Dismissal plumbing (restore of #2962, renamed): SERVICE_TYPES.GET_USDT0_LAUNCH_BANNER_DISMISSED / DISMISS_USDT0_LAUNCH_BANNER, message types, popup-side helpers in @shared/api/internal, background handlers getUsdt0LaunchBannerDismissed / dismissUsdt0LaunchBanner wired into popupMessageListener, and the usdt0LaunchBannerDismissed key in localStorageTypes. Storage stays background-owned; the popup goes through messages.

Banner — Usdt0LaunchBanner, rendered in AccountHeader after the Add/Send/Swap tiles:

• Hidden while the dismissed-state loads and once dismissed; the X persists dismissal via the background.
• The launch surface is a semantic <button> sibling of the dismiss button (keyboard/AT accessible, no nested controls) carrying the card padding, so the whole card is a click target; the logo is alt="" (decorative inside a labeled control).
• Card metrics per Figma: 12px/16px padding, 38px logo, no gap in the title/subtitle stack; surrounding vertical spacing intentionally halved vs. the bannerless layout (12px above via scoped negative margin, 8px below) so the promo takes less Home real estate.

Sheet — Usdt0LaunchSheet, opened from the banner through the same radix Sheet side="bottom" fullscreen pattern as Discover:

• Green→dark gradient hero with arcs/lockup SVGs exported from Figma; content flows top-down below the hero (rather than bottom-anchored) so sidebar mode collects surplus space above the footer instead of between the hero and copy.
• Close is the shared BackButton used by the QR code screen (via customButtonComponent, keeping a real <button> with a localized label) inside a header mirroring the View app-header metrics, so the X sits identically across the sheet → QR transition.
• Footer actions, top to bottom: Swap to USDT0 (SDS secondary filled pill + ArrowUpRight, openTab("https://www.sushi.com/stellar/swap")), Receive USDT0 (SDS tertiary outlined — its tokens match the design's background/border/text exactly, so no custom CSS — closes the sheet and navigateTo(ROUTES.viewPublicKey), the same destination as Add funds' "Transfer from another wallet"), and Transfer to Stellar (borderless, ArrowUpRight, openTab to the usdt0.to bridge — hand-rolled since no SDS Button variant is transparent, mirroring the lg metrics of the two above it).
• Layout is budgeted so all three actions clear the 600px popup without scrolling: 304px of chrome + 212px of copy leaves 84px for the copy column's top offset (set to 80px). The hero art is absolutely positioned, so the USDT0 lockup keeps its design position while the copy moves up.
• Root scrolls vertically and clips only horizontally, with a non-shrinking body, so short viewports (squat sidebar windows, high zoom) reach the CTAs by scrolling instead of clipping them.
• SDS Text components use addlClassName (a plain className replaces SDS's own classes due to prop-spread order) and keep stock SDS type metrics; the description renders as="div" to escape global.scss's p { color: inherit !important } and keep its muted color. Overrides that fight SDS resets use doubled selectors (.Parent .Parent__x).

i18n: all strings through t() with en + pt entries (pt machine-authored — native review welcome); catalogs sorted by the project's i18next scanner. Figma copy typos ("USDT0 is now", "backed,unified") normalized to single-spaced text.

Verification: yarn build:extension and yarn build:extension:translations clean; yarn test:ci 1706 passed / 0 failed (e2e suites fail at import under plain jest locally, pre-existing); pre-commit lint + scanner green throughout.

Review history: Copilot's a11y round (semantic button, localized aria-labels, decorative logo alt) and its clipped-CTA finding are fixed with in-thread replies; an internal review pass added the alt/i18n and full-card click-target fixes.

Follow-ups / out of scope:

• No analytics events on banner/sheet interactions; add if metrics are wanted for the campaign.
• No unit tests for the new components (temporary promo; matches the old banner and is declared intentional on the Copilot thread).
• usdt0LaunchBannerDismissed will orphan in storage when the promo is eventually removed — accepted, same as Remove the "Introducing Freighter Mobile" promo banner #2962.
• The sheet's gap under the lockup is tighter than the design (~9px vs ~41px): our 80px header (matching the QR screen's X) and lg buttons spend ~78px more than the Figma frame in the same 600px. Dropping the actions to size="md" would buy it back if design prefers.

🤖 Generated with Claude Code

[github-actions]

PR Preview build is ready: https://github.com/stellar/freighter/releases/tag/untagged-7bd4e5182fcc101bf54f
Backend: V1 prod + V2 beta (no sandbox configured for @CassioMG). SDF collaborators only — install instructions in the release description.

[Copilot]

Pull request overview

Adds a dismissible USDT0 launch promotion to Home, backed by persistent background storage and a fullscreen details sheet.

Changes:

• Adds the USDT0 banner, launch sheet, and promotional assets.
• Adds persistent dismissal messaging and storage.
• Adds English and Portuguese translations.

Reviewed changes

Copilot reviewed 14 out of 17 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
@shared/api/internal.ts	Adds dismissal API helpers.
@shared/api/types/message-request.ts	Adds dismissal message types.
@shared/constants/services.ts	Adds service identifiers.
extension/src/background/messageListener/handlers/dismissUsdt0LaunchBanner.ts	Persists dismissal.
extension/src/background/messageListener/handlers/getUsdt0LaunchBannerDismissed.ts	Reads dismissal state.
extension/src/background/messageListener/popupMessageListener.ts	Routes new messages.
extension/src/constants/localStorageTypes.ts	Defines the storage key.
extension/src/popup/assets/logo-usdt0.png	Provides the banner logo.
extension/src/popup/assets/usdt0-arcs.svg	Provides hero artwork.
extension/src/popup/assets/usdt0-lockup.svg	Provides USDT0 branding.
extension/src/popup/components/account/AccountHeader/index.tsx	Renders the banner on Home.
extension/src/popup/components/account/Usdt0LaunchBanner/index.tsx	Implements banner behavior and sheet state.
extension/src/popup/components/account/Usdt0LaunchBanner/styles.scss	Styles the banner.
extension/src/popup/components/account/Usdt0LaunchBanner/Usdt0LaunchSheet/index.tsx	Implements launch details and CTA.
extension/src/popup/components/account/Usdt0LaunchBanner/Usdt0LaunchSheet/styles.scss	Styles the fullscreen sheet.
extension/src/popup/locales/en/translation.json	Adds English copy.
extension/src/popup/locales/pt/translation.json	Adds Portuguese copy.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 14 out of 17 changed files in this pull request and generated 1 comment.

Suppressed comments (1)

Previously missed (1) — in code that hasn't changed since the last review.

extension/src/popup/components/account/Usdt0LaunchBanner/Usdt0LaunchSheet/styles.scss:106

• At shorter sidebar heights or increased browser zoom, the fixed header/footer leave less room than this body's hard-coded 188px hero offset and feature content require. Because the sheet root hides overflow and the body itself cannot scroll, the lower feature text can be clipped behind the footer with no way to reach it. Make the flex body vertically scrollable so the CTA can remain fixed while all launch details stay reachable.

[Copilot]

Pull request overview

Copilot reviewed 14 out of 17 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 14 out of 17 changed files in this pull request and generated no new comments.

Suppressed comments (3)

Previously missed (3) — in code that hasn't changed since the last review.

extension/src/background/messageListener/handlers/dismissUsdt0LaunchBanner.ts:12

• A failed storage write/read currently escapes this background handler as a rejected runtime message. Background handlers are expected to catch unexpected failures, report them, and return a structured { error } response; this also avoids the unnecessary read after a successful write.
  extension/src/background/messageListener/handlers/getUsdt0LaunchBannerDismissed.ts:11
• If browser.storage.local.get rejects, this handler rejects the runtime message instead of honoring the background-handler contract to return a structured error. Catch and report the storage failure, then return an error response so the message channel resolves predictably.
  extension/src/popup/components/account/Usdt0LaunchBanner/Usdt0LaunchSheet/index.tsx:40
• This lockup is decorative: the dialog already has the accessible SheetTitle “USDT0 is now on Stellar,” and the visible title repeats the brand. A non-empty alt makes screen readers announce “USDT0” redundantly before the title; use an empty alt as done for the banner logo and arcs.

[Copilot]

Pull request overview

Copilot reviewed 14 out of 17 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 14 out of 17 changed files in this pull request and generated no new comments.

Suppressed comments (3)

Previously missed (2) — in code that hasn't changed since the last review.

extension/src/popup/components/account/Usdt0LaunchBanner/index.tsx:35

• A rejected storage/message lookup does not mean the user has not dismissed the banner; forcing false here resurfaces the promo when a persisted dismissal temporarily cannot be read. Fail closed by hiding it on lookup failure, consistent with popup/views/Discover/hooks/useDiscoverWelcome.ts:19-22.
  extension/src/popup/components/account/Usdt0LaunchBanner/index.tsx:111
• Preventing Radix's open autofocus leaves keyboard focus on the banner behind the modal instead of moving it into the newly opened sheet. Let the dialog apply its default autofocus (which will reach the close button), or explicitly focus an element inside the sheet so keyboard and assistive-technology users enter the dialog.

extension/src/popup/components/account/Usdt0LaunchBanner/Usdt0LaunchSheet/index.tsx:150

• The PR description specifies exactly two sheet actions—“Receive USDT0” and “Bridge to Stellar”—but this introduces a third “Swap to USDT0” action (and the bridge action below is labeled “Transfer to Stellar”). Please align the implementation with the documented campaign flow, or update the stated requirements if this three-action design is intentional.

            onClick={handleSwapClick}
            data-testid="usdt0-launch-sheet-swap"
          >
            {t("Swap to USDT0")}

[Copilot]

Pull request overview

Copilot reviewed 14 out of 17 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 14 out of 17 changed files in this pull request and generated 2 comments.

[CassioMG]

Fixed in #2999 (a30b52c) — the handler now returns { isDismissed: true } straight after setItem, matching dismissDiscoverWelcome. #2990 had already merged, hence the separate PR; also backported to #2997 for v5.48.0.

[CassioMG]

Fixed in #2999 (a30b52c) — getUsdt0LaunchBannerDismissed now throws on a structured error like getHasSeenDiscoverWelcome, and the component's catch fails closed (setIsDismissed(true)) while still reporting to Sentry, matching the documented choice in useDiscoverWelcome. Also backported to #2997 for v5.48.0.

[piyalbasu]

Dismissal check fails open, so a transient error can re-show the banner

Nit — low likelihood (requires a messaging/storage failure), user-visible when it happens. Not a merge blocker.

TL;DR: When the banner asks whether it was already dismissed and that lookup fails, the failure is treated as "not dismissed" and the promo renders again. A user who already dismissed it can see it come back after a transient error. The Discover welcome modal handles the identical situation the opposite way — on failure it stays hidden, specifically so it's never re-shown to someone who already dismissed it. Worth matching that, since re-showing a dismissed promo is the more annoying of the two failure modes.

---

Detailed explanation (for agents)

Root cause: two independent paths resolve a failed dismissal lookup to false (= show the banner).

The API helper returns false on a structured error:

freighter/@shared/api/internal.ts

Lines 2219 to 2230 in a773c74

	export const getUsdt0LaunchBannerDismissed = async (): Promise<boolean> => {
	const { isDismissed, error } = await sendMessageToBackground({
	activePublicKey: null,
	type: SERVICE_TYPES.GET_USDT0_LAUNCH_BANNER_DISMISSED,
	});
	if (error) {
	return false;
	}
	return !!isDismissed;
	};

and the component's catch also sets false:

freighter/extension/src/popup/components/account/Usdt0LaunchBanner/index.tsx

Lines 28 to 42 in a773c74

	useEffect(() => {
	const checkDismissedStatus = async () => {
	try {
	const dismissed = await getUsdt0LaunchBannerDismissed();
	setIsDismissed(dismissed);
	} catch (error) {
	captureException(error);
	setIsDismissed(false);
	} finally {
	setIsLoading(false);
	}
	};
	checkDismissedStatus();
	}, []);

Precision on reachability: the if (error) return false branch in getUsdt0LaunchBannerDismissed is currently unreachable — getUsdt0LaunchBannerDismissed in popupMessageListener returns { isDismissed } and never a structured { error }. So that branch is latent, not live.

The live path is the component's catch: if localStore.getItem rejects inside the handler, the rejection propagates out of the handler, rejects browser.runtime.sendMessage, and lands in catch (error) at line 33 → setIsDismissed(false) → banner renders. That path is real today.

Sibling precedent — the repo already made the opposite call for the same shape of state:

freighter/extension/src/popup/views/Discover/hooks/useDiscoverWelcome.ts

Lines 12 to 26 in a773c74

	useEffect(() => {
	const checkWelcome = async () => {
	try {
	const seen = await getHasSeenDiscoverWelcome();
	if (!seen) {
	setShowWelcome(true);
	}
	} catch (error) {
	// Default to hiding the modal on messaging failure so we never
	// show it to a user who has already dismissed it.
	captureException(`Error checking Discover welcome flag - ${error}`);
	}
	};
	checkWelcome();
	}, []);

Note getHasSeenDiscoverWelcome throws on error (internal.ts L2755-2757) rather than returning a falsy default, which is what lets the hook's catch make the fail-closed choice deliberately.

Deterministic repro: mock getUsdt0LaunchBannerDismissed to reject, render <Usdt0LaunchBanner /> with the storage key already set, and assert on usdt0-launch-banner — it renders today; fail-closed would render null.

Suggested fixes (increasing depth):

1. Cheap guard: in the component's catch, setIsDismissed(true) instead of false — keep the captureException. One line, and it makes the failure mode "promo silently not shown" rather than "dismissed promo comes back".
2. Match the sibling exactly: make getUsdt0LaunchBannerDismissed throw new Error(error) like getHasSeenDiscoverWelcome, so the latent branch can't quietly disagree with the catch later, and let the component's catch be the single place that decides. Add the same one-line comment explaining why the default is hidden.

[piyalbasu]

Banner button doesn't announce that it opens a dialog

Nit — a11y polish, affects screen reader users only. Not a merge blocker.

TL;DR: The banner's main button opens a bottom-sheet dialog, but nothing tells assistive tech that it opens a dialog or whether that dialog is currently open. A screen reader announces it as a plain button, so there's no cue that activating it launches a modal. The codebase already handles this exact case — a manually-controlled sheet whose trigger can't be wired through the sheet's own component — and the fix there was two attributes on the button.

---

Detailed explanation (for agents)

Root cause: the sheet is opened by local state (setIsSheetOpen(true)) rather than by a SheetTrigger, so none of the Radix trigger semantics are emitted:

freighter/extension/src/popup/components/account/Usdt0LaunchBanner/index.tsx

Lines 65 to 70 in a773c74

	<button
	type="button"
	className="Usdt0LaunchBanner__content"
	onClick={handleBannerClick}
	data-testid="usdt0-launch-banner-open"
	>

<Sheet> is rendered as a sibling of the button (L106-L121) with open={isSheetOpen}, so a SheetTrigger can't reach it from inside the banner markup — same constraint as the precedent below.

In-repo precedent, including a comment that spells out the reasoning:

freighter/extension/src/popup/views/AddCollectibles/index.tsx

Lines 212 to 226 in a773c74

	{/* The sheet this opens is a Radix dialog, and its Root lives
	inside HiddenCollectibles, so Radix's own Dialog.Trigger can't
	reach it from here. These mirror what that trigger would emit;
	aria-controls is omitted because the id is generated inside the
	portal and isn't knowable at this level. */}
	<button
	type="button"
	className="AddCollectibles__show-hidden"
	data-testid="hidden-collectibles-btn"
	aria-haspopup="dialog"
	aria-expanded={isHiddenCollectiblesOpen}
	onClick={() => setIsHiddenCollectiblesOpen(true)}
	>
	{t("Show hidden")}
	</button>

Suggested fix: mirror it — add to the Usdt0LaunchBanner__content button:

aria-haspopup="dialog"
aria-expanded={isSheetOpen}

aria-controls is not applicable here for the same reason it's omitted in AddCollectibles: the dialog's id is generated inside the Radix portal and isn't knowable at this level.

Scope note: this is a nit rather than a finding because there's no written rule in the best-practice docs requiring it, and other manually-controlled sheet triggers in the repo also lack it. Flagging it only because this PR's a11y pass already touched this same button (nested-button semantics, localized labels, decorative alt), so it's cheap to finish the set here.

[CassioMG]

I've unintentionally merged the PR before addressing the last open comments so I'll open another small PR to address those 🤦‍♂️