# TensorCash

> Useful proof-of-work for verifiable AI. JSON-RPC fork of Bitcoin Core that
> turns AI inference into chain security; an OSS centralised verifier
> re-validates proof-of-inference claims; a small REST surface fronts the
> miner integration; a ZMQ pub/sub stream surfaces chain events.

This file is the entry point for AI agents and indexers. The structured
machine contracts below are the authoritative artefacts — `openrpc.json`,
`openapi/*.json`, and `zmq_topics.yaml` are generated from source and live
in CI. Prose pages are derivative.

## Machine contracts

- [JSON-RPC OpenRPC contract](https://tensorcash.org/openrpc.json) — OpenRPC 1.3.2, 445 methods, 3 populated from live `bitcoin-cli help`, 4 draft (defined in source but unregistered with the dispatcher).
- [OSS verifier OpenAPI](https://tensorcash.org/openapi/verifier.json) — OpenAPI 3.1.0, 32 endpoints, grouped under verifier-ladder rungs (full / model / pow / quick / quick-smell / logits / challenge), status polling, health. JSON-mirror endpoints reference the FlatBuffer-derived `proof_*` schemas in `components.schemas`.
- [core-node REST OpenAPI](https://tensorcash.org/openapi/core_node.json) — OpenAPI 3.1.0, 6 endpoints. Miner-facing: model metadata + node metrics. Port 8050 in production.
- [FlatBuffer IDL — proof.fbs](https://tensorcash.org/schemas/proof.fbs) · [validation.fbs](https://tensorcash.org/schemas/validation.fbs) · [blockheader.fbs](https://tensorcash.org/schemas/blockheader.fbs) — binary contract for verifier `/v1/verify/*` endpoints (request body) and the bcore↔verifier ZMQ PUSH/PULL channel.
- [JSON Schema (from .fbs)](https://tensorcash.org/schemas/json/proof.schema.json) · [validation](https://tensorcash.org/schemas/json/validation.schema.json) · [blockheader](https://tensorcash.org/schemas/json/blockheader.schema.json) — generated by `flatc --jsonschema`, draft 2019-09. Same types are spliced into `openapi/verifier.json` under `components.schemas` for typed JSON-mirror bodies.

## Docs surface (HTML)

- [Regtest guide](https://tensorcash.org/docs/regtest/) — three local-development paths (bcore-only with mock validation, full docker-compose stack, bcore functional test suite) plus end-to-end walkthroughs for model registration and asset issuance. The fastest way to start is bcore-only with `-validationapi=mock` (no GPU required).
- [JSON-RPC reference](https://tensorcash.org/docs/rpc/) — three-pane Astro shell over `openrpc.json`. 445 methods organised into 12 buckets (mining, model, reorg, cosign, assets, contracts, pricing, postquantum, vaults, adaptor, btc).
- [OSS verifier API](https://tensorcash.org/docs/verifier/api/) — Scalar render of the verifier OpenAPI.
- [core-node API](https://tensorcash.org/docs/core-node/api/) — Scalar render of the small REST surface.
- [ZMQ topics](https://tensorcash.org/docs/zmq/) — pub/sub topic catalogue (Bitcoin-Core inheritance) with frame layout per topic and Python/Node subscriber examples. Distinct from the bcore↔verifier PUSH/PULL channel, which carries FlatBuffer payloads documented at /docs/schemas/.
- [FlatBuffer schemas](https://tensorcash.org/docs/schemas/) — IDL + JSON Schema overview for `proof.fbs`, `validation.fbs`, `blockheader.fbs` with `flatc` codegen recipes.
- [llms-full.txt](https://tensorcash.org/llms-full.txt) — concatenated method content for agents that prefer one bulk fetch.

## Workflows

- `run-a-miner` — Register a model, point a miner at it, and start producing proof-of-inference blocks.
- `issue-an-asset` — Register an issuer, mint supply, and send asset units to another wallet.
- `spot-trade` — Discover a counterparty, propose a spot exchange, run a cosign session, and atomically execute.
- `repo-lifecycle` — Lender + borrower negotiate a collateralised loan, open it on-chain, and either repay or default-sweep.
- `forward-lifecycle` — Two parties open a forward delivery contract, then settle via cooperative close, self-delivery, or escrow claim.
- `cross-chain-swap` — HTLC-style swap between TensorCash chain and Ethereum, via cosign coordination layer.
- `post-quantum-signing` — Generate an ML-DSA address, fund it via a normal send, then spend with a PQ signature.
- `operate-a-verifier` — Bring up the open-source verification API, observe the validation queues, and revalidate blocks on demand.

## Provenance

- Generated from source-walk only on the bcore submodule.
- Schemas reflect the running node at last capture; live-help-mismatch drift findings are tracked in the build log.
- Project source: https://git.tensorcash.org/tensorcash/bcore — links into https://tensorcash.org/docs/rpc/ resolve, and `externalDocs.url` references the matching forge blob URL.