Polymarket
Vaults
Infrastructure.
Vault rails for partners shipping Polymarket products. Closed-end ERC-4626 vaults, a self-custodied smart wallet, and TEE-enforced custody — packaged as a managed white-label, an SDK, an embeddable widget, or a co-managed deployment. Your brand, your users, our rails.
A product your users want.
Without the build.
Prediction markets are an asset class your users would allocate to — if your product offered it. Integrate the vault rails instead of building them. Ship the product instead.
Your users want exposure
Polymarket is the largest prediction-market venue in crypto. Deterministic settlement, persistent mispricing, uncorrelated returns. Your users would allocate — if you offered the wrapper.
The wrapper is the hard part
Capturing the alpha requires a 24/7 operation, but offering it to users requires a custody-grade vault, an ERC-4626 share model, fund-style cycles, and an audit trail. That stack doesn’t exist off the shelf.
You don’t want to build it
Smart-wallet factory, TEE custody, vault contracts, cycle ops, terminal liquidation logic — months of audit and integration before your first deposit. We already did that work.
The stack between
your product and Polymarket.
Without our rails, every partner re-builds the same custody, factory, vault, and cycle logic — and re-audits all of it before accepting the first deposit.
- 01Polymarket’s deposit wallets ship from a third-party factory you don’t control
- 02Outcome tokens are ERC-1155 — they don’t fit your existing share or NAV reporting
- 03No native on-chain redemption mechanism — you’d build the share model yourself
- 04Cycle ops, terminal liquidation, and pro-rata payout logic are non-trivial to audit
- 05TEE-enforced policy custody, factory, and pause/sweep timelock are months of work
Three components.
One vault stack.
Vault infrastructure for partners building on Polymarket. Standards-native, self-custodied, defense-in-depth.
Closed-end ERC-4626 vaults
Standard tokenized-vault shares your product can wrap, report on, and surface in any portfolio tracker. Each vault is one fixed-term cycle — deposit, lockup, terminal liquidation, redeem.
- Plug-and-play with portfolio trackers and aggregators
- On-chain accounting, no integration work
- Deterministic deposit and redemption windows
- Composable with the rest of DeFi on day one
Self-custodied smart wallet
Each cycle deploys a fresh wallet contract from our own factory. We wrote it. We audited it. We control its upgrade path. Polymarket cannot upgrade, brick, or recover wallets your users deposit into.
- Independent factory — not Polymarket-controlled
- Fresh keypair per cycle, blast-radius contained
- Cold-key pause-and-sweep recovery built in
- Upgrade path governed by us, not the venue
Policy-enforced custody
Keys live inside Turnkey’s TEE. Cold owner keys require an N-of-M approver quorum to sign. Hot operator keys are scoped, rate-limited, and time-bounded — enforced inside the TEE, not in our application code.
- TEE-enforced policy, not app-layer guards
- N-of-M quorum for cold-key signatures
- Domain-locked, rate-limited hot operators
- Compromise of one layer contained by the next
Four surfaces.
One stack.
Same vault rails underneath. Pick what matches your team, your distribution, and how much ops you want to run yourself.
Managed white-label
We run cycle ops, custody, and strategy. You ship a branded vault product to your users — landing pages, deposit flow, dashboards, and statements under your name on your domain.
- Branded UI on your subdomain
- We operate cycles end-to-end
- Partner share of fees per contract
- Fastest path: weeks to first deposit
SDK and REST/WSS APIs
Integrate the vault, factory, and custody contracts directly. You drive deposit and redemption flows from your app, run your own strategy, and use our infra for the audited rails underneath.
- TypeScript SDK + REST + WSS
- BYO strategy and ops, our rails
- Webhooks for deposits, NAV, settlement
- Full programmatic surface
Embeddable widget
A drop-in deposit / redeem widget for your app. Iframe or React component — themed to match your brand. Best when you want the vault visible inside an existing product without building the UI.
- iframe + React component options
- Themeable to match your brand
- Handles deposit, redeem, statements
- Days to integrate
Co-managed deployment
Split responsibility. We provide custody, the smart wallet, and the vault rails. You provide the strategy and the LP relationship. Cleanest fit for trading firms with alpha but no LP wrapper.
- Custody and vault rails by us
- Strategy and LP relationship by you
- Operator keys scoped to your domain
- Branded vault, your fund structure
One cycle.
Six checkpoints.
Closed-end by design. Because cycles overlap, your users are never more than a few weeks away from the next entry window.
Deposit window opens
A new cycle opens on your branded surface. Typically 1–2 weeks.
Users deposit pUSD
Your users send pUSD to the vault contract. They receive ERC-4626 shares at 1:1.
Capital deploys
Window closes. Fresh wallet, fresh keypair, scoped operator. Strategy starts.
Cycle runs
Typical term is 4–8 weeks, configurable per vault you ship.
Terminal liquidation
All positions liquidate to pUSD. Terminal NAV is fixed and on-chain.
Pro-rata redemption
Users burn shares for pUSD. No queue, no liquidation discount, no operator discretion.
A few calls.
A live vault product.
Deploy a cycle, route deposits, listen for settlement events. The SDK wraps the factory, vault, and custody contracts so your app doesn't touch any of the underlying complexity. Use the embed widget if you don't want to build the deposit UI at all.
Run multiple partner-branded vaults in parallel. Each cycle is isolated — keypair, contracts, operator scope, fees.
Deposit confirmations, NAV updates, terminal settlement, and redemption events stream to your backend over WSS or webhooks.
Partner / operator / platform fee shares enforced at the contract level. No off-chain reconciliation.
Per-cycle trade history, fills, P&L, and terminal NAV — query via API or render in your dashboard.
import { VaultEngine } from '@gizmolab/polymarket-vaults';
const vaults = new VaultEngine({
partnerId: 'your-org',
brand: 'your-brand'
});
// Deploy a cycle under your brand
vaults.deployCycle({
asset: 'pUSD',
termWeeks: 6,
strategy: 'managed', // or 'byo'
fees: { partnerBps: 100 }
});
// Stream settlement events to your backend
vaults.on('cycle.settled', (e) => yourBackend.record(e));Three layers.
All must fail.
Independent security boundaries — policy, on-chain timelock, and cycle isolation. A single compromised layer is contained by the next. The story you tell your users, on day one.
Independence.
Standards. Transparency.
No upstream dependency
Our wallet contract has no dependency on Polymarket’s factory or whitelist. Only our governance can authorize upgrades. Polymarket cannot upgrade, brick, or recover wallets your users deposit into.
- Own wallet factory, audited in-house
- No third-party upgrade path
- Polymarket-agnostic at the custody layer
- Cold-key recovery without cooperation
ERC-4626 on day one
Standard tokenized-vault shares. Every existing piece of DeFi tooling — portfolio trackers, allocator strategies, on-chain accounting — works with your branded vault without integration work.
- ERC-4626-compliant deposit and redeem
- Composable with aggregators and trackers
- Standard event surface for accounting
- Plug-and-play with allocator workflows
On-chain track record
Every deposit, deployment, trade settlement, and terminal liquidation is publicly verifiable. Track record is reconcilable to the cent — the proof your users will ask for.
- Every cycle’s trade history on-chain
- Terminal NAV fixed, no operator discretion
- Pro-rata redemption, atomic
- Independent audit before mainnet
Venues.
Apps. Firms. Studios.
Built for partners shipping a Polymarket-shaped product to their users — without standing up the custody, factory, and vault stack themselves.
- Prediction-market platforms & venuesAdd a tokenized vault product to your venue. Branded surface, our rails, on-chain transparency for your users.
- Trading firms & strategy desksYou have alpha. You don’t have a fund admin, share class, or LP-facing custody stack. Use our rails, keep the strategy.
- Crypto fintechs & wallet appsDrop in an embeddable vault widget. Give your users a yield-shaped Polymarket product without rewriting your app.
- White-label studios & launchpadsPackage and resell branded vault products to your operator network. Multi-tenant by default, fee splits on-chain.
What you save
by not building it.
The ones partners ask.
Whose brand is on the product end-users see?
Yours. White-label, SDK, embed, and co-managed deployments all surface under your brand on your domain or inside your app. We are the infrastructure layer — invisible to end users unless you choose to disclose us.
Who owns the LP relationship and customer data?
You do. Partners own KYC, onboarding, and the LP relationship. We provide vault contracts, custody, and reporting APIs. End-user identifiers stay in your stack.
How do fee splits work?
Enforced on-chain at the vault contract level. Standard split is partner / operator / platform; the exact basis points are configurable per cycle. No off-chain reconciliation, no trust assumption between parties.
Managed vs BYO strategy — which surfaces support which?
White-label is managed by default (we run the strategy). SDK + APIs and Co-managed are BYO strategy — you operate the trading, we provide the custody and vault rails. Embed widget works with either, depending on which vault it points at.
Multi-tenant — can we run multiple branded vaults in parallel?
Yes. Each cycle is fully isolated: its own keypair, smart wallet, operator scope, and fee split. A partner can run many concurrent vaults; a studio can run many partners. Cycle isolation is also a security boundary — a compromised cycle never touches another.
What integration time should we plan for?
Embed widget: days. SDK + APIs: 1–2 weeks for a working integration. White-label: weeks to first deposit including branding and content. Co-managed: depends on your strategy and ops readiness — typically 2–4 weeks.
How is your custody different from Polymarket’s wallets?
Polymarket-issued wallets ship from a third-party factory whose upgrade path is controlled by Polymarket. Our smart wallet is deployed from our own factory and audited in-house, so the venue cannot upgrade, brick, or recover wallets your users deposit into. The trading interface is the only Polymarket dependency.
Why closed-end instead of an evergreen vault?
Prediction-market alpha realizes at market resolution. A closed-end design lets the strategy hold to resolution rather than be force-liquidated by intra-cycle redemptions. The shape matches the asset class.
Regulatory?
Closed-end fund structures have decades of legal precedent. Each deployment is structured per jurisdiction with appropriate counsel — usually yours. We can introduce counsel we have worked with previously.
What chains?
Polygon, where Polymarket settles. Vaults accept pUSD, Polymarket’s native collateral. Bridging from any major chain is supported via Polymarket’s bridge.
Pricing?
Usage-based at the vault and custody layer with volume discounts; partner economics depend on which surface you pick (white-label vs SDK vs co-managed) and the fee split you configure. Speak to us about your model.
Built to plug into the rest of the stack.
Ship A Vault
Under Your Brand.
White-label, SDK, embed, or co-managed — same rails underneath. Tell us your distribution and how much ops you want to run; we will pick the right surface.