Sources
← → Navigate · F Present · Esc Exit
Recap & examples
r33 reinvests rewards
r33, called hyperRAM on HyperEVM, automates voting and uses rewards to add xRAM backing to its shares.
AutoVaults prepare rewards to claim
AutoVaults vote and convert rewards into a supported output token. You claim that balance. It does not automatically become more deposited xRAM.
LP management is another job
These products automate voting and rewards. Your LP price range is managed separately.
ILLUSTRATIVE EXAMPLE
Where did the reward go?
Suppose an AutoVault deposit is 100 xRAM and it credits 5 units of a chosen reward token. Those 5 units form a separate claimable balance.
The deposit has not become 105 xRAM. In an r33 wrapper, rewards instead add to xRAM backing.
Key idea: AutoVault claims and exits follow weekly processing windows. An early exit may forfeit that epoch’s rewards.
Try the idea
Choose by workflowAdvanced Risk Check
- Check supported reward tokens, current availability, processing status, and exit rules for the product and network you use.
- AutoVault claims and withdrawals lock during processing and the final hour before the next epoch. Withdrawing early may forfeit that epoch’s rewards.
- Review both a wrapper and the contracts it uses. Automation does not remove price risk, contract risk, or withdrawal limits.
- An audit reviews a particular scope and does not guarantee safety. Selling a share may return a different amount from redeeming it.
- r33 withdrawals require the underlying withdrawal to be allowed. Managing a wrapper does not change a separate LP position.
Full explanation & example
Start with the result you want to understand. Manual xRAM participation leaves voting and claiming decisions with the user. r33 or hyperRAM delegates voting and compounds into xRAM backing. An AutoVault delegates voting and conversion while crediting a supported output token for the user to claim.
These products automate governance-token workflows. They do not automatically open, move or close a separate LP range. A user holding both an LP position and an AutoVault has two positions to review.
An AutoVault's reward token selector is the current source for supported outputs. Do not assume that any token with the same name, a native coin or a token supported by a different vault is eligible. The contract uses supported ERC-20 representations.
Processing can make actions temporarily unavailable. Read the current product status, underlying cooldown and effect of an early exit on rewards. A disabled action can reflect contract rules rather than a website fault.
Same deposit, different reward destination
Consider two illustrative strategies that each begin with 100 xRAM. If an AutoVault credits 5 units of its selected output token, those 5 units become a separate claimable balance; the illustration does not turn the deposit into 105 xRAM. In a wrapper example, newly compounded xRAM increases the backing per share instead.
The useful question is where the rewards end up: a claimable output-token balance or additional xRAM backing. Neither mechanism establishes which strategy will earn more.
Common mix-ups
“Automated rewards means I never need another transaction.”
AutoVault users still submit claims for converted rewards. Deposits and withdrawals also require user actions.
“A governance vault will move my LP range for me.”
Voting and reward conversion are separate from liquidity-position management.
Discussion question
What should you check if an AutoVault withdrawal is unavailable?
Show the answer
Confirm the wallet, network, stake and gas, then read the current lock and processing status. Do not keep signing different actions to work around a contract restriction.