1. Create a wallet, choose a unique local name and password, and save the 12-word recovery phrase offline.
2. Use Send to choose HLX or a held custom token, enter the recipient address and amount, then submit the signed transaction.
3. A submitted transaction stays pending until a miner confirms it. Its sender may cancel it from Send while it is still pending.
4. History shows this wallet's transactions. Activity shows confirmed transactions from every wallet, newest first.

1. The Dashboard shows your total wallet value priced in HLX (your HLX plus every held token converted through its pool price), since HLX is the stable unit of account. Token lists — on the Dashboard, in My Tokens, and in Discover — show one asset per line, and the HLX row shows exactly how much HLX you hold.
2. Open Tokens > Create Token and provide an HTTPS metadata JSON URL with name, symbol, description, and image fields.
3. The MNT address identifies the token. The DAD address is the authority allowed to mint more supply, burn supply, transfer authority, or revoke it permanently.
4. After creation is mined, use Management to mint supply, transfer, or Burn. Only the DAD authority can mint or burn; burning permanently destroys tokens from the DAD's balance and lowers the total minted supply.
5. Discover lists HLX and every confirmed token. A DAD can create a market by locking HLX plus its entire confirmed token balance; anyone can then buy or sell through the pool.
6. The dedicated Swap tab atomically trades one token for another, routed through both tokens' HLX pools. Quotes include both 0.3% pool fees, and a 1% slippage guard protects each trade.
7. Token price uses OHLC candlesticks. Choose the candle interval — Minute, Hour, Day, Month, or Auto — and set exactly when the chart starts with the Start date-and-time picker. Cropping the start rescales the vertical axis so small values stay readable next to large ones. Drag to pan, scroll to zoom, drag the corner to resize, and double-click to reset. Rising candles are green and falling candles are red.

1. Install Python 3.11 or newer and extract helix-node.zip (or open the project folder).
2. Create and activate a virtual environment. Windows: python -m venv .venv then .venv\Scripts\activate.bat. Linux/macOS: python3 -m venv .venv then source .venv/bin/activate.
3. Install dependencies: pip install -r requirements.txt.
4. Pick a stable admin API key once and reuse it on every launch — generate one with python -c "import secrets; print(secrets.token_hex(32))". Do not generate a new key each time: the identical value must also live in Cloudflare Pages, or the website cannot connect.
5. Set the key in the same terminal, then start the node. Windows: set HELIX_ADMIN_API_KEY=YOUR_KEY then python run_node.py. Linux/macOS: HELIX_ADMIN_API_KEY=YOUR_KEY python run_node.py.
6. Confirm http://127.0.0.1:8000/health returns node JSON. The same address also serves this wallet locally. Add peers from the Nodes tab or config.json.

1. With the node running, start a tunnel: cloudflared tunnel --url http://localhost:8000. A quick tunnel needs no domain, but its https://xxxx.trycloudflare.com address changes every time it restarts.
2. Verify the tunnel: open https://YOUR-URL.trycloudflare.com/health and confirm it returns node JSON. Optionally, email a working tunnel URL to jackson.tripp100@gmail.com to have it considered for the shared Helix node list.
3. In Cloudflare Pages → your project → Settings → Variables and secrets (Production scope), set: HELIX_NODE_URL = the current tunnel URL (no trailing slash, no /api; multiple nodes use a JSON array); HELIX_ADMIN_API_KEY = the exact same key as the node (choose Encrypt); and optionally HELIX_ENABLE_ADMIN_API = true to allow mining/admin actions through the site.
4. Deploy to the production branch. Pages bakes variables into a deployment, and a deploy tagged with a non-production branch only creates a preview (<branch>.helixwallet.pages.dev) — the live site will not change. Deploy with the production branch named explicitly: wrangler pages deploy web --project-name=helixwallet --branch=main. Use whatever Settings → Builds & deployments → Production branch shows for --branch.
5. Open https://helixwallet.pages.dev/api/health. It should return the same node JSON, and the wallet will connect on reload.

1. Extract helix-miner.zip, install Python 3.11+, then run python -m pip install -r requirements.txt.
2. Start it with python helix_miner.py.
3. Enter the 40-character reward wallet address and one or more reachable node URLs. The miner needs no admin API key. It checks for competing blocks about once per second and logs each round's elapsed time.
4. For NVIDIA CUDA 13, install python -m pip install -r requirements-nvidia.txt, then select NVIDIA CUDA. CUDA 12 users should install cupy-cuda12x[ctk] instead.
5. Choose the CPU worker count or NVIDIA device and start mining. The first valid submitted proof wins the block and the protocol pays the current reward.

• NVIDIA CUDA-capable GPUs with compute capability 3.0 or newer, provided the installed NVIDIA driver and selected CUDA runtime still support that card.
• Modern GeForce RTX, NVIDIA RTX/Quadro, Tesla, and data-center GPUs are typical compatible families. Your RTX 4050 has been hardware-tested with Helix.
• CUDA 13 uses cupy-cuda13x[ctk]; CUDA 12 uses cupy-cuda12x[ctk]. Run nvidia-smi to see the driver-reported CUDA version.
• Windows and Linux are supported by the official CuPy wheels. The current miner uses the first NVIDIA GPU and does not combine multiple GPUs.
• AMD, Intel, Apple Silicon, and other non-CUDA GPUs are not supported. CPU mode remains available on those systems.

Difficulty resets once to 3 at block 161. It stays at 3 through block 170, then resumes automatic adjustment every 10 blocks using a 160-second target. A solution may take more or less than the target because proof-of-work is probabilistic.

A pool lets several miners combine hashrate and share block rewards, so payouts arrive more steadily than solo mining. Anyone can host one.

1. Set the pool's payout wallet as an environment variable — its 12-word seed: Windows set HELIX_POOL_SEED=word word ... word, Linux/macOS export HELIX_POOL_SEED="word word ... word". This wallet receives block rewards and sends the split to miners, so keep it funded for fees and back it up.
2. Point the pool at a reachable node with HELIX_POOL_NODE (default http://127.0.0.1:8000). Optionally set HELIX_POOL_FEE_PERCENT (default 1), HELIX_POOL_SHARE_SUBTRACT (share difficulty = network difficulty minus this, default 2), and HELIX_POOL_PORT (default 8100).
3. Start it: python run_pool.py. Confirm http://127.0.0.1:8100/pool/info returns the pool address and difficulty.
4. Expose the pool the same way as a node — a cloudflared tunnel or public host — and share that URL with miners. /pool/stats shows live shares, each miner's estimated hashrate, and recent payouts.

1. Open Helix Miner and set Mining mode to Pool.
2. Enter the Pool URL and your 40-character reward address, choose CPU or NVIDIA, and Start.
3. You mine at the pool's reduced share difficulty and submit shares continuously. When any member solves a block, the reward is split proportionally to the shares each miner contributed (minus the pool fee) and paid automatically to your address — more hashrate means more shares means a larger payout. Payouts are on-chain transactions and confirm once a block is mined.

• Reward schedule: 10 HLX for blocks 0-89, 2 HLX for blocks 90-299, and 10 HLX from block 300 onward.
• Historical difficulty rules remain valid through block 160. Difficulty resets to 3 at block 161, stays at 3 through block 170, and can adjust again beginning at block 171.
• From block 161 onward, the target average is 160 seconds. A completed 10-block window below 80 seconds raises difficulty by one; a window above 160 seconds lowers it by one.
• Maximum native supply: 20,000,000 HLX.
• Atomic token swaps activated at block 200 (protocol 10). Token-to-token trades route through both HLX pools.
• The DAD token-burn feature requires every node to run the updated build; nodes on older code reject token_burn transactions, so upgrade all nodes together before relying on it.
• At block 300, 9d7c721b209cee99a8158c524fa433ead9236781 becomes the native HLX DAD governance identity. It cannot mint; all new HLX remains mining-only.
• Before upgrading or copying chain data, stop the node and back up its database.
• Use python helixctl.py validate to verify the local chain.