Liquidity & safety

PolyPort treats capital stewardship as a first-class feature. This overview explains the safety rails that operate behind the scenes so campaign leads and LP seeders can stay confident throughout the market lifecycle.

Vault structure

• Activation vault – Holds deposits until the threshold is met. Depositors receive “pending” tokens; if the market misses its cutoff or is closed, they can burn those pending tokens via the refund action to reclaim their stake.
• Trading pool – Once live, fees and payouts flow through a managed pool that tracks every movement in Supabase for real-time dashboards.
• Meteora mirror – For markets that opt-in, a portion of vault liquidity is mirrored into Meteora to capture partner fees and deeper order books.

Automatic safeguards

1. Activation timers – Campaigns include a cutoff window. Once it passes (and while the market is still pending), supporters can use the “Refund” action (calls refund_pending) to withdraw their pending stake.
2. Rebalance checks – Background workers compare PolyPort vault balances with Meteora positions. If the delta exceeds 5% or a settlement window is approaching, the system tops up or withdraws to stay aligned.
3. Risk review – Every major campaign triggers an ops checklist (documented in docs/ops/meteora-risk-review.md) before mirroring any funds.
4. Audit trails – All movements (claims, sweeps, rebalances) are recorded in docs/reference/meteora-devnet-log.md and surfaced in the dashboard.

When the team steps in

• Large divergence – If the system flags >5% imbalance repeatedly, ops receives an alert and can pause new trades while rebalancing manually.
• Data anomalies – Bad oracle data triggers a temporary circuit breaker. Support will notify campaign leads with next steps.
• Settlement disputes – In rare cases, admins can escalate to the governance council. Documentation and timelines are shared with all stakeholders.

Transparency tools

• Ops dashboard – Shows upcoming settlements, recent Meteora actions, and any paused markets.
• Devnet scripts – create-test-pool.ts and force-divergence.ts (available to partners upon request) demonstrate how we stress-test mirrored pools.
• Risk reviews – Ops publishes a go/no-go summary for every major launch. Request the latest report via your PolyPort contact.

Need a quick summary for stakeholders? Email ops@polyport.app for a custom briefing.