How to create a flight sheet in HiveOS? (Wallet Config)

Understanding Wallet Configuration in HiveOS

1. HiveOS requires precise wallet configuration to ensure mined cryptocurrency is directed to the correct destination address. This step occurs during rig initialization or when editing miner settings in the web interface.

2. The wallet field accepts a valid cryptocurrency address compatible with the selected coin and algorithm. For example, ETH mining requires an Ethereum address starting with “0x”, while RVN uses a Ravencoin address beginning with “R”.

3. HiveOS does not validate wallet addresses in real time. Users must verify correctness before saving—typos or incorrect network prefixes result in permanent loss of rewards.

4. Some pools require additional identifiers such as worker names or payment IDs. These are appended using specific delimiters like dot (.), dash (-), or colon (:), depending on pool documentation.

5. Multi-algo switching rigs demand wallet fields aligned with each coin’s native format. A single misconfigured wallet for one coin can halt payouts across the entire switching profile.

Accessing the Wallet Field via HiveOS Dashboard

1. Log into the HiveOS dashboard and navigate to the target rig’s Miner Config tab.

2. Select the active mining profile or create a new one under Profiles → Edit.

3. Locate the Wallet input box—typically placed near pool URL, port, and user fields.

4. Paste the full wallet address without spaces or extra characters. Do not include “wallet=” or similar prefixes unless explicitly required by the pool.

5. Save changes and reboot the rig to apply the updated wallet configuration across all miners.

Wallet Syntax Rules for Major Coins

1. Ethereum (ETH): 42-character hexadecimal string prefixed with “0x”, e.g., 0x742d35Cc6634C0532925a3b844Bc454e4438f44e.

2. Ravencoin (RVN): Base58-encoded address beginning with “R” or “X”, up to 34 characters, e.g., RJvKuVtLZqkQmGjFzDwYyHnWpTcXrSvBmN.

3. Bitcoin (BTC): SegWit (bc1q…) or legacy (1… or 3…) format accepted depending on pool support—never use testnet addresses.

4. Kaspa (KAS): Must be a Kaspa address starting with “kaspa:” followed by a Bech32 string, e.g., kaspa:qz9g4z7xv2f8p3n5t6y7u8i9o0p1a2s3d4f5g6h7j8k9l0.

5. Flux (FLUX): Zcash-style transparent address (t1…) or unified address (zflux…); HiveOS supports both but pools may restrict usage.

Common Wallet-Related Errors in HiveOS

1. “Invalid wallet address” warnings appear only if HiveOS detects obvious formatting issues like missing prefix or non-hex characters in ETH fields.

2. Payout failures often trace back to mismatched address types—e.g., submitting a BTC mainnet address to an LTC pool API endpoint.

3. Using exchange deposit addresses with withdrawal locks or two-factor requirements prevents automatic transfers from pools.

4. Copy-paste artifacts such as invisible Unicode spaces or smart quotes break wallet recognition silently—always paste into a plain-text editor first.

5. HiveOS caches wallet values per profile; changing the wallet in one profile does not update others—even if they share identical pool settings.

Frequently Asked Questions

Q: Can I use a hardware wallet address directly in HiveOS?A: Yes, provided it is a standard receive address compatible with the mining pool. Hardware wallets generate valid public addresses—just ensure the coin type matches the mining algorithm.

Q: Does HiveOS support sub-wallets or tagging for shared mining operations?A: HiveOS itself does not manage sub-wallets. Tagging is handled at the pool level via worker names or custom identifiers appended to the wallet field.

Q: What happens if I change the wallet after a mining session has started?A: Pending shares remain tied to the previous wallet until the pool processes the shift. Most pools require a few minutes to register the new destination, and some enforce minimum payout thresholds before sending.

Q: Is it safe to store private keys in HiveOS?A: No. HiveOS never requests or stores private keys. Wallet configuration involves only public addresses used for receiving funds.