Skip to main content
PolyShield
POLYGON MAINNET · BETA
Docs menu · Getting started
Getting started
OverviewThe basicsQuickstartFAQ
Core concepts
The privacy modelZero-knowledge proofsSpending notesThe Merkle tree & nullifiers
Architecture
System overviewVault contractZK circuitsOff-chain services
Security
Threat modelTrust assumptionsBackup & recoveryFees
Reference
Glossary
GETTING STARTED

Overview

PolyShield is a zero-knowledge privacy vault for Polymarket, live on Polygon mainnet. It lets you bet on Polymarket without your wallet ever appearing on the trade — while keeping full, self-custodial control of your money.

Polymarket runs on a public order book. Every order, fill, and settlement is permanently on-chain and tied to the address that signed it. Anyone — an analytics firm, a counterparty, a journalist — can pull your wallet's entire betting history and net position. For most traders that linkage is the privacy problem.

PolyShield breaks the link. Many people deposit into one shared vault. The vault owns a single Polymarket account, and every bet is placed by that one account. On-chain, all bets look like they come from the same trader. Which depositor is actually behind any given bet is hidden by cryptography, not by a promise.

Wallet AWallet BWallet Cdepositorsdeposit USDCPolyShieldshared vaultVault EOAone signing keyPolymarketpublic order bookall bets, one identityobserversees only the EOA
Three people deposit from three wallets. Every bet they authorize is placed by the vault's single Polymarket account, so an on-chain observer sees one trader — never which depositor is behind a given bet.

What PolyShield hides — and what it doesn't

Hidden
which depositor authorized which bet, and your running position. This is the property the cryptography enforces.
Public
that some wallet deposited into the vault, and how much. A deposit is an ordinary ERC-20 transfer — visible by design.
The privacy boundary
Think of PolyShield as a members-only trading desk. The world can see you walked in the door (the deposit). It cannot see which trades on the desk's shared account are yours.

Everything privacy-sensitive — generating your note, building every proof — happens locally in your browser with WebAssembly. No secret ever leaves your device, and no PolyShield server can link a bet back to a depositor, even if it wanted to.