Developer

This section documents open-source architecture and operational behavior relevant to contributors and technical reviewers.

Design Principles

• On-chain state as source of truth for trading and lifecycle state.

• Indexed data layer for performant query and charting UX.

• Separation of product UI from indexing worker behavior.

• Chain-explicit configuration for predictable runtime behavior.

Out of Scope

• Internal security controls and private operational runbooks.

• Secret management procedures.

• Non-public deployment infrastructure details.

Current Hardening Priorities

The main hardening priorities in the current branch are:

• truthful lifecycle readiness status

• market risk caps and emergency controls

• insurance fund / bad-debt tracking

• creator verification and launch gating

• truthful perp event indexing and analytics

Identity Model

The current hardening branch treats Privy as the identity/auth source and the app database as the policy layer. Linked social accounts are synced into user records, a primary creator identity is selected, and launch eligibility is derived from that synced state.

Operational Tooling

Operational visibility is being added directly to the app through health/status endpoints and an internal ops page. This is part of the move toward production-grade runbooks and incident response.