Share Card Verified Badges ✓

Token (title) and KYC (sharer) verified badges on share cards, rendered from the server-resolved display.titleVerified / display.sharerVerified flags. Wallet PR phantom/wallet#28921 · backend phantom/backend#31652 · captured on iPhone 16e simulator with the flags hardcoded on (backend flags are still dark).

Design vs implementation

Figma design: CATE share card with verified badges — **Figma** — Sharing System H2 2026, node 248:2863. Badge after the token title and after the sharer username.

Simulator: SOL share card with verified badges — **Implementation** — existing spot position. `SOL ✓` title badge and `@obliviumhaslonguname ✓` sharer badge.

Payload variants

Spot position share card — **Spot** — title badge next to the symbol, sharer badge next to the username.

Perp position share card — **Perp** — `BTC-PERP ✓`; perps are verified by construction server-side.

Profile — badge also lands on an @username title.

Badge spec

Property	Value	Figma reference
Icon	`IconSubscriptionTick2` (scalloped seal check)	same glyph as profile/leaderboard KYC badges
Color	`tokens.colors.legacy.spotBase` = `#AB9FF2`	design badge fill
Size	16 px	~15–16 px rendered
Title gap	`space.positive[6]`	6.25 px
Username gap	`space.positive[4]`	4.5 px

Badges are presence-only on the wire (true or absent, never false) and resolved per read, so a token later flagged as spam or a user who revokes KYC visibility un-badges existing shares. In the real flow they appear when the share record is created (Share tap), same timing as the server caption, and the PNG capture waits for them to commit.