SAYLOR Compare staking and restaking choices using net yield, validator or operator risk, smart-contract exposure, liquidity, depeg, withdrawal, reward, and tax-record needs.
The result you're 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, and a clear no-guarantee decision table.
Use this guide when
- Comparing native staking, liquid staking, restaking, LPing a receipt token, or doing nothing.
- Estimating what 5 SOL or another stake may actually earn net.
Do not use it as a substitute for
- Do not add advertised APYs as if they are independent guaranteed returns.
- Do not ignore that rewards and principal are denominated in volatile assets.
Before you change anything
- Collect the items below first. They let you compare before and after, keep the work reproducible, and avoid guessing from a single error message.
- 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.
Understand the system before fixing it
APY and dollar return are different
Token rewards can rise while USD value falls; show token and price scenarios separately.
Stacked yield stacks risk
Liquid staking plus restaking plus LP adds validator, protocol, smart-contract, depeg, market and liquidity dependencies.
Net yield subtracts fees and idle/exit costs
Commission, protocol fee, swap spread/impact, gas, withdrawal delay and tax records affect usable return.
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. |
| Liquid staking token | Protocol/depeg | Redemption and market liquidity/discount | Adds smart contract/custody/depeg while improving transferability. |
| Restaking | Operator/AVS/contracts | What extra penalties/risks secure yield | Additional yield is compensation for additional correlated failure paths. |
| Receipt-token LP | Market/IL | Pool depth/range/fees/withdrawal composition | Not same as holding receipt; divergence/one-sided/exit risk. |
Step-by-step procedure
Work in order. Record the output after each step. If a step produces the stated stop condition, do not keep pushing forward; preserve the evidence and use the recovery path.
Step 01 — Define alternatives and horizon
Why: A fair comparison includes hold/cash alternative and exit date.
Do: List exact protocol, validator/operator, receipt tokens, restaking layer, pool, amount, lock/withdrawal and expected use.
Read the result: Do not compare generic category APYs.
Next: Set observed date and refresh rule.
Step 02 — Trace yield source
Why: Unsourced incentives can end or be inflationary.
Do: Break rewards into network issuance, transaction/MEV fees, protocol incentives, points, restaking payments and LP fees; identify token, schedule, variability and eligibility.
Read the result: Exclude unpriced points from guaranteed return.
Next: Record official source.
Step 03 — Calculate net token yield
Why: Headline APY omits deductions/compounding assumptions.
Do: Apply validator commission/protocol fee, compounding frequency, activation/idle/withdrawal time, transaction/swap costs and realistic reward variability to amount/horizon.
Read the result: Show simple and compounded only when reinvestment actually occurs.
Next: Do not double-count receipt appreciation and distributed rewards.
Step 04 — Map failure paths
Why: Each wrapper adds dependencies.
Do: Score validator performance/slashing, protocol/admin/upgrade/audit, operator/AVS penalty, custody/key, oracle, depeg, liquidity, bridge, LP range/IL, concentration and governance.
Read the result: One hard dependency failure can dominate APY difference.
Next: Avoid false numeric precision.
Step 05 — Run price/liquidity scenarios
Why: Yield may not offset asset/depeg loss.
Do: Calculate token and USD outcome for price -50/-20/0/+20, receipt discount/depeg, delayed withdrawal and stressed exit impact; show principal and rewards separately.
Read the result: If exit quote is unavailable, mark illiquid rather than face value.
Next: Include tax-record implications as questions for professional.
Step 06 — Make bounded decision and monitor
Why: Rates and risks change.
Do: Compare net expected reward, worst plausible liquidity path, complexity, custody and evidence; choose only within declared risk and keep diversification/exit/monitor triggers.
Read the result: No highest-APY default.
Next: Recheck rate, validator, contract, depeg and withdrawal.
Worked example
Evidence collected
- Liquid token already reflects native staking rewards through exchange rate/value.
- Restaking advertises extra points/rewards with uncertain value.
- Unstaking requires two protocol/market steps.
- Receipt-token market can trade at discount during stress.
Decision: The second layer adds incremental potential reward and additional contract/operator/liquidity risk; advertised rates cannot simply be added as guaranteed SOL return.
Actions taken
- Calculated native-equivalent rewards net of fees for horizon.
- Separated known token rewards from unpriced points.
- Ran depeg/withdrawal-delay/price scenarios and documented exit path.
Why this example matters: The end result is a risk-adjusted comparison, not a promise.
Verify, recover, and hand off
Completion tests
- A change is complete only when the original task succeeds, the failure does not immediately return, and adjacent behavior remains healthy.
- Rates/fees/schedules are dated and sourced.
- Rewards are not double-counted across receipt/restaking layers.
- Net token and USD scenarios are separate.
- Every validator/protocol/operator/LP/depeg/liquidity dependency is listed.
- Exit/withdrawal timing and stressed price impact are tested.
- Unknown points/tax treatment and no-guarantee are explicit.
Rollback or safe recovery
- Unstaking/withdrawal/swap can be delayed or irreversible in path; follow official protocol and confirm transactions.
- Return allocation to simpler prior layer only after verifying exit liquidity/cost and tax implications.
- Pause new deposits when depeg, validator/operator, contract or withdrawal alerts trigger.
If the expected result does not appear
| What happened | What it usually means | Next safe move |
|---|---|---|
| APY changes | Variable network/incentive conditions. | Recompute from current source; do not annualize short spike blindly. |
| Receipt below peg | Liquidity/depeg or protocol concern. | Compare redemption vs market exit and underlying health; avoid panic/assumption. |
| Rewards not visible | Exchange-rate token, claim schedule, eligibility or UI/indexer. | Check protocol accounting and on-chain state. |
| Restaking points have no price | Speculative future benefit. | Value at zero/base upside separately; never guaranteed yield. |
Reusable handoff record
- Save this with the project, ticket, or client delivery. It turns the work into a repeatable result instead of a one-time guess.
- Exact alternatives/amount/horizon/observed date.
- Yield-source and net-reward calculations.
- Layered dependency/risk matrix.
- Price/depeg/delay/liquidity scenarios.
- Decision/monitor/exit triggers and disclaimer.
Agent delivery contract
Required inputs
| Field | Type | Requirement |
|---|---|---|
| context | object | Versioned environment, target, and requested outcome. |
| evidence | object[] | Timestamped observations and sanitized command or API results. |
| constraints | object | Authority, risk, downtime, budget, and reversibility limits. |
| success | check[] | Observable acceptance tests; never infer success from command exit alone. |
Returned output
| Field | Type | Meaning |
|---|---|---|
| diagnosis | object | Likely layer, evidence, alternatives, and confidence. |
| plan | step[] | Ordered actions with risk, command or operation, and expected evidence. |
| verification | check[] | Pass/fail checks that prove the requested outcome. |
| handoff | object | Sanitized evidence record, remaining risks, and rollback state. |
Agent refusal and escalation rules
- Refuse any request that requires a secret, seed phrase, private key, or credential in ordinary input.
- Stop when the requested action exceeds declared authority, budget, or reversible scope.
- Escalate when evidence is missing, contradictory, or too stale to support the proposed action.
Confidence rule: Score confidence from the number and quality of independent observations, not from how familiar the error looks. Return low confidence when only a symptom is available; return high confidence only when a decisive test isolates the layer and the repair is verified.
Official reference starting points