Architecture

Pools Markets is maintained as separate application, backend and contracts projects. The repositories share protocol concepts and schemas without being combined into a monorepo.

System flow


Host adapter / Explore source
          │
          ▼
  Normalized asset state
          │
          ▼
Question pipeline + risk engine
          │
          ▼
Market creation intent / relayer
          │
          ▼
     PoolsDiamond
          │
          ▼
Indexer → API → Extension views
          │
          ▼
Evidence → resolver quorum → payout

Projects

Project	Responsibility
Extension	Embedded launchpad controls, account experience, positions, swap and Explore
Backend	API, auth, asset registry, discovery workers, market orchestration and reconciliation
Contracts	ERC-2535 protocol facets, libraries, deployment and verification
Docs site	User rules, protocol behavior, integration guides and deployment status

Read and write boundaries

Read endpoints expose durable state; they do not create markets or advance lifecycle state as a side effect. State transitions happen through explicit commands, workers or onchain transactions with stable idempotency keys.

The extension renders its static interface without waiting for the API. Remote state enriches or corrects values after the surface is available, and network failure produces a bounded degraded state rather than a missing interface.

Canonical specifications

Public documentation explains behavior. Exact compatibility is defined by:

versioned API schemas;
database migrations;
contract ABIs and verified source;
market and settlement specification hashes;
deployment manifests for each supported chain.