GETTING STARTED
Kuxer documentation
What the protocol is for, what it is not, how mature it is, and how to work with it today.
Purpose
Kuxer coordinates the discovery, evaluation, attribution and inheritance of improvements in intelligence. A proposal names a baseline and parents; an experiment runs it under fixed conditions in an isolated sandbox; replication must reproduce the result; the accepted record becomes a parent for later work. Integrity commitments and statuses settle on Robinhood Chain · 4663.
The first release proves one proposition: the system can accept a proposed improvement, evaluate it reproducibly, preserve its lineage and make the result available for subsequent research.
Non-goals
- Not a generic agent marketplace, model inference API or GPU rental marketplace.
- Not a token dashboard, presale interface or leaderboard. There is no token.
- Not a universal intelligence score, and not a DAO with authority over scientific truth.
- Not a fully automated self-modifying model system or an on-chain machine-learning execution engine.
Maturity and limitations
Research stage. One bounded capability domain exists (Euclidean TSP heuristic optimization) with a baseline, a versioned suite and a working pipeline. Evaluations are executed by the operator's evaluator; independent evaluators, attribution policies and any funding mechanism are planned. The registry contract holds no funds and has not been independently audited. See security for the full list.
Supported network
Production targets Robinhood Chain · 4663 (gas in ETH; explorer robinhoodchain.blockscout.com). The testnet (chain id 46630) is optional staging only. Browsing records and documentation never requires a wallet; wallet connection is needed only for on-chain actions such as anchoring a proposal.
Repository and contribution paths
- Source code: the repository is not public yet. Every record carries the hashes needed to verify it against the on-chain commitment in the meantime.
- Propose an improvement through the contribution page or the API.
- Reproduce results: every evaluation record carries experiment ids, source hashes and the suite's public development seed.
- Report security issues through the disclosure process.