USDa

Avalon announced USDa on 7 November 2024. CoinGecko’s usda-2 now anchors it to Ethereum 0x8A60…d9c2 plus Mantle and BNB deployments, separating it from Arkadiko’s older USDA.

The launch offered two mint stories: debt against FBTC and a planned one-for-one USDT route. The protocol marketed a fixed borrowing rate, but rates and pool configurations are administrative parameters rather than permanent token properties.

LayerZero OFT expands the symbol across chains. It does not pool every chain’s supply into a bank reserve; peers and message routes determine which representations can move.

A borrower posts Bitcoin collateral, receives USDa and owes interest on outstanding debt under the borrowing terms. Liquidation is triggered when debt divided by oracle-valued collateral exceeds the pool’s configurable liquidation threshold. Maximum borrowing LTV and recovery LTV are separate settings, not substitutes for that trigger. The pool ABI exposes changes to these ratios, the liquidation threshold, buffer, rates, liquidation bonus and oracle.

A secondary holder receives transferable USDa, not title to FBTC in another user’s position. The reviewed code and documents did not establish a pro-rata collateral withdrawal route or a legal security interest for ordinary token holders.

Avalon advertised an Ethereum conversion vault for USDa and USDT at 1:1. That is a protocol facility whose output depends on USDT inventory, permissions, pause state and successful execution—not a statutory dollar redemption from a named licensed issuer.

The second exit is market sale. Its price can differ from one dollar, and local supplies—about 86.66 million Ethereum plus 11.09 million BNB Chain on review day—say nothing by themselves about collateral or conversion coverage.

USDa does not automatically earn the headline yield. Depositing into SavingAccount mints sUSDa; the manager funds distributeInterests, while pause and role controls govern deposit and redemption.

SlowMist identified logic issues and reported their fixes; this does not establish that the auditor implemented the changes. The report also recorded excessive authority and possible claim failures, and said the audited code had not been deployed to mainnet at the time. The audit addresses a code snapshot, not current reserves, oracle operations or legal repayment.

The reviewed Avalon terms describe the interface as non-custodial and unlicensed and did not identify a stablecoin obligor owing holders dollars. The materials describe an administered crypto debt system with a conditional USDT facility, not a deposit account; an unconditional legal dollar claim was not established in this review.