Seven things that would all have to fail before your capital is exposed

The question most yield products don't want you to ask is the first one worth asking: what happens when something goes wrong?

For DualMint, the answer is a specific sequence that would all have to fail before your capital is reached. Walking through it is more useful than any general claim about safety.

If the machine breaks

A broken machine is an operational event, not a capital one. When a machine goes offline for maintenance, the yield from that asset pauses. In the Boring Yield Index, that pause is absorbed across the pool — a single laundromat offline for a week doesn't determine whether you receive a distribution.

The Asset Performance Index scores every machine monthly. Declining utilisation, increasing downtime, deteriorating maintenance patterns show up in the score before a missed payment occurs. The model is built to catch operational decline before it becomes a financial event.

If the operator disappears

Most yield protocols underwrite the borrower. If the borrower defaults, recovery depends on collateral liquidation at whatever the market will bear at that moment. DualMint underwrites the machine.

The structural reason: coin-operated laundromats, commercial HVAC units, and robotic vertical farms generate revenue from location, equipment, and telemetry — not from who happens to be running them. Any qualified local operator can extract substantially similar cash flow from the same machine in the same location. The operator is swappable. The machine is not.

Why there is no pre-named backup operator

Most people assume there's a standby list — a pre-recruited replacement ready to step in. DualMint deliberately doesn't maintain one.

Pre-recruiting backup operators creates two structural problems. The first is adverse selection: the only operators willing to accept standby status are those without better deal flow, which is exactly the wrong pool to draw from. The second is that performing operators reasonably interpret a backup roster as distrust — damaging the relationship with the operators you actually want to keep.

Instead, redeployment runs through three independent channels designed to surface qualified replacements within 7–14 days of a default event. DualMint's operator acquisition pipeline notifies active multi-site operators when an asset becomes available. Regional equipment dealers — Speed Queen and Continental Girbau for laundromats, equivalent networks for HVAC — refer local operators at the moment of need, compensated via finder's fee and service contract retention. Industry associations across all three asset categories provide member distribution for available assets.

On top of those channels, every operator DualMint onboards identifies two to three local peers they would call if they had to walk away. That network intelligence costs nothing to maintain and is typically the fastest source of pre-vetted local replacements.

What the timeline looks like

A redeployment event runs 30–45 days from default trigger to full operational handoff. The revenue gap during that period is absorbed by the vault's liquidity buffer. A redeployment event reduces, but does not eliminate, the affected month's distribution.

The costs of stepping in — legal execution, logistics, and a working capital bridge for the transition — are covered by the 10% origination fee operators pay at asset entry. That buffer was sized to cover transition costs without touching LP capital.

The layers underneath operator failure

Operator failure is layer five. Capital doesn't reach it without passing through four earlier stages first.

• Operator cash flows are intercepted before vault losses emerge — they don't get paid until the machine's obligations are met.
• Operators post 1–10% first-loss capital at origination, absorbing underperformance before vault depositors are reached.
• Assets are originated at 10% overcollateralisation, providing a further buffer.
• The vault holds 20–70% of TVL in liquid reserves, handling redemptions without forced asset sales.

If the asset needs reassignment after all of that, the redeployment process above runs. Beyond it: Nexus Mutual insurance, and Mystic Finance as a last-line backstop.

The honest position

Twelve consecutive months of marketplace distributions. Zero operator defaults across the full portfolio. None of those layers has been triggered. The redeployment channels and timelines above are based on simulated exercises, not live default experience. DualMint has committed to publishing the first live case study within 30 days of the first operator default event.

The vault isn't live yet, which means the waterfall is structural but untested at vault scale. What has been tested: the machines ran, the telemetry verified the revenue, the distributions released on schedule, and no operator failed across 12 months of live operation. The vault inherits that infrastructure. The gap between structural and proven is worth knowing before depositing.