Connected users
Positions
Wallet, farm, and staking views, with emphasis on what remains withdrawable and what still depends on discovery.
2 sectionsFocused route
Reading progress
Navigate this topic
Current section
Wallet
Reading mode
Focused route with anchored sections
Quick section jump
Within this topic
Connected view
Wallet
Where the Wallet route groups Overview, Portfolio, Activity, Launches, LP, Farms, and Staking for the connected address.
The Wallet route is the connected-wallet hub. It groups Overview, Portfolio, Activity, Launches, LP / Risk, Farms, and Staking tabs while relying on the same public data availability as the rest of the app.
Within this section
Activity history
Find where wallet-level actions and recent user history appear in one place.
| Surface | Frontend | Data source | What the user sees |
|---|---|---|---|
| Wallet connection | The connection modal can run in Direct wallets, Hybrid, SDK primary, or SDK only mode depending on the admin rollout setting. | Public admin settings plus frontend SDK availability in the current build. If DogeOS SDK is not configured, the modal falls back to direct wallets to avoid blocking users. | DogeOS SDK can provide email, social, and external wallet entry points. Direct EVM wallets remain available as normal or advanced fallback depending on the selected mode. |
| Overview, Portfolio, and Activity | The /wallet route keeps Overview, Portfolio, and Activity in dedicated tabs instead of spreading wallet state across separate surfaces. | Indexed balances, priced portfolio summary, activity history, orders, launch exposure, and wallet-scoped DOGE refund correspondence for failed sales. | Overview stays compact, separates Latest activity from the Action center, and leaves longer history or asset lists to the dedicated tabs. |
| Extra tokens | The Portfolio tab calls these "extra tokens" instead of "hidden assets" so the label does not imply that funds disappeared. | The same indexed wallet balances, with test tokens or tokens needing more DogeFactory context tucked away by default. | The "Show unpriced or external tokens" toggle only changes visibility in the table. It never moves, blocks, or removes assets from the connected wallet. |
| Needs context filter | The Portfolio filter is shown as Needs context to describe the user-facing reason directly. | Locked sale tokens, demo/test tokens, and assets missing reliable price or route context. | The filter is a shortcut for inspecting those assets together. It is informational, not a warning that the wallet is unsafe. |
| Launches and LP | The /wallet route keeps launch follow-up and LP review in dedicated Launches and LP tabs. | Fixed-price sale state, held sale tokens, refund status, failed-sale balances, and public pool/routing metadata for connected-wallet positions. | Launch cards show one primary action at a time. Refund actions take priority over the generic launch link until the wallet no longer has a refund follow-up. |
| Farm cards | The /wallet page reuses the same current and older Farm cards as /farm for the connected wallet. | Eligible public reward sources when enabled and discoverable. | Users can deposit LP, withdraw LP, harvest rewards when supported, or use safety withdrawal from the same wallet-centric surface. |
| Staking cards | The /wallet page reuses the same Staking cards as /stake for the connected wallet. | Public staking data when available. | Users can stake, claim, withdraw, exit, or use safety withdrawal while the page keeps reward-period status visible. |
Launch positions
Review where launch participation, refunds, and sale state appear for a connected wallet.
Overview is intentionally compact: it keeps Actions needed, Latest activity, and Position map separate so past activity does not get mixed with follow-up actions. The wallet modal stays focused on connection, wallet, network, and explorer actions.
In Wallet Launches, each launch card keeps a single primary action. If a failed sale still needs refund handling, the card points to the refund page first; once that action is done, the generic launch detail action can come back.
Extra tokens in Wallet
See why the Portfolio tab keeps some test or context-needed tokens out of the main list by default.
Some assets can stay tucked away or marked as needing context when public data is delayed or the app cannot safely explain pricing and routing yet. That does not automatically mean the token is invalid or gone from the wallet.
Pool discovery
Farm / Staking
How V4 farm vaults, optional legacy farms, and staking pools are discovered, what stops rewards, and what stays withdrawable.
Farm, Stake, and Wallet all rely on the same farming and staking discovery logic. The global pages list pools, while the Wallet page groups the connected-wallet actions on top of those same reads.
Within this section
Rewards and claiming
Understand where earned rewards appear and when claiming is available.
| Aspect | Farm | Stake |
|---|---|---|
| Primary path | The current public farm path is used for eligible liquidity rewards; older modes are separate and optional. | Each staking pool distributes rewards with its own visible schedule. |
| Discovery path | Farm discovery combines public reward data with the current connected wallet state. | Stake discovery depends on public staking data being available. |
| Reward schedule | Rewards accrue according to the vault or enabled legacy farm schedule, then new emissions stop. | Rewards accrue during the visible reward window, then new emissions stop. |
| Withdrawals | withdraw and harvest depend on the active farm type and availability state; safety withdrawal should remain visible when supported. | withdraw, claim, and exit should stay available according to the visible pool rules. |
| After rewards end | Users can still withdraw LP and harvest whatever was already accrued before endTime. | Users can still withdraw principal and claim whatever was already accrued before the reward window ended. |
| APR in the frontend | Farm cards show APR as unavailable when the public route has no APR enrichment yet. | Staking APR is estimated from public reward and deposit data, then visually capped when the number becomes misleading. |
Withdrawals
See what usually stays withdrawable even when rewards stop or data is late.
Operational notes
- The Farm page shows reward opportunities only when they are configured and publicly discoverable.
- If a reward source is not available yet, the Farm page can look empty even when normal pools exist.
- The Staking page depends on public staking data being available.
- A pool does not appear automatically just because a token exists: an eligible reward source also needs to exist.
- The Wallet page aggregates the same modules for the connected wallet: wallet activity, LP alerts, farm cards, and staking cards.
- Staking APR is an estimate based on visible reward data and deposited value. On very low TVL, the display can become extreme, so it is visually capped.
- Farm cards support optional APR enrichment. If pricing or reward data is missing, a card should show unavailable or Not priced instead of inventing yield.
- Staking withdrawals remain available even after the reward period ends. The end of rewards should not lock principal.
- Safety withdrawals remain part of the farm model. Users should still confirm which visible product path receives approval before signing.
APR display limits
Know why APR can be missing, delayed, or only approximate.
APR is a public estimate, not a guaranteed return. It can stay delayed, incomplete, or unavailable when market data or reward visibility is late.