We're boringly reliable
.svg){kind=logo}
Why We’re Different
We bring familiar, income-producing assets onchain. Each asset is tokenised, revenue-tracked & distributed transparently
We tie yield directly to real-world revenue. You can see how assets perform, how yield is generated, and where it comes from
DualMint is built for boring performance over long periods with yield generated from habitual usage
Why We Built This
What’s backing the yield?
Yield is backed by real operating revenue generated by the asset in use.
In the case of AirUp, this comes from verified electricity savings produced by installed controllers; for EcoWash, from completed wash cycles at operating sites.
Revenue is tracked at the asset level and distributed onchain after contractual allocations.
What happens if the business fails?
The operating business remains responsible for the asset under existing contracts.
If an operator fails or underperforms, contractual remedies may include operator replacement, asset redeployment, or continued operation under a new manager, depending on the asset structure.
Token holders are entitled to the cashflow generated by the asset itself, not the operator’s equity or balance sheet.
Can I exit early?
There is no fixed lock-up period.
Your position is represented by a tradable token that can be sold on the DualMint marketplace, subject to available liquidity and platform rules.
Exit timing and pricing depend on market demand, not on redemption promises.
How are payouts calculated?
Payouts are calculated from realised operating revenue.
For AirUp, this is the portion of electricity savings actually achieved and paid by the venue; for EcoWash, it is revenue from completed cycles.
After operating expenses and contractual splits, your share of net revenue is distributed in USDC, typically on the last business day of each month.
How do I verify the A/C unit exists?
Each asset includes verifiable proof of provenance, which may include installation records, IoT telemetry, operator attestations, and onchain references linked to the specific deployment.
Where applicable, assets also surface location data, operating history, and performance metrics to support verification.
