QuaiAxe miner configuration
The QuaiAxe mining page builds worker settings from the
selected miner type, the user's disclosed payout address, and a nickname. The source-of-truth
builder is holding/miner-config.js; the product page calls it after the disclosure gate and does
not assemble the worker name itself.
Use the page
- Select the type that matches your device: Bitaxe/SHA-256, Scrypt, or GPU/KawPoW. The page starts with Bitaxe selected, so check the selection rather than assuming it has detected your hardware.
- Choose the burn share. Enter a valid Cyprus-1 payout wallet if a share is kept, then enter a
2-20 character nickname using letters, numbers,
_or-. - Read the fee, lock, and one-way-burn warnings. Accept the explicit consent checkbox and press Show my mining address. Until those checks pass, the derived address and worker string stay hidden.
- Copy the displayed host, port, worker and password into the miner. The generated worker format
is
<payout-address>.QAXE_<nickname>; the pool parses the payout address before the first dot. Use the page output rather than copying a static sample.
The Live page badge means the address-derivation configuration is present. It does not check
that a pool is reachable, that a miner accepts a particular driver/software version, or that a
reward has arrived.
Compatibility and payout evidence
Quai's current mining information lists KawPoW for GPUs, SHA-256 for ASICs, and Scrypt for ASICs. Quai's StratumX guide describes standard-Stratum-compatible mining and recommends a dedicated QUAI wallet; it says exchange addresses are unsupported. These broad algorithm families do not certify a particular GPU/ASIC model, firmware, driver, or miner release.
The repository tests pin the settings the current builder emits. This is source/test evidence,
not a live endpoint check. In the current source, endpoint.verified means a payout to a contract
address has been observed; false means that proof is absent, not that the endpoint is down.
Neither the page badge nor generated settings establish endpoint health or a successful reward.
Do not switch algorithms automatically, fall back to CPU, invent a host/port or miner flags, or bypass an operating-system security warning. If exact device/software compatibility is not covered by current official material, label it unverified.
Maintainers with access to the QuaiAxe source repository can use its agent-facing workflow at
.agents/skills/qaxe-miner-configuration/SKILL.md. This public guide contains the user-facing
setup and evidence boundaries without depending on repository access.