Bridge assets to the restaking chain

Before you can restake, you must move your assets from their native chain to the target L2 or sidechain where the protocol operates. This transfer is the highest-risk phase of the entire workflow. A single mistake here can result in total loss of capital. We will walk through the exact sequence to move assets securely, prioritizing protocol integrity over speed or convenience.

1
Select the official bridge or cross-chain protocol

Identify the primary bridge recommended by the restaking protocol. Do not rely on third-party aggregators or unverified links. Visit the official documentation of the restaking protocol to find the verified bridge URL. If the protocol supports Canonical Bridges or Cross-Chain Transfer Protocol (CCTP), prefer these for native asset transfers, as they eliminate wrapped token risks. For example, CCTP burns USDC on the source chain and mints it on the destination, ensuring a 1:1 secure transfer without liquidity pool risks [src-serp-3].

2
Connect your wallet and verify the contract address

Open your wallet extension and connect to the bridge interface. Before entering any data, verify the smart contract address displayed on the bridge matches the official documentation. Cross-chain bridges are prime targets for phishing attacks. Ensure the URL matches the official domain exactly. If you are using a browser wallet, check for any suspicious permissions or contract interactions before signing.

3
Enter the asset amount and select the destination network

Input the exact amount of assets you intend to restake. Select the source network (e.g., Ethereum L1) and the destination network (the L2 or sidechain running the restaking protocol). Review the estimated gas fees and bridge fees. Note that fees vary significantly between protocols; some may offer faster finality at a higher cost, while others prioritize security with longer wait times. Ensure you have enough native gas tokens on the source chain to cover transaction fees.

4
Confirm and monitor the transaction

Sign the transaction in your wallet. The bridge will initiate the transfer. Monitor the transaction status on a block explorer for both the source and destination chains. Cross-chain transfers can take anywhere from a few minutes to several hours depending on the protocol's security model and network congestion. Do not proceed to restaking until the assets are confirmed and visible in your wallet on the destination chain.

Deposit ETH into a Restaking Protocol

With bridged ETH secured in your destination wallet, the next phase involves locking those assets into a restaking protocol to generate yield and security points. This step converts idle liquidity into active stake, but it also introduces smart contract risk that does not exist with simple holding.

Before selecting a protocol, review the comparative metrics below to understand the trade-offs between yield potential and chain support.

ProtocolEst. APYSupported ChainsSecurity Model
EigenLayerVariable (4-8%)Ethereum MainnetSlashing penalties on ETH
ether.fiVariable (3-6%)Ethereum, Arbitrum, BaseLiquid staking derivative
KelpDAOVariable (5-9%)Ethereum, OptimismrsETH yield + restaking points

Choose Your Protocol

Select a protocol that aligns with your risk tolerance and desired chain exposure. EigenLayer remains the standard for direct Ethereum restaking, offering high security but limited chain diversity. For users seeking exposure to Layer 2 ecosystems, ether.fi and KelpDAO provide liquid staking derivatives (LSDs) that can be further deployed across multiple networks. Note that KelpDAO has faced security incidents in the past; verify current audit statuses and insurance coverage before depositing.

Execute the Deposit

  1. Connect your wallet to the official protocol interface. Always verify the URL against the project’s official Twitter or Discord to avoid phishing sites.
  2. Select the ETH asset you wish to restake. Ensure the network matches your bridged ETH location (e.g., if you bridged to Arbitrum, select the Arbitrum pool).
  3. Enter the deposit amount. Review the gas fees and the expected yield rate. Some protocols require a minimum deposit threshold.
  4. Confirm the transaction in your wallet. Wait for the blockchain confirmation.
The to Cross-Chain Restaking
1
Connect Wallet and Verify URL
Open the protocol’s official website. Click "Connect Wallet" and select your preferred provider. Before entering any funds, verify the domain name against the project’s verified social channels. Phishing sites often mimic legitimate interfaces to steal assets.
2
Select Asset and Network
Navigate to the "Deposit" or "Restake" tab. Choose the ETH token that matches your current network. For example, if you bridged via CCIP to Arbitrum, select the Arbitrum ETH pool. Selecting the wrong network will result in lost funds or failed transactions.
3
Confirm and Lock Assets
Enter the amount of ETH to deposit. The interface will display the estimated restaking points or yield. Review the smart contract terms, specifically the withdrawal lock-up period and slashing conditions. Click "Approve" for the token spend, then "Deposit" to finalize the transaction.

Monitor Your Position

After the transaction confirms, your ETH is now restaked. You will typically receive a liquid staking token (such as rsETH or ezETH) in your wallet, representing your position. Monitor this token’s value and the underlying protocol’s health. Most protocols distribute rewards automatically to your wallet, but some require manual claiming.

Security Checklist

  • Verify the official protocol URL via Twitter/Discord.
  • Confirm the network matches your bridged ETH.
  • Check for recent security audits or exploits.
  • Understand the slashing conditions and lock-up periods.

Configure Delegation to Validators

Delegation is the mechanism that translates your staked ETH into active security for specific Actively Validated Services (AVSs). Unlike standard staking, where you delegate to a generic validator, cross-chain restaking requires you to select specific operators who provide the computational power and security guarantees for the AVS you wish to support. This step determines your yield potential and, more importantly, your exposure to slashing risks.

The process involves choosing between high-yield, high-risk AVSs or conservative, established networks. Because you are effectively insuring multiple protocols simultaneously, a misconfiguration or a poorly chosen operator can lead to simultaneous slashing events across all delegated services. Precision in selection is the only defense against catastrophic loss.

1
Identify Your Target AVS

Before interacting with any interface, define which Actively Validated Service you intend to support. AVSs range from decentralized oracle networks to cross-chain messaging protocols. Review the AVS’s security model and historical uptime. Avoid AVSs with unproven codebases or recent audit failures. Your choice here dictates the risk profile of your entire restaking position.

2
Select a Reputable Operator

Operators are the entities that run the node infrastructure for AVSs. You must delegate your restaked ETH to an operator who is actively serving your chosen AVS. Check the operator’s commission rate, uptime history, and whether they are diversified across multiple AVSs. Diversification can mitigate risk, but ensure the operator’s total exposure does not exceed safe thresholds. Poor operator performance can result in missed attestations and subsequent slashing.

3
Execute the Delegation Transaction

Connect your wallet to the restaking protocol’s interface (e.g., EigenLayer or a specific AVS dashboard). Initiate the delegation transaction, specifying the operator ID and the amount of restaked ETH to delegate. Review the transaction details carefully, including gas fees and the specific smart contract addresses involved. Confirm the transaction on the blockchain. This action locks your delegation, aligning your economic stake with the operator’s security responsibilities.

4
Verify Slashing Conditions and Monitoring

Once delegated, you are liable for the operator’s actions. If the operator fails to perform its duties or acts maliciously, you may be slashed. Set up monitoring alerts for the operator’s performance and any governance proposals that might change the AVS’s security parameters. Regularly review your delegation status to ensure it remains aligned with your risk tolerance. If an operator’s risk profile changes, consider undelegating and re-delegating to a safer entity.

Monitor slashing and bridge risks

Cross-chain restaking amplifies yield but multiplies attack surfaces. Your capital is exposed to two distinct threats: slashing penalties from validator misbehavior and bridge exploits that drain liquidity. Monitoring these risks requires active vigilance, not passive trust.

Cross-chain bridges are high-risk attack vectors. Review the April 2026 KelpDAO exploit for context on bridge security failures. Attackers drained 116,500 rsETH (~$292M) by forging a cross-chain message, highlighting the fragility of LayerZero-based infrastructure.

Track slashing events

Slashing occurs when a validator node violates protocol rules, resulting in the permanent loss of staked assets. In cross-chain environments, this risk is compounded by the complexity of validating across multiple networks.

Set up real-time alerts for slashing events on your primary validator nodes. Use block explorers and protocol-specific dashboards to monitor validator status. If a validator is slashed, your restaked assets may be frozen or reduced immediately. Do not assume insurance or recovery mechanisms are in place; many restaking protocols lack robust slashing protection.

Monitor bridge health

Bridges are the weakest link in cross-chain security. The KelpDAO incident demonstrates how a single compromised bridge can drain millions in minutes. Regularly check the health status of the bridges you use.

Verify the integrity of cross-chain messages before confirming transactions. Look for anomalies in transaction volumes or unusual activity on bridge contracts. If a bridge experiences a delay or fails to finalize transactions, pause your restaking activities immediately. Do not rely on automated bridges for high-value transfers without manual verification.

Respond to security incidents

If you detect a potential exploit or slashing event, act quickly. Disconnect your wallet from the affected protocol and withdraw your assets if possible. Document the incident and report it to the protocol’s security team.

Stay informed about security updates and patches. Follow official announcements from restaking protocols and bridge providers. Do not engage with suspicious messages or links claiming to offer "recovery" or "compensation." These are often secondary scams targeting distressed users.

Verify rewards and withdraw safely

Before moving your assets, you must confirm that the restaking rewards have settled and the withdrawal queue has cleared. In cross-chain restaking, rewards are often distributed asynchronously across different consensus layers. If you attempt to withdraw before the validator’s exit is finalized on the source chain, the transaction will fail or, worse, result in a loss of principal.

Execute the withdrawal in three precise steps:

1
Confirm reward accrual

Check your restaking dashboard or the smart contract explorer to ensure all pending rewards are marked as "available" or "claimable." Do not proceed if the status is still pending, as this indicates the validator is still active or the reward distribution cycle has not closed.

2
Initiate the exit request

Submit the withdrawal request on the source chain where your staked assets reside. This triggers the slashing period and exit queue. Record the transaction hash and the estimated completion time provided by the protocol.

3
Bridge the assets back

Once the exit is finalized, use a canonical bridge or a trusted interoperability layer to transfer your principal and rewards to your destination wallet. Verify the bridge’s current liquidity depth to avoid slippage or delays.

Always double-check the bridge’s status page before initiating the final transfer. Bridge failures are a common vector for loss, as seen in past exploits where liquidity pools were drained during high-volume transfers. If you are moving significant value, consider splitting the withdrawal into smaller transactions to mitigate risk.

Common questions about cross-chain restaking

Cross-chain restaking introduces complexity that can expose capital to bridge failures or smart contract vulnerabilities. Before deploying assets, verify the security model of every protocol in the path. Use official documentation to confirm how liquidity moves and where the custody risks lie.