We’re excited to announce that the Token Developer Attestation feature of the Cross-Chain Interoperability Protocol (CCIP) is now generally available for use by developers across all supported blockchain networks. 

Expanding on the release via a private beta in the CCIP v1.5 update, the Token Developer Attestation feature enables token developers to participate in an optional layer of verification by attesting to token burn or lock events on source chains before CCIP can mint or unlock tokens on destination chains.

Prominent token developers such as Lombard, a leading liquid staking protocol with nearly $1.7B in TVL, have already adopted the Token Developer Attestation feature to provide additional security for the cross-chain transfer of LBTC. 

The expanded rollout of the Token Developer Attestation feature was driven by user demand from the development teams of stablecoins, liquid staking tokens, wrapped assets, and tokenized real-world assets who sought more tailored control over how their Cross-Chain Tokens (CCTs) move across chains. With this upgrade, CCIP now provides enhanced support for enterprise-grade compliance, developer-defined policy enforcement, and flexible, secure token programmability.

How Token Developer Attestations Enhance CCIP Security Configurability

CCIP’s Token Developer Attestation feature enables token developers to independently confirm that each transaction aligns with their specific asset issuance standards. This token developer-controlled verification process is enabled through an Attestation API that integrates seamlessly into CCIP’s existing cross-chain workflow. The attestation logic is agnostic to the verification logic of the token developer. 

When CCTs are transferred from one blockchain to another, the Attestation API is engaged by CCIP nodes to confirm that the tokens burned on the source chain align with the token developer’s designated issuance criteria. This verification step ensures each minting operation on the destination chain is validated and approved by the token developer, or otherwise tokens are not minted on the destination chain.

The core benefit of the Token Developer Attestation is its emphasis on developer-defined security. By embedding developer-specific validation into the cross-chain transfer process, token developers maintain full oversight and integrity of their assets and their transferability across multiple blockchains. The attestation process also integrates directly with existing CCIP and CCT functionalities, minimizing complexity and costs.

How Leading Token Developers Leverage Token Developer Attestation 

Lombard, the token developer of liquid staking token LBTC leverages the Token Developer Attestation to enhance the security configurability of cross-chain transfers of LBTC. By integrating the Token Developer Attestation, Lombard is able to ensure that each cross-chain LBTC transfer via CCIP aligns with its internal compliance and operational standards.

LBTC Cross-Chain Token Transfer Process

1. A user initiates a cross-chain LBTC transfer through Lombard’s front end, which sends a cross-chain request to the CCIP Router. 
2. The CCIP Router forwards the request to Lombard’s custom LBTC token pool, which interacts with other Lombard components to initiate a token burn and generate a unique burn identifier.
3. This burn ID is returned to the CCIP OnRamp, completing the source chain side of the transfer.
4. The CCIP Committing DON validates and commits to the message. 
5. The CCIP Executing DON queries Lombard’s Attestation API using the burn ID before relaying the message to the destination chain. The attestation result from the Lombard Security Consortium is included in the CCIP message.
6. On the destination chain, Lombard’s token pool verifies the attestation and, if valid, executes the minting of LBTC to the recipient specified in the original request.

Integrating Token Developer Attestations provides Lombard with:

• Enhanced security—Only allows burns verified by the Lombard Security Consortium to trigger token minting of LBTC.
• Clear Record Keeping—Establishes a clear attestation audit trail for every LBTC transfer, helping meet both internal and external reporting obligations.
• Cost Efficiencies – Providing attestations offchain in this architecture reduces gas costs for Lombard in comparison to an approach where attestations are done onchain.
• Agile Configuration—Allows for verification logic to be adjusted as needed, enabling easier iteration of issuance policies without redeploying contracts.
• Issuance Retention—Keeps full control over LBTC’s cross-chain movement without deploying or maintaining custom infrastructure across each destination chain.

By adopting CCIP’s support for Token Developer Attestations, Lombard positions itself effectively within the tokenization ecosystem, enhancing user confidence and helping ensure robust operational management.

Enhancing Developer Configurability With CCIP  

The general availability launch of the CCIP’s Token Developer Attestation feature gives token developers enhanced configurability over the security properties of their Cross-Chain Tokens by providing an additional, optional verification method for cross-chain transfers. Notably, Token Developer Attestations introduce a new method for how token developers can verify cross-chain activity against their internal systems and policies, without overhauling their internal infrastructure.

For development teams managing assets that require stricter oversight—whether due to internal risk controls, regulatory requirements, or institutional trust standards—the Token Developer Attestation feature offers a framework for embedding developer-defined checks into cross-chain operations. Developers can build attestation layers that reflect their own minting, burning, or supply logic, and modify them over time as requirements evolve.

If you’re a DeFi protocol or traditional financial institution looking to explore how CCIP’s support for Token Developer Attestations can support your cross-chain and tokenization initiatives, reach out to our team of experts.

If you’re a developer and want to get started with Token Developer Attestation and CCIP, check out the CCIP documentation, learn how to deploy your own cross-chain token, or begin directly through the Chainlink Token Manager.

—

Disclaimer: This post is for informational purposes only and contains statements about the future, including anticipated product features, development, and timelines for the rollout of these features. These statements are only predictions and reflect current beliefs and expectations with respect to future events; they are based on assumptions and are subject to risk, uncertainties, and changes at any time. There can be no assurance that actual results will not differ materially from those expressed in these statements, although we believe them to be based on reasonable assumptions. All statements are valid only as of the date first posted. These statements may not reflect future developments due to user feedback or later events and we may not update this post in response. Chainlink CCIP is a messaging protocol which does not hold or transfer any assets. Please review the Chainlink Terms of Service, which provides important information and disclosures.