OptionaluserConfig: DymensionBridgeConfigCreate Kaspa deposit payload (not full transaction)
Since Kaspa has no smart contracts, this creates a Hyperlane message payload that must be included in a Kaspa transaction to the escrow address.
Deposit parameters
Serialized Hyperlane message bytes to include in Kaspa tx
Create forwarding memo for RollApp -> EVM via EIBC
Creates the JSON memo to include in an IBC MsgTransfer from RollApp that will be forwarded via Hyperlane after arriving on Hub.
Forwarding parameters
JSON memo string to include in IBC MsgTransfer
Estimate all fees for a bridge transfer
Calculates approximate fees for different transfer scenarios:
Fee estimation parameters
Breakdown of all fees and recipient amount
Get the resolved configuration
Get the fee provider instance for direct fee queries
Create unsigned transaction for EVM -> Hub transfer
Create unsigned transaction for Hub -> EVM transfer
Uses MsgRemoteTransfer for the native Hyperlane warp module.
Create unsigned transaction for Hub -> Kaspa transfer
Uses MsgRemoteTransfer for the Hyperlane warp module (native SDK message). Requires IGP fee payment via the KAS IGP hook.
IGP fee in KAS denom (get from FeeProvider.quoteIgpPayment)
Create unsigned transaction for Hub -> Solana transfer
Uses MsgRemoteTransfer for the native Hyperlane warp module. Requires IGP fee payment via the token-specific IGP hook.
Create unsigned transaction for Solana -> Hub transfer
Create an unsigned transfer transaction using chain and token symbols
This high-level method automatically:
// EVM to Hub
const result = await client.transfer({
from: 'ethereum',
to: 'dymension',
token: 'KAS',
amount: 100000000n,
recipient: 'dym1abc...',
sender: '0x123...',
});
// Hub to Kaspa
const result = await client.transfer({
from: 'dymension',
to: 'kaspa',
token: 'KAS',
amount: 100000000n,
recipient: 'kaspa:qz...',
sender: 'dym1abc...',
});
BridgeClient provides methods to construct unsigned bridge transactions