Skip to content

Make yields great again #11633

@twblack88

Description

@twblack88

A big ole list of feedback:

1. . Surface Yield Opportunities in Wallet Drawer

Title: Surface yield opportunities inline in wallet drawer
Description:
Expose yield availability for each asset directly in the wallet drawer with quick entry into the appropriate position flow.

Acceptance criteria:

  • Wallet drawer shows, per supported asset:
    • balance,
    • “up to X% APY” pill/badge when yield exists.
  • Clicking the pill opens the enter-position flow for that asset.
  • If multiple opportunities exist, default “best” is preselected, with option to change.

2. Streamline Exit / Close Position Flow

Title: Streamline exit and “close position” flow
Description:
Reduce friction for exiting positions with a clear “Exit / Close position” action and minimal steps, including an easy “exit all” option.

Acceptance criteria:

  • From position view, there is a primary “Exit” or “Close position” button.
  • Full “exit all” can be completed in ≤2 confirmations from position view.
  • Partial exit remains available but is not required for a simple close.
  • Usability test: 3/3 users close a position without guidance in ≤3 clicks from main Yield screen.

3. Reduce Opportunity List Overload

Title: Reduce information overload in opportunity list (recommendations + view all)
Description:
Tame the long flat list of opportunities by surfacing a small set of “best” options first and allowing full exploration via “view all.”

Acceptance criteria:

  • Default (connected wallet) shows:
    • top N (e.g., 3) recommended opportunities,
    • clear “View all opportunities” entry point.
  • Sorting state (APY / TVL / other) is explicit and user-adjustable.
  • For users with balances, default recommendations are biased to assets they hold.
  • Usability test: 3/3 users can answer “What are my best options right now?” without feeling overwhelmed.

4. Add Alpha Label for Yield Feature

Title: Add alpha/beta tag and explanation for Yield feature
Description:
Mark Yield as early access and briefly set expectations on rough edges without blocking use.

Acceptance criteria:

  • Yield entry point or header has an “Alpha” or “Beta” badge
    • on in the navbar earn --> yield
  • At the top of the header on the page

5. Clarify “Available / APY / Earnings” Metrics

Title: Clarify yield metrics (Available, APY, Earnings) on Yield dashboard
Description:
Make “Available to earn”, “APY”, and “Earnings/Potential earnings” unambiguous. Add helper text/tooltips and ensure “Potential earnings” is based on a documented formula so users can distinguish balance, rate, and realized vs projected earnings.

Acceptance criteria:

  • Each of “Available to earn”, “APY”, and “Earnings/Potential earnings” has:
    • clear labelling
    • short helper text or tooltip
  • Users can tell:
    • which number is stake-able balance,
    • which is the rate
    • which is realized vs projected earnings
  • “Potential earnings” value matches a documented formula (e.g., balance × APY × period).
  • Usability test: 3/3 users internally accurately explain each metric.

6. Fix Asset Filters to Prioritize User Holdings

Title: Fix Earn filters to prioritize opportunities for user-held assets
Description:
Adjust the Earn view so the default experience surfaces opportunities that are directly actionable with current wallet holdings, with a clear separation from opportunities that require a swap.

Acceptance criteria:

  • Default Earn view (wallet connected) shows only opportunities usable with current balances or a clearly labeled “My opportunities” tab.
  • Opportunities that require a swap are:
    • hidden by default, or
    • visually separated and marked (e.g., “requires swap”).
  • Usability test: 3/3 users describe default view as "things I can do right now with what I have."

7. Fix TVL Display and Sorting

Title: Fix TVL display and sorting for Yield opportunities
Description:
Ensure TVL is correctly populated, displayed, and sortable in lists/tables, with a graceful fallback when unavailable.

Acceptance criteria:

  • TVL appears for all integrations that support it.
  • If TVL isn’t available, show a clear placeholder (e.g., “–” with tooltip).
  • Sorting by TVL works and matches backend values across a test sample.
  • QA spot-check: random positions have matching TVL between API and UI.

8. Improve Native Staking & Validator UX

Title: Improve native staking and validator selection UX (Cosmos, etc.)
Description:
Make native staking flows (especially Cosmos SDK) clear around validator selection, staking states, and cooldowns.

Acceptance criteria:

  • Validator list shows:
    • APY,
    • commission,
    • at least one simple risk/reputation indicator.
  • A default validator choice is auto-selected based on defined criteria.
  • States are clearly labeled:
    • entering/bonding,
    • staked/active,
    • exiting/unbonding with cooldown duration,
    • claimable rewards.
  • Users can view validator detail (e.g., commission, LIR) from staking flow.

9. Add Aggregate Portfolio Yield View

Title: Add aggregate portfolio and yield overview for Yield positions
Description:
Create a portfolio-level view summarizing total deposits, total yield, and payouts across all Yield positions.

Acceptance criteria:

  • Portfolio section shows:
    • total deposits across positions (token + USD),
    • total realized earnings,
    • overall effective yield metric and/or range,
    • recent payout history or link to it.
  • Values update correctly when positions are opened/closed or partially exited.
  • Usability test: 3/3 users can answer

From this view: How much yield am I earning overall?


10. Improve Position Detail Clarity & Add Payout details

Title: Clarify single-position details (balance, rewards, payout mechanics)
Description:
Redesign position detail view so users clearly understand their balance, APY, rewards token, payout cadence, and total rewards earned.

Acceptance criteria:

  • Position view clearly shows:
    • staked balance (token + USD)
    • current APY
    • rewards token
    • payout cadence (per block / daily / epoch, etc.).
  • Shows:
    • “Total rewards earned”
    • “Claimable now” (if applicable)
    • state (entering / active / exiting / cooldown).
  • If rewards accrue per block/epoch, show either a live-ish counter or “last updated” time.
  • Usability test: 3/3 users can identify:
    • how much they’ve earned,
    • in what asset,
    • how/when it’s paid.

11. Add Provider / Protocol Tooltips

Title: Add provider/protocol tooltips and links
Description:
Make provider icons understandable through tooltips and optional links to more information.

Acceptance criteria:

  • Each provider/protocol icon:
    • has a tooltip with full name and one-line description,
    • optionally links to more details (internal doc or official site) in a new tab/safe context.
  • Usability test: 3/3 users can identify what a given provider is when hovering.

12. Spike and then Implement Swap & Stake Entry Flow

Title: Implement “Swap & stake” flow for unsupported asset balances
Description:
Enable users to acquire the necessary asset and enter an opportunity in a single guided flow when they don’t already hold the required token.

Acceptance criteria:

  • Mocks required?
  • If user lacks required asset:
    • UI clearly shows required token and a “Swap & stake” or “Get asset” CTA.
  • “Swap & stake”:
    • pre-fills the target asset,
    • returns user to staking with updated balance after successful swap.
  • Swap fee is surfaced in the swap flow; staking has no extra platform fee.
  • End-to-end test: user holding only asset A can discover, swap, and stake into asset B in a single guided sequence.

12. Normalize Layout, Sizing, and Visual Hierarchy

Title: Normalize layout, sizing, and visual hierarchy for Yield UI
Description:
Tighten layout and component sizing (buttons, cards, tables) and fix misalignments (e.g., progress bar) to improve scan-ability and reduce visual noise.

Acceptance criteria:

  • Core Yield screens fit a standard desktop viewport with:
    • visible list,
    • obvious primary actions,
    • minimal unnecessary scrolling.
  • Component sizes follow agreed design tokens for typography and spacing.
  • Progress bar between icons is visually centered.
  • Colors/gradients use design tokens only (no random AI-generated gradients in production).

13. Clarify Vaults and Underlying Assets

Title: Clarify vault opportunities and underlying asset differences
Description:
Disambiguate multiple vaults for a “single” asset (e.g., Curve USD page is a great example to clarify) and explain why a user might pick one over another.

Acceptance criteria:

  • Vault entries show:
    • underlying asset(s),
    • key differences (strategy, risk, lockup, etc.).
    • different icons, or some way to tell them apart.
  • A “best” vault is visually highlighted with rationale (e.g.,Best APY with TVL > X and low slippage)
  • Advanced users can still expand to see full vault list and compare.
  • Usability test: 3/3 users feel confident selecting a vault or using the default selection.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions