Joining Parasite Pool involves two separate checks: obtaining the pool's current identity and worker settings, and confirming that your miner submits accepted shares. A dashboard that says “connected” is not enough. Before changing a working miner, save its existing pool configuration so you can restore it if the new connection fails.
Parasite's official Miner Setup Guide, checked on October 29, 2026, lists parasite.wtf on port 42069, with username BTC_ADDRESS.WORKER_NAME. It says the password is not checked. Replace the address placeholder with your own Bitcoin address; do not copy somebody else's address or the site's deliberately invalid example. These are documented settings, not the result of a LeedMiner live mining test.
Confirm the current onboarding route
The current help offers two routes: connect with Xverse, or mine directly with a Bitcoin address ready. Xverse is therefore an option, not a mandatory new-wallet requirement for every miner. For direct mining, obtain your Bitcoin receiving address from your own wallet and check it carefully before using it as the worker prefix. Review fees and payout conditions with the operator separately; the setup fields alone do not establish those terms.
If onboarding asks for a wallet interaction, read its purpose and permissions before proceeding. Never enter a seed phrase or private key into a pool website, miner configuration screen or support chat. A public payout identifier is different from the secret that controls funds. Connecting a miner is also different from making a payment.
Give each device a distinguishable worker name, such as homeMiner. The format is YOUR_BTC_ADDRESS.homeMiner: this is a template, not a valid address. Keep the dot between the address and worker name and remove accidental spaces. A corrupted “email protected” string is not a miner username.
Map the settings to your miner
| Field | What to check |
|---|---|
| Pool host | The official setup guide lists parasite.wtf. |
| Port | Use 42069 for the standard endpoint; keep it separate if the UI has a port field. |
| Protocol | The help shows parasite.wtf:42069 or stratum+tcp://parasite.wtf:42069, depending on the interface. |
| Worker / username | BTC_ADDRESS.WORKER_NAME, with your own address and chosen worker name. |
| Password | The current guide says any password is accepted because it is not checked; avoid reusing a sensitive password. |
Some firmware accepts a combined pool URL; other interfaces separate server and port. Avoid adding the protocol or port twice. The help also lists high-difficulty port 42068 for powerful miners, but gives no numerical switching threshold. Keep the standard endpoint unless the pool's guidance fits your device; a higher-difficulty port is not a guaranteed performance upgrade.
Apply the change and verify accepted work
Make one controlled configuration change. Preserve a copy of the original pool, worker and password values privately; do not publish screenshots containing a personal identifier. Save the new settings using the miner's normal interface. Restart only when the interface or device documentation calls for it.
Then check the miner's connection status, accepted and rejected share counters, and pool-side worker visibility. Accepted work is the useful connection test. A local hashrate number alone only tells you that the miner reports work; it does not prove that this particular pool accepts it. Allow for dashboard aggregation delays rather than changing several fields repeatedly.
Keep pool troubleshooting separate from power tuning: changing frequency and voltage at the same time makes failures harder to isolate. For a Gamma 601, our Bitaxe baseline and tuning checks explain why a documented, stable baseline matters. The photograph above illustrates a small Bitcoin miner; it is not evidence of a live Parasite connection or an endorsement by the pool.
Troubleshoot one layer at a time
| Symptom | First checks |
|---|---|
| No connection | Confirm network access, DNS, hostname and port; compare with the current official help. |
| Authorization rejected | Recheck the complete worker identifier and password rule. Remove accidental spaces. |
| Connected, no accepted shares | Inspect miner logs, time since startup and rejected-share messages; check firmware compatibility. |
| Local shares, missing dashboard worker | Verify that the dashboard is showing the same identity and worker; account for reporting delay. |
Keep a short troubleshooting record: device model, firmware version, settings changed and the exact error message. Share only the minimum needed with support, with personal identifiers redacted. If service details are unclear, restore the known-working configuration instead of following random endpoint suggestions.
Understand what successful setup does not prove
Accepted shares demonstrate that work reaches the pool; they do not guarantee a reward, a payout time or a profit. Current payout rules and fees must be checked with the operator. Electricity, downtime and hardware operating costs remain your responsibility even when no reward is received.
Use the mining cost calculator to explore electricity inputs separately from pool connection checks. Calculated results depend on assumptions and do not promise Parasite payouts. For equipment questions, use LeedMiner's contact page and state the exact model and firmware. Pool account and payout issues belong with the operator's official support.
