Vexon Vexon Docs

Vexon Mining Documentation

Mine VEX with Blake256r14 ASIC hardware.

A practical guide for Vexon wallets, pool connection, ASIC configuration, payout rules, monitoring, and server-side operations.

Start mining Open wallet Pool dashboard
Pool port4499
Worker nameVEX_ADDRESS.worker
Password123
Minimum payout0.001 VEX
Payout windowDaily 08:00 CST

Quick Start

Five-minute mining checklist

Vexon
  1. Create or import a Vexon wallet at wallet.vexonus.com.
  2. Back up the 24-word mnemonic offline. Never send it to pool support or paste it into chat.
  3. Copy your VEX receiving address. It is the mining username.
  4. Configure your ASIC pool URL as stratum+tcp://pool.vexonus.com:4499.
  5. Set username to YOUR_VEX_ADDRESS.001 and password to 123.
  6. Wait for accepted shares on the pool dashboard, then check payout eligibility after block maturity.

Wallet

Create, secure, and use a VEX address

Create a new wallet

Open the web wallet, choose a strong password, and save the generated mnemonic in order. The password unlocks the local browser wallet; the mnemonic restores the wallet if the browser data is lost.

  • Use at least 10 characters.
  • Include uppercase, lowercase, and numbers.
  • Do not use simple passwords such as 123456.
  • Store the mnemonic offline, preferably on paper or in a hardware password vault.

Use for mining

The pool identifies miners by VEX address. Worker names are appended after a dot, so one wallet can track multiple ASICs.

VEX_ADDRESS.001
VEX_ADDRESS.D1
VEX_ADDRESS.DR5

Never use your wallet password as a miner password. The miner password can stay 123.

ASIC Setup

Configure WhatsMiner D1 or Antminer DR5

Field Value Notes
URL stratum+tcp://pool.vexonus.com:4499 Some firmware accepts pool.vexonus.com:4499 without the scheme.
Algorithm Blake256r14 D1 and DR5 must be on Blake256r14-compatible firmware mode.
Worker VEX_ADDRESS.worker Example: Vs...cQV.001
Password 123 Used only by Stratum. It is not your wallet password.
Difficulty Pool managed Start with the default. Fixed difficulty is only for firmware that requires it.
WhatsMiner D1 40 TH/s

Recommended for stable Blake256r14 mining. Keep firmware, fan, and PSU status healthy before troubleshooting pool-side issues.

Antminer DR5 35 TH/s

Use the same pool endpoint and worker format. Confirm accepted shares before judging hashrate from the pool dashboard.

Rewards

Estimate daily VEX output

TH/s
TH/s
Estimated daily reward Calculating...

This is an estimate. Real rewards depend on network difficulty, pool luck, rejected shares, block maturity, and payout schedule.

Payouts

When miners receive VEX

1

Miner submits accepted shares to Vexon Pool.

2

The pool finds a VEX block and waits for maturity.

3

Rewards are credited after block maturity and accounting checks.

4

Balances above 0.001 VEX are paid daily at 08:00 CST.

Small balances remain on the pool account until they reach the minimum payout. If a wallet address is mistyped, the pool cannot recover funds sent to that address.

Monitoring

How to confirm your miner is working

Connected minerWorker appears

The worker table should show your IP, worker name, firmware version, and last seen time.

Accepted sharesIncreasing

Accepted shares confirm that the miner is sending valid work to the pool.

Reject rateNear 0%

High rejection usually means firmware, difficulty, or stale job timing needs attention.

Pool hashrateDelayed

Pool hashrate is estimated from shares and may lag the ASIC dashboard.

Troubleshooting

Common mining problems

Miner connects but no accepted shares

Check that the ASIC is in Blake256r14 mode, the username is a VEX address plus worker suffix, and the pool port is 4499. Allow several minutes for low-frequency share accounting.

Pool dashboard hashrate is lower than ASIC hashrate

The pool estimates hashrate from accepted shares. Short windows are noisy, especially when difficulty is high. Compare over 15 to 60 minutes before changing settings.

Too many rejected shares

Use the default difficulty first. If the miner firmware forces fixed difficulty, test one value at a time and watch accepted/rejected share counts.

No payout yet

Confirm that your balance is above the minimum payout, blocks are mature, and the pool wallet service is online. Payouts are scheduled daily at 08:00 CST.

Operators

Server-side pool commands

For Vexon Pool operators, the deployment package installs the pool under /opt/vexon-pool and keeps it separate from any other pool on the same server.

cd /root/vexon-pool-deploy
bash scripts/status.sh
bash scripts/deploy-web.sh
bash scripts/health-check.sh
bash scripts/miner-watch.sh
bash scripts/miner-watch.sh 222.86.244.202
bash scripts/payout-status.sh
bash scripts/payout-closed-loop-check.sh
bash scripts/start-pool.sh
bash scripts/stop-pool.sh

Typical service checks:

ss -lntp | grep -E '4499|18555|18556'
tail -100 /opt/vexon-pool/stratum-config/vexon.log
curl -I http://127.0.0.1 -H 'Host: pool.vexonus.com'

Health gate

Before opening the pool publicly, confirm node RPC, local peers, Stratum, recent shares, explorer HTTP, and payout rows with scripts/health-check.sh.

Miner watch

Use scripts/miner-watch.sh MINER_IP during ASIC testing to inspect TCP sessions, worker rows, accepted shares, estimated hashrate, and Stratum logs.

Payout gate

Use scripts/payout-status.sh to review balances above 0.001 VEX, mature earnings, recent payout transactions, and failed payout rows. Use scripts/payout-closed-loop-check.sh before launch to verify wallet RPC and automatic payout readiness.

Web deploy

After UI or docs changes are synced to the server, run sudo bash scripts/deploy-web.sh to publish files and restore runtime permissions.

Production backup

Create a private archive before upgrades with sudo bash scripts/backup-production.sh /root/vexon-pool-production.tar.gz.

Service mode

Launch with screen first. After stable shares and a clean health check, switch to systemd using sudo bash scripts/install-systemd.sh --enable-now.

The pool status API for monitoring dashboards is https://pool.vexonus.com/api/pool. It returns public telemetry only and does not expose RPC passwords or wallet keys.

Security

Protect wallets and infrastructure

  • Never publish wallet seeds, RPC passwords, database passwords, or TLS keys.
  • Use HTTPS for wallet, pool, and docs domains.
  • Keep pool database backups encrypted and offline.
  • Restrict node and wallet RPC ports to localhost unless there is a deliberate firewall plan.
  • Rotate deployment credentials after sharing temporary server access.