Loading
Loading

Neuron registration trends
Most AI research isolates contributions: a published paper shares methods, but competitors must rediscover them independently. Finished models get selected while useful recipes stay private. Bug reports often go unrewarded when they don't lead to published work. Research evaluation is centralized, fixed benchmarks reward tuning rather than generalization, and there's no mechanism to preserve and reuse proven techniques across contributors.
Cortex addresses this by treating verified research as the unit of work rather than finished checkpoints. Miners submit reproducible experiments—a claim, code, data manifest, compute budget, and measured evidence—evaluated against operator-published topics on private test data. Scores are verified against holdout sets before rewards are calculated and signed. The network preserves useful methods from many contributors, not just the final model weights. Bounty challenges reward verified security findings with precision × severity scoring, so useful bug reports earn immediate recognition.
On Bittensor subnet 100, Cortex implements two live challenges: Proof (80% of emissions) for reproducible research against signed topics, and Bounty (20%) for verified product and backend bugs. Proof miners submit code artifacts with claims and get evaluated on operator-controlled Lium pods or Firecracker VMs with no network egress. Bounty miners pair a hotkey to a dedicated chat account, file reports, and earn based on operator-assigned severity and triage accuracy. Validators verify signed bundles, recompute aggregated weights from challenge-signed leaves against local trust roots, and cross-check peer validators before submitting on-chain.
Use cases were auto-generated from the GitHub repository and may not reflect the latest changes.
Cortex is an autonomous research network built on Bittensor subnet 100 that coordinates reproducible AI research and bug reports. It rewards verified research claims with reproducible code and evidence, while also incentivizing security contributions through bug bounty reporting. The network emphasizes preserving useful research methods and enabling synthesis of proven findings rather than selecting only finished model checkpoints.
Cortex is a Bittensor subnet with a master-validator split topology. Master (operator-controlled) runs the gateway (registry, bundle seal), challenge services (bounty-challenge reads CortexLM/backend public API; proof-challenge orchestrates evaluation), and optional Firecracker VM host (proof-vm-orchestrator). Miners submit Bounty reports over HTTP or Proof experiments (claim + code + artifact) with sr25519 signatures and single-use nonces.
Proof evaluates via digest-pinned RLM judge on operator Lium pods (nll/throughput harvest families) or Firecracker VMs (custom topics like tbench with no network egress). Validators fetch signed bundles, recompute weights from leaf signatures against local trust-root challenge keys and emission shares, cross-check with peer validators, and submit on-chain via CRV4 timelocked commit-reveal. Non-equivocation is peer-consensus + local evidence, not on-chain anchored.
Bundles use RFC 6962 merkle trees, SCALE encoding, and separate signatures: challenge keys sign individual Score/NoScore leaves, gateway signs the full bundle. Validators verify participant-set completeness (derived from policy per challenge: AllMetagraphHotkeys, StakeAtLeast, allowlist, or denylist), merkle root, aggregation output (Hamilton house 65535, IEEE 754 summation for parity with BASE master), and dissent on mismatch. Trust roots (challenges.toml, measurements.toml, owner.pubkey) are owner-signed and loaded from validator disk, never from HTTP.
The open alternative to frontier AI | Efficient autonomous research
This information was auto-extracted from the GitHub repository and may be incomplete or out of date. Always refer to the subnet's GitHub repository for the latest instructions.
Proof scoring: Each topic specifies a metric family (nll/throughput for harvest, custom/agent for Firecracker), payout mode (wta winner-take-all or discovery pass-floor + novelty-pool), and pass rules (epsilon relative improvement thresholds). Reproducibility is verified by re-running miner code against organizer infrastructure. Private holdout prevents memorization; canary metrics stay off-score.
Topics may defer scoring while baselines install (queued state). Custom/agent topics like tbench run in Firecracker guest VMs with anti-cheat checklist rules checked before any paid inference. Bounty scoring: Miner precision (valid reports / (valid + malicious)) × mean severity of adjudicated findings.
Floor of 6000 bps precision required to be champion. Malicious reports burn toward uid 0; duplicates and already-fixed reports earn nothing but count as off-score triage noise. Both challenges produce signed leaves under challenge keys, bundled by gateway, verified by validators against local owner-signed trust roots before chain submission.
The sections above were auto-generated from the GitHub repository and may not reflect the latest changes. View repository
FAQs were auto-generated from the GitHub repository and may not reflect the latest changes.
Holder & total-staked metrics as of 2h ago (hourly snapshot)
Proof topic tbench runs in Firecracker guest VMs with no network interface, so artifacts must be uploaded to gateway. Harvest topics (nll/throughput) run on operator-rented Lium pods (16vCPU/32GB locked). Custom topics may use dedicated experiment VMs (16vCPU/32GB). Pod costs billed via LIUM_API_KEY.
Validators verify sealed weight bundles, perform peer consensus checks, and submit on-chain. No challenge execution or Lium billing. Postgres database for bundle/evidence persistence required.
Install ctx CLI tool (Cortex command-line interface)
curl -fsSL https://raw.githubusercontent.com/CortexLM/cortex/main/scripts/install-ctx.sh | sh
Check if Proof challenge is ready to score (can_score, eval_image_digest, open topics)
ctx proof status
List all open Proof topics and their signed documents
ctx proof topics
Pair Bittensor hotkey to Cortex Chat account for Bounty (creates dedicated mining account)(optional)
ctx bounty pair --hotkey <ss58-hotkey> --account-id <chat-account> --wallet-name <wallet> --accept-terms
File a bug report for Bounty challenge (requires prior pairing)(optional)
ctx bounty report --title '...' --body-file report.md --repro-file repro.md
Create uncompressed artifact tar for Proof submission(optional)
tar -cf recipe.tar recipe/ && sha256sum recipe.tar
Submit Proof experiment claim with code artifact and model API key (for tbench topic)(optional)
ctx proof submit --secret-file /path/to/hotkey.sk --topic-id <topic_id> --artifact recipe.tar --claim '...' --env OPENROUTER_API_KEY
Clone the Cortex monorepo
git clone https://github.com/CortexLM/cortex.git && cd cortex
Set validator environment variables (mainnet; use testnet endpoints for staging)
export BASE_ROLE=validator && export BASE_NETUID=100 && export BASE_CHAIN_ENDPOINT=wss://mainnet-finality.subtensor.network:443 && export BASE_GATEWAY_ENDPOINT=https://gateway.cortex.foundation
Configure validator Bittensor wallet for on-chain weight submission
export BASE_VALIDATOR_WALLET=<wallet-name> && export BASE_VALIDATOR_HOTKEY=<hotkey-name>
Materialize environment configuration from templates
./deploy/scripts/materialize-env.sh
Start validator services (fetches bundles, verifies, submits weights, handles dissent)
docker compose -f docker-compose.yml -f deploy/compose/role-validator.yml up -d
Monitor validator logs for bundle verification and submission progress(optional)
docker logs -f validator