Non-production prototype
These contracts are unaudited. The configured treasury currently has no contract code, so real-money betting and LP deposits are not operational. Do not deposit; check the current deployment status before any interaction.
Payouts & Margin
The interface's nominal potential payout is:
stake × lockedMultiplier
The locked multiplier comes from the quote's combined probability after the vault applies primeBps and minSharePrice. The deposit mints vault shares with integer division, so the exact base-unit claim can be slightly lower than a decimal display.
No separate protocol-fee transfer
Polypar does not transfer a separate protocol fee during depositWithQuote. The economic margin is embedded in the higher entry price and therefore the lower number of shares minted for a stake. Polygon gas is separate and is not part of the vault payout.
primeBps is not proof of a profitable house strategy. Market movement, stale or incorrect prices, correlation, bettor selection, operational failures, and outcome distribution can outweigh that margin.
Loss outcome
If any selected leg receives a resolved CTF payout other than the complete selected outcome, the vault becomes Lost. Its USDC.e balance goes to the configured treasury, and its shares redeem for zero.
Win outcome and shortfall
If every selected leg settles to the complete selected outcome, the vault becomes Won. During that same resolve() call it compares:
- the vault's actual USDC.e balance; and
- its total outstanding share supply, which represents nominal winning claims.
If shares exceed the balance, the vault asks the factory to fund the difference from the configured treasury. The intended HouseTreasuryVault supplies no more than its current balance.
Redemption is then always pro-rata over what the parlay vault actually holds:
user assets = user shares / total shares × current vault balance
Nominal is not assured
If treasury funding is short, every winning shareholder receives the same proportional shortfall. Once a partially funded win resolves, the current contract has no automatic later top-up path; sending more money to the treasury later does not cause that resolved vault to ask again.
The current configured treasury has no contract code, so the expected shortfall call cannot operate as designed. Do not deposit real funds; verify Network & Contracts.
Next: follow the explicit state and wallet actions in Resolve & Redeem, then assess shortfall and pricing risk in Risks & Limitations.