Menu

PUSHIN reference model · The terminal uses generated data and virtual collateral. On-chain settlement is not deployed.

Documentation index

Components and responsibilities

The target architecture separates the browser, HTTP API, relayer, contracts and database. In this release, PUSHIN runs a local practice account; these server components describe the integration design.

ComponentResponsibility
BrowserDisplay markets, build intents and manage scoped session keys.
APIVerify signed requests, reject invalid input and queue accepted intents.
RelayerCollect venues, calculate indices, process orders and refresh the oracle.
ContractsHold collateral, enforce payout reserves and apply settlement rules.
PostgresPersist accounts, market snapshots, events and the ledger.

Execution and settlement

The pool is the counterparty. Opening a position reserves its maximum profit before execution. Liquidation occurs after losses and accrued costs consume 90% of margin; the specified liquidator reward is 5% of forfeited margin.

When something breaks

A missing source is excluded from the collection round. Without sufficient inputs, the index stops updating. A stale oracle blocks price-dependent operations. A database lease permits only one active relayer; monitoring should alert on stalled orders, stale feeds and reserve violations.