Protocol
How Offbook works, and every address it uses.
Your private balance on NEAR Intents, the attested agent, the vault contract and the fresh wallets that trade on Polymarket: what each does, and where to check it.
The four parts
Offbook is a privacy layer for Polymarket, built on NEAR. Your money and your bets live in different places, and nothing public connects them.
NEAR Intents
Private balance
Your money sits in your own NEAR Intents account in confidential mode, as USDC. Your wallet or passkey controls it, not Offbook, and moves inside it are shielded.
Secure hardware
Agent
Plans and places bets inside an Intel TDX confidential machine on Phala Cloud. Your browser checks it against the vault before sending anything. It keeps a bet’s instructions only while the bet runs, and never which wallets are yours.
NEAR contract
Vault
Controls every betting wallet through NEAR Chain Signatures. It signs only what its public allowlists permit, and only for agent code it has approved.
Polygon
Betting wallets
Each bet gets a fresh Polymarket wallet. Its address comes from a secret only your wallet can produce, so nobody can work out which wallets are yours.
A bet, start to finish
Deposit
Any chain → NEAR IntentsYou pay from a wallet or send to a one-time address. NEAR Intents converts it to USDC on Base and credits your confidential account. The deposit is public on the chain you send it from.
Confirm a bet
Your browser → the agentYour browser derives a fresh wallet path from your secret, which your wallet’s signature created when you signed in, and sends the request to the agent end-to-end encrypted.
Funding
NEAR Intents → Base → PolygonYour private balance pays the new wallet in standard amounts: a NEAR Intents withdrawal of USDC on Base to the wallet’s Polymarket bridge address. Polymarket’s bridge turns it into pUSD on Polygon.
Wallet setup
PolygonPolymarket’s relayer deploys the wallet and runs one batch of approvals, each of them on the vault’s allowlist.
The order
NEAR → PolymarketThe agent builds the order with Offbook’s builder code. The vault checks it against its rules, NEAR’s MPC network signs it, and it goes to Polymarket’s order book like any other order.
Coming back
Polygon → Base → NEAR IntentsWhen you sell or the market resolves, the wallet sends the proceeds through Polymarket’s bridge to one-time NEAR Intents addresses, split into standard amounts at randomized times, and they land in your private balance.
Withdraw
NEAR Intents → any chainBet again, or withdraw to any supported chain. The arrival there is public.
Privacy levels
Every level places the bet the same way. They differ only in how long the agent waits before the order and how many chunks the funding is split into.
| Privacy level | Randomized wait | Funding chunks |
|---|---|---|
| Privatedefault | none | up to 1 |
| Very private | 1 to 3 min | up to 2 |
| Max private | 3 to 10 min | up to 4 |
Wallets are always funded in standard amounts (10, 25, 50, 100, 250, 500, 1,000, 2,500, 5,000 USDC), never your exact bet size, and what a bet doesn’t use comes back. Returns go back to your private balance at randomized times, 1 to 10 minutes after they’re ready.
With no wait, the funding and the order are easier to match by timing. Very private and Max private add a randomized wait.
What’s public and what isn’t
- The bet itselfPublicPublicMarket, outcome, size and price are on Polymarket’s public order book and on-chain, like every other trade.
- The betting wallet’s addressPublicPublicAnyone can see it. It’s a fresh Polygon wallet with no history and no link to you.
- That the wallet belongs to youPrivatePrivateWallets are derived from a secret only you hold, and funded from your private balance with shaped timing and amounts.
- That the bet went through OffbookVisible as OffbookVisible as OffbookPolymarket records Offbook’s builder code on every fill, so a bet can be recognized as an Offbook bet. Not whose it is.
- Your deposit into OffbookPublicPublicVisible on the chain you send it from, like any transfer.
- Your private balancePrivatePrivateHeld in your own NEAR Confidential Intents account. Moves inside it are shielded.
- Your withdrawal to another chainPublicPublicThe arrival is visible on the destination chain.
- Your activity historyPrivatePrivateFetched live for your session and never stored on Offbook’s servers.
Addresses
Everything Offbook relies on, with links to check it. There’s no fixed deposit address: NEAR Intents issues a new one for every deposit and return, and Polymarket’s bridge one per betting wallet.
NEAR Intents
Verifier contract
NEAR Intents’ core contract. Every intent you sign, such as a withdrawal, names it as the contract that verifies it.
Private balance asset
USDC on Base as NEAR Intents holds it. Every private balance is kept in this token.
1Click API
Quotes, one-time deposit addresses and confidential transfers. Offbook’s servers call it; your browser never does.
1click.chaindefuser.comLook it up
NEAR Intents’ own explorer and documentation.
Offbook on NEAR
Live from the vaultVault contract
Controls every betting wallet. NEAR mainnet.
- RunningTEE requiredUpgradeable by governance
Governance
Approves agent builds and sets the vault’s rules through public proposals, which take effect as soon as they’re executed.
Guardian
Can pause the vault. A pause ends on its own after 72 hours and can never move funds. The same account as governance.
Chain Signatures signer
NEAR’s MPC network. It signs for betting wallets only when the vault asks.
Agent
Runs in an Intel TDX confidential machine on Phala Cloud. The vault registers an agent only if its attestation matches an approved build.
No agent registered · 13 approved builds
bfb110875c6d1b42c26bf357c6ff7fbd79fe4ffb27c76e287bfd00d6f1c3410cThe deployed build’s code hash. Stats lists every approved one.
Limits
Enforced by the vault on every signature.
- Each betting wallet can send out at most $25,000 in any 24 hours.
- Every signing request expires within 10 minutes.
Polymarket on Polygon
Polymarket’s contracts, as the vault’s allowlists name them. Betting wallets can’t call anything else, on Polygon. Offbook is independent of Polymarket.
Contracts betting wallets may call
pUSD
Polymarket’s collateral: what bets are paid in.
May call
approvetransferConditional Tokens
Holds outcome shares (ERC-1155).
May call
setApprovalForAllCTF collateral adapter
Redeems resolved positions on standard markets.
May call
redeemPositions
Spenders they may approve
CTF Exchange
Polymarket’s exchange contract. Orders on standard markets are signed for it.
Neg Risk CTF Exchange
Polymarket’s exchange for neg-risk markets, where only one outcome can win.
CTF collateral adapter
Redeems resolved positions on standard markets.
Neg-risk CTF collateral adapter
Redeems resolved positions on neg-risk markets.
Orders
Builder code
Every order must carry it, so fills show as Offbook orders. Not whose they are.
0xdb584ddd88b97aef978bd8b14e71ab667d09e965d3bb3ac0e223660988760654
Verify it yourself
Your browser doesn’t take Offbook’s word for any of this. Before it sends the agent anything, it reads the vault over NEAR RPC and checks that the key it’s about to use was published by an agent the vault registered, which the vault does only for approved builds.
Anyone can call the same views on offbook-vault.near:
get_status: governance, guardian, MPC signer, pause, timelock, lockget_code_hashes: the agent builds it approvesget_agents: the registered agents and their channel keysget_allowlists: the contracts, spenders and order domains aboveget_caps: the per-wallet limits