CryptoDirectory

Minimal static directory for active onchain companies and projects.

Current status (February 13, 2026)

• Repository: https://github.com/Bittrees-Technology/crypto-directory
• Default branch: main (protected)
• Required status check on main: build-and-check
• Latest verified build output: Built 1030 projects across 14 categories.
• Security policy: SECURITY.md

Scope (v1)

• Active companies/projects with live products
• Global coverage; all copy in English
• Target cap: up to 1,000 entries
• Exclude obvious scams and dead projects
• Mostly exclude memecoins (exception: cultural/community significance)
• Multi-tag entries, sorted by lead category

Entry fields

Each project entry is a Markdown file in content/projects/ using front matter:

• name
• lead_category
• tags
• ecosystem
• description
• primary_url
• product_url
• founded
• hq
• token
• twitter
• verification_status

Policy and operations docs:

• content/curation-policy.md
• content/monthly-ops.md

Process/spec tracking:

• content/processes/specs/ holds the written design and plan specs
• content/processes/projects/ defines tracked projects and weighted requirements
• content/processes/history/ stores progress snapshots used for timeline projection

Build

npm run build

Build output is static HTML/JSON in site/.

• site/process-status.html shows project completion vs design/plan specs
• site/data/process-status.json exposes machine-readable progress and timeline data

Audit report:

node scripts/audit-report.mjs

Direct process status report:

npm run process-status

Submission import:

npm run import-submissions

Submission docs:

• content/submissions/README.md
• content/submissions/submission-template.json
• site/submit.html

Bulk status updates:

cp content/status-updates.example.csv content/status-updates.csv
# edit content/status-updates.csv
npm run update-statuses

Then rebuild:

npm run build

Review queue page:

• site/review.html (generated by build)
• site/needs-update.html (generated by build)

Automatic first pass (no manual review required initially):

npm run auto-first-pass
npm run build
npm run audit

Monthly release ritual:

npm run release:monthly -- "optional notes for this release"

Reference checklist: monthly-release-checklist.md. This enforces the core release order audit -> build -> publish -> ENS update -> append releases.md and also records a timestamped process-status evidence log under reports/ for the release.

Extending completion logic

• Add new tracked projects in content/processes/projects/*.json
• Add more historical snapshots in content/processes/history/*.json to improve timeline projections
• Extend scripts/lib/process-metrics.mjs with new check types as more scripts and data sources become available

IPFS + ENS later

When ready:

1. Build site (npm run build)
2. Add/pin site/ to IPFS
3. Point cryptodirectory.eth contenthash to the IPFS CID
4. Keep monthly release notes with CID history in releases.md

Snapshot strategy (recommended)

• Keep immutable release folders/CIDs: v1, v2, v3
• Update ENS to latest stable CID
• Preserve old CIDs in releases.md for rollback/audit