Fusion is a job manager for hardware, not just a single static miner.
Fusion is the automatic worker system for earning CPAY with CPU and GPU hardware. Instead of forcing one fixed miner or one fixed coin, Fusion checks which supported job fits your device best and routes the work there.
Those jobs can include AI workloads, scientific calculations, encryption tasks and, in special cases, direct CPAY blockchain mining. You start the worker with your Cryptix ID; job selection, benchmarking and payout happen in the background.
Fusion is a job manager for hardware, not just a single static miner.
Because jobs change, Fusion measures contribution with CCPI rather than only hashrate.
Work is written into repeating job blocks, credited first as locked balance, then released.
The simplest description: Fusion is an automatic profit and job-routing system for compute hardware.
Fusion can run different compute jobs. Mining is only one possible route, not the whole product.
CPUs receive CPU-suitable work, GPUs receive GPU-suitable work, so hardware is used where it fits best.
The backend can move your worker to a better task when profitability or hardware fit changes.
Fusion dashboard view with worker activity, payout flow and member-area integration.
Fusion first learns what your machine can do, then keeps checking whether it is still on the right job.
| Step | What happens | Why it matters |
|---|---|---|
| 1 | Start the worker with your Cryptix ID and hardware flags | Fusion knows which account and which device class should be used |
| 2 | A compatible fallback or first job is assigned | The system can benchmark the real performance of your setup |
| 3 | Supported jobs are rechecked for profitability about every 60 seconds | Your worker can be moved to a better task without manual switching |
| 4 | Expected CCPI is reviewed in 5-minute job blocks | Underperforming setups are redirected to jobs where they fit better |
| 5 | Finished work is written to Locked Fusion Balance | Your contribution is prepared for CPAY release inside the member account |
Hashrate works for mining only. Fusion needs one metric that also works for non-mining jobs.
Values like H/s or MH/s make sense for blockchain mining, but not for AI, encryption or scientific workloads.
CCPI is the universal indicator that lets Fusion compare hardware contribution across different task types and convert it into CPAY payout logic.
These timings explain why Fusion does not look instant in the member area even though rewards already started.
| Phase | Timing | Meaning |
|---|---|---|
| Worker visible | About 5 minutes | Your device usually appears in the member area after the first protection and sync window |
| Stable CCPI display | About 10 to 15 minutes | The system needs enough runtime to calculate a reliable first CCPI |
| Locked Fusion Balance | Every 5 minutes | Each job block is paid into locked balance automatically |
| Account balance release | Every 60 minutes | Locked Fusion Balance is released in batches to keep the payout system stable |
Startup delays are compensated after disconnect so users cannot exploit fast reconnect jumping.
Both paths exist in Cryptix, but they are not the same thing.
| Aspect | Fusion | Direct blockchain mining |
|---|---|---|
| Main idea | Automatic job manager that uses supported compute tasks to earn CPAY | Run a specific miner against a blockchain or pool |
| Task choice | The system can switch jobs for you when profitability changes | You stay on the miner and target you selected manually |
| Measurement | CCPI and timed payout blocks | Hashrate, difficulty, shares and block or pool rewards |
| Hardware logic | CPU and GPU are routed to jobs they are good at instead of competing on one metric | Hardware performance depends on the selected mining algorithm and miner support |
| CPAY blockchain | Can be used, but only as one job option and usually only when it is clearly the better route | Is the primary destination from the start |
Example patterns for worker startup.
| Mode | Command |
|---|---|
| CPU | ./cryptix-fusion -u <cryptixID> --use-cpu |
| CPU + Threads | ./cryptix-fusion -u <cryptixID> --use-cpu --threads=4 |
| NVIDIA GPU | ./cryptix-fusion -u <cryptixID> --use-gpu --use-nvidia |
| AMD GPU | ./cryptix-fusion -u <cryptixID> --use-gpu --use-amd |
| Mixed/OpenCL | ./cryptix-fusion -u <cryptixID> --use-gpu --use-mixed |
You can run Fusion twice on one machine: once for CPU jobs and once for GPU jobs. Worker naming example: -u <cryptixID>.rig01
Use official routes for worker binaries, docs and integration tools.
| Resource | Purpose | Link |
|---|---|---|
| Fusion Worker (Windows) | Windows worker package | Download |
| Fusion Worker (Linux) | Linux worker package | Download |
| Fusion Worker (HiveOS) | HiveOS package | Download |
| MMPOS integration | Managed mining OS route | Open repo |
| CCPI documentation | Accounting model details | Open CCPI page |
| Fusion software guide | Setup, commands, platform-specific install notes | Open software page |
Most startup issues are environment, permissions or timing expectations.
Run Fusion as administrator when the worker reports low-level access or MSR permission issues.
Check Cryptix ID and startup flags, but also give the system time: about 5 minutes for visibility and about 10 to 15 minutes for stable CCPI.