Loading beta launch
BDUSD beta launch BlockDAG Stable Coin

Stable Coin

Add native BDAG as collateral and get BDUSD on BlockDAG mainnet. This beta launch is experimental, limited, and subject to the terms below.

BD
BDUSD BDAG-backed beta stablecoin
Beta market
Reserve value-
BDUSD minted-
System capacity-
OracleChecking

Your BDUSD Position

Wallet not connected Accept the beta launch terms, then connect.
Not connected
NetworkBlockDAG Mainnet
GasPaid in BDAG
OracleChecking
ContractLoading
Updated-
Available to Get - Maximum BDUSD currently available from this wallet.
Wallet BDAG-
Wallet BDUSD-
Position health-
BDAG added-
BDUSD to return-
Unlocked BDAG-
Import BDUSD token
Loading contract...
Reserve value-
System capacity-

Live value from vault collateral and oracle pricing. The vault holds BDAG.

Recommended: Add BDAG Your next step Add BDAG

Add BDAG to open or strengthen your BDUSD position.

Add BDAG first. Example: 10,000 BDAG.

BDAG in wallet-
Available to add-

Waiting for deployed contracts.

How BDUSD Works

1 Add BDAG

Add BDAG to open or strengthen your position.

2 Get BDUSD

Get BDUSD only within the available collateral limit.

3 Use BDUSD

Use BDUSD in supported beta launch flows.

4 Return and withdraw

Return BDUSD first, then withdraw unlocked BDAG.

Trust and Control Transparency

These are the beta deployment facts exposed for review. User actions are wallet-signed on BlockDAG; the frontend cannot mint BDUSD or move BDAG without the connected wallet signing the transaction.

Staking contract

No staking contract is part of this BDUSD beta mint flow. BDUSD minting is collateral-vault based: users add native BDAG to the vault, then mint within the collateral limit.

Mint authority and minted wallet addresses

No externally owned wallet has direct BDUSD mint/burn authority. The authorized minter is the native vault contract. BDUSD is minted directly to the connected user wallet that signs the mint transaction.

View recent mint, repay, deposit, and withdrawal activity

Whitepaper allocation match

The beta was configured against a 50,000 USD reserve target and a 25,000 BDUSD debt ceiling at 200% collateralization. The frontend does not assert a whitepaper-allocation match by itself; that requires treasury/allocation records plus on-chain reserve reconciliation.

Ownership and admin rights

Governance/risk multisig controls risk parameters, pause roles, and OpenZeppelin ProxyAdmin upgrade ownership: 0x924D66BAB65B98f6A43ed5ab8630D154f5C6cf68. Treasury ownership is assigned to the treasury multisig: 0x5F1Fd05713198834066069d2f16BD226e033744B. Deployer admin roles were revoked after bootstrap.

Dashboard and backend controls

The consumer dashboard signs user transactions in the wallet. Vercel APIs remain for read-only reserve/stat displays and low-privilege oracle automation. Off-chain services cannot withdraw user BDAG or mint BDUSD to arbitrary wallets; governance is still required for upgrades, risk changes, pause controls, and oracle-role changes.

Risk Notice

BDUSD is a beta launch synthetic dollar backed by BDAG collateral. It is not USDT, USDC, fiat money, or a guaranteed one-dollar claim. The full version of the BDAG Stable Coin is expected after the beta launch phase, subject to further review and rollout decisions.

OpenZeppelin Library References

This interface references OpenZeppelin Contracts and Contracts Upgradeable v5.6.1 components, including ERC20, AccessControl, Pausable, ReentrancyGuard, Ownable2Step, and TransparentUpgradeableProxy. These links point to OpenZeppelin library documentation, security policy, and public advisories for those components.

Contract addresses
StatusPending deployment