Know what you own.
Your position is a balance of LP tokens and a share of two real reserve balances on the selected chain.
Read the position view
| Field | Interpretation |
|---|---|
| LP balance | Your connected account's pool-specific ERC-20 balance. |
| Pool share | Your LP balance divided by total LP supply. |
| Redeemable stock | Your pro-rata raw stock-token amount, rounded down. |
| Redeemable USDG | Your pro-rata accounted stable reserve, rounded down. |
| Estimated value | Stock claim multiplied by a reference price, plus the USDG claim. |
| Expiry and status | Whether trading or additions are available; not a redemption guarantee from an issuer. |
The current LP balance includes tokens received by transfer and excludes tokens transferred away. It is not derived solely from this browser's deposit history. Reading a different account naturally changes the positions you see.
The mainnet catalog loads up to 12 pools per market at a time, newest first. When there are additional pages, Portfolio labels its balances as Positions on this page. These totals cover only the loaded pools; browse newer and older pages to find other holdings. The stock-market catalog counts all funded pools, while liquidity and fee totals cover the current page.
NAV is an estimate
Estimated position NAV
= redeemableRawStock × referencePricePerRawToken
+ redeemableUSDGA reference valuation is not an executable sale price. Slippage, fees, stale prices, token transfer restrictions, and USDG depegs can affect realizable proceeds. A missing stock reference makes the combined valuation unavailable; the actual token amounts remain readable. Local development uses separate mock-market values.
Where LP fees appear
The LP portion of trading fees stays in accounted USDG reserves. Your proportional claim includes that retained inventory. There is no separate LP reward token or claim transaction for those fees.
The protocol portion is accounted separately and excluded from your redeemable USDG. Collecting protocol fees must reduce the protocol liability and actual balance together without reducing accounted LP reserves.
Follow transaction states
- Awaiting authorization: the wallet request has not yet been signed or accepted.
- Pending: a transaction hash exists, but the state transition is not yet confirmed.
- Confirmed: the receipt reports success; refreshed on-chain state should reflect the result.
- Reverted: a mined receipt reports failure; the action's state changes were rolled back.
- Unknown: the available RPC response cannot establish the transaction's outcome. Check again before resubmitting.
- Replaced: a different transaction used the same account nonce. Inspect that replacement before deciding what to do next.
Activity keeps a browser transaction journal scoped to the chain, genesis, deployment, and account. After a refresh or reconnect, the application checks pending transactions against chain receipts and replacement evidence. It never signs another action automatically. History on a different browser is not a complete account index; balances and ownership still come directly from contracts.
If you sped up or cancelled a transaction in your wallet, open its unresolved Activity details, enter the Replacement transaction hash, and choose Verify receipt. The application checks the confirmed replacement's sender, nonce, and action data against the original. This check does not ask you to sign and can inspect a saved account while disconnected.
A browser refresh does not reverse a mined transaction. Resetting or redeploying a local development chain can change available contracts and balances; it is a development operation, not a withdrawal.