S&P 5007,683.69▼0.8% Nasdaq26,820.38▼0.9% Dow51,481.51▼0.7% Russell 2K2,817.91▼0.7% 10-Yr5.24%+6bp VIX16.07+1.20 WTI$93.42▲1.1% Gold$4,147.50▼4.0% EUR/USD1.137▼0.1% BTC$84,063▲0.7% Nikkei65,339▼1.6%
At close · Tue, Sep 29, 2026
Daily Market Updates.

Crypto

Home›Crypto›Market Structure›Chainlink CCIP 2.0 allows issuers to require verifiers…

Chainlink CCIP 2.0 allows issuers to require verifiers before token delivery

The mechanism can make a required verifier's attestation decisive after tokens are locked or burned on the source chain, potentially delaying release or minting on the destination network.

Chainlink's CCIP 2.0 update lets token issuers require an additional verifier before tokens finish moving from one blockchain to another, adding a new optional check alongside CCIP's default Committee Verifier, CryptoSlate reports.

Under the CCIP flow described by CryptoSlate, a sending pool can already have locked or burned the tokens when the issuer-run verifier requirement becomes decisive. If the receiving chain does not receive the needed attestation, it cannot release or mint the tokens.

CryptoSlate says the feature relies on CCIP's OnRamp to assemble the applicable verifier requirements for a transfer, lock or burn the tokens, and record the message for offchain verifier services. Those services then watch the source event, apply finality and verification rules, and publish attestations tied to the message ID.

On the destination side, CCIP's OffRamp checks the required attestations before completion, CryptoSlate notes. The outlet also adds that Chainlink's launch materials do not name a specific production asset and cross-chain lane using an issuer-run required verifier, so the mechanism is not presented as direct proof that transfers are already blocked.

More like this

Sources

Get the close, explained.

One email every trading day: what moved, why it moved, and what's on deck tomorrow. Read in 3 minutes.

Free. Unsubscribe anytime.