Trust model
Unlinkable, not invisible.
Offbook hides who owns a bet, not the bet itself. This page lists everything that stays public, everything that stays private, and every party you are trusting. Nothing here is hidden in small print.
The short version
What anyone can see, and what they can’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.
Positions are public on Polymarket. Every Offbook bet is an ordinary Polymarket position. Its market, outcome, size, price and the betting wallet’s address are on the public order book and on Polygon.
Deposits and withdrawals are visible at each end. Money entering Offbook is visible on the chain it came from, and money leaving is visible on the chain it arrives at. What happens in between, inside NEAR’s confidential layer, is not.
Bets can be identified as Offbook bets. Polymarket records a builder code on every order, and it appears in the public fill events on Polygon. Anyone can tell a bet came through Offbook. They can’t tell whose it is.
Trust assumptions
Who you are trusting.
NEAR’s confidential layer
Your private balance and the transfers inside it are shielded by NEAR Confidential Intents, which runs on a private chain operated by an approved set of validators and settles back to public NEAR.
RiskIf those validators leaked or colluded, transfers inside the private layer could be linked.
The Chain Signatures network
Betting wallets are controlled by NEAR’s multi-party signing network. Each signature needs a threshold of independent nodes; no single node holds a whole key.
RiskIf enough nodes colluded, they could sign for betting wallets. The vault contract’s rules would not stop them.
Secure hardware (TEE)
The Offbook Agent runs inside a trusted execution environment and proves, through remote attestation, exactly which code it is running. The vault only accepts approved code.
RiskHardware flaws or side-channel attacks could expose data the agent handles while serving a request. The Shade Agent framework that runs the agent has not yet had a formal audit.
The vault contract
Public rules on NEAR: allowlisted Polymarket contracts only, per-wallet exposure caps, nonces, expiry. Rule changes wait behind a public 14-day timelock, and the contract can be locked permanently.
RiskA bug in the contract could allow something the rules were meant to prevent. It has had an independent security audit, which reduces that risk but can’t rule it out.
Offbook, the operator
Runs the website, the agent and the servers. Can pause the system for up to 72 hours. Cannot move user funds, and cannot see which wallets are yours outside the agent’s secure hardware.
RiskAn operator could stop serving requests. Your private balance stays withdrawable through any NEAR Intents interface, and positions wait for an approved agent.
Polymarket
Runs the order book and matching engine. It sees Offbook’s servers submitting orders for many wallets, not you.
RiskPolymarket can see that orders come from Offbook, and could refuse to serve them.
Data
What Offbook stores, and what it never does.
- Cached public market data from Polymarket
- Aggregate, anonymous statistics (daily totals and size buckets)
- A minimal eligibility record: the day, region code, Terms version and a keyed hash of your account (never the account itself). Nothing that links to a wallet.
- Inside the agent’s secure hardware only, never readable by Offbook’s servers: a 31-day tally of your deposits, bets and returns (times and amounts, no wallets or markets), used only to enforce the limits you set, and the in-flight instructions for your bets while they run.
- Your secret or your betting-wallet paths
- Any link between you and your betting wallets
- Your positions, or which markets you bet on
- Polymarket API credentials (sealed inside the agent’s secure hardware)
- IP addresses, or anything tying a session to a wallet
- Third-party trackers, pixels or session replay. Analytics are self-hosted and aggregate-only.
Known limits
Where privacy can still leak.
- Timing and amount analysis. Standard amounts and randomized waits make matching hard, not impossible. Fast mode is easier to match; the privacy meter says so before you confirm.
- Small crowds. Privacy comes from blending in with other withdrawals of the same size at the same time. All NEAR Intents withdrawals to Polygon come from one shared bridge contract, so the sender reveals nothing, but at quiet times there are only a few withdrawals an hour. When the crowd is small, the meter says so, and Private mode or a prepared wallet helps most.
- Your own behavior. Announcing a bet, depositing an unusual amount right before a bet, or withdrawing winnings straight to a wallet everyone knows is yours can undo the protection.
- Very large positions. Each betting wallet is capped at 25,000 USD while Offbook operates it. Large, unusual trades stand out on the order book no matter who places them.
- Offbook attribution. Because the builder code is public, Offbook’s total activity on a market is visible.
Resilience
If Offbook goes offline.
Your private balance is your own NEAR Intents account, so you can withdraw it through any NEAR Intents interface without Offbook. Open positions stay on Polymarket, held by their betting wallets. Those wallets can only be operated by an approved agent, so selling or redeeming waits until an agent is running again. A replacement agent build can be approved through the vault’s public 14-day timelock. Market resolution doesn’t depend on Offbook.
Verification
Audit status.
Independently audited
The vault contract and agent have had an independent security audit. The report will be published here. The approved agent code hash and contract addresses are on the Stats page.