Chainlink CCIP 2.0 Lets Companies Add Their Own Bridge Security — the Answer to a 292 Million USD Hack

Chainlink has launched CCIP 2.0, a major upgrade to its cross-chain bridge technology that lets companies add their own security checks on top of Chainlink’s default network — a direct answer to April’s 292 million USD Kelp DAO hack, which was blamed on a rival bridge that relied on a single verifier.

By Keisha Williams | September 29, 2026

The upgrade, released Monday according to CoinDesk, changes how the Cross-Chain Interoperability Protocol (CCIP) protects token transfers between blockchains. For everyday crypto users, the stakes are simple: bridges are the plumbing that moves your tokens between networks, and broken plumbing has drained billions from investors over the years. Chainlink’s answer is to let the companies holding your funds bolt on extra locks of their own choosing.

The Hook: Why This Launch Matters Now

Blockchains cannot talk to each other directly. When you move a token from one network to another, a piece of software called a bridge holds your funds on one side and issues a copy on the other. That handoff depends on verifiers — computers that confirm a transaction really happened on the first chain before funds are released on the second. If a verifier is fooled, an attacker can withdraw money that was never deposited.

That is exactly what happened to Kelp DAO in April 2026. Attackers, allegedly linked to North Korea’s Lazarus Group according to CoinDesk reporting, drained roughly 292 million USD worth of rsETH from Kelp’s bridge after tricking the single verifier the setup depended on. The bridge ran on LayerZero, Chainlink’s biggest rival. It was the largest DeFi exploit of the year, and it left wrapped ether stranded across some 20 chains.

On-Chain Evidence: How the New System Works

CCIP, first launched in 2023, is Chainlink’s system for moving tokens and messages between blockchains. CCIP 2.0 keeps a default network of 16 independent node operators that must reach agreement on every transfer. The new part: companies using the protocol can now stack additional verifiers of their own on top of that base layer — either running their own or hiring outside providers such as Infosys and Nethermind.

• Default layer — 16 independent Chainlink node operators must reach a quorum before any transfer goes through
• Optional layer — companies add their own security checks, run in-house or via providers like Infosys and Nethermind
• No forced migration — existing integrations keep working with CCIP 2.0 without changes, Chainlink says
• Early adopters — Aave and Maple have started adopting some of the upgrade’s other features, though no institution is using the new custom verifiers yet

Chainlink argues users should not have to be “cross-chain security infrastructure experts” to stay safe. Johann Eid, Chainlink Labs’ chief business officer, said in a statement that legacy bridges have historically “lost billions due to insecure infrastructure, while in-house builds are slow and expensive.”

The Core Conflict: One Network Instead of Two?

Here is the catch that critics are watching. The upgrade also changes a safeguard Chainlink used to promote heavily: the Risk Management Network, a separate set of nodes that double-checked every transaction, no longer plays that role. Chainlink says that kind of independent review can now come from the optional verifiers instead. In practice, a company that adds nothing now relies on one verifier network — albeit one made up of 16 operators rather than a single machine — where the old design offered two separate layers of checking.

The blame game around Kelp never fully resolved, and it explains why this design matters. LayerZero publicly blamed Kelp for choosing a one-verifier setup when it could have used several. Kelp countered that LayerZero staff had reviewed its configuration and never objected, as CoinDesk reported. Adding to the unease, CoinGecko data showed nearly half of active LayerZero apps used the same one-verifier arrangement. Kelp subsequently said it would move its rsETH token to Chainlink.

Market Implications: What This Means for Your Wallet

If you hold tokens that move between networks — wrapped bitcoin, liquid staking tokens like rsETH, or stablecoins bridged across chains — the security of that bridge is effectively the security of your money. A bridge failure does not care whether you bought the token on an exchange or earned it as yield. The Kelp hack showed what a single point of failure costs; CCIP 2.0 is the industry’s latest attempt to make sure no one verifier can ever be the only thing standing between an attacker and the vault.

There is also a competitive story here. Chainlink is best known as an oracle network — the feed of real-world data, like asset prices, that lending and trading apps depend on. Cross-chain infrastructure is its bid to become the default connective tissue of the entire industry. Winning over institutions that were spooked by the Kelp incident is part of that playbook, and letting those institutions bring their own security checks is a sales pitch as much as a safety feature: trust us, but verify us too.

The Verdict

CCIP 2.0 is a pragmatic upgrade with an honest trade-off. Default users get a 16-operator quorum — far stronger than the single verifier that sank Kelp — but lose the automatic second network of checks unless they opt in. Companies serious about security now have easy tools to layer their own verification on top, and the fact that Aave and Maple are already adopting parts of the upgrade suggests genuine uptake. The real test will come the first time something goes wrong: whether the optional checks get used widely enough to matter, and whether 16 operators proving tougher to trick than one proves true in practice. For now, the direction of travel — away from single points of failure — is the right one for anyone holding bridged assets.

The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.