Chainlink Local V3, with CCIP 2.0 support, is live!
This is a breaking change, so check out release notes https://t.co/LVuJqpF5ni
🎬 And because every launch needs a trailer, here's a quick one I put together with Opus 5.5
We've been working hard on making the Claude Code desktop app great for running lots of sessions side by side.
It's now much quicker to start sessions, easier to split work across a few, and you can always see what each of them is doing. Here’s what's new:
🥧BAKED IN🥧
Any developer that uses OpenZeppelin templates or token wizard for their token (hint: they all do) can now easily get CCIP and ACE standards baked in.
NEW: @OpenZeppelin, which S&P Global agreed to acquire, embeds Chainlink into its tooling standard used by the vast majority of the industry, including BlackRock, WisdomTree, Franklin Templeton, and more.
Chainlink CCIP, CRE, & ACE are now built into the tools behind $38+ trillion in transferred value.
Chainlink CCIP 2.0 added to Chainlink Local for developers!
Chainlink Local is a Chainlink Local Simulator that developers import into their Foundry or Hardhat or Remix projects.
This testing tool runs Chainlink CCIP locally for developers to rapidly explore, prototype and iterate CCIP dApps off-chain in a local environment.
Chainlink Local V3, with CCIP 2.0 support, is live!
This is a breaking change, so check out release notes https://t.co/LVuJqpF5ni
🎬 And because every launch needs a trailer, here's a quick one I put together with Opus 5.5
Huge day for Ethereum interop!
@chainlink CCIP has integrated the Fast Confirmation Rule (FCR)!
NOTE: If you're a solver, bridge or messaging provider, CEX or anyone else benefiting from quick reorg guarantees - reach out to @ethlabs_org!
Ever since first EVM equivalent chains started launching, one of the biggest technical challenges and one of the biggest vulnerability surfaces has been the bridge connecting Ethereum to those chains.
By holding the largest amount of TVL and having most assets issued on it (not to mention being the native home of ETH itself - one of the most valuable assets in all of human history), Ethereum has long served as the center of gravity for the vast majority of L1s and L2s.
However, moving from Ethereum to those chains and back always had one big drawback - per the current consensus rules of Ethereum, the chain finalizes every ~15 minutes. This means, in essence, that a message sent from Ethereum to another chain (such as transferring ETH or some other token) will take around 15 minutes to execute.
However, some time back (April ‘23), some very talented researchers (including Ethlabs’ very own @fradamt) concluded that the Ethereum consensus is much more performant under “usual” conditions. I’ve written a primer on the rule before (https://t.co/mTuT5bM5Qc), but boiled down to the core proposition - instead of waiting for full consensus finality (15 minutes), the Ethereum nodes are able to give a softer guarantee that the Ethereum chain won’t reorg much much quicker - within just 12 - 24 seconds!
Why is this important? Because message passing protocols and bridges, such as Chainlink CCIP require the source chain not to reorg in order to feel confident to send a message to an L2.
However, this guarantee being “softer” than full finality doesn’t mean in any way that it’s a soft guarantee. In order for the Fast Confirmation Rule to trigger and for the blockchain to reorg simultaneously - some truly extraordinary circumstances must happen (explained more in the primer document).
Having the rule integrated into clients, supported by RPCs and bridges has been one of the primary priorities of Ethlabs since the inception. It’s a technical advancement which makes Ethereum faster, more secure and more deterministic - today!
Introducing Claude Opus 5.5, the first model in our new Claude 5.5 family.
It performs at the level of Claude Fable 5.1 for most tasks, and costs 40% less to run than Opus 5.
AI agents are already becoming your customers.
This is a good time to audit your products against three pillars:
1. GEO (can agents discover your product)
2. Agentic experience (can agents successfully use your APIs, SDKs, CLIs, MCP servers or agent skills)
3. Payments (can agents pay for using your product autonomously)
The North star is: "Can an AI agent use your product without human intervention?"