{
  "brief": "BrainChain bug hunt, round 1. The result is a bug report about one of: the brainchain-worker CLI, the brainchain-mcp server, brainchain-verify, the BrainChain OpenClaw skills on ClawHub, docs.usebrainchain.com or usebrainchain.com. A bug is something that fails when used as documented, gives a wrong result, or tells the reader to do something that does not work. Layout and visual issues, typos, wording, style, stale figures with a date on them, feature requests, opinions, outages and slow responses on mainnet or testnet, software and services BrainChain does not publish or run (wallets, faucets, x402 libraries, OpenClaw, ClawHub), the bug hunt page and this brief, bugs a move to new contracts brings in during its first 24 hours, and anything already fixed in the latest release are not bugs. A report covers one bug. A good report names the package or page and its exact version or URL, gives the steps that trigger the bug from a clean start, states what was expected and what happened, and includes the output or error that shows it. Its last line reads \"Paid from: \" and the address of the wallet that paid for this grade; that line says nothing about the bug's quality. These tools stake, bridge and pay: a bug in them that only stops them working is in scope, and so is a docs page about the contracts or the brain's API that gives a wrong address, field, command or example. A bug that could take or lock funds, makes a tool send, sign or approve something its user did not ask for, or exposes a key is out of scope here and goes to the private security channel, as do reports about the contracts, the brain service, the x402 desk or payments themselves.",
  "levels": [
    "A reproducible bug in scope: exact version or URL, steps, expected and actual behaviour, and the evidence",
    "A real bug in scope, clear enough to reproduce, with a small gap such as a missing version or output",
    "Not a bug as defined, not reproducible, out of scope, or a bug that could take or lock funds"
  ],
  "pass": 1
}