Quantus QTC mining on Mac: mainnet sync and monitoring
Quantus mainnet is not the retired Planck testnet. On a Mac, wait until the node log moves from Syncing to Idle at the current tip before the miner should be producing. This site reads indexed mainnet block rewards only. It does not install a node or read local hashrate.
| What you see | What it means | Next step |
|---|---|---|
| Log still says Syncing | Not at the mainnet tip | Wait for Idle; orphans earn nothing |
| Data under planck | Retired testnet, not this index | Switch to mainnet; do not copy the old database |
| Miner exits immediately | Usually a version or auth mismatch | Match quantus-miner/2 and the auth files |
| Monitor has height, address has no reward | The network is producing blocks | Check the public wormhole address |
Confirm the mainnet tip
On a Mac, Quantus mining starts with a node that has reached the current mainnet tip, then a miner attached to that synced node. The official mining guide says to use --chain mainnet, not --chain planck. Planck is the retired public testnet. Mainnet does not share its history, database, or rewards. The node must be v1.0.1 or newer; older binaries do not include the mainnet chain spec. Apple Silicon uses the aarch64-apple build; Intel Macs use x86-apple. Linux ARM64 has no official native quantus-miner release; that path does not apply to this Mac.
The Quantus monitor shows index fields: chain height, the count of addresses historically recorded with mining rewards, account count, and recent indexed blocks with height, time, and reward. Those numbers are not Activity Monitor. The index does not supply a network hashrate. A gap appears only between consecutive heights in the fetched window. That gap is a sample, not a protocol block target and not your share. The public website’s proof-of-work wording, supply-cap narrative, and active-miner figure are that site’s own statements. They are not the monitor’s count of online machines, and they do not convert into your daily income.
Figures on the monitor
Check the Mac locally. This website cannot read the log.
- The chain must be mainnet, with data under
chains/mainnet/, not a reusedchains/planck/database. - When migrating, the official guide says you may keep the same wormhole inner hash so rewards stay on the same address. The installer
--forcepath refreshes binaries and keeps that inner hash. It does not copy Planck chain data. - Sync is complete when the log switches from Syncing to Idle at the current tip. Blocks found before that are orphans and earn nothing.
- The miner pauses automatically if the node has no peers. The guide expects roughly 15 minutes to a couple of hours, depending on hardware and connection.
- If sync stalls with Verification failed and the peer count drops to zero, the guide attributes that to a node version out of step with the network. Check the release the network is using.
Node and miner must be a matching pair. Authenticated builds use the ALPN quantus-miner/2. The setup script passes auth flags only when both sides support miner QUIC auth. A mixed pair fails the handshake. Older pre-auth releases omit those flags. GPU mining is the recommended host path so the miner can use Metal. That is a setup preference, not a payout promise. Do not pass --force-authoring to join mainnet; the guide limits that flag to bootstrapping a new network. The comparison below is the branch to follow.
When sync is not finished
Illustrative example: the Mac process is alive, the log still says Syncing, and the local height sits far below the height on the monitor. Under the official guide those local finds are orphans and are not QTC rewards. The monitor continuing to list other indexed blocks is expected. Wait until Idle at that tip, then confirm the wormhole public address printed at node start is the one you saved.
If the node is still syncing, wait for the tip instead of reading fan or GPU load as blocks. If the handshake fails, pin node and miner to one release pair. When the public address is ready, read what today and lifetime mean in wormhole rewards. If the row stays empty, use no rewards. This site does not install or stop the node, does not read logs under the macOS application-support chain directory, and the on-page agent does not operate Quantus. Free keeps three saved devices per project, and Pro keeps 100. An address that only appears in a list does not add a device. A separately saved device record does, and extra sources on the same saved device do not add another slot. A separate crash analysis does not change the sync conclusion.
Common questions
Does a running Mac process mean QTC mining has started?
No. The official guide requires the node to reach the mainnet tip (Idle in the log). Blocks before that are orphans and earn nothing.
Do Planck balances appear on this mainnet page?
No. The project states that mainnet does not carry Planck history or rewards. This page reads the mainnet index only.
Is the height on the monitor my Mac’s mining progress?
No. It is the chain height in the mainnet index. Whether your machine is synced is the local log showing Idle at that tip.