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

sonk83

newbie

Activity: 27

Merit: 0

Quote from: BlueDragon747 on January 25, 2018, 11:58:32 AM

Quote from: sonk83 on January 25, 2018, 10:32:49 AM

Now you have to explain what the heck happened ... I was undermining quietly, then I entered the "edit account" to enter the address of the wallet for the payout and when I went to type the pin (which I remember from memory and it is always that) has always given the error "wrong pin".
I tried to reset it but the pool system replied "we can not send you email to the specified address" (which is a fully functional gmail address).
Now the amount is also suspended and the pool writes me to check my email to unlock it ... well, it's 72 hours that I do not receive any mail !!

What's now? Also because I had undermined a lot and I would not lose the blc ...

I reply to this on google/twitter/pm did you not read the reply Huh

any issues it is best to just contact me direct will sort things out asap

the emails are off due to people abusing them to crash pool and get blocked for spam due to amount of emails generated, I have unlocked your account on eu3

uhm.. account unlocked, but the pin (that I know perfectly) doesn't work... and if I try to reset pin, pool reply: "Unable to send mail to your address

BlueDragon747

legendary

Activity: 1509

Merit: 1030

Solutions Architect

Quote from: sonk83 on January 25, 2018, 10:32:49 AM

Now you have to explain what the heck happened ... I was undermining quietly, then I entered the "edit account" to enter the address of the wallet for the payout and when I went to type the pin (which I remember from memory and it is always that) has always given the error "wrong pin".
I tried to reset it but the pool system replied "we can not send you email to the specified address" (which is a fully functional gmail address).
Now the amount is also suspended and the pool writes me to check my email to unlock it ... well, it's 72 hours that I do not receive any mail !!

What's now? Also because I had undermined a lot and I would not lose the blc ...

I reply to this on google/twitter/pm did you not read the reply Huh

any issues it is best to just contact me direct will sort things out asap

the emails are off due to people abusing them to crash pool and get blocked for spam due to amount of emails generated, I have unlocked your account on eu3

sonk83

newbie

Activity: 27

Merit: 0

Quote from: BlueDragon747 on January 04, 2018, 07:45:17 AM

Quote from: Neshdan on January 04, 2018, 04:19:03 AM

Happy new year to all of you

Atm the spikes are really heavy. I think it is because of the raised price of Photon which led to a switch to the Blakecoin-Algo on Zpool.

So they want to build Asics for the BLC Algo? Sad

Yeah seen a lot of activity and I think they have already built asic they at least in theory can mine Blakecoin still waiting on a reply from the manufacture about support

cant rule out "Testing" of asics before release as well as large gpu farms profit switching but whatever the case network is still minting new blocks just average times can be off until things stabilize

best time to mine has been the years before all this action Cheesy

the "most profitable" on a day basis maybe just is not best way to make larger gains on time/effort due to the sheer competition time will tell I guess Tongue

Now you have to explain what the heck happened ... I was undermining quietly, then I entered the "edit account" to enter the address of the wallet for the payout and when I went to type the pin (which I remember from memory and it is always that) has always given the error "wrong pin".
I tried to reset it but the pool system replied "we can not send you email to the specified address" (which is a fully functional gmail address).
Now the amount is also suspended and the pool writes me to check my email to unlock it ... well, it's 72 hours that I do not receive any mail !!

What's now? Also because I had undermined a lot and I would not lose the blc ...

Neshdan

jr. member

Activity: 67

Merit: 3

Quote from: BlueDragon747 on January 21, 2018, 07:32:37 AM

Quote from: Neshdan on January 20, 2018, 06:09:00 PM

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?

not cleanly exiting threads looks like boost issue imho

Yup, i think so too. Just asked, because there were some occurances of this fault in 2013 on the Bitcoin-wallet too, but that seemed to have to do with closing unlocked encrypted wallets. As my wallets are not encrypted yet, it wont apply on my messages. https://github.com/bitcoin/bitcoin/issues/2704

BlueDragon747

legendary

Activity: 1509

Merit: 1030

Solutions Architect

Quote from: Neshdan on January 20, 2018, 06:09:00 PM

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?

not cleanly exiting threads looks like boost issue imho

Neshdan

jr. member

Activity: 67

Merit: 3

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?

BlueDragon747

legendary

Activity: 1509

Merit: 1030

Solutions Architect

~~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

jr. member

Activity: 67

Merit: 3

Quote from: pokermaniacxxx on January 18, 2018, 06:27:46 AM

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.

pokermaniacxxx

newbie

Activity: 53

Merit: 0

What cryptoexchanges are you going to get listed on?

Neshdan

jr. member

Activity: 67

Merit: 3

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)

BlueDragon747

legendary

Activity: 1509

Merit: 1030

Solutions Architect

Quote from: fedmahnkassad on January 18, 2018, 05:55:18 AM

Quote from: BlueDragon747 on January 18, 2018, 05:49:34 AM

Quote from: fedmahnkassad on January 18, 2018, 05:22:35 AM

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

will it work on BlakeCoin which algo is Blake256R8 hmm Roll Eyes

= 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 Undecided

fedmahnkassad

hero member

Activity: 840

Merit: 500

Twitter: @FedKassad

Quote from: BlueDragon747 on January 18, 2018, 05:49:34 AM

Quote from: fedmahnkassad on January 18, 2018, 05:22:35 AM

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

will it work on BlakeCoin which algo is Blake256R8 hmm Roll Eyes

= 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

legendary

Activity: 1509

Merit: 1030

Solutions Architect

Quote from: fedmahnkassad on January 18, 2018, 05:22:35 AM

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

will it work on BlakeCoin which algo is Blake256R8 hmm Roll Eyes

= 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

hero member

Activity: 840

Merit: 500

Twitter: @FedKassad

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

Neshdan

jr. member

Activity: 67

Merit: 3

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.

BlueDragon747

legendary

Activity: 1509

Merit: 1030

Solutions Architect

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

jr. member

Activity: 67

Merit: 3

Quote from: Ignatius on January 17, 2018, 06:41:36 PM

Quote from: Neshdan on January 17, 2018, 05:52:46 PM

Quote from: Ignatius on January 17, 2018, 09:52:38 AM

Quote from: Neshdan on January 17, 2018, 08:54:43 AM

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! Grin

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, not solve,=,0,1,. 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.

joshwaan

member

Activity: 148

Merit: 10

Any talks of another exchange for this coin?

Ignatius

sr. member

Activity: 409

Merit: 250

Quote from: Neshdan on January 17, 2018, 05:52:46 PM

Quote from: Ignatius on January 17, 2018, 09:52:38 AM

Quote from: Neshdan on January 17, 2018, 08:54:43 AM

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! Grin

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, not solve,=,0,1,.

Neshdan

jr. member

Activity: 67

Merit: 3

Quote from: Ignatius on January 17, 2018, 09:52:38 AM

Quote from: Neshdan on January 17, 2018, 08:54:43 AM

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! Grin

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?

Topic: [ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net - page 7. (Read 409453 times)