Docs

1. Architecture

SSC uses a hybrid architecture. The user frontend handles browsing, login, wallet signatures, deposits, withdrawals, betting forms, account display, and internationalization. The backend handles market data, bets, balances, ledger, referrals, settlement, withdrawal review, chain event listening, and reconciliation.

2. Market data

The user frontend reads V2 market APIs such as /markets, /markets/featured, /markets/:slug, /markets/nav-tags, and odds history endpoints. The frontend adapts backend fields into the Market and BetEvent structures used by the UI.

3. Funding flow

USDT or test-token deposits use a Vault contract. The frontend performs wallet checks, approval when needed, and deposit transactions. The backend listens for chain events and writes internal ledger records.

4. Betting and settlement

Bets submit market slug, event id, outcome, and amount to the backend. The backend validates balance and market status, records the bet and ledger changes, and later settles market results into internal balance.

5. Advanced market concepts

Some prediction or derivatives platforms support advanced products such as continuous contracts, dynamic quote systems, collateral, forced closing, funding-style payments, liquidity systems, and risk dashboards. These concepts can help explain how more complex trading products work, but they are not part of SSC's current MVP unless specifically shown in the product.

In the current SSC user flow, users place fixed-outcome bets, funds enter and leave through the supported custody flow, and account balances, bets, ledger entries, and settlement are calculated by the backend.

6. Building and monitoring tools

Developers and operators may build dashboards that read market data, balances, positions, ledger entries, transaction status, and risk indicators through supported interfaces. Any tool built on top of SSC should respect user privacy, platform terms, rate limits, and applicable local laws.

Risk monitors should pay attention to margin-like exposure concepts, settlement status, unusual account activity, large withdrawals, duplicate rewards, and reconciliation differences between chain custody and internal balances.

7. Continuous contract concepts

Some advanced trading products track an underlying asset such as an index, commodity, crypto asset, or equity and continue trading without a fixed event-resolution date. Traders can open, manage, and close leveraged exposure while the tracked market moves.

These concepts are provided here as educational context only. SSC's current MVP does not enable leveraged continuous contracts unless a future product page clearly says so.

8. Pricing, positions, collateral, and closing risk

Advanced continuous products often use a traded price and one or more reference prices. A reference price may track the underlying asset, while a platform price may be used for account equity, collateral checks, and closing-risk calculations.

Opening or changing a position changes the account's exposure. A long position benefits when the tracked asset rises, while a short position benefits when it falls. Collateral supports open positions and absorbs losses while exposure remains open.

If account equity falls too far relative to required collateral, a system may close exposure to manage risk. SSC will not apply such mechanisms to the current MVP unless they are explicitly introduced and documented.

9. Funding-style adjustments and builder use cases

Some advanced products use periodic funding-style payments to keep traded prices close to reference prices. When a market trades above its reference, one side may pay the other; when it trades below, the payment direction may reverse.

Common builder use cases for advanced market data include signal-driven trading tools, quoting systems, portfolio dashboards, risk monitors, balance and position trackers, market data products, and analytics for trades, quotes, fees, and funding-style payments.