Documentation
Getting started
Run AssetForge locally, understand demo mode, and make your first validation call.
Install and run
AssetForge runs with no database and no credentials. On a clean checkout it starts in demo mode, serving deterministic sample data so the whole product is explorable before anything is configured.
npm install cp .env.example .env.local npm run dev
Demo mode is on whenever DATABASE_URL is unset. It is labelled throughout the interface, no transaction is broadcast, and every write path returns a typed demo_mode error rather than silently doing nothing.
Your first validation
Open /validate and submit an asset. The engine runs ten weighted categories and reports two numbers: a readiness score, and a coverage figure telling you how much of the record it was actually able to evaluate.
Read both numbers. A high score over low coverage means very little was checked — it is not the same claim as a high score over full coverage, and the interface never merges them.
Going beyond demo mode
- Set DATABASE_URL to a PostgreSQL instance and run `npm run db:push`.
- Set ALCHEMY_API_KEY, or RH_MAINNET_RPC_URL and RH_TESTNET_RPC_URL, for a dedicated RPC endpoint.
- Generate API_KEY_HASH_SECRET and WEBHOOK_SIGNING_SECRET with `openssl rand -base64 48`.
- Set NEXT_PUBLIC_DEMO_MODE=false once the above are in place.