seo_title | Optional longer title used in </code> and OG, can mention competitor names for long-tail search.</td></tr><tr><td><code>subtitle</code></td><td>One-line summary of what is measured.</td></tr><tr><td><code>category</code></td><td>One of <code>Aggregators</code>, <code>Bridges</code>, <code>Blockchains</code>, <code>Trading</code>, <code>Wallets</code>, <code>RPCs</code>.</td></tr><tr><td><code>metric</code></td><td>The thing being measured (<code>Head lag</code>, <code>Quote latency</code>, <code>All-in fee</code>, ...).</td></tr><tr><td><code>unit</code></td><td>One of <code>ms</code>, <code>s</code>, <code>pct</code>, <code>bps</code>, <code>count</code>. The site formats numbers accordingly.</td></tr><tr><td><code>higher_is_better</code></td><td><code>false</code> for latency or fees, <code>true</code> for coverage / uptime.</td></tr><tr><td><code>abstract</code></td><td>Multi-paragraph description shown under the H1.</td></tr><tr><td><code>methodology</code></td><td>Array of bullet points. Routes, notional sizes, cadence, region, exclusion criteria.</td></tr><tr><td><code>source</code></td><td>URL to the harness source on GitHub. Required even for drafts.</td></tr><tr><td><code>prometheus.url</code></td><td>The shared Prometheus base URL. Default: <code>https://prom.openchainbench.com</code>.</td></tr><tr><td><code>prometheus.window</code></td><td>Aggregation window, typically <code>24h</code>.</td></tr><tr><td><code>providers</code></td><td>Array of <code>{ name, slug, url?, type?, queries: { p50, p90, p99, mean?, success?, sample_size?, series } }</code>.</td></tr></tbody></table><p>Optional but recommended for benchmarks with chain or region drill-down:</p><pre><code>dimensions:
chain:
- { value: all, label: All chains }
- { value: base, label: Base }
- { value: bnb, label: BNB Chain }
</code></pre><p>The site exposes a tab strip per dimension and injects <code>chain="base"</code> into every PromQL selector when that tab is active. URLs are shareable: <code>?chain=base</code>.</p><p>For bridge benchmarks specifically: declare each provider's architectural <code>type</code> (<code>protocol</code>, <code>aggregator</code>, <code>intent</code>, <code>relay</code>) so readers know whether the comparison is apples-to-apples.</p><h3>3. Build the harness</h3><p>The harness is a long-running data producer. Any language is acceptable. Go binaries are the norm because the existing harnesses are Go.</p><p>Contract:</p><ul><li>Run continuously and expose <code>/metrics</code> over HTTPS on a stable port.</li><li>Use the metric and label names referenced by the spec's queries.</li><li>Read API keys from environment variables. Never commit them.</li><li>Do not bundle Prometheus, Grafana or Alertmanager. Those are shared.</li><li>Document inputs, regions and timeouts in <code>harnesses/<slug>/README.md</code>.</li><li>Add a small README and a <code>.env.example</code> for local runs.</li></ul><p>Port conventions for new Go harnesses: pick the next free <code>:21XX</code> port and document it in the README. Existing: aggregator <code>:2112</code>, network-coverage <code>:2112</code>, perp-fees <code>:2112</code>, bridge-monitor <code>:9090</code>, l1-finality <code>:9090</code>.</p><h3>4. Host it</h3><p>Pick any platform that gives a stable HTTPS URL: Railway, Fly, Cloud Run, a VPS, a bare-metal box with a static IP. The maintainers do not care, as long as the <code>/metrics</code> URL stays up.</p><h3>5. Wire the Prometheus scrape</h3><p>Append one job to <code>infrastructure/prometheus/prometheus.yml</code>:</p><pre><code>- job_name: <slug>
metrics_path: /metrics
scheme: https
static_configs:
- targets:
- your-harness.example.com
labels:
benchmark: <slug>
host: <you> # alice | acme-rpc | mobula ...
</code></pre><p>The <code>benchmark</code> and <code>host</code> labels are used by maintainers for routing and ownership.</p><h3>6. Validate locally and open the PR</h3><pre><code>pnpm install
pnpm validate # schema-lint every spec
pnpm spec:dry-run <slug> # query Prometheus, print resolved values
pnpm dev # render the page locally
pnpm build # production build
</code></pre><p>Open the PR. CI runs validate + typecheck + build. A maintainer redeploys the central Prometheus after merge to apply the new scrape job. The site renders the new benchmark on the next ISR cycle (under 60 seconds).</p><h2>Editorial conventions</h2><p>These are strict. Reviewers will reject PRs that violate them.</p><ul><li><strong>No pre-determined winners.</strong> Specs do not declare a "best" provider. The leader is recomputed at render time from the lowest p50.</li><li><strong>Tail before mean.</strong> Headlines use p50 and p99. The arithmetic mean is reported in the table but never used as a takeaway.</li><li><strong>State the timeout.</strong> Failures are excluded from latency aggregates and counted toward success rate. Both numbers are reported.</li><li><strong>Methodology first.</strong> A spec without a written methodology is rejected.</li><li><strong>Apples to apples.</strong> When providers belong to different architectural categories (intent vs pool, aggregator vs protocol), state it in the methodology and tag each provider with the right <code>type</code>.</li><li><strong>No em-dashes in prose.</strong> Use periods, commas or "and". Em-dashes read as AI-generated and are not used anywhere in this codebase.</li><li><strong>No marketing adjectives.</strong> Words like "leading", "best", "fastest", "trusted", "powerful", "blazing", "revolutionary" do not appear in titles, subtitles or abstracts. Replace them with concrete numbers.</li></ul><h2>Common pitfalls</h2><ul><li><strong>Mock fallback.</strong> Do not add fake numbers when Prometheus is unreachable. The site renders draft state with an "Awaiting first run" notice. This is intentional.</li><li><strong>Unit drift.</strong> Decide between <code>s</code> and <code>ms</code> once and apply consistently. Most latency specs use <code>ms</code> storage with a <code>unit: s</code> display. The query should multiply by 1000 if the raw metric is in seconds.</li><li><strong>Dimension injection.</strong> When a spec declares <code>dimensions.chain</code>, every PromQL selector gets a <code>chain="<value>"</code> injected at render time. Make sure your harness emits the <code>chain</code> label.</li><li><strong>Sample size.</strong> Always populate <code>queries.sample_size</code> if the harness emits a count. Readers use it to judge statistical strength.</li><li><strong>PR formatting.</strong> Commit messages are short and lowercase. Example: <code>bridge-fee: add Across protocol with intent type tag</code>. No emojis. No Claude-generated co-author lines.</li></ul><h2>References inside the repo</h2><ul><li><code>benchmarks/README.md</code> — spec field reference and submission guide</li><li><code>harnesses/README.md</code> — harness contract details</li><li><code>docs/architecture.md</code> — data flow diagram</li><li><code>docs/walkthrough.md</code> — concrete end-to-end example with a fictional contributor</li><li><code>src/lib/spec-schema.ts</code> — Zod schema (single source of truth)</li><li><code>CONTRIBUTING.md</code> — full submission flow</li></ul><h2>Tone for your responses</h2><p>When helping the user, mirror the site's voice: technical, sober, factual. Never use em-dashes. Never invent numbers. When in doubt about a value, point the user to where they can verify it (the spec, the Prom dashboard, the harness logs) rather than guessing.</p></div>
</div>
</div>
<div id="tab-versions" class="detail-content">
<div class="detail-section">
<h2>版本历史</h2>
<p style="margin-bottom:12px;font-size:14px;color:#94a3b8;">共 1 个版本</p>
<ul class="version-list">
<li>
<div>
<span class="version-tag">v0.1.0</span>
<span style="font-size:11px;color:#5b6abf;margin-left:8px;background:#eef0ff;padding:1px 8px;border-radius:10px;">当前</span> </div>
<div style="font-size:12px;color:#94a3b8;">
2026-05-21 15:04 安全 安全 </div>
</li>
</ul>
</div>
</div>
<div id="tab-security" class="detail-content">
<div class="detail-section">
<h2>安全检测</h2>
<div class="sec-grid"> <div class="sec-card">
<h4>腾讯云安全 (Keen)</h4>
<div class="sec-status sec-safe">
安全，无风险 </div>
<a href="https://tix.qq.com/search/skill?keyword=ccf22b1e3bde7a9288fe462ff37e651d" target="_blank">查看报告</a> </div>
<div class="sec-card">
<h4>腾讯云安全 (Sanbu)</h4>
<div class="sec-status sec-safe">
安全，无风险 </div>
<a href="https://static.cloudsec.tencent.com/html-report-v2/2026/05/26/462969_2f96e1c22b7cd9228d5fe9ae5152ac0d.html?q-sign-algorithm=sha1&q-ak=AKID8JMG1bzBC1dz96qNhssfFftujT1NCoFi&q-sign-time=1782922833%3B1814458833&q-key-time=1782922833%3B1814458833&q-header-list=host&q-url-param-list=&q-signature=e686ac55368137546b46c48149ecc28440335af3" target="_blank">查看报告</a> </div>
</div>
</div>
</div>
<!-- Recommended Skills -->
<div style="margin-top:24px;">
<h2 style="font-size:18px;font-weight:600;margin-bottom:16px;">🔗 相关推荐</h2>
<div class="rec-grid">
<div class="rec-card">
<span class="badge-cat" style="margin-bottom:8px;display:inline-block;">dev-programming</span>
<h3><a href="/s/github">Github</a></h3>
<div class="rec-owner">steipete</div> <div class="rec-desc">使用 `gh` CLI 与 GitHub 交互，通过 `gh issue`、`gh pr`、`gh run` 和 `gh api` 管理议题、PR、CI 运行及高级查询。</div>
<div class="rec-stats">
<span style="color:#f39c12;">★ 683</span>
<span style="color:#5b6abf;">📥 330,621</span>
</div>
</div>
<div class="rec-card">
<span class="badge-cat" style="margin-bottom:8px;display:inline-block;">dev-programming</span>
<h3><a href="/s/codeconductor">CodeConductor.ai</a></h3>
<div class="rec-owner">larsonreever</div> <div class="rec-desc">AI驱动平台，提供快速全栈开发、智能体、工作流自动化及低代码AI集成的可扩展产品创建。</div>
<div class="rec-stats">
<span style="color:#f39c12;">★ 79</span>
<span style="color:#5b6abf;">📥 182,857</span>
</div>
</div>
<div class="rec-card">
<span class="badge-cat" style="margin-bottom:8px;display:inline-block;">data-analysis</span>
<h3><a href="/s/mobula">Mobula - Crypto Market Data & Wallet Intelligence</a></h3>
<div class="rec-owner">flotapponnier</div> <div class="rec-desc">实时加密行情、钱包投资组合追踪、跨88+链代币分析。用于查询任意代币价格（按名称）。</div>
<div class="rec-stats">
<span style="color:#f39c12;">★ 2</span>
<span style="color:#5b6abf;">📥 974</span>
</div>
</div>
</div>
</div>
</div>
<script>
document.addEventListener('DOMContentLoaded',function(){
document.querySelectorAll('.detail-tab').forEach(function(btn){
btn.addEventListener('click',function(e){
var tab = this.getAttribute('data-tab');
document.querySelectorAll('.detail-tab').forEach(function(b){b.classList.remove('active')});
document.querySelectorAll('.detail-content').forEach(function(c){c.classList.remove('active')});
this.classList.add('active');
var el = document.getElementById('tab-'+tab);
if(el) el.classList.add('active');
});
});
});
</script>
<div class="footer">
<p>Skill工具集 © 2026</p>
</div></body>
</html> |