Developer

This section gives technical readers a high-level view of how perps. is structured.

It is intentionally public-facing. It does not document private infrastructure, secrets, deployment procedures, or internal operational runbooks.

Design Principles

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

• Indexed data supports fast reads, charts, search, and profile views.

• The app is chain-explicit so users and developers can reason about the active network.

• Product surfaces should distinguish lifecycle state from trading readiness.

Core Public Components

• Creator profile and identity layer.

• Social token launch and bonding-curve lifecycle.

• Perpetual market engine for supported markets.

• Market data indexing and read models.

• XP, badge, and rank progression.

Out of Scope

• Private deployment topology.

• Secret management.

• Internal monitoring procedures.

• Admin-only actions.

• Incident response runbooks.