RISKS & MITIGATIONS

This section lists the primary risks for a stablecoin routing layer. It also lists the practical mitigations we can ship and operate.

Technical risks

Bridge protocol exploits

Risk:

• A bridged route uses a protocol that gets exploited.

• Users may lose funds during the bridge operation.

Mitigations:

• Integrate only audited and battle-tested bridges.

• Diversify routes across multiple bridges.

• Continuous health monitoring (failure rate spikes, delayed finality, downtime).

• Kill-switch: disable a bridge integration quickly.

• Optional: maintain an insurance or user-compensation policy later.

API downtime and degraded performance

Risk:

• If the routing backend is down, quotes fail.

• If monitoring fails, users lose trust fast.

Mitigations:

• Multi-instance deployment with health checks.

• Graceful degradation: cached quotes for supported pairs when possible.

• Database backups and restore runbooks.

• Alerting with clear on-call ownership.

• Public status page once we have meaningful traffic.

Incorrect routing (bad quotes or wrong path)

Risk:

• The route engine picks a path that is cheaper on paper but fails more often.

• Users pay more than expected or get stuck in a failing route.

Mitigations:

• Test suite with replayed historical quotes and outcomes.

• Sandbox mode for new bridge integrations.

• Guardrails: minimum reliability threshold per route.

• Show alternatives and allow user override (UI) for edge cases.

• Tight feedback loop: adjust weights using real completion data.

Market risks

Low adoption

Risk:

• Users and devs don’t switch because existing solutions are “good enough”.

Mitigations:

• Start with the consumer UI to prove demand before scaling the API.

• Focus on underserved use cases: remittances, payroll, commerce, small transfers.

• Transparent pricing and clear receipts (fee + gas + net received).

• Ship integration examples early (simple API + webhooks).

Bridge protocols ship competing UIs

Risk:

• A protocol adds a consumer UI and tries to own distribution.

Mitigations:

• Aggregation moat: always show best option across multiple protocols.

• Developer API + support + docs are harder to replicate than a UI.

• Protocol competition can still benefit YardRoute users via lower underlying costs.

Regulatory risks

Money transmitter classification

Risk:

• Regulators may treat some routing/aggregation flows as money transmission.

Mitigations:

• Non-custodial design (no deposits to YardRoute-controlled addresses).

• Document the flow clearly: users interact with bridge contracts directly.

• Obtain a legal memo for target jurisdictions before scaling.

• If needed: partner with licensed entities for parts of the stack (e.g., fiat ramps).

Stablecoin rules + KYC/AML pressure

Risk:

• Stablecoin regulations may require KYC/AML in certain markets or flows.

Mitigations:

• Add optional compliance hooks for enterprise integrators.

• Geo-blocking for restricted jurisdictions if required.

• Prefer regulated issuers where appropriate (e.g., USDC) for specific customers.

This list is intentionally short. We can expand it later into an “Operational readiness” checklist once the product ships.