PrivateDAO is loading wallet-ready controls, Testnet context, and proof-linked routes so the app lands with real content instead of an empty frame.
Product brief for AUDD merchant settlement, treasury management, invoice collection, programmable Australian-dollar finance, and browser-signed stablecoin billing across the PrivateDAO treasury layer.
Stablecoin operating brief only; it ships route logic, SPL transfer construction, and the official AUDD mint plus funded-wallet activation path.
Audience: Grant reviewers, treasury operators, merchant builders, finance teams, institutional stablecoin partners
Open raw filePrivateDAO treats stablecoin settlement as treasury infrastructure, not as a cosmetic token toggle.
The AUDD layer is designed for teams that need:
AUDD fits this layer because the sponsor brief is practical and production-oriented: build something people can use, make AUDD the on-chain Australian-dollar asset, and connect it to real payments, settlement, treasury, or programmable finance flows on Solana.
The product can stage an AUDD payment request from the browser, attach memo-coded intent, preserve route context, and keep the resulting signature inside the same reviewer path as the treasury request.
Primary routes:
Treasury operators can prepare AUD-denominated reserve motions, supplier settlement, or invoice funding requests without splitting governance, route logic, and settlement proof across separate tools.
Primary routes:
The same surface can support policy-bound merchant disbursements, recurring treasury operations, and route-reviewed finance actions while keeping governance and wallet execution linked.
Primary routes:
The sponsor ask is direct:
PrivateDAO already matches that shape with:
That makes AUDD a strong fit for the existing architecture because we do not need to redesign the product to support an Australian-dollar rail. We need to configure the official AUDD mint and run the same governed flow through the treasury layer.
The web product now exposes AUDD as a first-class treasury asset when these environment values are configured:
NEXT_PUBLIC_TREASURY_AUDD_MINT=
NEXT_PUBLIC_TREASURY_AUDD_RECEIVE_ADDRESS=
NEXT_PUBLIC_TREASURY_AUDD_DECIMALS=6
NEXT_PUBLIC_TREASURY_AUDD_TOKEN_PROGRAM=TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA
PRIVATE_DAO_MICROPAYMENT_MINT=
PRIVATE_DAO_MICROPAYMENT_SYMBOL=AUDDThe browser flow constructs a wallet-signed SPL token transfer using:
No unverified AUDD mint is hardcoded into the repository. The official Solana mint is injected through environment configuration, and the same route activates the AUDD-specific transfer path with a funded wallet.
This layer aligns directly with the grant categories:
The result is not a slide-deck concept. It is a shipped treasury surface that can be pointed at AUDD as the settlement asset.
Recommended review order:
PrivateDAO now ships the browser route, treasury configuration, payout profiles, and wallet-signed SPL transfer construction for AUDD.
The remaining activation input is the official AUDD Solana mint plus a funded wallet for live asset-specific settlement. The product lane itself is already present and reusable across merchant settlement, treasury management, and programmable finance flows.
Operational brief for DAO-controlled micropayment batches, showing how approved policy becomes batched stablecoin settlement with judge-visible runtime proof and telemetry continuity.
Shortest reviewer path across live proof, V3 hardening, trust links, and launch boundary surfaces.
Generated reviewer-visible route into telemetry, hosted reads, runtime evidence, indexed governance, and the infrastructure value layer behind PrivateDAO.