Knowledge Base

Guides, documentation, market infromation and support for Block Collider.

Documentation Forum

Before & After-Target Mining

FAQ requiring to two mining periods "Before-Target" (BT) and "After-Target" (AT)

Block Collider has two coins built into it’s blockchain, Emblems and NRG. Emblems are fixed at 300M, cannot be mined, and are available only during the Genesis Event and purchased in small amounts during Evangelist Events. NRG can only be mined and therefore is the transaction coin of Block Collider. It is similar to GAS in Ethereum in that it is required to execute every transaction. The relationship between Emblems and NRG is most comparable to NEO and GAS except that the NRG received from owning Emblems is only earned by actively mining the network.

We have not found an implementation of Proof of Stake that does not recreate the negative consequences of the old banking system. Centralized aggregation of money controlled by a limited number of decision makers.

Mining Block Collider has been broken into two stages. Both targets are built into the consensus protocol. Balances and rewards persist from Before-Target into After-Target "AT".

Before-Target “BT”

  • BT mining The period of time for from 1 to 1.5M Block Height or a hash power of 1.1GHZ.
  • Emblem balance bonuses are disabled.
  • Transactions (outside of Miner’s rewards) are disabled.
  • Rewards decreased 1/10 to 16 NRG per block.
  • CPU Miner provided.

After-Target “AT”

  • Block speed begins at a cycled rate of 5.5 seconds per block for AT-mining.
  • Emblem dynamic block size bonus enabled.
  • Transactions enabled.
  • Miners based on the EMB balance at their address earn up to 166 NRG per block. A minimum of 16 NRG.
  • GPU (BEAMX1) miner (followed closely by browser, ARM, and ASIC)

Protecting the stability of Block Collider’s NRG.

When ZCash launched it suffered from a lack of liquidity on exchanges and extreme price volatility. A few small Miners “in the know” may have also colluded and created price cartels that could have been another reason for the volatility. The solution to this is simply to ensure more people have less of the coin.

The early days exposed the ZCash network to Rent pricing in that a small party of individuals had the opportunity to stock pile a disproportionate percentage of the market.

Consensus algorithm at scale

A critical part of the scaling simulations requires a strong footprint of miners dedicated to transaction mining in addition to block mining. While the consensus protocol will survive even if there was only block mining, the overall transaction per second and average block size exponentially increases up to 8% of total hash power.

Avoiding Transaction Load

Some don't recall that Ethereum also launched with a "thawing" period to allow the network time to pickup speed before carrying transactions and to remove barriers to entry due to high GAS costs read more about it here.

Q & A

If I am an early miners in the BT (before-target) period is it just a testnet?

No it is full mainnet mining, your block rewards and balance will transfer over in their entirety.

Is a hard fork needed to move between BT and AT periods?

Moving between BT and AT will only require a soft fork although expect significant upgrades/changes as we add to the code base.

Can I use a mining pool?

Yes, we are working on one but several other groups are as well who are much bigger then our humble effort and will likely be optimum for most solutions. Ours, like our other flagship applications is for demonstration of best practices.

Can I merge mine with BTC or ETH or XMR etc?

During the BT period it is unlikely there will be merge mining of this kind. We know how to do something in that regard but our priority is accessibility and distribution for BT, AT is when we will start releasing performance oriented solutions.

Before & After-Target Mining

FAQ requiring to two mining periods "Before-Target" (BT) and "After-Target" (AT)

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.