Minimal static directory for active onchain companies and projects.
Directory email/wallet sign-in, Editor/Reviewer permissions, submissions and required deployment/authority setup: directory roles. Page/workflow coverage and the default-off, Roles-authorized editorial MCP: editorial MCP contract.
- Repository: https://github.com/Bittrees-Technology/crypto-directory
- Default branch:
main(protected) - Required status check on
main:build-and-check - Directory source: 1,131 listings across 15 categories, including 13 crypto/Web3 AI Agents.
- The 500-listing expansion has two publication reviews: the first 100 additions and 400 completion additions. The latter replaces unsuitable research candidates with additional primary-site projects; research alone never approves a listing.
- Source proposals reach both public addresses only after the protected release is approved, deployed and synchronized.
- Security policy:
SECURITY.md
- Active companies/projects with live products
- Global coverage; all copy in English
- New research batches may extend coverage beyond the initial 1,000-entry target; suggestions remain separate from accepted listings until reviewed.
- Exclude obvious scams and dead projects
- Mostly exclude memecoins (exception: cultural/community significance)
- Multi-tag entries, sorted by lead category
- AI Agents initially covers crypto and Web3 agents only; see
content/categories.mdfor its scope.
Each project entry is a Markdown file in content/projects/ using front matter:
namelead_categorytagsecosystemdescriptionprimary_urlproduct_urlfoundedhqtokentwitterverification_status
Policy and operations docs:
content/curation-policy.mdcontent/monthly-ops.md
Process/spec tracking:
content/processes/specs/holds the written design and plan specscontent/processes/projects/defines tracked projects and weighted requirementscontent/processes/history/stores progress snapshots used for timeline projection
npm run buildBuild output is static HTML/JSON in site/.
- Public catalogue and category pages use bounded crawlable pagination; the full data feed and project IDs remain unchanged.
site/process-status.htmlshows project completion vs design/plan specssite/data/process-status.jsonexposes machine-readable progress and timeline data
Audit report:
node scripts/audit-report.mjsDirect process status report:
npm run process-statusSubmission import:
npm run import-submissionsSubmission docs:
content/submissions/README.mdcontent/submissions/submission-template.jsonsite/submit.html
Bulk status updates:
cp content/status-updates.example.csv content/status-updates.csv
# edit content/status-updates.csv
npm run update-statusesThen rebuild:
npm run buildReview 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 auditMonthly release ritual:
npm run release:monthly -- "optional notes for this release"Reference checklist: monthly-release-checklist.md.
This records audit and process-status evidence, builds and pins a release, appends its CID to releases.md, and prints an offline ENS contenthash packet. It does not sign or submit an ENS transaction. Normal live updates use the approved production IPNS synchronizer described in docs/ipns-publishing.md.
- Add new tracked projects in
content/processes/projects/*.json - Add more historical snapshots in
content/processes/history/*.jsonto improve timeline projections - Extend
scripts/lib/process-metrics.mjswith new check types as more scripts and data sources become available
The deployed ENS name uses the existing IPNS publisher. Keep that IPNS
record for normal site releases; publishing a new release does not require a new
ENS transaction. These commands prepare recovery information for
cryptodirectory.eth on Ethereum mainnet. They do not hold a signer or send
transactions, and cannot prepare a direct IPFS replacement for an active IPNS
record. Any such migration belongs in the existing TLD/Safe review flow.
Install the declared, locked CID dependency and run the tests:
npm ci --ignore-scripts --no-audit --no-fund
npm run test:ensmultiformats validates CIDs and normalizes them to CIDv1. Contenthash packets
follow ERC-1577, including its CIDv1
payload requirement for CIDv0 input. ENS packet generation, gating and tests are
self-contained. The pre-existing publish:ipfs uploader still requires the
separately installed shared IPFS storage integration; these ENS tools do not
import that sibling installation.
For a manual recovery review:
- Build (
npm run build), publish and verify a pinned release through the existing shared IPFS storage process. - Record the complete CID in a dated entry in
releases.md:- YYYY-MM-DD: CID=<cid> | entries=... | notes=.... - Inspect an offline packet:
npm run ens:contenthash -- <cid>. - Configure
ETH_RPC_URLlocally and install Foundry'scastfor read-only chain checks. Optionally setENS_RESOLVER_ADDRESSto the expected resolver; a mismatch with the live ENS registry blocks the operation. Keep RPC credentials out of source control and command-line arguments. - Run
npm run ens:gate -- --cid <cid>andnpm run ens:set-contenthash -- --dry-run --cid <cid>. - Where appropriate, explicitly request an unsigned proposal:
npm run ens:set-contenthash -- --prepare --cid <cid>. - Review availability, current ENS authority, the transaction destination and calldata, and simulation in the existing wallet, Safe or TLD approval flow. All owner, membership, controller and Safe threshold requirements still apply there.
The release gate runs before external reads or unsigned transaction preparation. CIDv0 and equivalent CIDv1 entries match by content identity; substring matches or mentions in notes do not satisfy the gate. Read-only checks verify mainnet, the current registry resolver, contenthash support and the current record. An already-current record produces no transaction proposal.
The default is read-only even when an inherited environment sets
ENS_SET_CONTENTHASH_EXECUTE. --execute is rejected. No signer key is accepted
or forwarded to child processes. RPC secrets stay out of argv, and raw child
errors are suppressed because they may contain credentials. The --prepare
result is unsigned and grants no authority; it must go through the existing
wallet/Safe/TLD approvals.
Keep immutable release CIDs in releases.md for rollback and audit. Preserve old
pins. A packet or an entry in that file does not prove network availability or
grant permission to change the live ENS record.
The root bittrees.tools.json registers Crypto Directory in the
Bittrees central MCP catalog.
The catalog's source allowlist
includes this repository; its sync script
reads the manifest from main at a resolved commit SHA.
The manifest uses bittrees.app-tools.v1, version 1, with project ID
crypto-directory and discovery endpoint https://mcp.bittrees.org/mcp.
Its reviewed local stdio adapter offers public read-only search, listing lookup,
category counts and checked release metadata. See adapter setup and boundaries.
The data-artifact URL in its local route is not an HTTP MCP endpoint. The static
site build does not read the manifest; existing publishing gates still apply.
Consumers remain responsible for endpoint trust, authentication, project scope and operation permissions. Catalog discovery does not launch code or grant access; gateway registration requires its exact route and setup to be separately reviewed and allowlisted.