# PYRE / Prometheus Protocol

> **Burn the dead. Feed the PYRE. Claim the Spawn.**

**Links:** [feedthepyre.com](https://feedthepyre.com) · repo: `git.lumiai.dev/RogueWave/pyre` · dev status: [feedthepyre.com](https://feedthepyre.com) (status dashboard)

PYRE is a **Solana wallet-cleanup and ritual meme-rebirth protocol**. You connect
a wallet; PYRE scans your SPL token accounts (classic **and** Token-2022),
classifies them conservatively, and helps you safely close empty associated token
accounts (ATAs) and burn obvious junk — **returning recovered rent to you** (minus
a transparent 5% protocol fee) and producing a clear, shareable receipt. The
Prometheus engine uses AI to generate a meme-token "Spawn" from burned remnants
for **manual, human-reviewed** launch on Pump.fun.

The burner core is **live at [feedthepyre.com](https://feedthepyre.com)** and the
5%-fee close/burn flow has been verified end-to-end on mainnet.

The first emotional win is simple: *"PYRE cleaned my wallet and returned SOL I
forgot was trapped in token accounts."*

## What PYRE is — and is not

PYRE **is**: wallet cleanup, token-scrap transmutation, recovered-rent return,
transparent contribution accounting, AI-generated meme rebirth, and ritual
entertainment.

PYRE is **NOT** an investment product, yield mechanism, trading bot,
guaranteed-profit system, or protected launch mechanism. It makes no profit
promises.

**Trust guarantees:** PYRE never holds your private keys, never signs
custodially, and always shows a decoded transaction preview that matches what you
sign. Recovered rent goes back to your wallet, minus a single **transparent 5%
protocol fee** shown before you sign (it funds the Spawn — see the roadmap).
Swap proceeds always go to you. Anything the system cannot safely reason about is
skipped.

## The burner flow at a glance

```
Connect wallet
 → scan token accounts
 → classify accounts (closeable / burnable / transmutable / protected / unsupported)
 → preview the transaction (accounts, rent, destination, 5% fee, warnings)
 → you sign locally in your wallet
 → recovered rent (minus the fee) returns to you; the fee feeds the PYRE
 → see your PYRE receipt
```

## Roadmap & status

- **v0.1 — Burner / Cleaner** — **working.** Wallet connect, scan, conservative
  classification (classic SPL + Token-2022 with extension gating), close empty
  ATAs, burn-then-close junk, rent return minus the transparent 5% fee, receipt.
  Live on mainnet.
- **v0.2 — Prometheus Meta Mixer** — **working.** AI generation of a Spawn
  identity (name/ticker/lore/tagline/image-prompt + safety) from burned/cleaned
  token context; provider-abstracted with a deterministic stub fallback. Produces
  a candidate package only — no auto-launch. *In progress:* admin review UI and
  finishing the receipt → generation wiring.
- **v0.3 — Manual Pump.fun Workflow** — **working (manual, approval-gated).**
  Admin-gated generate/launch endpoints record mint, URL, metadata, and tx; public
  `/spawn` page. Human creates the token.
- **v0.4 — Essence Ledger** — **working (database-only).** The on-chain 5% fee is
  recorded as Essence per round in Postgres; a public "🔥 fed the PYRE" panel and
  `/api/essence` show round progress. Experimental, no claim promises.
- **Sell / Transmute** — **detection only.** Jupiter quotes + Shield + dust gate
  classify TRANSMUTABLE tokens; swap **execution is not built yet**.
- **v1.0 — PYRE Core Program** — **not built.** Future Solana (Anchor) program for
  trust-critical accounting: rounds, Essence vault, contribution receipts, Spawn
  distribution, claims, refunds.

## Repo structure

```
apps/
  web/        Next.js user app (wallet connect, scanner, preview, receipt)
  api/        Fastify HTTP API (scan, classify, build tx, receipt, generation)
  worker/     BullMQ background worker (skeleton — jobs not yet wired)
packages/
  core/       shared types, classification enums, risk rules, schemas
  solana/     token-account parsing, close/burn tx builders, decoder, simulation
  prometheus/ AI prompt templates, meta mixer, output parser, safety checks
  db/         database schema and migrations
  config/     shared config & env loading
programs/
  pyre-core/  future Anchor program (v1.0)
docs/         design, architecture, security, classification
```

## Quick start

**Prerequisites:** Node 22, pnpm, PostgreSQL, Redis.

```bash
cp .env.example .env   # then fill in values (no private keys — by design)
pnpm install
pnpm -r build          # build all packages/apps
pnpm -r test           # run the test suites
pnpm dev               # run web + api in dev
```

Secrets are read from the gitignored `.env` at the repo root; never commit keys.
Admin endpoints require an `ADMIN_API_TOKEN` (see `.env.example`). In production
the apps run under pm2 (`ecosystem.config.cjs`).

## Docs

See [`docs/`](docs/) — start with
[`docs/PYRE_MVP_DESIGN.md`](docs/PYRE_MVP_DESIGN.md) (the canonical design), then
[`ARCHITECTURE.md`](docs/ARCHITECTURE.md), [`SECURITY.md`](docs/SECURITY.md), and
[`TOKEN_CLASSIFICATION.md`](docs/TOKEN_CLASSIFICATION.md).