Everything below runs against the public Quantus indexer. Nothing here talks to our servers, and none of it can be faked by us — the chain either says it or it doesn't.
THE PROOF STONE#0001 — inscribed and verifiable right now
The first stone is inscribed on the Quantus mainnet. These are the exact values you should get
back:
- Transaction
0x76e997b511f406ac8e67bda3ab54af2ddd135ca422ac173e1628727bf7f623e9
- Block 219,428 · call
System.remark · result Success
- Fee paid by the project 0.000901305957 QTC · payload 292 bytes · magic QTCR · stone 1
- Embedded PNG 235 bytes, sha256
5ed6654eb3469c7c41a79604caac6aff3b0d43b68118ee7944a888354c2e85b8
Explorer:
the transaction ·
block 219,428
THE COMMANDRead the stone out of the chain
curl -s https://sqm.quantus.com/v1/graphql \
-H "Content-Type: application/json" \
-d "{\"query\":\"{ extrinsic(where: {hash: {_eq: \\\"0x76e997b511f406ac8e67bda3ab54af2ddd135ca422ac173e1628727bf7f623e9\\\"}}) { block_id pallet call success fee args } }\"}" \
| python3 -c "import sys,json,hashlib
d=json.load(sys.stdin)[\"data\"][\"extrinsic\"][0]
a=d[\"args\"] if isinstance(d[\"args\"],dict) else json.loads(d[\"args\"])
raw=bytes.fromhex(a[\"remark\"][2:]); png=raw[48+raw[47]:]
print(\"block\",d[\"block_id\"],\"| call\",d[\"pallet\"]+\".\"+d[\"call\"],\"| ok\",d[\"success\"])
print(\"magic\",raw[:4].decode(),\"| stone\",int.from_bytes(raw[5:7],\"little\"))
print(\"owner\",raw[7:39].hex())
print(\"png\",len(png),\"bytes | sha256\",hashlib.sha256(png).hexdigest())"
Expected output ends with png 235 bytes | sha256 5ed6654e…c2e85b8
Prefer it as a script? The same thing is here:
verify_onchain.sh
BYTE BY BYTEWhere each field sits
offset size field
0 4 magic "QTCR"
4 1 version
5 2 stone number (little-endian)
7 32 owner account id
39 8 price in plancks
47 1 mime length (9)
48 9 "image/png"
57 … the PNG itself
To see it as an image: take the bytes from offset 57 onward, save them as a
.png, and open the file. That is the stone, exactly as it lives on-chain.
WHAT THE CHAIN CARRIESRead it from the source
Every transaction on
Quantus is public and signed with post-quantum keys: its hash, call, block, signer, fee and result stay
readable forever — no account, no key, no permission needed.
Who wrote it. Every QTCrocks record is carried by a transaction signed with the
project's treasury key — one public address, checkable in any explorer:
qzmhVLEuLt4Lqy9dm9D6K4CVvdCkiXG7FS3aZ7PYSDprW7srb. Anyone can write bytes that look like a
record; only records signed by that key are ours, and only those are shown here.
Which record counts. A stone number can appear in more than one transaction
over time — the first pieces were inscribed while the collection was being built, and every stone that
changes hands is written again, for its new owner. Ownership is always the newest record for that
number: the one in the highest block. Everything older stays on the chain as history, readable forever,
and this page always shows the current one.
This page reads the very source the network serves — the public indexer — and turns the
remark payload back into a picture. The payment transaction is your receipt; the payload inside it is the
proof of the stone.
FIND ANY STONEThe query behind it
POST https://sqm.quantus.com/v1/graphql
{ extrinsic(where: { call: { _eq: "remark" } },
order_by: { block_id: desc }, limit: 20) {
block_id hash signer_id args } }
No key, no login, no rate-limit contract. Every QTCrocks inscription begins with the
hex 51544352 — that is "QTCR" — so you can also filter on it to see the whole series.
