SAYLOR The result you are building
A net-yield and risk comparison using current reward sources, fees/commissions, token price and depeg scenarios, validator/operator and smart-contract exposure, liquidity/withdrawal timing, slashing/penalty rules, concentration, recordkeeping needs, and a clear no-guarantee decision table.
Use this guide when: comparing native staking, liquid staking, restaking, LPing a receipt token, or doing nothing — or estimating what a given stake amount may actually earn net.
Do not use it as a substitute for: adding advertised APYs together as if they're independent guaranteed returns, or ignoring that both rewards and principal are denominated in a volatile asset.
Before you change anything, collect: the asset/chain, amount, and time horizon; current protocol/validator/operator reward rates, commissions, and fee sources; receipt/restaking contracts, custody, upgradeability, depeg/liquidity, and withdrawal rules; tax/record needs and scenario price assumptions.
Stop a favorable comparison when official terms/contracts/withdrawal paths can't be verified, the yield source is unexplained, the receipt token has insufficient exit liquidity, or smart-contract/operator concentration exceeds the user's declared risk tolerance.
Understand the system before fixing it
- APY and dollar return are different things. Token rewards can rise while USD value falls — show token-denominated and price-scenario returns separately, never blended.
- Stacked yield stacks risk. Liquid staking plus restaking plus LPing the receipt token adds validator, protocol, smart-contract, depeg, market, and liquidity dependencies on top of each other.
- Net yield subtracts fees and idle/exit costs. Commission, protocol fee, swap spread/impact, gas, withdrawal delay, and tax-record overhead all reduce the usable return below the advertised number.
Evidence-to-decision map
| Evidence | Likely layer | First decisive check | What the result means |
|---|---|---|---|
| Native staking | Validator/network | Commission, performance, slashing/unstake rules | Simpler contract path, but illiquidity/validator/asset risk remains |
| Liquid staking token | Protocol/depeg | Redemption path and market liquidity/discount | Adds smart-contract/custody/depeg risk while improving transferability |
| Restaking | Operator/AVS/contracts | What extra penalties secure the extra yield | Additional yield is compensation for additional, correlated failure paths |
| Receipt-token LP | Market/impermanent loss | Pool depth/range/fees/withdrawal composition | Not the same as holding the receipt — divergence/one-sided/exit risk applies |
Step-by-step procedure
01. Define alternatives and horizon. A fair comparison includes the hold/cash alternative and an exit date. List the exact protocol, validator/operator, receipt tokens, restaking layer, pool, amount, lock/withdrawal terms, and expected use — never compare generic category APYs. Set the observed date and a refresh rule.
02. Trace the yield source. Unsourced incentives can end or be inflationary. Break rewards into network issuance, transaction/MEV fees, protocol incentives, points, restaking payments, and LP fees, identifying token, schedule, variability, and eligibility for each. Exclude unpriced points from any "guaranteed" return figure, and record the official source for each number.
03. Calculate net token yield. Headline APY omits deductions and compounding assumptions. Apply validator commission/protocol fee, compounding frequency, activation/idle/withdrawal time, transaction/swap costs, and realistic reward variability to the actual amount and horizon. Show simple and compounded returns, and only assume compounding when reinvestment actually happens — don't double-count receipt-token appreciation and distributed rewards as separate gains.
04. Map failure paths. Each wrapper layer adds a dependency. Score validator performance/slashing, protocol/admin/upgrade/audit status, operator/AVS penalty exposure, custody/key risk, oracle risk, depeg risk, liquidity, bridge risk, LP range/impermanent-loss exposure, concentration, and governance risk. One hard dependency failure can dominate the entire APY difference between two options — avoid false numeric precision that hides this.
05. Run price/liquidity scenarios. Yield may not offset asset or depeg loss. Calculate the token and USD outcome for price moves of -50/-20/0/+20%, receipt discount/depeg, delayed withdrawal, and stressed exit impact — showing principal and rewards separately. If no exit quote is available, mark the position illiquid rather than using face value.
06. Make a bounded decision and monitor. Rates and risks change over time. Compare net expected reward, the worst plausible liquidity path, complexity, custody, and evidence quality, and choose only within your declared risk tolerance — keeping diversification and exit/monitor triggers in place. There is no "default to highest APY."
Worked example
Starting problem: 5 SOL is liquid-staked, then the receipt token is restaked; the user expects the two advertised APYs to simply add together.
Evidence collected: the liquid token already reflects native staking rewards through its exchange rate/value; restaking advertises extra points/rewards with uncertain value; unstaking requires two separate protocol/market steps; the receipt-token market can trade at a discount during stress.
Decision: the second layer adds incremental potential reward and additional contract/operator/liquidity risk — the advertised rates cannot simply be added as a guaranteed SOL return.
Actions taken: calculated native-equivalent rewards net of fees for the horizon; separated known token rewards from unpriced points; ran depeg/withdrawal-delay/price scenarios and documented the exit path.
Proof of completion: the comparison shows expected SOL/token and USD ranges, all deductions, layered risks, the unknown value of points, and monitoring/exit triggers.
Why this matters: the actual end result is a risk-adjusted comparison, not a promise.
Verify, recover, and hand off
A comparison is complete only when: rates/fees/schedules are dated and sourced; rewards are not double-counted across receipt and restaking layers; net token and USD scenarios are kept separate; every validator/protocol/operator/LP/depeg/liquidity dependency is listed; exit/withdrawal timing and stressed price impact are actually tested; and unknown-point valuation, tax treatment, and the no-guarantee statement are explicit.
If the APY changes, that reflects variable network/incentive conditions — recompute from the current source rather than annualizing a short spike. If a receipt token trades below peg, compare redemption vs. market exit and underlying protocol health rather than assuming the worst or panicking. If rewards aren't visible, check protocol accounting and on-chain state — it may just be an exchange-rate token, a claim schedule, or an eligibility/indexer issue. If restaking points have no listed price, value them at zero for base-case purposes and treat any upside separately — never as guaranteed yield.
Reusable handoff record: exact alternatives/amount/horizon/observed date; yield-source and net-reward calculations; the layered dependency/risk matrix; price/depeg/delay/liquidity scenarios; the decision/monitor/exit triggers and disclaimer.
For agents
An agent comparing staking options for a user should never sum advertised APYs across stacked layers as a single guaranteed number — it should present token-denominated net yield and a separate price-scenario table, exactly as this guide's step 05 does, and flag unpriced "points" rewards as zero-value for any base-case calculation.
Official references: https://solana.com/docs/references/staking · https://www.jito.network/docs/jitosol/ · https://docs.orca.so/liquidity/concepts/impermanent-loss
*This is educational technical and risk-analysis information, not financial, investment, legal, or tax advice. Blockchain transactions can be irreversible and no checklist can guarantee safety or profit.*