debridge

Use the deBridge Solana SDK's invoke_debridge_send function with the target chain ID, 20-byte EVM receiver address, amount, and fee mode. Pass the required accounts via remaining_accounts in the documented order, or use the DLN API create-tx endpoint from a TypeScript client.

Native fee pays protocol fees in SOL, while asset fee deducts fees from the bridged token itself. Asset fee is not available on all chains, so check availability with is_asset_fee_available before selecting that mode.

Derive the Bridge PDA with seeds ["BRIDGE", token_mint] under the deBridge program, Chain Support Info with ["CHAIN_SUPPORT_INFO", chain_id] under the settings program, and Nonce Storage with ["NONCE_STORAGE", sender]. The SDK provides helper traits like find_bridge_address for each PDA type.

deBridge infrastructure runs on mainnet only, so testing requires a mainnet fork or small real transactions. The SDK supports an env feature flag to override program IDs for custom environments, but the actual bridging protocol is mainnet-based.

This error means an account passed to the SDK is not the expected type, usually due to incorrect PDA derivation or wrong account ordering in remaining_accounts. Verify all PDAs against the documented seeds and follow the exact required account order.

Build the external call data, compute its Keccak256 shortcut, and pass it in SendSubmissionParamsInput along with an execution fee and fallback address. For large payloads, initialize external call storage first with invoke_init_external_call.