2things the chain has to publish. Your position is not one of them.
An order book has to show you the other side of the trade. A pari-mutuel pool does not. Everyone stakes into one pot, the pot sets the odds, and the winners split what is left after takeout. The pot has to be public, because the pot is the odds. Who put what into it does not.
Hidden
- ·Who holds which position
- ·The amount of each position
- ·Payout amounts
- ·The links between your deposit, your stake, your claim and your withdrawal
Public by necessity
- ·The pool total on each outcome — the odds are the product
- ·Deposits into the shielded pool: the amount and the depositor are visible at deposit time
One honest limit, from the same spec: the RPC provider you read through can see which note addresses your client asks for. Self-hosted indexing is the answer for school instances, and decoy reads for everyone else.
Status: specified, not shipped. The private-position program is designed in specs/02-stub.md and the hooks exist in the on-chain program, but they refuse to run until it is deployed. Until then, points-tier stubs are ephemeral Discord replies — only you see them in chat, and the chain records a plain position. The roadmap says exactly where this sits.
Read how the privacy works