Monetization (design Rev 4, §3.1) — transparent in-tx fee, non-custodial:
- @pyre/core: computeFeeBreakdown (single source of truth, BigInt) + FeeBreakdown
threaded through close/burn previews; fee tests.
- @pyre/config: PYRE_TREASURY_WALLET / PYRE_FEE_BPS (500) / swap fee / max contribution.
- @pyre/solana: close-empty + burn→close now append ONE System transfer of exactly
the disclosed fee to the treasury; rent/authority/feePayer pinned to wallet.
buildBurnTx re-validates EVERY account on-chain and value-gates via the classifier
(classic SPL + Token-2022) — never burns protected/valuable/NFT/unsupported;
ignores client amount (burns real balance); whole-build rejection.
- @pyre/api: close-empty/burn endpoints carry the fee + bounded optional contribution;
/api/receipt persists (cleanup_receipts) and records the on-chain treasury fee as
Essence; GET /api/essence; startup migrate(). Best-effort DB (never fails receipts).
- @pyre/db: Postgres Essence ledger (rounds, cleanup_receipts, essence_contributions),
idempotent migrations, parameterized + u64-safe.
- @pyre/web: fee preview ("reclaim · feeds the PYRE · you net" + treasury) + optional
"feed more" slider; burn flow w/ destructive confirm; decode+match verifies the fee
transfer (treasury + exact lamports) before signing; public "🔥 fed the PYRE" panel.
Built by agents (2 waves) + 2 audits. Security audit found a HIGH — buildBurnTx
didn't value-gate CLASSIC spl tokens (a direct API caller could burn USDC/an NFT);
FIXED (classify classic accounts too) + 2 regression tests. Integration: SHIP.
typecheck 8/8, core 91, solana 30, web build green. Live: burn preview on the dust
token shows 5% → treasury; non-empty/non-owned/valuable rejected. Nightly DB backup
cron enabled.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@pyre/core
Shared types and business logic for PYRE / Prometheus Protocol.
Purpose
The canonical home for cross-cutting type definitions and (eventually) pure
business logic shared by apps/* and the other packages/*. Per §13 its
responsibilities are:
- Classification enums —
TokenClassification(§6). - Risk rules — conservative safety-rule types/constants (§7). Placeholder.
- Shared DTOs — request/response shapes for the HTTP API (§14).
- Receipt schema —
CleanupReceipt(§8, §15). - Prometheus I/O schema —
PrometheusInput/PrometheusOutput(§9).
This package carries real type definitions but no application logic in the skeleton.
Modules
src/classification.ts—TokenClassificationenum.src/dto.ts— API request/response DTOs.src/receipt.ts— cleanup receipt schema.src/prometheus.ts— Prometheus meta-mixer input/output.src/risk.ts— risk-rule placeholder.
TODO
- Define concrete risk-rule identifiers, threshold shapes, and pure evaluators.
- Tighten DTO shapes flagged
TODOonce the scan/classify/build pipeline lands. - Define the concrete token
metadataJSON shape used by receipts and Prometheus.