Understand the assumptions.
A working transaction path is a starting point. Public capital requires stronger mathematical, economic, and operational evidence.
Current assurance level
The application exposes real reserve accounting and explicit wallet transactions. It does not establish that a covered-call-like strategy is profitable, that all market conditions have been simulated, or that stock-token issuer and administrative powers cannot affect your holdings.
Risk register
| Risk | Effect | Required work |
|---|---|---|
| Market and inventory | LPs remain exposed to stock declines and adverse reserve changes. | Publish scenarios and actual reserve accounting. |
| Replication error | Discrete trading can diverge from the benchmark. | Independent event-driven simulations with trading frictions. |
| Numerical implementation | Approximation or rounding flaws can misprice swaps or leak value. | Proven bounds, high-precision differential tests, adversarial round trips. |
| Issuer and token | Freezes, rebases, transfer rules, or changed economic rights can impair exits. | Verify exact token code, powers, decimals, and corporate-action units. |
| USDG | Depeg, issuer restrictions, or redemption limits affect inventory value. | Document denomination and conversion assumptions. |
| Reference data | Stale or incorrect prices can block or misguard trades. | Authenticated production sources and explicit freshness policies. |
| Chain and execution | Outages, reorgs, MEV, and delayed inclusion affect transactions. | Chain-specific review, bounds, deadlines, monitoring. |
| Administration | Compromised status authority can disrupt new risk. | Least privilege, documented powers, operational controls. |
Ownership properties to preserve
- Keep LP inventory separate from protocol-fee liabilities, direct donations, and any future staking funds.
- Never use oracle failure, pause, or expiry as permission to confiscate reserves.
- Keep direct proportional withdrawal independent of keepers, indexers, and reward funding.
- Reject unsupported token transfer behavior atomically rather than recording assumed balances.
- Keep existing pool economics immutable and require explicit user action for rollover.
- Do not derive staking rewards or fee revenue from LP principal, multiplier changes, or model theta.
Numerical gate
The full specification requires conservative error analysis over every approved reserve, time, volatility, strike, and decimal range. It targets no more than two smallest output-token units of absolute rounding error in differential tests and rejects a quote if numerical uncertainty exceeds its stated budget. These are acceptance targets, not completed certifications.
A tolerance that passes a single trade can still be harvested over many round trips. Test repeated small trades, signed offsets, expiry proximity, maximum reserves, unsupported transfers, and combinations of minting, swapping, and burning.
Economic and public-release gate
- Run reproducible event-driven simulations with external arbitrage, spreads, gas, finite liquidity, delay, and the exact USDG-side fee rule.
- Include volatility mismatch, earnings gaps, closures, missing arbitrage, depegs, data outages, and corporate actions.
- Attribute value changes to inventory movement, actual trades, actual fees, rounding, and model error.
- Evaluate the specification's predeclared baseline replication thresholds; publish stress losses without inventing a profit floor.
- Obtain independent review of the math, reserve accounting, token units, administration, and simulation methodology.
- Verify production token and data interfaces before a capped pilot with published addresses and limits.
VANTA staking comes after the core protocol and a verified fee-collection cycle. It is not an insurance layer and does not repair LP losses. Token emissions do not substitute for evidence of genuine trading revenue.
Reporting a problem
Document the affected source, transaction hash or reproduction steps, selected network and deployment, expected behavior, and observed result in the project's development workflow. Do not include private keys or unrelated personal data. No external bug-bounty program or security contact is represented as established by this repository. A public beta operator must publish its support and incident-reporting channel before inviting users.