Introducing NerbusNerbus is an independent cryptocurrency network with NRB as its native coin. It combines CPU mining through VerusHash 2.2 with the hybrid Proof of Work / Proof of Stake consensus inherited from VerusCoin.
The core parameters are straightforward: a 30-second target block interval, an initial reward of 100 NRB per block, zero premine and a maximum cumulative block reward schedule of 209,000,000 NRB. The genesis block pays no reward.
The project is based on VerusCoin v1.2.18. Nerbus has its own network identity, genesis block and issuance parameters. Its public software includes Core, a standalone Qt desktop wallet and a block explorer, with source code available for inspection.
For miners, the entry point is a compatible CPU miner and an NRB receiving address. For users, the Qt wallet creates addresses and signs transactions locally. For node operators and developers, Core provides the daemon, command-line tools and consensus implementation.
Network specifications| Name / ticker | Nerbus / NRB |
| Codebase | VerusCoin v1.2.18 fork |
| Consensus | Hybrid Proof of Work / Proof of Stake |
| Target PoW / PoS balance | 50% / 50% |
| PoW algorithm | VerusHash 2.2; CPU mining |
| Target block interval | 30 seconds |
| Initial block reward | 100 NRB |
| Halving interval | 1,045,000 blocks |
| Maximum cumulative block rewards | 209,000,000 NRB |
| Premine / genesis reward | 0 NRB / 0 NRB |
| Precision | 8 decimal places |
The 50/50 figure describes the target balance between PoW and PoS blocks. It is not a split of each individual block reward or a requirement that block types alternate strictly.
How NRB issuance worksThe reward starts at 100 NRB and halves after each 1,045,000-block period:
First block of period Base reward
1 100 NRB
1,045,001 50 NRB
2,090,001 25 NRB
3,135,001 12.5 NRB
There are 34 reward periods. The final subsidized block is 35,530,000; its reward includes a rounding adjustment so that cumulative permitted block rewards reach exactly 209,000,000 NRB. After that height, the new block subsidy is zero. Transaction fees transfer existing coins.
Halvings follow block height. At the target interval, one period is approximately 363 days; actual timing depends on block production. Circulating supply can be lower than the reward ceiling because of unclaimed rewards or burned coins.
Extract the complete package, keeping its bundled libraries and plugins together. On Windows, open nerbus-qt.exe. On Linux, use ./nerbus-qt.sh; the Linux package requires glibc 2.35+ and X11 or XWayland.
To receive mining payouts, open
Receive, create a new receiving address and copy your transparent NRB address. Back up your wallet after creating new addresses. Password encryption is available under
Wallet & backup.
Start CPU miningUse a
PBaaS-compatible CPU build of ccminer 3.8.3 with VerusHash 2.2 support. The algorithm option is
-a verus. Platform-specific miner downloads and setup instructions are in the
How to Mine guide. Miner binaries are separate from Wallet and Core downloads.
Pool: stratum+tcp://pool.nerbus.com:39480
Username: YOUR_NRB_ADDRESS.worker1
Password: x
Algorithm: verus
Payment method: PROP
Pool fee: 0%
Minimum payout: 1 NRB
ccminer.exe -a verus -o stratum+tcp://pool.nerbus.com:39480 -u YOUR_NRB_ADDRESS.worker1 -p x -t 4
./ccminer -a verus -o stratum+tcp://pool.nerbus.com:39480 -u YOUR_NRB_ADDRESS.worker1 -p x -t 4
Replace YOUR_NRB_ADDRESS with your own receiving address. The .worker1 suffix identifies your machine, and -t 4 selects four CPU threads. Adjust the thread count to your hardware and cooling. The pool only needs your public address; x is a placeholder, not your wallet password.
Pool mining does not require a local node or keeping the wallet open. Check for accepted shares in the miner, then follow your address on the pool. PROP rewards depend on your accepted shares in each round. Payouts follow block maturity and the minimum payout threshold; network transaction fees are deducted from payouts. Current settings and statistics are on the
Mining Pool.
Follow the included README and configuration example, including fetching the cryptographic parameter files before starting a full node. The 0.1.0 Core package currently reports 0.1.0-dev internally. Wallet and Core are separate applications.
Direct downloads above point to the listed versions. Use the Releases pages for future versions and verify archives against the corresponding SHA-256 files.
