HartiiLabs docs

HartiiLabs

Receipts

Receipts is a public page at hartiilabs.com/receipts, live in Labs 1.54.0. It lists what is deployed so anyone can check it against the chain instead of taking a claim on trust. It is read only: it has no wallet connection and nothing on it signs or sends a transaction.

What it shows

  • This build. The Labs version and commit that are serving the page, and, from Labs 1.75.0, the hash of the signed build manifest and the id of the key that signed it (a dash if the manifest cannot be read). See Verify the website.
  • Releases. Every tagged release since v1.42.0, each with its date and commit. Versions 1.40.0, 1.41.0, 1.43.0 and 1.44.0 shipped without a tag and are not listed.
  • Contracts. The core mainnet contracts Labs uses (launch factories, HartiiSwap, LP locker, agent vault factory, QuaiRelay, Boost, Subscriptions), with code size, code hash and a Quaiscan link. Not every address Hartii has deployed.

The data is regenerated by scripts/gen-receipts.mjs before each release, so the page matches the tagged build it ships in. To check a row yourself, call quai_getCode for the address on Cyprus-1, confirm the code is non-empty and compare its size and hash with the page.

Verify the website

From Labs 1.75.0, hartiilabs.com publishes a signed list of every file in the build it serves. This is a defence against a tampered web update: you can check that the code your browser receives is a release Hartii signed.

  • Manifest: https://hartiilabs.com/.well-known/hartii-build.json (format hartii-web-build/v1: the version, the commit and the sha256 of every file in the build).
  • Signature: https://hartiilabs.com/.well-known/hartii-build.json.sig, an ed25519 signature over the manifest.
  • Key: the web release key, id a17f68595150dac6. The public key is built into the Hartii CLI, which is itself a signed release, so the check does not depend on a key that the website provides.

Run the check with the CLI (CLI 0.7.0 or newer):

bash
hartii verify-site
hartii verify-site --json   # { ok, version, commit, keyId, checked, failures }

It verifies the signature, compares the sha256 of every listed file that is not an HTML page with what the site serves, and requires the home page to reference only signed scripts and styles. It exits 0 only when every check passes and 1 otherwise. See CLI 0.7.0.

What is covered, and what is not. Scripts, styles, images and other files are compared byte for byte. HTML pages are not: the site rewrites each route's HTML for link previews, so the bytes differ by route. The home page is checked by the scripts and styles it loads instead. The check reports a mismatch; it cannot repair one. It does not review the code or the contracts, and it is not a safety verdict on any token.

Official addresses. The list of official Hartii websites, downloads and release keys is at hartii.org/official. Every Hartii site also publishes /.well-known/security.txt, which says where to report a security problem.

Contracts listed

Addresses are checksummed. Code was confirmed non-empty with one quai_getCode call per address against the Cyprus-1 RPC, verified 2026-11-06.

ContractAddressCode present
TokenFactoryV50x003fb8428777cDFED5de367519818D4240b08A12Yes, 6,889 bytes (verified 2026-11-06)
TokenFactoryV40x005566187B52313e03978C2caF4BE1a0A88eb90AYes, 6,739 bytes (verified 2026-11-06)
HartiiSwap factory0x002E75653C6189087Eb9E512cE7319eC21140956Yes, 9,908 bytes (verified 2026-11-06)
HartiiSwap router0x006B3450cca780066A3A8aA8b508103d25315Ea4Yes, 13,483 bytes (verified 2026-11-06)
SubscriptionFactory0x007420f8fDfBa7048bB04c8B87DE12Df49176665Yes, 11,043 bytes (verified 2026-11-06)

The sizes above are the deployed runtime code length at the time of the check. The code hashes are on the Receipts page itself; this page does not copy them, because the page is regenerated each release and is the source. Release tags and commits are likewise only on the Receipts page.

See also Contract reference and Versions.

Quai Network mainnet · chain 9 · Cyprus-1. Figures marked "read on" a date were read from the chain that day; re-read before relying on them.