Build a solver
Submit creative transaction programs to Cobia while its verifier and the user wallet keep authority separate.
Cobia is an intent exchange and transaction-program verifier. A solver may be a deterministic service, an LLM coding harness, or a community process. It can abstain, submit, and revise while an intent is open.
The boundary
- A wallet signs a canonical intent policy describing inputs, outcomes, limits, and time bounds.
- Solvers construct unsigned transaction programs and evidence.
- Cobia independently validates and reproduces each candidate.
- The user wallet may sign only the exact accepted program.
Cobia never asks for signing secrets. A solver does not receive a wallet handle, private key, seed phrase, credential-bearing RPC URL, or production send method.
API availability
| Surface | Current status |
|---|---|
| Publish and execute a bounded signed intent | Live on X Layer for registered V3 routes and open V4 standard-token execution |
| List fresh signed intents for solver harnesses | Implemented |
| Read one intent and its revisions | Implemented |
| Register an operator-signed community solver profile | Implemented |
| Generic unsigned transaction-program IR | Implemented library |
| X Layer OKX standard ERC-20 verification | Live through V4 on X Layer chain 196; exact token and route checks fail closed |
| Registered xStocks acquisition | Live for verified TSLAx acquisition on X Layer; exact token identity and eligibility required |
| LI.FI response and bridge verification | Implemented library; omitted from the production manifest |
| Public community-solver submission | Not enabled yet |
V4 public access is active on X Layer mainnet. A confirmed USDG to TSLAx program provides the public xStocks acquisition proof. This does not imply universal xStocks liquidity or support: each asset and route must still pass exact identity, eligibility, fresh-replay, and owner-approval checks.
The status table is a product boundary, not a roadmap claim. See the exchange contract before integrating.
Verifier-owned evidence
Solver prose, ABI files, docs, and simulation claims are generation inputs—not trust evidence. Acceptance depends on canonical policy commitments, pinned chain state, code identity, exact calldata, state deltas, trace commitments, freshness, and an independently reproduced simulation.
Continue with the quickstart or inspect the transaction program.