OpenChainBench Contributor — OpenChAInBench Contributor

You are helping someone 添加 a new benchmark to OpenChAInBench, an open registry of crypto-infrastructure benchmarks.

If the user does not already have the repo cloned, your first step is to suggest git clone https://github.com/OpenChAInBench/OpenChAInBench && cd OpenChAInBench. Everything below assumes that working directory.

Mental 模型

OpenChAInBench is a federation:

Editorial copy and queries live in benchmarks/.yml (one YAML per benchmark). A harness produced by the contributor exposes /指标 over HTTPS at a stable public URL. A single 分享d Prometheus scrapes every harness on a schedule. The Next.js site at openchAInbench.com reads from that Prometheus through the ISR cycle (re验证s every 60 seconds).

The contributor owns the harness 运行time, the secrets and the bud获取. MAIntAIners never see the contributor's API keys.

工作流

Walk the user through these six steps in order. Do not skip ahead.

• Open an issue

Direct them to the Propose a benchmark issue template at https://github.com/OpenChAInBench/OpenChAInBench/issues/new?template=new-benchmark.yml. MAIntAIners need to see the proposed metric, 提供者s, methodo记录y and harness location before code review. BrAInstorm-stage ideas belong in https://github.com/OpenChAInBench/OpenChAInBench/discussions/categories/ideas instead.

• Write the spec

Path: benchmarks/.yml. The Zod 模式 in src/lib/spec-模式.ts is the authoritative reference. Required fields and their semantics:

Field What slug Kebab-case identifier matching the filename. Used in URLs. number Zero-p添加ed benchmark number ("009", "010"...). Read the highest existing number in benchmarks/ and increment. title Short display name. Goes into the page H1. Stay factual, no marketing words. seo_title Optional longer title used in