Technology
Four layers, one source of truth.
369X is built in four layers: a user layer (the app and your wallet), a smart-contract layer on BNB Smart Chain that holds funds and settles markets, a resolution layer that decides outcomes with bonds, and a data layer that only caches what the chain already records.
The stack, top to bottom
Only one layer can move money. The rest can fail and be rebuilt.
- L1
User layer
Web app · any Web3 wallet (MetaMask, Trust Wallet, WalletConnect, Coinbase Wallet) · RPC fallback list · planned iOS and Android apps
- L2
Smart-contract layer · BNB Smart Chain
PredictMarketLMSR · FeeVault · LeverageVault · LPVault · one BetProxy per leveraged position
- L3
Resolution layer
Bonded proposal → 48-hour dispute window → finalise · whitelisted resolvers · planned automated feeds for sports and crypto · staked-$369X voting after token launch
- L4
Data layer
Event-streaming indexer → database cache for charts and leaderboards. A speed layer only: every view can be rebuilt from on-chain events.
Why BNB Smart Chain?
Three practical reasons. Gas is typically under a cent, which matters when the minimum trade is $1. Blocks are fast, so a trade confirms in seconds. And it has one of the largest bases of active wallets, including a growing set of prediction-market users. Additional EVM chains are planned for the 6–12 month window.
The contracts and what each does
PredictMarketLMSRCore markets: prices outcome shares with the LMSR, handles buys, sells, resolution and claims.FeeVaultCollects the protocol share of fees and, after token launch, funds buybacks.LeverageVaultOpens and manages 2× to 10× outcome positions.LPVaultHolds LP deposits that back market making and leverage lending.BetProxyOne per leveraged position, keeping each position's collateral isolated.
Until contract addresses appear on this site, treat any address claiming to be a 369X contract as fake.
An immutable core
The core contracts are designed with no proxy and no admin upgrade key. An upgrade means deploying new contracts; markets created on the old ones keep resolving under their original rules. That trades flexibility for predictability: the rules you traded under can’t be changed underneath you, but bugs can’t be patched in place either, which is why the audit comes first.
Why the indexer is a cache, not an oracle
Charts and leaderboards need fast queries, so an event-streaming indexer copies on-chain events into a database. It never decides an outcome, holds funds or feeds data back into the contracts. If it breaks or disagrees with the chain, the chain wins and every view can be rebuilt from on-chain events.
LMSR in one paragraph
Each market’s prices come from the Logarithmic Market Scoring Rule, a formula by economist Robin Hanson. Prices stay between 0 and 1, YES and NO sum to 1, and each purchase nudges its own side’s price up. A liquidity parameter, b, sets how far a trade moves the price; the 0.4% depth fee raises b over time so busy markets get deeper.
Show the maths
Cost C(q) = b · ln(e^(q_yes/b) + e^(q_no/b))
Price of YES = e^(q_yes/b) / (e^(q_yes/b) + e^(q_no/b))
Buying Δ YES shares costs C(q_yes + Δ, q_no) − C(q_yes, q_no)
The market maker’s maximum loss on a binary market under this model is b × ln 2, about 0.693 × b. That bound covers market making only. It does not cover leverage lending, contract bugs or a wrong oracle outcome, and changing b mid-market needs separate funding.
Built for speed where it’s safe
- Batched reads fetch many positions in one call.
- A near-real-time feed updates odds in the app.
- Fixed-point maths in the LMSR contract is written to avoid overflow.
- An RPC fallback list keeps the app usable when one node provider is down.