Compounding and liquifying restaking rewards, explained

Source note. This article describes the “Compounding and Liquification” section of AutoLayer’s Arbitrum LTIPP application, dated 26 February 2024, where it is listed under V2 features. These are plans as of February 2024, not live features. The text of the post is the only source for AutoLayer-specific claims. Not financial advice.

Two kinds of reward

Restaking can pay in more than one form. The application puts it this way: the EigenLayer ecosystem “will share both liquid and illiquid assets”. That split drives the whole design.

Reward type	Behaviour	Example problem
Liquid	Tokens or incentives you can sell or swap now.	They sit idle until you claim and reinvest them.
Illiquid	Points or allocations that cannot be transferred.	You cannot sell, lend or move them, so they are dead capital until a token exists.

The post proposes one vault design with a different function for each type.

Function one: auto-compounding

For liquid rewards, the post describes a straightforward loop. The vault collects AVS tokens or incentives, converts them to ETH, and reinvests the ETH. In its words, “we can auto-compound the results, obtaining AVS tokens/incentives, converting them to ETH, and reinvesting them.”

In steps:

1. The vault harvests the liquid rewards earned by its restaked position.
2. It swaps them into ETH through the routing layer.
3. It deposits that ETH back into the same position.
4. The next round of rewards is calculated on a larger balance.

Compounding is not magic. It saves the user from claiming, swapping and redepositing by hand, and it matters most when each manual transaction costs more than a small reward is worth. It also has costs: swap slippage, gas, and the price risk of reward tokens that may be volatile or thinly traded. The post does not quantify these, and neither can we.

Auto-compounding connects to the rest of AutoLayer’s design. Swaps and deposits are bundled in a single transaction through the routing and transaction consolidation described in intent-based routing on Arbitrum. The product page lists how that appears in the app.

Function two: liquifying points

The second function addresses a harder problem. As the post notes, “points are non-transferable”. A user holding points cannot trade or collateralise them. The vault’s proposed answer is:

1. Accumulate points on behalf of depositors until the next token generation event (TGE), the moment a project issues its token.
2. Allocate each user’s share of those points.
3. Mint a wrapped token that represents that user’s share of the rewards.

The wrapped token is what makes illiquid rewards liquid. The post is careful on one point: AutoLayer “will not create markets for these tokens, but users can”. In other words, the project does not promise a trading venue or a price. Anyone may create a market, and the value of a wrapped token would be set by that market.

Mint and burn at any time

Users would be able to “mint and burn these tokens at any moment”. The post adds the redemption rule: at a TGE, every user can claim the EigenLayer or AVS tokens at a 1:1 ratio by burning the wrapped versions.

So the claim chain is:

• Points accumulate in the vault.
• Wrapped tokens represent a user’s share.
• When the real token exists, burning a wrapped token redeems it 1:1.

What 1:1 does and does not mean

A 1:1 redemption ratio is a statement about the burn at a TGE: one wrapped unit corresponds to one unit of the underlying token. It does not say what the wrapped token will trade for before a TGE, nor that a TGE will happen. Several things stay open:

1. No guaranteed token. Points are not a promise of a token. A project may never issue one, or may issue it on different terms.
2. No market guarantee. Since AutoLayer does not create markets, liquidity depends on third parties.
3. Dependence on the vault. The wrapped tokens are only redeemable if the vault holds and correctly allocates the underlying rewards. That is a smart contract and operational risk.
4. Allocation rules. How a project distributes tokens to points holders is set by that project, and may use criteria the vault cannot control.

The source does not address these points in detail. They are the questions a careful user would ask before relying on a wrapped version of a point.

A simple illustration, with hypothetical numbers

Suppose a vault holds points for a service and 1,000 users deposited into it. A user who owns 1% of the vault would be allocated 1% of the points. The vault would mint a wrapped token for that share. The user can hold it, sell it to someone who creates a market, or burn it later. At the TGE, if the project issues tokens to the vault’s address, the holder of the wrapped token burns it and claims the matching amount.

All numbers here are made up to show the flow. They are not data from AutoLayer.

How this relates to Operators and vaults

The application places these functions inside the AVS Vault Manager, where users allocate funds to AutoLayer’s Operators. Each Operator validates a different set of services, so vaults carry different yields and risk profiles. The post says vaults aggregate “both illiquid and liquid assets” and that strategies include auto-compounding liquid rewards and creating wrapped versions of illiquid ones.

The Vault Manager is also described as assessing profitability and showing “realistic dollar-based APRs, thereby measuring incentive inflation”. That is an important idea. Reward tokens often look attractive until you price them in dollars and account for the way issuing them dilutes their value. For more on how Operators work in the application, see slashing bounties and Virtual Operators.

Risks to weigh

Any product that harvests and reinvests rewards, or that wraps points, adds layers:

• Smart contract risk in the vault and wrapped-token contracts.
• Reward-token price and liquidity risk during conversion.
• Dependency on the underlying restaking system, including slashing and the scores discussed in AVS scoring.
• Uncertainty over whether and how points convert to tokens.

The security page and the risk disclosure cover the product’s general risk posture. For how the whole system fits together, see how it works.

Planned as of February 2024

In the application, “Compounding and Liquification” sits under V2 features. No launch date is given. The post uses future tense throughout (“our vaults will have two functions”), and we have kept that framing. For the wider background of the team and the V1 product, read From Tortle Ninja to AutoLayer.

Takeaway

The design splits rewards by type: liquid ones are compounded back into ETH, and illiquid ones are turned into wrapped tokens that can be burned for the real tokens at a 1:1 ratio once a TGE happens. The idea is clear and practical. Its value depends on execution, on third-party markets and on projects actually issuing tokens, none of which the source can promise.