Protocol Overview
The market data, execution and settlement responsibilities of WINFLOW Protocol.
Market information
A market is identified by its question and outcome set, denomination asset, prices, open positions and resolution status. Keeping these fields distinct prevents a price update from being mistaken for an outcome or a completed settlement.
Trading and positions
WINFLOW connects pricing information with order execution and position accounting. The existing model uses prices between 0 and 1 for binary outcomes and calculates average fills across available depth. Position quantity and denomination are essential settlement inputs.
Current boundaries
Some market information and resolution depend on external venues and backend data. This documentation does not claim universal onchain resolution, deployed signature thresholds or a live public SDK. Planned mechanisms are not presented as current guarantees.
Collateral gate: design and verification boundary
The previous architecture describes a solvency gate comparing available protocol collateral with required liability before execution. Deployment-level evidence for worst-case liability accounting and smart-contract enforcement must be verified before this model is treated as a universal guarantee.
Available protocol collateral ≥ Required liability
Architecture condition, not a guarantee of returns or universal enforcement.
Six safeguards in the earlier architecture
The earlier model identifies pre-trade solvency checks, collateralized liabilities, smart-contract governed funds, deterministic execution, source-aware resolution and programmatic settlement. These describe intended control boundaries; source-aware resolution still depends on applicable external result sources.
Assess each control against the deployed contracts, configuration and operational procedures. Collateral checks alone do not eliminate token, liquidity, contract or resolution risk, and no unsupported audit or capital-protection claim is made here.