DoxedCryptoFounder

Live: doxxedcrypto.digital

Curated crypto intelligence for retail who want tech and accountable founders — not anonymous pumps. We surface projects building in public, power Founder OS (AI-assisted shipping), and Founder Node (self-custody vault + optional local AI).

---

Privacy & security — read this first

Vault encrypted on our servers; readable only on your devices. Choose Phala or local Ollama when you want confidential AI — not just encrypted storage.

Full guide (diagrams, disclaimers, protect PC/phone): PRIVACY.md ← start here on GitHub

flowchart TB
  subgraph yours["Your devices"]
    PC["PC — Founder Node vault"]
    PH["Phone — Founder OS app / web"]
  end

  subgraph dcf["Doxxed Crypto"]
    API["API + encrypted vault blob"]
    DB["Neon — cannot decrypt your notes"]
  end

  subgraph ai["AI — you choose"]
    OLL["Ollama on PC — local"]
    PHA["Phala TEE — confidential cloud"]
    BYO["BYOK — OpenRouter / DeepSeek / …"]
  end

  PC -->|"AES-GCM ciphertext"| API
  PH --> API
  API --> DB
  PC --> OLL
  API --> PHA
  API --> BYO

Question	Answer
Can the server read my private vault notes?	No (encrypted relay when using Founder Node mode)
Can my PC read vault files?	Yes — normal; vault lives on your machine
Where is my code?	GitHub — not inside Founder Vault
Strongest cloud AI privacy?	Phala TEE in Builder settings
Strongest local AI privacy?	Ollama via Founder Node on PC

Protect your devices: lock screen, official Founder Node releases only, revoke old paired nodes in Settings, never share node-config.json. Details → PRIVACY.md.

→ Mobile app: coming soon at /mobile (legacy APK removed; see docs/MOBILE_APP.md) · pair desktop from Founder IDE
→ Mobile vault roadmap (historical): docs/MOBILE_VAULT_ROADMAP.md
→ System architecture: docs/ARCHITECTURE.md
→ Privacy stack (Steps 1–5): docs/PRIVACY_STACK.md

---

Documentation

→ Why we exist: docs/MISSION.md
→ All docs index: docs/README.md
→ External audit (ChatGPT-safe): AUDIT.md · docs/AUDIT_FOR_CHATGPT.md
→ Public vs private files: docs/REPOSITORY_LAYOUT.md

Tech Stack

Layer	Technology
Frontend	Next.js 15, React, TypeScript, Tailwind CSS, shadcn/ui
Backend	NestJS, Node.js, TypeScript
Database	PostgreSQL + Prisma
Cache	Redis
Auth	NextAuth (Phase 3)
Monorepo	Turborepo + npm workspaces

Project Structure

doxedcryptofounder/
  apps/
    web/          # Next.js frontend
    api/          # NestJS backend
    founder-node/ # Electron desktop vault (see apps/founder-node/README.md)
  packages/
    ui/           # Shared UI components
    types/        # Shared TypeScript types
    config/       # Shared configuration
    utils/        # Shared utilities
  prisma/         # Database schema & migrations
  docs/           # Mission, privacy stack, audit guides (no secrets)
  docker/         # Docker configs
  scripts/        # Utility scripts (ops — not in audit export)
  services/       # Showcase trading bot (btc-conservative-agent)

Repository zones

Zone	Location	Commit to git?
Public source	This repo	Yes
Secrets vault	../doxedcryptofounder-secrets/vault/	Never
Audit export	../doxedcryptofounder-audit/ (generated)	Never

After clone: npm run secrets:link · For reviewers: npm run audit:export — see docs/REPOSITORY_LAYOUT.md.

Quick Start

1. Install dependencies

npm install

2. Configure environment

cp .env.example .env

3. Start infrastructure

Option A — Docker (recommended long-term):

npm run setup

Option B — No Docker (fastest if Docker won't start):

npm run setup:neon

Uses free Neon cloud PostgreSQL. No WSL/Docker required.

If Docker fails to start:

npm run setup:repair   # runs wsl --update
# RESTART PC, open Docker Desktop, then npm run setup

Docker Desktop must show "Running" before docker compose up works. If you see Docker Desktop is unable to start, run npm run setup:repair, restart your PC, or use npm run setup:neon instead.

4. Run database migrations

npm run db:migrate

5. Seed initial data

npm run db:seed

6. Start development servers

npm run dev

• Frontend: http://localhost:3000
• Backend API: http://localhost:4000/api/health

Production deploy (Neon + Railway + Vercel)

1. Database: npm run setup:neon → copy connection string to Railway/Vercel env as DATABASE_URL.
2. API (Railway): connect repo, set env from .env.production.example, first deploy set PRISMA_DB_PUSH=true, then run npm run db:seed against Neon once.
3. Web (Vercel): import repo, set Root Directory to apps/web, add NEXT_PUBLIC_API_URL, NEXTAUTH_URL, NEXTAUTH_SECRET, Google/Stripe keys.
4. Stripe webhook: point to https://YOUR-API/api/paper-trading/stripe/webhook.
5. Google OAuth redirect: https://YOUR-DOMAIN/api/auth/callback/google.

Railway uses railway.toml. Vercel uses apps/web/vercel.json.

This is the beginning of the README. Read the rest at the original. Read the full README ↗