Yield Hub DocsDocumentation and verification
This page collects the app documentation in one place: what the dashboard does, which protocols it touches, where contracts live, and which flows have verification evidence before they are exposed to users.
Protocols documented11
Verified route records33
Verified contract references207
What Manage SupportsAction and transaction boundaries
A route can appear for comparison without being executable. Manage buttons only appear when the exact route contracts and its position read plus enter or exit transaction have passed the verification gate.
Immediate exitsDEX LP, lending, Clearpool, Cyclo, Mystic, and Spectra LP routes complete their supported exit transaction directly from the manage modal.
Queued exitsFlamix and Upshift can require a redemption request and protocol processing before assets return. The modal labels the request as queued instead of implying an instant withdrawal.
Spectra sidecarsAdding Spectra liquidity also creates YT exposure. Removing LP returns the pool's IBT/PT legs; any remaining PT/YT-only balance is shown as read-only and links back to Spectra for specialist actions.
Reward claimsDirect claims are enabled only for a route with a verified user-callable claim transaction. Other rFLR distributions stay linked to the Flare Portal or the protocol app.
Verification model
Managed positions are reviewed before launch. The app checks contract addresses, ABI availability, wallet position reads, reward data, and whether enter, claim, and exit flows have enough evidence to be safely enabled in the dashboard.
Dashboard scopeThe app tracks Flare yield opportunities, wallet positions, claimable rewards, and dashboard-supported enter or exit flows.
Route verificationEach managed route is gated by contract addresses, ABI checks, data checks, and small mainnet transaction proofs where available.
Reward dataAPR and reward values are separated into base protocol yield and extra rFLR incentives so users can see where returns come from.
Wallet actionsThe dashboard only enables in-app actions for routes marked launch-ready. Each modal shows every approval and transaction before the wallet asks for a signature.
Active Flare pool lifecycle evidence
These four active pools were tested on Flare mainnet on 14 July 2026 with small deposits from the local runner. Every entry, wallet position read, LP approval, and full LP removal succeeded. Newly discovered Spectra pools remain comparison-only until the same lifecycle is repeated.
Runner plansdata/test-plans/spectra-stxrp-aug-2026-enter.json
data/test-plans/spectra-stxrp-aug-2026-exit.json
PT/YT sidecarsread-only after LP exit
Runner plansdata/test-plans/spectra-stxrp-nov-2026-enter.json
data/test-plans/spectra-stxrp-nov-2026-exit.json
PT/YT sidecarsread-only after LP exit
Runner plansdata/test-plans/spectra-sflr-sep-2026-enter.json
data/test-plans/spectra-sflr-sep-2026-exit.json
PT/YT sidecarsread-only after LP exit
Runner plansdata/test-plans/spectra-stxrp-sep-2027-enter.json
data/test-plans/spectra-stxrp-sep-2027-exit.json
PT/YT sidecarsread-only after LP exit
Token addresses used across routes
Shared coin contracts are listed once here so they do not repeat on every protocol card.
Upshift VerificationUpshift vault contracts and runner evidence
Upshift rows are tracked as base yield opportunities, not rFLR reward rows. The dashboard can manage the FXRP deposit and redemption-request lifecycle; final delayed claims stay external until the epoch claim path is verified.
Runner plandata/test-plans/upshift-flare-xrp-deposit-request-redeem.json
Direct claimexternal after epoch
Epoch follow-up on 2026-05-27 found the vault processed the request and returned 0.249999 FXRP to the runner wallet. Direct final-claim execution remains external until a user-callable claim path is runner-verified.
Runner plandata/test-plans/upshift-monarq-xrp-deposit-request-redeem.json
Direct claimexternal after epoch
Epoch follow-up on 2026-05-30 found the vault processed the request and returned 0.249999 FXRP to the runner wallet. Direct final-claim execution remains external until a user-callable claim path is runner-verified.
Protocols, contracts, and evidence
Shared token contracts are listed once above. Each protocol card keeps the route, pool, vault, router, and other protocol-specific addresses that matter for verification.
Entry flow1/1 routes
Position read1/1 routes
Exit flow1/1 routes
Direct claim0/1 routes
Entry flow5/5 routes
Position read5/5 routes
Exit flow5/5 routes
Direct claim0/5 routes
Entry flow4/26 routes
Position read26/26 routes
Exit flow4/26 routes
Direct claim0/26 routes
Entry flow4/6 routes
Position read6/6 routes
Exit flow4/6 routes
Direct claim0/6 routes
Entry flow1/1 routes
Position read1/1 routes
Exit flow1/1 routes
Direct claim1/1 routes
Entry flow3/3 routes
Position read3/3 routes
Exit flow3/3 routes
Direct claim0/3 routes
Entry flow5/5 routes
Position read5/5 routes
Exit flow5/5 routes
Direct claim0/5 routes
Entry flow6/6 routes
Position read6/6 routes
Exit flow6/6 routes
Direct claim0/6 routes
Entry flow3/3 routes
Position read3/3 routes
Exit flow3/3 routes
Direct claim0/3 routes
Entry flow2/2 routes
Position read2/2 routes
Exit flow2/2 routes
Direct claim0/2 routes
