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.
Network & Contracts
Polypar's current reference deployment is on Polygon PoS (chain ID 137). It is a non-production, unaudited prototype. Do not deposit real funds while the configured treasury target is inactive.
Current deployment status
Last verified from the Polygon factory on July 28, 2026:
| Item | Address | Role and current status |
|---|---|---|
| ParlayVaultFactory | 0x9e98069175aA00bBAB139b1cBdA8bEf18b475635 | Creates offered parlay-vault clones and holds the current signer, treasury, collateral, CTF, and implementation settings. |
| ParlayVault implementation | 0x35e372Ba6d6D720bb8141C5cE2F1cEF9e7874578 | Reference implementation used by factory-created clones. Not audited. |
| Collateral: bridged USDC.e | 0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174 | ERC-20 token accepted for stakes and redemptions. |
| Conditional Tokens Framework | 0x4D97DCd97eC945f40cF65F87097ACe5EA0476045 | Immutable outcome source configured in the current factory and used when its vault clones resolve. |
| Price signer | 0x0cC5f6664b94314e8b6Df999DE1d7Cbe85fc4d46 | Authorizes short-lived vault-specific price quotes. |
| Configured treasury target | 0x6e315371478abF5D43321ccae3c4163dA9BB2400 | Inactive: no contract bytecode and no native-token balance were present when verified. It is not a live HouseTreasuryVault. |
What the inactive treasury means
A winning vault asks its configured treasury for any collateral shortfall. The current target cannot execute the expected treasury funding call because it has no contract code. Real-money betting and liquidity-provider deposits are therefore not operational in this deployment.
The intended HouseTreasuryVault would allow only owner-whitelisted callers to deposit or mint. The current app has no public /treasury UI. Those restrictions remain relevant even if a valid treasury contract is configured later.
Even after a valid treasury is configured, a vault pays from its actual USDC.e balance. If that balance is below nominal winning claims when the vault resolves, redemption is pro-rata; the displayed nominal payout is not assured.
Trust boundaries
The deployed contracts and surrounding application are a reference implementation, not an audited production system.
- Factory administrators can change the factory's treasury, price signer, and collateral settings. Check the live getters rather than assuming this page will remain current. The current factory's implementation and CTF addresses are immutable.
- A created clone stores its own legs and factory address. Administrative roles cannot rewrite those stored leg tuples.
- The quote service and price signer control which offered vaults receive executable entry prices.
- Settlement depends on the configured Polymarket Conditional Tokens contract and its underlying outcome resolution.
- Contract source, labels, frontend status, and operational controls have not received a claimed independent security audit.
Verify before any interaction
Check the factory getters and the treasury target's bytecode on Polygonscan immediately before interacting. Until a valid treasury contract is configured and the system receives an independent review, treat every screen as prototype documentation and do not deposit real funds.
Next: read Risks & Limitations for the complete risk model, or learn the intended LP design in Be the House.