SECURITY
Security practices and responsible disclosure.
Using a blockchain does not make a system trustless or fully decentralized. This page states what the protocol defends against today, what it does not, and how to report a problem.
contract status
- Network
- Robinhood Chain · 4663
- KuxerRegistry
- 0xDC95f1…59de64
- Source verified
- yes
- Independent audit
- none yet
THREAT MODEL
Risks and required controls.
Controls marked planned are design commitments, not shipped defenses.
- Benchmark gaming
- Held-out tasks with committed seeds, controlled baselines, versioned suites and suite rotation.
- Evaluator collusion
- Independent evaluators, conflict disclosure, diverse evaluation sources and reproducible runs. Signatures alone do not prove independence.
- Malicious experiments
- Firecracker isolation, resource limits, all network egress denied, timeouts, and no production secrets inside the sandbox.
- False attribution
- Source hashes, dependency records, contribution claims, artifacts and explicit attribution rules.
- Reward manipulation
- Explicit formulas, rate limits, challenge windows, transparent eligibility and auditable settlement (planned; no rewards exist today).
- Data poisoning
- Dataset provenance, versioning, contamination controls and protected evaluation sets.
- Governance attacks
- Minimal governance: an owner for challenge resolution and evaluator-set changes with a time delay, pause for emergencies, no authority over scientific truth.
KNOWN LIMITATIONS
What the current release does not do.
- Evaluations and replications are run by the operator's evaluator. Independent evaluators are planned; until then replication proves determinism, not independence.
- The registry contract has not had an independent security review. It holds no funds and manages no rewards, and nothing that does will be deployed before review.
- Challenge resolution is performed by the contract owner. There is no bond, no appeal body and no decentralized arbitration yet.
- Held-out instance seeds are committed but not yet revealed; third parties cannot regenerate those instances until a suite rotation publishes them.
- Rate limiting falls back to per-instance memory when the shared store is unavailable.
RESPONSIBLE DISCLOSURE
How to report a vulnerability.
- Security contact: the protocol owner, verifiable on-chain as the registry owner 0xc2bc9794beb9944d55d841995fe5d6d533ebfefd. Direct messages on X will open once the protocol account is published; until then, sign a message from a wallet that we can reply to on-chain.
- Do not test against production records, other users' proposals or the registry contract with real transactions beyond what is needed to demonstrate the issue.
- We acknowledge reports within five business days and publish a disclosure once a fix is deployed.
- Incident history: none recorded.