Three local development paths, ordered by friction. Each one puts a TensorCash JSON-RPC in front of you to call with bitcoin-cli or any JSON-RPC client. The bcore functional test suite is the canonical, executable spec for everything below, and every walkthrough links the test it was distilled from.
Core only · docker compose · functional tests
Validation modes
TensorCash adds an external validation step to block acceptance. -validationapi selects the backend that serves it, and it is the most important choice for a local run: it decides whether you need a GPU, a verifier process, or neither.
Flag
What it is
When to use it
-validationapi=real
The default. Talks to an external verifier over the node-to-verifier ZMQ PUSH/PULL channel using FlatBuffers. The production setting.
Needs a real verifier process. Used on mainnet, testnet, and any regtest run that exercises real model replay.
-validationapi=mock
In-process and deterministic. The mock backend exposes three RPCs (validationmockdefault, validationmockclear, validationmockrequests) for canned Quick, Full and Model responses; with the -mockval-default-* startup flags, every verification outcome is scriptable.
The default for the functional test suite. The right choice for driving the chain logic without a verifier or real inference.
-validationapi=desktop
Hybrid. Quick checks run in-process; Full and Model are sent to a local HTTPS verifier (the default desktop binary). No ZMQ broker needed.
Single-machine demos that want a real Quick and Smell pass without operating a separate verifier service.
For a first look at the chain logic, mock is the right answer. The rest of this page assumes it unless stated.
Path A · core only, with mock validation
The lowest friction. One C++ daemon: no docker, no GPU, no model files on disk. Enough for every walkthrough on this page.
1. Build the daemon
Follow the Bitcoin Core build instructions against services/core-node/bcore/. The TensorCash code builds under the same CMake target as upstream; there is no separate flag.
2. Start a regtest node
These flags mirror what test_framework/test_tensorcash.py passes to every functional test, so anything that runs there runs here too. The default mock responses are pinned to green, so block acceptance is deterministic.
Authentication uses the cookie file at $HOME/.tensorcash-regtest/regtest/.cookie, which bitcoin-cli reads automatically when you pass -datadir. The RPC port is the upstream regtest default, 18443.
For when mock is not enough: a real verifier process, a real model serving inference, and the miner API wired in. The repository root has launch scripts for Macs and for Linux with CUDA.
On Apple silicon the launcher pulls a llama.cpp build and brings up the full core-node + miner-api + verification-api compose stack:
The compose file binds host ports 8333 (P2P), 8050 (the core-node REST API) and 7067 (ZMQ). The verifier serves its Verifier REST API on its own container port.
Path C · run the functional test suite
Once the daemon is built (Path A, step 1), the test runner starts throwaway nodes for you. Useful when you want a known-good sequence to copy from rather than a daemon to poke at.
cd services/core-node/bcore
# Single test
build/test/functional/test_runner.py feature_model_registration.py
# All TensorCash-specific tests
build/test/functional/test_runner.py 'feature_model_*' 'feature_asset*' 'feature_fairsign_*'
# All tests, parallelised
build/test/functional/test_runner.py --jobs=$(nproc)
The TensorCash tests group by surface: model lifecycle, native assets, fair-sign adaptors and the covenant repo wallet. Each is a self-contained scenario you can read top to bottom; the walkthroughs below point at the most representative ones.
Walkthroughs
Three short sequences against the mock node from Path A. Each one is a sketch; the linked functional test is the full, executable scenario.
TensorCash-specific. A model is registered by escrowing a deposit, collecting successful Quick and Model verifications across N commits, then moving to registered once the verification window closes. With -validationapi=mock you can drive every step from RPCs, without a real verifier or GPU. This is an outline; the linked test is the full scenario.
TensorCash-specific. registerasset is the high-level wallet RPC that builds the bond and ICU outputs, attaches the issuer registration TLV and broadcasts. After one confirmation the asset can be queried by id or ticker. The full lifecycle (mint, transfer, burn) is in the linked test.