Please note we use Blake2B (which is SHA3 grade) and not the original Blake referenced in that discussion.

To any who encounter errors connecting:

It will be back. Sometimes I dont catch it quickly, but this is due to my servers being "embargoed". My IPs are blocked from the main seed nodes and I have to rely on proxies and network peers to maintain a connection. You can thank Blakecoin's dev for that. Anyways, I'm doing all I can to keep nodes connected, since whenever one coin loses network all coins except blakecoin stop mining. So if you have resources, feel free to host seeds nodes (especially for BlakeBitcoin) and encourage others to do so.

Please visit unitus.info

Skein & Qubit - myriad.p2pool.geek.nz/merge

PLEASE NOTE:
Blake256 pool at unitus.blake256.com is offline while we work on a block submission issue.
Blake256 merge mining is not running at shares.blake256.com due to the same issue.

** You can still mine this coin solo!!! **

I am mining solo on a single 7970 (2GH/s) and get a block every hour or so.

Create a unitus.conf file in your blockchain directory, and add the following:


Obviously change your user/pass, port does not matter- choose one available on your system.

Save this file, and reopen your wallet. Then setup cgminer to connect to your local machine, address is simply 127.0.0.1:10000 (or whichever port you chose)

At this time, we are not 100% sure why blocks are not confirming when submitted through pool software, be it Eloipool+MMP or NOMP. It seems p2pool development had been in progress but was abandoned.

While mining normally, the following is encountered when a block is submitted:

When merge mining, the following is encountered when a block is submitted:

This may be caused by the Blake256 algorithm pools expect encoding the hash and the block with the PoW algorithm (blake), while Unitus does hashing with PoW (blake) but the block is SHA. However, this is the configuration of X11, and it functions normally.

The Blakecoin/Photoncoin/etc developers have already made it perfectly clear they will not assist in this matter, so myself and the Unitus dev are working on this issue as we can. Community input is welcome.

blake256 wont have merge mining at launch, still working on all that. Will have a standalone blake256 pool online later today.

Work on merge mining Unitus with the existing ecosystem is underway, hence the reason I asked for the algorithm to be included

blakeShares is fully online and processing payments to miners: http://shares.blake256.com
Merge-mining XDQ, BLC, B+, UMO, PHO, ELT, LIT - 1% fee, hourly payments

XDQ node is online at seed.blake256.com, be sure to add to your dirac.conf file:

other nodes online (excepting Society nodes that will be shutting down 12/8):

Yes, it is. The site is still under development, but for now you can create an account and mine. Payout code will be complete this afternoon, and ill be exposing the payout address fields at that time. Till then all shares are being tracked and miners will be paid accordingly.

Doubtful. Most of the blake ecosystem networks run at 300-400GH/s, so Dirac is still more than a quarter of those networks. No more vulnerable than them.

'I may be mistaken, but I believe the reporting on that site is incorrect. The entire pool hashrate (40+GH) is effectively applied to the network, on each chain, when work is submitted under merge mining. Therefore 40GH is actually present on Dirac from that pool.

On my pool in testing, with two users, we are seeing an average of 25GH. Thus, in 'public' (known) pools there is 65GH. Solo mining the network is possible at this point even with one GPU/FPGA.

That is excellent to see, glad it was kept on that pool.
Dirac network hashrate is holding steady around 125GH.

Expecting to have blakeShares online later today, if not this morning. (fingers crossed)

A Blake256 merge mining pool has been on my list of things to get going for some time now. Ive been quite busy with Multipool projects (NAUT, ARCH, JBS/PINK/+++) and hadnt gotten around to working on a merge pool. Bryce approached me a couple weeks ago to speed up/prioritize my work as XDQ was being removed from the ecosystem's pools and it needed a new home.

The blakeShares pool will be online soon. I realize I have been saying that for a few days now, but my time to work on it is limited. I have an operational back-end pool adapted from BlueDragons eloipool and the UMO NOMP pool, and it took alot of digging around to get things configured right and working. I spend the majority of last week attempting to get a superior pool infrastructure running the merged mining (Simple's PowerPool - still working with the developer on it) but the time crunch forced me to use the already existing pools.

At this time I am coding up a custom front end interface for account management with workers and payout addresses using the Meteor framework. Please let me know any and all questions you might have.

Please make sure you have the following added to your dirac.conf file in the blockchain directory (usually C:\Users\[Username]\AppData\Roaming\Dirac - AppData is hidden so you may need to enter that directory manually)

addnode=46.127.128.61
addnode=162.252.58.22
addnode=108.61.242.204
addnode=107.170.132.68
addnode=192.237.163.116
addnode=91.156.103.152

These were pulled from actively synced wallets. Majority of these seed nodes are run by Blakecoin servers and will be taken offline at 12/8. Bryce and myself are preparing new seed nodes and encourage others to do the same.

Multipool admin here...
Payouts are daily after 8PM CST. If the algorithm being mined doesnt produce any blocks (very unlikely right now) payout will be delayed till the next day, until blocks are found.

The server and wallet are online, but the login gateway is offline. This is due to the recent changing of hands of the fluttercoin website. Im working with the android/web wallet developer to get a gateway going again.