[ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net

[Neshdan]

So now. Maybe i should have said i start eloipool and mmp in one runit.sh

Code:

#!/bin/sh

PYTHONPATH=/home/osboxes/Desktop/eloipool_Blakecoin/python-bitcoinrpc:/home/osboxes/Desktop/eloipool_Blakecoin/python-base58:/home/osboxes/Desktop/eloipool_Blakecoin/midstate \
	nohup /home/osboxes/Desktop/eloipool_Blakecoin/eloipool.py 2>&1 >/dev/null &

python /home/osboxes/Desktop/eloipool_Blakecoin/merged-mine-proxy.py -w 8330 -p http://ssecreteloipool:222@localhost:8337/ -x http://phousername:phopassword@localhost:9377/ -l /home/osboxes/Desktop/eloipool_Blakecoin/mmp_log.txt >/dev/null &

i have changed it now to

Code:

#!/bin/sh

PYTHONPATH=/home/osboxes/Desktop/eloipool_Blakecoin/python-bitcoinrpc:/home/osboxes/Desktop/eloipool_Blakecoin/python-base58:/home/osboxes/Desktop/eloipool_Blakecoin/midstate \
	nohup /home/osboxes/Desktop/eloipool_Blakecoin/eloipool.py 2>&1 >/dev/null &
wait
python /home/osboxes/Desktop/eloipool_Blakecoin/merged-mine-proxy.py -w 8330 -p http://ssecreteloipool:222@localhost:8337/ -x http://phousername:phopassword@localhost:9377/ -l /home/osboxes/Desktop/eloipool_Blakecoin/mmp_log.txt >/dev/null &

and now it is as followed:
The error occurs further, but even after the exception it still writes the logfile. I will leave it hashing now to see if it really finds a block on PHO chain too. Can it be, that i started both processes too fast?

But even if so... it would be interesting, what raises this exception. I am using the merged-mine-proxy that is included in the eloipool_Blakecoin git. Is there maybe a separate updated one?
Could you think of any place where to get further information on this fault? I googled for it, but didnt find any suitable thing (suitable for my mind ).

I will report back, when i found a BLC block, as latest then i should have found a PHO block too... i'm a bit excited and nervous now, as i want it to run

[BlueDragon747]

So now. Maybe i should have said i start eloipool and mmp in one runit.sh

Code:

#!/bin/sh

PYTHONPATH=/home/osboxes/Desktop/eloipool_Blakecoin/python-bitcoinrpc:/home/osboxes/Desktop/eloipool_Blakecoin/python-base58:/home/osboxes/Desktop/eloipool_Blakecoin/midstate \
	nohup /home/osboxes/Desktop/eloipool_Blakecoin/eloipool.py 2>&1 >/dev/null &

python /home/osboxes/Desktop/eloipool_Blakecoin/merged-mine-proxy.py -w 8330 -p http://ssecreteloipool:222@localhost:8337/ -x http://phousername:phopassword@localhost:9377/ -l /home/osboxes/Desktop/eloipool_Blakecoin/mmp_log.txt >/dev/null &

i have changed it now to

Code:

#!/bin/sh

PYTHONPATH=/home/osboxes/Desktop/eloipool_Blakecoin/python-bitcoinrpc:/home/osboxes/Desktop/eloipool_Blakecoin/python-base58:/home/osboxes/Desktop/eloipool_Blakecoin/midstate \
	nohup /home/osboxes/Desktop/eloipool_Blakecoin/eloipool.py 2>&1 >/dev/null &
wait
python /home/osboxes/Desktop/eloipool_Blakecoin/merged-mine-proxy.py -w 8330 -p http://ssecreteloipool:222@localhost:8337/ -x http://phousername:phopassword@localhost:9377/ -l /home/osboxes/Desktop/eloipool_Blakecoin/mmp_log.txt >/dev/null &

and now it is as followed:
The error occurs further, but even after the exception it still writes the logfile. I will leave it hashing now to see if it really finds a block on PHO chain too. Can it be, that i started both processes too fast?

But even if so... it would be interesting, what raises this exception. I am using the merged-mine-proxy that is included in the eloipool_Blakecoin git. Is there maybe a separate updated one?
Could you think of any place where to get further information on this fault? I googled for it, but didnt find any suitable thing (suitable for my mind ).

I will report back, when i found a BLC block, as latest then i should have found a PHO block too... i'm a bit excited and nervous now, as i want it to run

no that is the updated one    *just checked Luke Jr github and link to old mmp is dead so yeah as I said that is latest updated one in my repo on github

I dont run it as one and i also use bash vs sh this is my reset/start script

Code:

#! /bin/bash
cd /yourpath/eloipool_Blakecoin
pkill -f -Uroot merged-mine-proxy
sleep 2
/yourpath/scripts/mmp.sh >/dev/null
sleep 1
/yourpath/scripts/run-eloipool.sh 2>&1 >/dev/null &
exit 1

my mmp.sh is similar to yours just with more rpc's  *again handled with "#! /bin/bash"

Code:

#! /bin/bash
sudo nice -n -2 nohup python /yourpath/eloipool_Blakecoin/merged-mine-proxy -w 8330 -p http://ssecreteloipool:222@127.0.0.1:8337/ ... rpc's here .... -l /yourpath/eloipool_Blakecoin/mmp_log.txt -s 16 >/dev/null &

my run-eloipool.sh

Code:

#!/bin/bash

cd "$(dirname ${BASH_SOURCE[0]})"
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"

pkill -f -Uroot eloipool.py
wait

PYTHONPATH=$PYTHONPATH:$DIR/../python-bitcoinrpc/jsonrpc:$DIR/../python-bitcoinrpc/bitcoinrpc:$DIR/../python-base58:/usr/local/lib/python3.2/dist-packages/cymysql \

	sudo nice -n 1 nohup python3 ../eloipool_Blakecoin/eloipool.py 2>&1 >/dev/null &

using nice and mysql which is not necessary for you doing a solo merged pool and midstate can be dropped

[Neshdan]

It works! Got a BLC and a PHO block solved

Still curious, that it works now - didnt change anything else than the wait line. As i want to install the other four Blake-Coins too, i will see if it will work again after restarting the system / processes.

Thanks alot for your patience and your help!

[BlueDragon747]

It works! Got a BLC and a PHO block solved

Still curious, that it works now - didnt change anything else than the wait line. As i want to install the other four Blake-Coins too, i will see if it will work again after restarting the system / processes.

Thanks alot for your patience and your help!

no problem glad I could help any other issues just let me know always happy to help those that try it for themselves 

[Ignatius]

It works! Got a BLC and a PHO block solved

Still curious, that it works now - didnt change anything else than the wait line. As i want to install the other four Blake-Coins too, i will see if it will work again after restarting the system / processes.

Thanks alot for your patience and your help!

Congratulations on getting things working! 

[Neshdan]

It works! Got a BLC and a PHO block solved

Still curious, that it works now - didnt change anything else than the wait line. As i want to install the other four Blake-Coins too, i will see if it will work again after restarting the system / processes.

Thanks alot for your patience and your help!

Congratulations on getting things working! 

Thanks Was really excited it finally worked - even if there is the repetitive exception which is at the moment unexplainable for me. But i think time comes, this will be solved too.

Possible merged malfunction for my setting? At this time i merged BLC, PHO & LIT

2.5 hours ago i got a solving share value of ~411k

At this time the were the following difficulties:

BLC - ~100k
PHO - 199,3k
LIT - 269k

My pool solved blocks for BLC and LIT - but not for PHO, which should have happened in my understanding.

Code:

2018-01-17T19:15:00.646516,solve,=,0,1,a5e3ca98acf0dc37415895e41e56eaad83a392e41798788fcf28000000000000

Any thoughts?

[Ignatius]

It works! Got a BLC and a PHO block solved

Still curious, that it works now - didnt change anything else than the wait line. As i want to install the other four Blake-Coins too, i will see if it will work again after restarting the system / processes.

Thanks alot for your patience and your help!

Congratulations on getting things working!  

Thanks Was really excited it finally worked - even if there is the repetitive exception which is at the moment unexplainable for me. But i think time comes, this will be solved too.

Possible merged malfunction for my setting? At this time i merged BLC, PHO & LIT

2.5 hours ago i got a solving share value of ~411k

At this time the were the following difficulties:

BLC - ~100k
PHO - 199,3k
LIT - 269k

My pool solved blocks for BLC and LIT - but not for PHO, which should have happened in my understanding.

Code:

2018-01-17T19:15:00.646516,solve,=,0,1,a5e3ca98acf0dc37415895e41e56eaad83a392e41798788fcf28000000000000

Any thoughts?

There have been many times I saw a high value share not solve all coins, only 1 or more, despite being above their required diff. I always noticed the merged coins had a lower hashrate than BLC and assumed this was normal. Perhaps Blue has a more technical explanation.

I'm not sure why your log line only has 2 block solve outputs and not 3? solve,=0,1,0,<share> not solve,=,0,1,<share>.

[joshwaan]

Any talks of another exchange for this coin?

[Neshdan]

It works! Got a BLC and a PHO block solved

Still curious, that it works now - didnt change anything else than the wait line. As i want to install the other four Blake-Coins too, i will see if it will work again after restarting the system / processes.

Thanks alot for your patience and your help!

Congratulations on getting things working!  

Thanks Was really excited it finally worked - even if there is the repetitive exception which is at the moment unexplainable for me. But i think time comes, this will be solved too.

Possible merged malfunction for my setting? At this time i merged BLC, PHO & LIT

2.5 hours ago i got a solving share value of ~411k

At this time the were the following difficulties:

BLC - ~100k
PHO - 199,3k
LIT - 269k

My pool solved blocks for BLC and LIT - but not for PHO, which should have happened in my understanding.

Code:

2018-01-17T19:15:00.646516,solve,=,0,1,a5e3ca98acf0dc37415895e41e56eaad83a392e41798788fcf28000000000000

Any thoughts?

There have been many times I saw a high value share not solve all coins despite being above their required diff. I always noticed the merged coins had a lower hashrate than BLC and assumed this was normal. Perhaps Blue has a more technical explanation.

I'm not sure why your output only has 2 block solve outputs and not 3? solve,=0,1,0,<share> not solve,=,0,1,<share>. Have you found any LIT blocks?

That is what made it weird for me. The contradiction between the actual diff and the explanation (as i understood it) of sharevalue > diff = solve.

The second thing - i think it is because i only mine two coins over mmp, BLC itself is the master-coin configured in eloipool, but not in mmp. I found a LIT block, but no PHO, sharevalue was > PHO & LIT diff - this is why i asked. This happened three times now. BLC & LIT generated, but PHO not.

[BlueDragon747]

its just not as simple as "sharevalue > diff = solve" in reality there are other factors at play

there is some propagation delay both on network which can lead to orphans and in the work sent to miner

I did say it will solve if the work is upto date and more than likely while you have been finding that share the PHO work is no longer the latest hence the share is just not valid on chain anymore do remember each of these chains is totally independent and act of mining is random by nature

overall I would say the merge mining is only about 80% efficient due to a number of reasons so dont expect it to solve them all every time there are other factors at work that effect things (propagation delays being most common)

good peering helps if your on any sort of non data center connection expect higher latency and more propagation delay thus slower effective work generation (cpu speed of what is running pool/node also has a minor effect too) and possibly more orphans *pretty much same for any coins based off this type of p2p networking code and consensus its not blake specific

The Merge Mine Proxy(mmp) does know about main(BLC) as it gets it via getwork (JSONRPCAddresses) and the ssecreteloipool user else it would not work and aux work would not be got via the aux chains rpc call and eloipool would not merge it into the work sent to the miner

the output is simple logging for mmp it does not handle the main eloipool does that and also does work generation mmp is just doing simple getting and submitting not much more rest is all in eloipool

[Neshdan]

So it may be, that my virtual environment is a bit too slow and doesnt get updated fast enough? That may be, as i observed slight lags in handling it, when all six wallets are running.

Forget about the below. I just leave it in, for the case anyone else has same problems.
I solved that with a clue BlueDragon gave a few posts ago. I added

Code:

-s 16

to my runmmp commandline and then it worked. Getting the following output now

Code:

2018-01-18T09:23:24.701008,solve,=,0,0,0,0,0,2069dea7ff25194364694bf2945febd25332bf43467c6b960fcb040100000000

----------------------------------------------------------------------------------------------

Over night, i downloaded the six blockchains and now tried to start mmp with 5 rpc calls. I now get following error when starting mmp:

Code:

  File "/home/osboxes/.local/lib/python2.7/site-packages/twisted/internet/base.py", line 426, in _continueFiring
    callable(*args, **kwargs)
  File "/home/osboxes/Desktop/eloipool_Blakecoin/merged-mine-proxy.py", line 417, in main
    raise ValueError('the merkle size must be at least as large as the number of aux chains')
exceptions.ValueError: the merkle size must be at least as large as the number of aux chains

The logfile says merkle size = 3.

I made a little file, that calls getinfo of all six wallets and write it into a logfile. On two of these chains (UMO & BBTC) i am not sure if they are up to date. The blockheight of my getinfo is bigger as on the block explorers (the explorer just dont seem to be up to date, UMO isnt working at all, BBTC just runs until January 3th). Second thing is that at UMO's and BBTC's getinfo output i get

Code:

"timeoffset" : -1

while all the others are 0.

The error itself occurs if i add ELT, BBTC or UMO (tried to add them one by one).

This is the whole runmmp.sh

Code:

#!/bin/sh

python /home/osboxes/Desktop/eloipool_Blakecoin/merged-mine-proxy.py -w 8330 -p http://ssecreteloipool:222@localhost:8337/ \
-x http://phousername:phopassword@localhost:9377/ \
-x http://litusername:litpassword@localhost:9378/ \
-x http://umousername:umopassword@localhost:9379/ \
-x http://bbtcusername:bbtcpassword@localhost:9380/ \
-x http://eltusername:eltpassword@localhost:9381/ -l ./Logs/mmp_log.txt >/dev/null &

RPC-Ports and user:pass are ok. If i add them all 6, mmp-log says merkle size = 3. If i add only one (of the three non-working) it says merkle size = 2.

[fedmahnkassad]

Will the new BitMain Antminer A3 Blake (2b) work on BlakeCoin?

[BlueDragon747]

Will the new BitMain Antminer A3 Blake (2b) work on BlakeCoin?

will it work on BlakeCoin which algo is Blake256R8 hmm   = No Blake2B is different algo

the asic I did hear about that does same algo had no reply from manufacture about compatibility and Blakecoin has a few little bits in software that I have given full details to manufacture about that would need to be changed or added for it to work e.g hardware should work the mining software/firmware might not out of the box as the manufacture has close source miner software so needs to be done their end little I could do apart from point it out to them and hope they add/respond

[fedmahnkassad]

Will the new BitMain Antminer A3 Blake (2b) work on BlakeCoin?

will it work on BlakeCoin which algo is Blake256R8 hmm   = No Blake2B is different algo

the asic I did hear about that does same algo had no reply from manufacture about compatibility and Blakecoin has a few little bits in software that I have given full details to manufacture about that would need to be changed or added for it to work e.g hardware should work the mining software/firmware might not out of the box as the manufacture has close source miner software so needs to be done their end little I could do apart from point it out to them and hope they add/respond

Thanks, the article about it did say "it seems that BitMain already has a working ASIC miner for the Blake (2b) mining algorithm (and maybe even for other variants of Blake)". I saw the price start going up right after this announcement. Might be coincidence though.

[BlueDragon747]

Will the new BitMain Antminer A3 Blake (2b) work on BlakeCoin?

will it work on BlakeCoin which algo is Blake256R8 hmm   = No Blake2B is different algo

the asic I did hear about that does same algo had no reply from manufacture about compatibility and Blakecoin has a few little bits in software that I have given full details to manufacture about that would need to be changed or added for it to work e.g hardware should work the mining software/firmware might not out of the box as the manufacture has close source miner software so needs to be done their end little I could do apart from point it out to them and hope they add/respond

Thanks, the article about it did say "it seems that BitMain already has a working ASIC miner for the Blake (2b) mining algorithm (and maybe even for other variants of Blake)". I saw the price start going up right after this announcement. Might be coincidence though.

most likely coincidence or testing market for demand

due to some of the non standard hashing in the work generation(single sha256 vs standard double sha256) Blakecoin needs some bits changing in software for compatibility from any/all asic manufactures otherwise all your shares will get rejected and could even land you a ban from auto admin on pools

the specific algo it need to do in hardware is Blake256r8 as its known + a few changes in software nothing else will work afaik

best would be to ask manufacture direct as I am not getting a reply myself atm  

[Neshdan]

or it just got first in the p&d queue. Whatever it is, the few satoshis i invested when it was low pay out now without touching my mining wallet Now power costs for a few days are paid - or maybe a Blake256(8r) asic if they really come and offered for a reasonable price (not like the shit/scam/whatever a few posts ago)

[pokermaniacxxx]

What cryptoexchanges are you going to get listed on?

[Neshdan]

What cryptoexchanges are you going to get listed on?

Its not a matter of going to get listed... if you would have read the initial post of this thread, you would know its on Cryptopia and C-Patex.

[BlueDragon747]

Need to do some maintenance on AT1/NY2 it could take a few hours will payout all unconfirmed before I start

Edit:
done *ok found a bug working on it now and fixed  
unconfirmed paid
fresh hot wallets
added SSL

some other bits will leave for now and update later

Edit2:
some issues from ISP "We are currently experiencing degraded network performance in our Atlanta location."

[Neshdan]

Code:

electrond: /usr/include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.
photond: /usr/include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.
lithiumd: /usr/include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.
blakebitcoind: /usr/include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.
universalmoleculed: /usr/include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.

This is what i get, when i try to shut down all six wallets. The servers of all six wallets are shut down (second try to stop i get "Couldn't connect to server", process is killed to in system monitor), but before i get these messages. As you can see, it is on all wallets besides BLC - did you change anything there which wasnt changed on the other Blake-Wallets?