Scaling blockchains to thousands of on-chain transactions per second.

Project stage

Only a whitepaper

Detailed description

bloXroute is the first Blockchain Distribution Network (BDN), which increases a blockchain’s on-chain throughput by more than three orders of magnitude via an effective broadcast primitive, without affecting a blockchain’s functionality and the balance of power among current system participants. Further, due to the fast underlying network, this throughput increase can be easily realized by tweaking the block size and block time interval. This is achieved via a provably neutral network design as the first-order priority for bloXroute.

This system is the first to combine a legacy peer-to-peer network and a novel global BDN where the peer-to-peer network is used to audit the BDN and its neutrality. bloXroute is protocol coin, and blockchain-agnostic, capable of simultaneously supporting any number of blockchains. Additionally, we introduce BLXR, an investment vehicle which allows both investing in bloXroute and directing bloXroute’s revenues back to the crypto ecosystem.

bloXroute’s goal is to enable cryptocurrencies and blockchain systems to scale to thousands of on-chain transactions per second. Moreover, it aims to provide said scalability to numerous cryptocurrencies and blockchains simultaneously, utilizing a global infrastructure to support distributed blockchain systems in a provably neutral fashion. Here, we outline the system’s trust model and the components it utilizes to achieve scalability, to prevent discrimination, and to enable new features for the blockchains it serves.


Scalability problem includes:

The way Bitcoin works, is that every time a new block is mined, it is being propagated to the entire Bitcoin network using a “P2P Propagation Mechanism”, which is a fancy name for saying the miner sends it to its 8–10 peers, who send it their peers, etc., until it reaches the entire network (or 95% of the network, since some nodes might have just gone offline, or restarting, or whatnot), and it is used because it is trustless.

The current capacity of Bitcoin (BTC) is 1MB every 10 minutes, and since the average transaction size is ~540 bytes, it processes ~1950 transactions every 10 minutes, which translates to ~3 transactions per second (TPS).

If you increase the block propagation time by x10, the probability for a fork to occur increases by almost x10, at least until that probability is very close to 1.0, since its directly depend on the ratio between (1) the block propagation time, and (2) the time between blocks (this is also why it doesn’t matter if you increase the block size or reduce the 10 minutes interval).

So, if you increase the blocksize by x10, you increase the block propagation time by x10, and you will see ~x10 more forks (once 10MB blocks are full), but this is still OK! Blockchains know how to resolve forks once the next block is mined.

But, if you want to scale from 3 TPS to 300 TPS (which is nowhere close to the tens of thousands required for B2B micro-transactions), and to increase the blocksize by x100, the block propagation time becomes so long that in reality it exceeds the 10 minutes interval between blocks! You will see forks occur at a higher rate than blocks which resolves them, and the blockchain “unravels” to more and more forks (since there is no longer consensus which is the “right” fork), and the blockchain breaks.

This is the scalability problem, and the reason why no blockchain can do full 300MB blocks every 10 seconds.


While bloXroute is the first propagation system that addresses the blockchain scaling problem without a centralized trusted intermediary, block propagation systems do exist in Bitcoin. In particular, in order to minimize the negative effects of long block propagation times, as well as to put smaller miners on equal terms with larger mining farms, centralized Bitcoin relay networks were deployed.

Bitcoin Fast Relay Network / FIBRE
The first relay network to be deployed, the Bitcoin Fast Relay Network (BFRN) relays blocks using multiple gateways around the globe to reduce block propagation time for miners. BFRN focuses on utilizing low-latency connections and block compression to reduce the block propagation time. 

The Falcon Network was deployed (by two members of our bloXroute Labs team) after BFRN and before FIBRE and aims to reduce block propagation time by using cut-through routing, where relay-nodes relay the first bytes of an inbound block as soon as they arrive rather than wait for the entire block to arrive.

Off-Chain Scaling Solutions
An alternative approach, using off-chain transactions, aim to reduce some of the redundancy on the main blockchain. Generally speaking, an off-chain scaling solution will open up a payment channel between two parties, have the parties exchange funds while keeping track of intermediate balances, and then post a settlement transaction on the blockchain. These solutions include the Lightning Network, TeeChan, and more. These solutions are promising and are complementary to bloXroute’s proposition. If the underlying blockchain can support 1000 times the number of transactions as before thanks to bloXroute, and if off-chain transactions increase the throughput by another factor of 1000, then that blockchain’s throughput has increased by 6 orders of magnitude.

All on-chain scaling solutions
They will perform strictly better with a faster network layer and this is where bloXroute improves their performance. Indeed, in every distributed consensus protocol, every honest node must reach the same decision. Thus, regardless of the consensus protocol, every honest peer must obtain information about each transaction in the system. bloXroute focuses on this particular problem, which is fundamentally a broadcast problem, since every valid piece of information (transaction/block) must be propagated to every honest peer in the system. bloXroute is thus complementary to a native consensus protocol used, and it is capable of boosting up the performance, often dramatically, for any blockchain.


No Protocol Changes

  • Runsunderneath the consensus layer
  • Immediately available
  • Supports all blockchains

Provably Neutral

  • Fair to all nodes
  • Cannot discriminate nodes
  • Cannot censor blocks

Gradual Deployment

  • Immediately usable
  • Usable by any single node
  • Does not require majority adoption
Show details

Additional links

  • Token details

    • Token symbol ? Token symbol — a shorten token name. It is used during an ICO and after the coin listing at the cryptocurrency exchanges. : BLXR
    • Fundrasing target ? Fundraising target — the maximum amount of funds to be raised during an ICO. When it is reached, the developers stop selling the tokens because they do not need to raise more money for the project development. : NA
    • Token type ? Token type — a platform for a startup launch that influences the stability of blockchain operation, the speed of transactions and the fees. :Ethereum (ERC20)
    • Soft cap ? Soft cap — the minimum amount of funds to be raised for the project development. Sometimes when the soft cap has not been reached, the money is returned to the participants. : NA
    • Role of token ? Role of Token — type of token depending on the opportunities it offers to its owner. Utility tokens give their owners a right to use the project services, security tokens are aimed at bringing profit, and currency tokens are a money substitute. :Security token
    • Total supply ? Total supply — a total amount of tokens that will be released by the developers. :NA
    • Escrow agent ? Escrow agent — a qualified agent who has the right of signature in a multisig wallet. An escrow agent participates in an ICO, monitors the financial operations of the developers and confirms their fairness. :No
    • Tokens for sale ? Tokens for sale — the number of tokens offered to the participants of an ICO. :NA
    • Whitelist ? Whitelist — a list of participants, who get an opportunity to buy tokens. To be whitelisted, you need to register on time because the number of participants and the registration period are usually limited. :Whitelist N/A
    • Additional emission ? Additional emission — an additional release of tokens. It can be done once after the crowd sale or on an ongoing basis. In the projects with a limited emission there is no additional emission. :No
    • Exchange listing ? Exchange listing — an assumed date when the token will be listed at a cryptocurrency exchange. The developers usually indicate it in a roadmap and a white paper. :NA
    • Accepting currencies ? Accepting currencies — cryptocurrencies and fiat currencies that can be used for buying the project tokens. :ETH,
    • Can't participate ? Can't participate — the countries where it is prohibited to buy tokens. These can be countries where ICOs are prohibited altogether, or countries that have the requirements that a particular project does not meet. :No
    • Know Your Customer (KYC) ? Know Your Customer — a verification procedure for ICO participants, during which the developers can ask for personal data, a photo and a scanned copy of a passport of a potential investor. :No
    Get details
  • Token and Funds Distribution

    Token distribution date


    Unsold tokens


Sale schedule

Round Token Price Bonus Min / Max Purchase Soft Cap Hard Cap
Public sale — Soon
Start Soon
NA No - Uncapped Uncapped
Seed Round — Ended
Start Soon
NA No - Uncapped Uncapped
  • Team

    • Uri Klarman photo
      Uri Klarman
    • Emin Gün Sirer photo
      Emin Gün Sirer
      Chief Scientist
    • Aleksandar Kuzmanovic photo
      Aleksandar Kuzmanovic
      Chief Architect
    • Soumya Basu photo
      Soumya Basu
  • Advisors

    • Naval Ravikant
      Angel Investor
    • Injong Rhee
      Entrepreneur in Residence
    • Bruce Maggs
      Pelham Wilder Professor of Computer Science
    • Sarit Markovich
      Clinical Associate Professor of Strategy


  • Q4 2017
    • bloxRoute born
    • Initial conversations with investors
    • Closed strong advisor team
  • Q1 2018
    • Closed seed round
    • Hired COO
    • Launched website and released whitepaper
  • Q2 2018
    • Moved to new offices in the Chicago area
    • Hired first developers
    • Hired DevOps
    • Hired community manager
  • Q3 2018
    • Hired investor relations manager
    • Closed SAFT
    • Hired system engineer