Block Collider & Borderless Markets

Documentation, market information and support for Miners and Market Makers.

Get Started Forum & Support Developer API

How it works

What are Rovers & Miners?
Rovers are built into the mining process. They are responsible for relaying blocks to the miners as fast as possible from each supported network. A rover is also bi-directional in that it also broad casts transactions back to a blockchain on behalf of the miner.

My miner has the blocks of each blockchain, now what?
The heads of the blockchains or the latest block are selected. These are the block that your miner will “mine” on top of. The miner must find a string that when hashed with a Blake2BL hash has a minimum edit-distance from the merkle and none pair of each block in the blockchain.

Once this is found a miner could submit the raw string “pre-hashing” and the hash headers which are above the minimum threshold.

What if a blockchain adds another block before the next block has been found?
A blockchain block received by a miner before the next Block Collider block has been found is concatenated to its parent block hash and the mining process continues with a slightly lower minimum distance threshold until the threshold is so low the block’s match is easily found.

How do transactions work?
Each transaction submitted to the Block Collider chain includes a fee and it’s own minimum distance threshold. The minimum distance threshold is the similarity of a string that must be found for the TX hash. For instance a transaction submitted to the Block Collider would look like this:

FEE: 0.13 (in NRG)

In the above example a string binding must be found of minimum distance 1.1 to the TX_HASH. If that is found a miner could broadcast the TX and claim a portion of the fee which is split between the discovering miner of the transaction and the miner of the block. This ensures that the TX Pool maintains maximum uptime while also providing access to miners who don’t have resources or capital to invest in significant hardware.

How are transactions added to a block?
Instead of using byte size or transaction count, the Block Collider using a maximum total sum of distances of transactions as a limit. For example if my default max sum of distance is 5 and I wanted to add transactions with distances 1.3, 3.3, and 6 I would be forced to drop one of the transactions (the third) to provide a valid block. Of course a miner might find it prudent to conduct further work on a transaction to make sure it gets added to a block.

Updated 8 months ago


Review specs and speed of other rigs mining the Block Collider.


How it works

Suggested Edits are limited on API Reference Pages

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