When LRTs are moved across chains, the discount often widens. The root cause is usually not the LRT itself, but the bridge that transfers the LRT from chain A to chain B. If the bridge has a problem, the discount can spread like a virus.
Step 1: Check if the bridge uses "single-point trust" or "multi-point verification"
The bridge's trust model directly determines how trustworthy the LRT becomes after crossing chains, which in turn affects the discount.
What to do: Find out what verification setup your LRT bridge uses.
How to do it: Check the LRT protocol's technical docs or community discussions to see how many verifier nodes it uses. The Kelp DAO incident in April 2026 is a classic lesson—it used only 1 DVN (Decentralized Verifier Network) node to verify cross-chain messages. After attackers poisoned that node's data source, they minted 116,500 fake rsETH out of thin air. A 1-of-1 setup means "one notary calls the shots," which is extremely fragile in cross-chain scenarios.
Completion standard: You clearly know whether this cross-chain path uses 1-of-1 or M-of-N verification.
Step 2: Check if the discount comes from "fake supply"
When a cross-chain bridge is attacked or has a vulnerability, the most direct result is that the LRT supply on one side is artificially inflated, but the underlying assets haven't increased.
What to do: Check the total supply of the LRT on the destination chain and compare it with the amount of underlying assets locked on the source chain.
How to do it: Use a block explorer or DeFiLlama to check the LRT's contract total supply on the destination chain, then check how much underlying ETH/LST is locked in the corresponding reserve address on the source chain. If they don't match, the supply has been artificially inflated. In the Kelp incident, the fake rsETH minted by the attacker made up 18% of the circulating supply. These unbacked tokens were quickly deposited into lending protocols like Aave to borrow real ETH, causing rsETH to trade at a discount on multiple chains.
Completion standard: You confirm that the current discount is not normal market fluctuation, but that the supply has been contaminated by "unbacked assets."
Many people see LRT discounts after a bridge and think it's a "buy the dip" opportunity, but the root of the discount is that the bridge's security assumptions have been broken, and you don't know how many of those LRT tokens are fake. In the Kelp incident, the attacker deposited the fake rsETH into Aave and borrowed $236 million worth of WETH, leaving a huge bad debt that depositors will eventually have to cover. You think you're "buying the dip," but you might actually be picking up contaminated tokens.
Step 3: Factor "bridge risk" into your LRT pricing model, not just the exchange rate
LRT discounts are not just a liquidity issue; they are also a credibility issue.
What to do: When assessing LRT cross-chain discounts, treat the bridge's security history, verification setup, and emergency response speed as independent risk factors.
How to do it: If an LRT protocol uses a 1-of-1 bridge setup, its discount should be larger than similar assets using M-of-N configuration—this isn't a market error, it's the market pricing in "single-point trust." After the Kelp incident, LayerZero clearly stated that its DVN will refuse to sign for applications still using a 1-of-1 setup.
Completion standard: You no longer view the discount as just an "arbitrage opportunity," but as a composite signal that includes bridge risk.
In essence, LRT discounts after a cross-chain transfer are discounts on "bridge credibility," not just on "liquidity." Once a cross-chain path is proven to have a security flaw, the LRT on that path will quickly lose value, and the discount is hard to repair in the short term—because the market needs time to rebuild trust in whether the bridge might fail again. Also, if that LRT is widely used as collateral in lending protocols, the cross-chain discount could trigger chain liquidations, further pushing down prices.
Verification steps before cross-chain transfers
Before every cross-chain LRT transfer, search the protocol's official Discord or governance forum for keywords like "bridge," "DVN," and "security" to see if there have been recent discussions about bridge config changes or security incidents. If the verification setup is single-point or there was an abnormal event recently, it's better to accept higher slippage and use the official redemption path rather than move assets through a risky bridge.
Next steps
Add the "bridge's DVN setup" to your LRT operation checklist. If the setup is 1-of-1, unless you are absolutely certain the bridge operator is extremely reliable, prioritize using other paths or buying spot directly on that chain to avoid the potential discount from cross-chain transfers.
