Quai developer tools · open source

Serious tools.
Clear operations.

Four small tools for teams building an app on Quai Network. Review a transaction before it is sent, check a deployed contract, watch an indexer, replay a failed call.

A CLI is a tool you run by typing a command.
The examples below are samples. They do not run anything.

Get it on GitHub See what each tool does

Beta 0.1.0-beta.1 · unaudited · MIT licenceNODE 22.14+ · WINDOWS · LINUX

Four tools, one core.

quai-txMOCKUP · SAMPLE DATA

No wallet connected. Nothing is sent.

02 / What this does

Who would use it?

What it does not do

Try a scenario

One shared core

Address validation, RPC boundaries, local evidence and transaction review live in one package. All four tools use it.

What exists today

Recorded checks, not a launch.

These are facts from tests and CI. Last checked 2026-11-12.

Tests35 tests pass locally. CI runs them on Windows and Linux with Node 22 and 24.
pass
CLI help and strict flags8 tests. Every tool refuses an option it does not know.
pass
Transaction safety engine12 tests, including single-use submission and receipt reconciliation.
pass
Four-tool protocol check7 steps against a local test server. No live chain.
pass
Reproducible packages5 packages, byte-identical across Windows and Linux on Node 22 and 24.
pass
Outside useNot yet used by an outside team. Treat it as beta.
none yet

Get it

From GitHub, in four steps.

It is not on npm. You build it from the repository.

Node 22.14 or newerOS Windows or LinuxGit and npm

Clone the repository

Source is open under the MIT licence.

git clone https://github.com/IboTheSecond/hartii-operator-tools.git
cd hartii-operator-tools

Install dependencies
Scripts are not run during install.
```
npm ci --ignore-scripts
```
Run a tool
Prints the commands and options. Use release, watch or replay in place of tx for the others.
```
node packages/tx/bin/cli.mjs --help
```
Optional: build the packages
Builds five tarballs twice, compares their bytes, and writes SHA256SUMS to artifacts/packages. Install the core and the tools you want from those tarballs together.
```
npm test
npm run pack:verify
```

Safety and limits

What it checks, and what it does not.

The tools check and refuse. They cannot promise an outcome on a live network.

Report a security issue

Your keys stay yoursIt never holds a key and has no signing-key option. You sign with your own signer, outside these tools.
Chains and zoneMainnet (chain 9) and chain 15000, on Cyprus-1 only. Other zones, Qi and zero destinations are refused.
The node is trustedThe RPC endpoint you choose is a trust dependency. Chain ID and identity checks do not prove a node is honest.
A failed broadcast is unknownThe same signed bytes may already be in the network. It is never retried automatically. Reconcile with a receipt before sending again.
Beta and unauditedNo outside audit. The upstream quais SDK is pinned to a pre-release, 1.0.0-alpha.54.
Mocks are not proofTests use local fixtures. A passing test is not evidence about a live network.
Local state mattersReservations live in a private folder on your machine. Losing it loses that knowledge. One process should own it.