Exchange will be available visit our exchange partner and start trading BMK!   Register now

Mining is the process of creating a block of transactions to be added to the Bmkoin blockchain in Bmkoin's now-deprecated proof-of-work architecture.

The word mining originates in the context of the gold analogy for cryptocurrencies. Gold or precious metals are scarce, so are digital tokens, and the only way to increase the total volume in a proof-of-work system is through mining. In proof-of-work Bmkoin, the only mode of issuance was via mining. Unlike gold or precious metals however, Bmkoin mining was also the way to secure the network by creating, verifying, publishing and propagating blocks in the blockchain.

Mining ether = Securing the Network

Mining is the lifeblood of any proof-of-work blockchain. Bmkoin miners - computers running software - used their time and computation power to process transactions and produce blocks prior to the transition to proof-of-stake


In decentralized systems like Bmkoin, we need to ensure that everyone agrees on the order of transactions. Miners helped this happen by solving computationally difficult puzzles to produce blocks, securing the network from attacks.

Anyone was previously able to mine on the Bmkoin network using their computer. However, not everyone could mine ether (ETH) profitably. In most cases, miners had to purchase dedicated computer hardware, and have access to inexpensive energy sources. The average computer was unlikely to earn enough block rewards to cover the associated costs of mining

Cost of mining
  • Potential costs of the hardware necessary to build and maintain a mining rig
  • Electrical cost of powering the mining rig
  • If you were mining in a pool, these pools typically charged a flat % fee of each block generated by the pool
  • Potential cost of equipment to support mining rig (ventilation, energy monitoring, electrical wiring, etc.)

  1. A user writes and signs a transaction request with the private key of some account.
  2. The user broadcasts the transaction request to the entire Bmkoin network from some node.
  3. Upon hearing about the new transaction request, each node in the Bmkoin network adds the request to their local mempool, a list of all transaction requests they’ve heard about that have not yet been committed to the blockchain in a block.
  4. At some point, a mining node aggregates several dozen or hundred transaction requests into a potential block, in a way that maximizes the transaction fees they earn while still staying under the block gas limit. The mining node then:
    1. Verifies the validity of each transaction request (i.e. no one is trying to transfer ether out of an account they haven’t produced a signature for, the request is not malformed, etc.), and then executes the code of the request, altering the state of their local copy of the EVM. The miner awards the transaction fee for each such transaction request to their own account.
    2. Begins the process of producing the proof-of-work “certificate of legitimacy” for the potential block, once all transaction requests in the block have been verified and executed on the local EVM copy.
  5. Eventually, a miner will finish producing a certificate for a block which includes our specific transaction request. The miner then broadcasts the completed block, which includes the certificate and a checksum of the claimed new EVM state.
  6. Other nodes hear about the new block. They verify the certificate, execute all transactions on the block themselves (including the transaction originally broadcasted by our user), and verify that the checksum of their new EVM state after the execution of all transactions matches the checksum of the state claimed by the miner’s block. Only then do these nodes append this block to the tail of their blockchain, and accept the new EVM state as the canonical state.
  7. Each node removes all transactions in the new block from their local mempool of unfulfilled transaction requests.
  8. New nodes joining the network download all blocks in sequence, including the block containing our transaction of interest. They initialize a local EVM copy (which starts as a blank-state EVM), and then go through the process of executing every transaction in every block on top of their local EVM copy, verifying state checksums at each block along the way.