Nerbus is an independent chain based on VerusCoin. CPU mining, hybrid PoW/PoS consensus and coin issuance rules set in advance.
NRB runs on its own blockchain. New coins follow a block reward schedule. Both the premine and the genesis block reward are zero.
NRB is issued by its own chain. Block height, rewards and halvings determine its supply schedule. One NRB contains 100,000,000 base units, giving transactions eight decimal places of precision.
The project is based on VerusCoin v1.2.18. Nerbus defines its own network and issuance parameters.
Nodes create blocks, synchronize a shared chain history and process coin transfers. The Linux build has also been checked for state persistence after a restart.
As of the October 13 project report, mainnet has not launched. Public source code, Windows/Linux builds and live pool mining tests are in preparation.
The NRB issuance limit is built from block rewards. Rewards fall over time, and the number of reward periods is set in advance.
The first period begins at 100 NRB per block. Every 1,045,000 blocks, the base reward halves: first to 50, then 25, 12.5 and so on. There are 34 reward periods in total.
The schedule follows chain height. The first halving occurs at block 1,045,001. Its calendar date depends on how quickly the network produces blocks.
Share of 209 million NRB by the end of each of the first four periods.
The first period permits 104.5 million NRB in rewards. The second adds 52.25 million. Each successive period introduces fewer new coins.
| Period | First block | NRB |
|---|---|---|
| 1 | 1 | 100 |
| 2 | 1,045,001 | 50 |
| 3 | 2,090,001 | 25 |
| 4 | 3,135,001 | 12.5 |
| 5 | 4,180,001 | 6.25 |
| 6 | 5,225,001 | 3.125 |
| 7 | 6,270,001 | 1.5625 |
| 8 | 7,315,001 | 0.78125 |
| … | … | … |
| 34 | 34,485,001 | 0.00000001 |
Balances are counted in whole base units. Very small rewards must be rounded when halved. The final block receives an adjustment so that total permitted rewards reach exactly 209,000,000 NRB.
At block 35,530,000 the final reward is 0.11495001 NRB. After this block, new coin issuance through the subsidy ends.
Precision is 0.00000001 NRB. The last table row shows the base reward; the final adjustment is accounted for separately.
NRB has zero premine and a zero genesis reward. Neither mechanism creates an initial supply. Rewards begin with the first block after genesis.
209 million is the maximum total permitted rewards. Actual circulating supply can be lower if rewards go unclaimed or coins are burned. Determining circulation requires the history of the chain itself.
After block 35,530,000, the new subsidy is zero. Fees consist of existing coins: they move between participants and do not increase the issuance limit.
One reward period takes about 363 days at a 30-second block interval. This is a calculation, rather than a fixed calendar schedule.
Halvings are therefore tracked by block height. Calendar estimates depend on the actual progress of the chain.
Regular NRB PoW blocks use the VerusHash family, which is suitable for mining on a central processing unit.
A miner performs computational work to propose a new block. Other nodes check it against the chain rules. Finding a block is only part of the process: the network must also accept it as valid.
The algorithm defines the computation. Actual mining depends on hardware, software, network parameters and the connection method. Owning a CPU does not guarantee a fixed number of coins per day.
Nerbus tests have already produced real PoW blocks. The next practical step is pool mining, from connecting a miner to accepting a discovered block.
Live pool mining tests are still ahead. Public source code and release archives are also being prepared.
Nodes and pools serve different parts of the process. A node enforces the chain rules; a pool coordinates connected miners. The complete setup needs to be tested together.
Nerbus inherits Verus hybrid consensus with a target 50/50 balance. Proof of Work and Proof of Stake both contribute to the chain.
In PoW, participants use computation to create a block. Regular Nerbus blocks use CPU-suitable VerusHash. A proposed block must pass node validation.
PoS adds a way for coin holders to participate in building the chain. Its rules are inherited from the Verus implementation, with a target share of one half of the hybrid.
The 50/50 ratio describes the target balance of mechanisms. It does not require blocks to alternate strictly, nor does it determine any individual participant reward.
It is the target interval between blocks, rather than a guaranteed time for every transfer. Confirmations are counted in new blocks; the actual time depends on network operation.
Checks in an isolated network covered block creation, coin operations, invalid data handling and restart behavior.
| Scenario | What was checked |
|---|---|
| PoW blocks | Block creation and reward maturity |
| Synchronization | A shared chain history across connected nodes |
| Transfer | Coin transfers and message signing |
| Invalid block | Rejection of invalid data |
| Restart | Chain verification and state persistence |
The explorer was also tested in the isolated environment. Mainnet was not launched after these tests.
Functional checks cover the listed scenarios. A full audit of consensus, PoS and shielded transfers remains a separate task.
Nerbus already has coin parameters, server builds and test results. The next stage takes the project from private preparation toward public participation.
The Linux version has been built and tested. Checks covered block creation, transfers, synchronization and persistence after restarts.
Publication of source code and verified Windows/Linux archives. The project is currently a private fork.
Live testing of miner connections and block submission through a pool.
Starting the main network after preparations.
Status is based on the October 13, 2026 project report. These milestones describe the work underway.
THE RULES ARE SET BEFORE THE FIRST BLOCK
Why is the CPU back in the story? How do block rewards shrink? Where does 209,000,000 come from? Inside the Nerbus chain.