CCIP v2.0.0 IBridgeV2 API Reference
Summary
IBridgeV2 defines the minimal interface for Lombard Bridge V2 integrations.
It exposes:
- Mailbox discovery
- Message version detection
- Deposit initiation
- Destination token resolution
This interface is used by:
[LombardVerifier](/ccip/evm/api-reference/v2.0.0/lombard-verifier)[LombardTokenPool](/ccip/evm/api-reference/v2.0.0/lombard-token-pool)
Contract
chains/evm/contracts/interfaces/lombard/IBridgeV2.sol
Import
import {IBridgeV2} from "chainlink-ccip/chains/evm/contracts/interfaces/lombard/IBridgeV2.sol";
Interface surface
interface IBridgeV2 {
mailbox
function mailbox() external view returns (address);
Returns the associated IMailbox contract address.
MSG_VERSION
function MSG_VERSION() external view returns (uint8);
Returns the bridge message format version.
deposit
function deposit(
bytes32 destinationChain,
address token,
address sender,
bytes32 recipient,
uint256 amount,
bytes32 destinationCaller
) external payable returns (uint256, bytes32);
Initiates a cross-chain deposit.
Parameters:
destinationChain— Lombard chain identifier.token— Source token address.sender— Logical sender for the deposit.recipient— 32-byte destination recipient identifier.amount— Token amount.destinationCaller— Authorized destination handler.
Returns:
uint256— Bridge-defined numeric identifier.bytes32— Bridge-defined message or payload hash.
Function is payable to allow bridge-native fee handling.
getAllowedDestinationToken
function getAllowedDestinationToken(
bytes32 destinationChain,
address sourceToken
) external view returns (bytes32);
Returns the destination token identifier approved for the (destinationChain, sourceToken) pair.
}
Integration notes / expectations
- Consumers should validate
MSG_VERSION()matches expected version. depositmay require native value depending on bridge implementation.- Destination token resolution must be verified before initiating deposits.
- Return values from
depositare bridge-defined and not interpreted by this interface.