Frequently asked questions

The project

Is RQT worth anything? No. Requant runs only as a test network. Test coins have no value, and the chain may be reset when the rules change. There is no main network, no sale and no premine.

Is the mining useful AI work? No. TNet uses AI hardware the way AI does, multiplying int8 matrices on tensor cores, but its inputs and weights are random. No model is trained or served.

Is it ASIC-resistant? Not established, and Requant does not claim it. A chip built only for int8 matrix products is effectively an AI inference chip; how much faster it could be than existing AI hardware is an open question (open questions).

How is Requant different from other GPU proof-of-work coins? The work is the tensor-core computation itself (86–88% of an attempt on the measured GPUs), the proof in a block is only 272 bytes, and verification recomputes one row in about 11 ms on a laptop CPU, without a proof system. Spending conditions for swaps and channels are in consensus from the start, and the node ships with an explorer, public API, faucet, pool and signed self-updates. The research record, including failures, is public.

Is matrix-product proof of work new? No. Pearl already deploys an int8 GEMM proof of work with tickets verified by recomputation. TNet borrows that ticket structure and differs in its deep, exactly requantized network (research path).

Who funds development? A development fund receives 6% of each block reward for the first 2,097,152 blocks (about four years at one block a minute), then the rule ends by itself. Fees always go to the miner. There is no premine and no miner fee in CPPminer for Requant (economics).

Mining

Which GPUs can mine? NVIDIA GPUs of the Turing generation or newer: RTX 20, 30, 40 and 50 series, and CMP 30HX–90HX. AMD, Intel and CPU mining of TNet are not supported by CPPminer.

How fast is my GPU? Measured: about 3.6 million tickets per second on a CMP 50HX in CPPminer, 4.5–5.3 million on an RTX 5070 with an earlier build, and about 6.3 million on an RTX 3090 in the research benchmark (measurements). Results depend on the card, power limit, driver and batch size.

How much GPU memory is needed? About 512 MiB for the epoch weights plus roughly 6 × batch × 8192 bytes; the default batch of 8192 rows needs about 400 MiB more. Lower --batch on small cards.

Pool or solo? The pool pays a share of every block it finds, by PPLNS, with a 1% fee and payouts from 1 RQT. Solo mining needs your own node and pays whole blocks when you find them (mining).

Why does my balance show "maturing"? Block rewards become spendable 100 blocks after the block (about 100 minutes). The pool credits balances only after that and only if the block is still on the best chain.

Is there a HiveOS or Docker image? Not with TNet yet. HiveOS and the Docker images of CPPminer cover other algorithms; use the Windows or Linux packages.

Wallets

Which wallet should I use? The Web Wallet and requant-wallet use a 24-word recovery phrase for many addresses. The desktop, Android and extension apps use single keys with an encrypted key-file backup; they do not import phrases (wallets).

Can I sign offline? Yes. requant-wallet prepares a payment on an online machine from a watch-only copy and signs it on a machine without network access; the signer checks the coins against their parent transactions before signing (wallet CLI).

Do wallets send my keys anywhere? No. Keys are generated and used for signing on your device. Nodes and the wallet gateway receive only addresses and signed transactions. A node does learn which addresses you ask about.

Nodes

What does a node need? A 64-bit Linux or Windows machine, about 1 GiB for the current and next epoch weights (kept in a file through the page cache), a few hundred MB of memory for the process, and TCP port 19333 for peers.

How long is synchronisation? The node downloads headers first and then blocks; each block verifies in about 0.1 s. On restart it loads a snapshot and replays only newer blocks.

What does --auto-update do? The node installs newer releases signed with the project's release key after a random delay, checks their hashes and version, and rolls back if a new version fails to start repeatedly. Without the flag nothing is downloaded (node operations).