BLUR is a cryptocurrency built with privacy in mind. Take a first-hand role in protecting yours.

About the Blur Network

The Blur Network (BLUR) is a privacy-focused peer-to-peer network, built upon the premise that privacy is not compatible with centralization. Blur makes use of a private, standalone blockchain in which transaction participants and amounts are hidden, to enable a degree of privacy that is impossible on a transparent ledger, such as Bitcoin.

The Blur Network has been designed to address the direct threats to privacy and security resulting from specialized mining hardware and centralized mining pools. Miners have turned to these to reduce variance in block reward payouts from mining. Our network views these current solutions as detrimental to decentralization. Centralized pools and limited access to specialized mining hardware place the security of existing networks into the hands of few.

Out of a desire to keep mining hardware accessible to hobbyists, the approach of hardware-specific resistance has arisen. However, this approach limits access to compatible hardware even further. To compound this, resistance to hardware is something of a perpetual cat-and-mouse situation. Instead of subscribing to this philosophy, Blur seeks to build an ecosystem that is inclusive for all mining hardware. This manifests itself as an experiment we are calling The Fractal Multichain, which is planned to feature discretionary and hardware-specific Proofs-of-Work. Each chain will be weighted inversely in value, to a single devices relative hashpower (compared to a CPU).

The current chain will become the base-value chain (modular chain values will be denominated by BLUR units, proportionally). As such, BLUR's current blockchain will remain central to our attempt at favoring multi-purpose hardware, while we bring the other chains, designed for specialized hardware, online as well. In CryptoNote blockchains, emission is biased to favor early adopters. Subsequent, in-tandem chain launches will seek to leverage this aspect of emission curves, to incentivize away specialized hardware, theoretically resulting in less competition for CPU miners, on the base chain.

CryptoNight-Dynamic, our novel application of the CryptoNight algorithm was developed to maximize decentralization of network hash power. This is accomplished by favoring CPU-specific strengths, to enable “mining hardware” to extend to anyone who owns a computer. The algorithm dynamically varies the amount of iterations that are performed at various points in its computations. The iteration count is a direct function of the current block's timestamp and the previous block's hash.

This translates to mean that Blur’s algorithm varies dynamically, on both intra-block and inter-block bases. The result is an algorithm that changes roughly once every five seconds, with each block's specific iteration count being directly dependent on the hash of the block before it and the current time. These specific aspects of the algorithm make an active connection with the network necessary, for computing the proof-of-work for each block. All information is taken directly from the block header. Therefore, mining with specialized hardware is possible. However, nodes with direct access to the historical blocks will perform with an advantage due to not needing to relay this information across the web, or between clients.

Core Components of the Blur Network

Selective transparency allows BLUR to be much more fungible, and censorship-resistant than transparent blockchains. Amounts and participants are obfuscated when sending or receiving BLUR. This means users can decide precisely who may view their transactional information. This is impossible on Bitcoin's network, where anyone can look up addresses and associated balances. Click on the icon above to read a technical paper by Shen Noether from Monero, detailing the RingCT mechanism.

The Blur Network runs on a custom Proof-of-Work algorithm, called CryptoNight-Dynamic. The algorithm changes dynamically every second five seconds, on average. The calculations required for the algorithm use values directly dependent on: the previous block's hash, the current block's height, and a UNIX timestamp. The resulting algorithm varies dynamically, and unpredictably, between (and within) each block that is mined. Our goal is facilitating CPU-centric mining, devoid of illogical mining pools. Click the icon above, for a technical paper detailing the need for a solution in response to miner centralization.

The Blur Network seeks to enable individuals to transact in BLUR without the variable of "trust." This is made possible by the CryptoNote Protocol, which employs cryptographic primitives to secure the transactions. Users can generate a keypair, from which addresses are derived, without ever connecting to the internet. This means we cannot and do not control who chooses to use the Blur Network. The Cryptonote Protocol whitepaper can be found by following the hyperlink above and is annotated with commentary from researchers at Monero Research Labs.

The Network at a Glance

Max Supply: 9,223,300 BLUR + Tail Emission

Circulating Supply: Real-Time Supply API endpoint on the BLUR Blockchain Explorer

Fixed Tail Emission: 2.0 BLUR per block mined.

Decimal Places: 12

Pre-mine: 360,000 BLUR hardcoded into first mined block’s emission (~4% of Total Supply).

Block Emission Profile: See the spreadsheet located here for a lifetime emission profile.

Mining Algorithm: Cryptonight-Dynamic

Block Target Time: 1 Minute

P2P Port: 52541

RPC Port: 52542

An API for the Blur Network Explorer can at found on the explorer’s webpage.

For example: returns a list of the past 25 transactions on the network

See documentation for the explorer on GitHub for more info

Node 1:

Node 2:

Node 3:

Project Roadmap

Please note: Our development is extremely active, and this roadmap is subject to change at any time. A green checkmark () denotes item completion.
June 2018
June 2018
  • Network Launch (Mainnet)
  • Linux and Windows CLI Wallet Releases
  • Rapid Hardforks to v5 at Block Heights 1-5
  • Hardfork to v6 at Block 7500
July 2018
July 2018
  • MacOS CLI Wallet Release
  • Development of GUI Wallet/Miner Begins
  • Application for Listing on Bisq and MapleChange
  • Website Redesign & Social Media Presence

Aug - Sept 2018
Aug - Sept 2018
  • Network Launch (Mainnet)
  • Linux and Windows CLI Wallet Releases
  • Rapid Hardforks to v5 at Block Heights 1-5
  • Hardfork to v6 at Block 7500
Oct 2018
Oct 2018
  • Listing on Bisq Decentralized Exchange
  • Hardfork v8 (Mining Algorithm Change: CryptoLite-Adaptive v2)
  • CryptoNight-Dynamic v1 Development Begins
  • Upgrade of Existing GUI Wallet
Nov - Dec 2018
Nov - Dec 2018
  • Windows GUI Wallet Release
  • Hardfork v9
  • Release of CryptoNight-Dynamic v1
  • Announcement of Future Multi-Chain Architecture
  • Release of Linux Snap Package
Q1 2019
Q1 2019
  • Hardfork v10
  • Release of CryptoNight-Dynamic v2
  • Listing on
  • GUI Wallet Aesthetic Improvements
Q2 2019
Q2 2019
  • Listing on Altilly Exchange
  • Harden/Simplify Monero Codebase
  • Development: Begin Integration of Komodo DPoW
  • Development: Cross-Chain Compatibility (BTC-derived codebases)
Q3-Q4 2019
Q3-Q4 2019
  • Continued Development of DPoW Rewrite, for Compatibility with RingCT-Enabled Codebases
  • Investigate possibilities of Merkle Mountain Ranges and CryptoConditions on BLUR
  • Blur Network CLI & GUI Wallet Snap Packages Release
Q1-Q3 2020
Q1-Q3 2020
  • Complete Development of Checkpointing Scheme for BLUR
  • Technical Paper on Rewritten DPoW Mechanism
  • Integration with Iguana/KMD Notary Network
  • Testing of DPoW in Conjunction with KMD Notary Network  (Currently Underway)
  • Complete Development of Broader DPoW Rewrite
Q4 2020
Q4 2020
  • Begin Development of Modular Chain Framework, for Fractal MultiChain 
  • Begin Development of Functional Atomic Swap Code for Modular Chains to Main BLUR Chain
  • Prepare for Launch of First Tandem Launch for Faction-Based Mining

Graphical Wallet

With One-Click Mining

Command-Line Tools/Wallet

With Embedded Miner in Daemon

BLUR Transaction Viewer