Skip to content
DeltaUSD

Minting / BNB CHAIN + X LAYER

How to mint dUSD with USDT on BNB Chain and X Layer

Minting exchanges supported USDT collateral for newly issued dUSD at the protocol contract price. Choose the network first: BNB Chain and X Layer use separate deployments, separate collateral balances and different gas tokens. This guide explains what to verify before submitting a transaction.

AT A GLANCE

  • Choose the network before approving collateral.
  • Read the estimated dUSD output, not a fixed 1:1 assumption.
  • An approval and a mint are different transactions.
01

Match the wallet, network and collateral

Open the official protocol page and select BNB Chain or X Layer. The wallet must use the same network, and the collateral must be the token accepted by that deployment. A matching ticker in another network is not enough. The contract addresses for both deployments are listed below.

BNB Chain requires BNB for gas and uses collateral with 18 decimals. X Layer requires OKB and uses its configured USDT/USD₮0 collateral with 6 decimals. dUSD has 18 decimals in both deployments. The interface performs unit conversion; do not multiply or divide the displayed input by a decimals factor yourself.

The network selector is not a bridge. Switching it does not move your USDT or dUSD between chains. You need collateral in the chosen network before minting there.

02

Understand the dUSD quote

Enter the USDT amount in the Mint panel. The quote uses the current contract price, so depositing 1,000 USDT does not necessarily produce 1,000 dUSD. For example, at 1.02 USDT per dUSD, the result is approximately 980.392156 dUSD before the contract integer rounding.

This example is not a current quote. Check the network, input amount and estimated output again in the live interface. The minDUSDOut argument protects a mint by making it revert if the output falls below the submitted minimum. It does not protect against strategy losses or future price changes.

Estimated dUSD = USDT amount / contract price
Example: 1,000 / 1.02 ≈ 980.392156 dUSD
03

Approve USDT, then mint

The reviewed implementation has no separate protocol mint fee. Network gas is paid separately, and approval may require another transaction. A failed on-chain transaction can still consume gas.

  1. Connect the wallet that will hold dUSD. Verify that the site domain is deltausd.com and the wallet network matches the selection.
  2. If allowance is insufficient, approve the protocol contract to spend the required collateral amount. Check the spender address in the wallet confirmation against the deployment below.
  3. After approval confirms, submit mint(amount, minDUSDOut). Read the wallet transaction details and the estimated gas cost before confirming.
  4. Wait for a successful receipt in the network explorer. A successful approval alone does not mean dUSD was minted. Check the resulting token balance and the Minted event.
04

If a mint does not complete

Check for a wrong network, insufficient supported USDT, insufficient BNB or OKB for gas, a missing allowance or a paused protocol. A pending transaction, a rejected wallet prompt and a reverted transaction are different states; inspect the transaction hash before sending another mint.

Minting creates exposure to the protocol. The owner can change pricing parameters and new-request waiting periods, pause new operations and withdraw contract-held collateral. Read the yield and redemption guides before deciding whether the asset fits your needs.

Verify the deployment

Use the addresses for the network selected in your wallet. These links open the network explorer; the full documentation explains the contract permissions and price formula.

Common questions

Why did I receive fewer dUSD than the USDT deposited?

The output is divided by the contract price. When one dUSD costs more than one USDT, the number of dUSD received is lower than the USDT amount.

Can I use the same wallet address on both networks?

An EVM address can be used on both networks, but balances, approvals and transactions are separate. Switching networks does not transfer tokens.

Why are two wallet confirmations sometimes needed?

One may approve USDT spending and the other execute the mint. Existing sufficient allowance can remove the need for a new approval.

SOURCES & CONTEXT

This explanation follows the published DeltaUSD implementation and documentation. Check live values and any later changes before a transaction.

Technical documentation ↗Live protocol parameters ↗