Skip to main content

Backend & Indexing

Flipit uses a first-party Fastify/PostgreSQL service rather than making every browser scan chain history.

Responsibilities​

The backend:

  • stores pending launch records;
  • persists token images and immutable metadata JSON;
  • independently verifies confirmed launch receipts;
  • stores confirmed launch identities and current state;
  • tracks known sale and pool contracts;
  • reconciles current state against LiteForge;
  • serves fast Explore, search and token-discovery APIs.

The backend does not:

  • hold user private keys;
  • sign Create, Buy, Sell, Swap or Claim transactions;
  • decide final token balances;
  • override smart-contract state.

Current-state-first bootstrap​

The current system discovers launch identities using launchCount transitions and exact creation blocks, then reads current contract state at a fixed block. Explore readiness does not wait for complete historical activity reconstruction.

Checkpoints​

Live and historical checkpoints are separate. Live state can remain current even when optional historical activity processing is behind. Processed events are deduplicated by chain, transaction hash and log index.

Metadata​

Uploaded JPG, PNG, GIF and WebP images are validated and normalized before storage. Metadata JSON is immutable once published for a launch. Public image and metadata URLs require a real HTTPS backend base URL; localhost is not suitable for on-chain metadata.