How Cross-Chain Restaking Works in 2026

Restake assets across chains

Cross-chain restaking takes your staked ETH or liquid staking tokens (LSTs) and pledges them to secure additional services on networks other than Ethereum. This process allows the validator set and security of one chain to support multiple external projects simultaneously, effectively multiplying the utility of your initial stake.

The primary mechanism involves an Actively Validated Service (AVS). Instead of locking your capital in a single validator role, you delegate that security to an AVS that needs robust validation. In return, you earn yield from the AVS on top of your base staking rewards. This creates a layered income stream, but it also introduces complexity.

This model shifts the burden of security from individual protocols to the Ethereum consensus layer. AVSs can focus on building their specific services without maintaining their own decentralized validator networks, while stakers gain exposure to new ecosystems without moving their assets off-chain.

Choose a bridging and relaying protocol

Cross-chain restaking relies on a specific technical stack to move security consensus between networks. You must select a protocol that matches your risk tolerance regarding validity proofs versus messaging reliability. The infrastructure generally falls into three categories: ZK-based relayers, optimistic messaging layers, and native restaking integrations.

ZK-based relayers (Brevis)

Brevis uses zero-knowledge proofs to verify and relay restaking consensus. This approach offers high security guarantees because the validity of the cross-chain action is mathematically proven on the destination chain. It is ideal for scenarios where trust minimization is the primary concern. Brevis has integrated with Kernel to expand BNB restaked security to other networks using these ZK proofs [[src-serp-2]].

Optimistic messaging layers (Celer IM, Hyperlane)

Optimistic messaging layers like Celer IM and Hyperlane rely on dispute periods rather than immediate cryptographic proofs. Celer IM allows restaking positions to be relayed to other chains, enabling Bedrock to enter the cross-chain restaking realm [[src-serp-3]]. This model often offers lower latency and cost but requires users to trust the economic security of the dispute mechanism during the challenge window.

Native restaking integrations (Renzo)

Native restaking protocols like Renzo simplify the user experience by abstracting the underlying bridging complexity. Renzo integrates with Hyperlane and Chainlink to facilitate true cross-chain native restaking, ensuring that liquidity remains unified [[src-serp-6]]. This method is often preferred for its seamless interaction, though it may introduce smart contract complexity.

Execute the restaking transaction

Cross-chain restaking requires moving your staked assets to a destination chain where an Active Validator Set (AVS) can utilize them. This process typically involves depositing into a liquidity vault, bridging the tokens, and confirming the message on the target network.

1

Select your Liquid Staking Token (LST)

Identify the liquid staking token you wish to restake, such as stETH or rETH. Verify that this specific token is supported by the cross-chain restaking protocol you intend to use. Not all LSTs are compatible with every vault, so checking the supported asset list is the first critical step.

2

Choose an AVS or Vault

Select the Active Validator Set or the specific vault that manages it. Review the slashing conditions and the expected reward rate for that AVS. This decision determines where your security capital will be deployed and which risks you are assuming.

3

Bridge or relay to the destination chain

Initiate the cross-chain transfer. Most protocols use a relayer network to send a proof of your deposit to the destination chain. Ensure you have enough native gas tokens on the destination chain to cover the transaction fees for the final confirmation.

4

Confirm on the destination chain

Sign the transaction on the destination chain to finalize the restaking. Once confirmed, your LST is now securing the AVS on that network, and you will begin accruing additional rewards on top of your original staking yield.

Previous

1234

Next

Monitor slashing and bridge risks

Cross-chain restaking amplifies your exposure by linking your stake to multiple independent chains. When you restake, you are not just securing one network; you are extending your validator's liability across a mesh of protocols. This structure creates two distinct failure modes that do not exist in single-chain staking: bridge exploits and compounded slashing.

Bridge risk stems from the message relay mechanism. To move proof of activity from the source chain to the destination chain (the Application Specific Validator or AVS), the system relies on bridges or relayers. If a bridge contract is hacked or the relay fails to deliver a valid message, your staked assets can be frozen or permanently lost. The security of your restaked position is only as strong as the weakest link in the cross-chain communication layer.

Slashing risk is equally severe. In traditional staking, a validator is slashed for double-signing or downtime on a single chain. In cross-chain restaking, your validator must adhere to the consensus rules of every AVS it supports. If you misbehave on any single destination chain, you face a slash. This means one error can trigger penalties across all secured networks simultaneously, potentially wiping out a significant portion of your principal.

To mitigate these dangers, you must monitor the health of both the underlying bridge and the AVSs you support. Use official dashboards to track bridge liquidity and relay latency. Additionally, review the slashing conditions of each AVS before restaking, as these rules vary widely between protocols. Understanding the specific penalties for each service is essential to managing your overall risk profile.

Review your cross-chain positions

Managing cross-chain restaking requires active oversight. Because your assets secure multiple services simultaneously, they are exposed to the unique slashing conditions of every individual service they validate. Treat your dashboard like a flight instrument panel; you need to monitor bridge health, claim rewards, and track slashing events regularly.

Checklist for ongoing management

• Verify AVS uptime: Ensure the Active Validation Services (AVS) you support are functioning. Downtime can lead to missed rewards or penalties.
• Monitor bridge health: Cross-chain restaking relies on bridges to relay consensus. Check for any network congestion or downtime on the bridging protocols.
• Claim rewards: Rewards accumulate across different chains. Periodically claim and compound them to maximize yield.
• Track slashing events: Stay informed about any slashing incidents. If an AVS you support is slashed, your position may suffer a loss.