Beethovenx shows stS APY after validator and protocol fees

S, stS and validators connect a deposit to its yield

S supplies the underlying stake, validators generate staking rewards and stS represents exposure to the pooled stake. Beets brings those parts together through its staking contract on Sonic. The contract delegates pooled S across selected validators, then compounds the rewards allocated back to the pool. Holding stS gives exposure to that process without managing individual validator delegations.

The yield accrues through the amount of S each stS represents. Reward additions increase that exchange rate, so measuring the token count alone misses the mechanism. The displayed stS APY concerns this underlying staking activity. Other Beets products have their own sources of income, fees and exposure, even when they include stS.

Validator and protocol fees apply in sequence

Validators take their share of gross staking rewards first, and Beets charges its protocol fee on the remaining rewards. Both deductions concern rewards, rather than a percentage of the S principal you deposit.

The reward bases differ

Validator share

The stS fee schedule updated on March 21, 2025 gives validators 15% of gross staking rewards. Their fee pays for managing the underlying nodes. Gross rewards mean the rewards before either deduction. The remaining reward amount supplies the base for the protocol fee, which applies to a smaller amount.

Protocol share

Under this stS fee schedule, Beets takes 10% of rewards remaining after validator fees. Treating both percentages as deductions from gross rewards would overstate the combined charge. The sequence matters whenever you're comparing a gross reward amount with what remains to support stS.

View full-size image

Does net stS APY predict my return in S?

Net stS APY expresses annualized staking yield after fees; it doesn't fix the rewards you'll realize over your holding period. APY includes compounding, whereas a reward allocation describes how one reward amount divides among recipients. You don't need to deduct the validator and protocol percentages again from the displayed net rate. Doing so would count the same staking fees twice. Nor does retaining 76.5% of gross rewards mean a 76.5% annual yield. The underlying reward generation and compounding determine annual growth, with fee settings affecting the rewards available to compound.

An entry date, an exit date and the exchange rates at those points describe your actual holding period. A changing APY can inform expectations, but it doesn't replace those measurements. A shorter holding period also gives less time for rewards to accumulate against any entry or exit costs.

A token balance and an exchange rate measure different things

An stS balance multiplied by the S-per-stS exchange rate gives its underlying S equivalent. That rate measures the stake backing each token, which differs from a trading quote.

An increase in the exchange rate can raise that S equivalent without requiring a larger stS token balance. Reward compounding works through the stake backing the token. An unchanged token count therefore doesn't, by itself, show missing rewards. Transfers, purchases or sales change the balance for different reasons, so balance growth alone also doesn't establish how much staking yield accrued.

A DEX quote measures what a particular trade would exchange at its available liquidity. It can differ from the protocol's underlying exchange rate. Keep those two values distinct when valuing a holding or considering a sale.

The entry quote estimates the size of your stS position

Staking S acquires stS through the staking mechanism, while swapping S for stS acquires it through market liquidity. The deposit amount and applicable exchange rate determine the staking position. A swap quote reflects the selected pool's pricing and available liquidity, which may produce a less favorable rate.

Before a first deposit, identify the S amount being committed on Sonic and reserve S for network fees. Distinguish an expected stS amount from tokens actually received. A completed stake produces stS in the receiving wallet. An estimate or wallet connection alone doesn't establish that outcome. An unsubmitted deposit leaves the proposed S amount uncommitted.

A first staking session can end with stS held in the wallet. Adding liquidity changes the exposure and introduces pool-specific conditions.

Unbonding time and swap pricing determine the exit

A staking withdrawal follows the protocol's unbonding terms, while a market sale depends on a DEX quote and usable liquidity. The stS withdrawal process described on March 21, 2025 has a 14-day unbonding period. After initiating an unstake, a user returns to claim S once that period ends. Contract controls can change withdrawal settings or pause operations, so the documented delay isn't an unconditional deadline.

A sale can exchange stS for S without following that withdrawal process, subject to available trading liquidity. Its proceeds may differ from the staking exchange rate. The Sonic v2 Staked Sonic Symphony pool carries a recovery-mode warning following an exploit affecting some v2 Composable Stable pools. The warning concerns affected v2 pools and identifies v3 pools as unaffected by that exploit.

Additional pool yield changes the position you're evaluating

A pool position containing stS combines underlying staking exposure with the pool's own assets and trading activity. The standalone stS APY therefore doesn't describe the complete pool position. Weighted pools distribute exposure across their constituent assets, while swap income follows the pool's activity and fee rules.

Some pools also offer staking incentives, which require staking the pool tokens. Those incentives differ from the rewards already accruing through stS. Governance through maBEETS adds another arrangement: its Reliquary mechanism adjusts voting power and rewards with position maturity. These relationships matter when comparing yield labels, but they aren't additional components of the standalone stS APY.

Contract controls qualify the rate and withdrawal terms

Beets' administrative roles can alter protocol fees and withdrawal delays, while pause controls can interrupt staking operations. The stS security configuration described on March 21, 2025 assigns upgrades and administrative changes to distinct timelock arrangements. A delay protecting an upgrade doesn't give every operational change the same waiting period.

Delegating across multiple validators spreads exposure to individual validator failures. Slashing can still affect the underlying stake, and a contract vulnerability can affect the staking system itself. Neither the net APY label nor the reward-retention calculation measures those potential losses.

A deposit remains exposed to future configuration changes throughout the holding period. Its starting net APY won't freeze the protocol fee or withdrawal rules for as long as you hold stS.