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. Open Tokens > Create Token and provide an HTTPS metadata JSON URL with name, symbol, description, and image fields.
2. The MNT address identifies the token. The DAD address is the authority allowed to mint more supply, transfer authority, or revoke it permanently.
3. After creation is mined, mint supply from Management. Tokens become visible from confirmed blockchain state.
4. Discover shows HLX and every confirmed token. A DAD can create a market by locking HLX and its entire confirmed token balance; users can then buy or sell against the pool.

1. Install Python 3.11 or newer and extract helix-node.zip.
2. Open a terminal in the extracted folder and run python -m venv .venv.
3. Install dependencies with .venv\Scripts\python.exe -m pip install -r requirements.txt on Windows, or .venv/bin/python -m pip install -r requirements.txt on Linux/macOS.
4. Set a persistent, private HELIX_ADMIN_API_KEY, then start with .venv\Scripts\python.exe run_node.py. Do not generate a new key on every launch.
5. Open http://127.0.0.1:8000/health. Add synchronized Helix peers in the Nodes tab or in config.json.

Other nodes may use different admin keys. The key protects local administrative endpoints and is not part of consensus or shared chain data.

1. For temporary testing, run cloudflared tunnel --url http://127.0.0.1:8000. No port forwarding or personal domain is required.
2. Confirm https://YOUR-URL.trycloudflare.com/health returns healthy node JSON, then email the TryCloudflare URL to jackson.tripp100@gmail.com so it can be considered for the Helix node list.
3. Put the resulting HTTPS URL in the Pages HELIX_NODE_URL variable. Multiple nodes use a JSON array such as ["https://node1.example","https://node2.example"].
4. Redeploy Pages after changing variables. TryCloudflare URLs expire when the tunnel stops, so replace them when necessary.
5. For a permanent public node, use a named tunnel, TLS, firewall rules, backups, rate limits, and trusted peers.

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.
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.

• 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.
• All nodes must upgrade to protocol 9 and restart before mining or accepting block 161.
• 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.