We are at block 3361! Block rewards have commenced.

Thank you to all of our supporters and miners who have got us up until this point and helped us sort out any early issues in our soft launch.

Stay tuned for our Bounty Campaign which will include bounties for signatures, translations and other tasks.

Lots of love from the b hash team <3<3<3

We appreciate your support!

For those who intend to start mining tomorrow when block rewards commence, we recommend setting up your miner in advance to ensure it is running properly if you haven't mined on XEVAN before.

We would also like to extend our gratitude to those mining currently in absence of a block reward. Thank you for your support and for helping to build the foundation of b-hash.

\

1 more day!!!!

you can follow the countdown on our website www.bhash.io

block 3361 will be the first block offering block rewards.

We structured it this way to create as fair a distribution as possible. We didn't offer rewards for the first week because we wanted to prevent large mining farms from mining a large portion of supply while the difficulty is low. This gives the community an equal opportunity to participate.

Currently on block 2281, the time is near! 

That is correct, thank you for assisting and for your support

This is a more detailed explanation from one of our developers in our Discord( https://discord.gg/wxYUt4z) :

" The status bar sync error is caused by the wallet being unable to sync masternode payments due to the fact that there aren't any active masternodes on the network.  This will change soon and the error will go away once the first masternodes propagate through the network.  The important thing that matters now is that the blockchain is synced which is separate from the error in the status bar.

The decision was made to always "enforce" masternode payments and is why the masternode payment enforcement spork is active by default thus causing the error that leads to the constant confusion.  This decision was made to ensure masternode collateral investments are protected just as much as miners from the start.

Adding static nodes is not recommended at this time.  Once connected to the DNS seeders you will get a list of nodes but this process can take minutes to complete.  If there are connectivity issues like the port is blocked, or something, then we recommend using FQDN so that IP addresses can be changed later if needed and of course IP addresses as the last resort.
"

Due to a lot of recent attacks and members of teams being targeted / hacked, we are withholding our identities for now while we are still in the development stage.

We understand concerns associated with this, which is why we've focused on a fair distribution. The dev team isn't taking a large pre-mine, we've bootstrapped the project ourselves up until now. Most of our allocation is for marketing because we haven't done much, we've been focusing on finalizing the code first. Many of us have worked on other projects in the space in various capacities and have noticed a lot of areas for improvement to benefit the end-user. We've been working on implementing those improvements as well as other features. Traditionally in the space the trend has been to advertise first and accept your money in blind faith while you wait for product delivery. We are reverse engineering that approach.