buildBridgeDeposit

​

Planned function

​

buildBridgeDeposit

1. Read the pause state and limits, and throw BridgeValidationError if the bridge is paused, the amount is outside the limits or the destination isn’t supported.
2. Return an unsigned call to the bridge router’s deposit(destinationChainId, resourceId, recipient, amount), which you sign and send.

​

Bot gas

• Who asks for it. The sender calls depositWithBotGas instead of deposit on the source chain. It takes the same four arguments.
• What arrives. When the transfer lands on BOT Chain, the router works out what the configured BOT amount costs in USDT, using a time-weighted average price. It sends the recipient that BOT plus the rest of the USDT. With 0.1 BOT configured on mainnet, the recipient gets 0.1 BOT and slightly less USDT than a plain deposit.
• When it fails. If the USDT arriving is less than the BOT costs, or the price can’t be read, the delivery reverts on BOT Chain and has to be retried or refunded.

​

It doesn’t apply to deposits from BOT Chain

​

Do it today

import { encodeFunctionData, parseUnits } from "viem";
import { botBridgeAbi, getAddresses, TOKENS, USDT_RESOURCE_ID } from "@uzolabs/sdk/contracts";

const recipient = "0xEc526474F4F9De027942d5f7118A9613266B0C4c"; // your address on the destination chain
const tx = {
  to: getAddresses(968).bridgeRouter,
  data: encodeFunctionData({
    abi: botBridgeAbi,
    functionName: "deposit",
    args: [97n, USDT_RESOURCE_ID, recipient, parseUnits("11", TOKENS.USDT.decimals)],
  }),
};
console.log(tx);

​

Related