Why don't withdrawals to pay ? The coin is rejecting a lot of transactions it seems, I'll recredit those failed payments to the accounts so you can just withdraw again
|
|
|
I'm not sure about that question but you can pick one of the coins from www.suprnova.cc and mine them by looking at the "Getting Started" Pages .. Or come into IRC #suprnova on freenet of you have questions or need help getting the miner set up
|
|
|
The one from your site is 189 MB (198,889,472 bytes) exact on hard disc. SO I have no idea what the cause is. I will try to download again and see if get same results.
Ok, then it seems you somehow get an old file, it's 198997968 (198 MB) bytes here (scratchpad.bin) And it's md5sum is: 57d8ef50bf2c6722a55e2173f8f3df59 Link is: http://bbr.suprnova.cc/scratchpad.binMaybe try deleting it first ?!
|
|
|
for ocminer. Downloaded scratchpad file Rebuilt URL to: http://bbr.suprnova.cc:7777/ Hostname was NOT found in DNS cache Adding handle: conn: 0x17b1f0f0 Adding handle: send: 0 Adding handle: recv: 0 Curl_addHandleToPipeline: length: 1 - Conn 0 (0x17b1f0f0) send_pipe: 1, recv_pipe: 0 Trying 37.59.21.58... TCP_NODELAY set Connected to bbr.suprnova.cc (xxxx) port 7777 (#0) Connection #0 to host bbr.suprnova.cc left intact 2016-09-16 18:21:59.553] > {"method": "login", "params": {"login": "iLikeCoins.med", "pass": "x", "hi": { "height": 609134, "block_id": "71641df2dc4514c597e8c5 b2d2f1f5e3ce9a0b0476ae93c8c9bb4f5e1658848" }, "agent": "cpuminer-multi/0.1"}, "id": 1} 2016-09-16 18:21:59.579] < {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"scratchpad too old ! you have to (re)download scratchpad.bin"}} 2016-09-16 18:21:59.583] Stratum authentication failed 2016-09-16 18:21:59.584] ...retry after 10 seconds And I have downloaded scratchpad just before this post and tried again with same results. What's the exact size of your scratchpad.bin?
|
|
|
There are no stupid questions ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) I checked the pools wallet and I can confirmed didn't find a block yet. Seems like the settings are not correct. I will keep my miner there and try to have a look on stratum this evening. I am useing combination of mpos for front end and unomp proxy. We have many many shares in the sql database so the shares are getting collected correctly. If you want to find blocks i suggest you move your miners back to your wallets until i figured out why we didn't find a block. Maybe it is just very very bad luck. There are no stupid questions ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) I checked the pools wallet and I can confirmed didn't find a block yet. Seems like the settings are not correct. I will keep my miner there and try to have a look on stratum this evening. I am useing combination of mpos for front end and unomp proxy. We have many many shares in the sql database so the shares are getting collected correctly. If you want to find blocks i suggest you move your miners back to your wallets until i figured out why we didn't find a block. Maybe it is just very very bad luck. I've had a Coinium pool running for last 2 days with no luck ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) Same issue as you valid shares but no blocks found even tried removing the difficulty check at the pool level but still didn't find any. Setup a UNOMP pool 1hour ago shares are submitting so will leave it for a bit but guessing ill have the same issue again. Just been watching the difficulty of my submit's compared to the block difficulty and it looks within range that it could get one. Only time will tell ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Testnet.... guys.. Use testnet.. it's not so hard and you'll find lots of blocks instantly Wasn't the testnet removed? I thought it got removed after VRM testphase was over. I have found a mistake on the stratum and i fixed it. Restarting the proxy now, your miners should all reconnect after 30s disconnct time. You can easily create your own, private testnet by calculating a new genesis block and recompiling the daemon with that, I did it the same way
|
|
|
There are no stupid questions ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) I checked the pools wallet and I can confirmed didn't find a block yet. Seems like the settings are not correct. I will keep my miner there and try to have a look on stratum this evening. I am useing combination of mpos for front end and unomp proxy. We have many many shares in the sql database so the shares are getting collected correctly. If you want to find blocks i suggest you move your miners back to your wallets until i figured out why we didn't find a block. Maybe it is just very very bad luck. There are no stupid questions ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) I checked the pools wallet and I can confirmed didn't find a block yet. Seems like the settings are not correct. I will keep my miner there and try to have a look on stratum this evening. I am useing combination of mpos for front end and unomp proxy. We have many many shares in the sql database so the shares are getting collected correctly. If you want to find blocks i suggest you move your miners back to your wallets until i figured out why we didn't find a block. Maybe it is just very very bad luck. I've had a Coinium pool running for last 2 days with no luck ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) Same issue as you valid shares but no blocks found even tried removing the difficulty check at the pool level but still didn't find any. Setup a UNOMP pool 1hour ago shares are submitting so will leave it for a bit but guessing ill have the same issue again. Just been watching the difficulty of my submit's compared to the block difficulty and it looks within range that it could get one. Only time will tell ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Testnet.... guys.. Use testnet.. it's not so hard and you'll find lots of blocks instantly
|
|
|
Any advise on how to resolve following error when using gpu to mine with. [GPU1] share doesn't validate on CPU, hash=8d04abf7, target=000018da [GPU1] share doesn't validate on CPU, hash=fb933a2c, target=000018da minerd -a wildkeccak_ocl -o stratum+tcp://bbr.suprnova.cc:7777 -u iLikecoin.med -p x -l scratchpad.bin -k http://bbr.suprnova.cc/scratchpad.binAny advise on how to fix this please. Using miner cpuminer-multi-opencl CPU miner works fine when suing the comnds and taking out ocl however using gpu gives the error above hoping someone can resolve this problem for me. I get the same error Resolved my problem after back tracking in this thread. Found was drivers for gpu. use catalyst 15.12 or lower Uninstall all your gpu drivers and install http://support.amd.com/en-us/kb-articles/Pages/latest-catalyst-windows-beta.aspxNow running smooth cant say the same for the pool am assuming its under ddos. Glad you got it working, nope, no DDoS on suprnova, running fine. I see too many reconnects to your pool. About 10% time my miners do nothing waiting for auth. It didn't happen with mbk's pool. Yep, thats when your scratchpad.bin is invalid/too old.. As explained also on the Pool header. It's a common bug of some clients, it works fine with bbr-cudaminer though. Well am not nvidia am amd here maybe client needs to be fixed and updated to pan out the plagued bugs. And too add 2 miner threads started, using 'wildkeccak_ocl' algorithm. Starting Stratum on stratum+tcp://bbr.suprnova.cc:7777 Stratum authentication failed ...retry after 10 seconds Stratum authentication failed ...retry after 10 seconds Same here Stratum authentication failed ...retry after 10 seconds add -P to your cmdline and you'll see it's the error with the old scratchpad. Working fine now, thanks. Withdraw to exchanges are coming too? Yup, but i'm working on a profit calc and an XMR pool currently, so it might take a bit, you can still withdraw to your wallet all the time.
|
|
|
Any advise on how to resolve following error when using gpu to mine with. [GPU1] share doesn't validate on CPU, hash=8d04abf7, target=000018da [GPU1] share doesn't validate on CPU, hash=fb933a2c, target=000018da minerd -a wildkeccak_ocl -o stratum+tcp://bbr.suprnova.cc:7777 -u iLikecoin.med -p x -l scratchpad.bin -k http://bbr.suprnova.cc/scratchpad.binAny advise on how to fix this please. Using miner cpuminer-multi-opencl CPU miner works fine when suing the comnds and taking out ocl however using gpu gives the error above hoping someone can resolve this problem for me. I get the same error Resolved my problem after back tracking in this thread. Found was drivers for gpu. use catalyst 15.12 or lower Uninstall all your gpu drivers and install http://support.amd.com/en-us/kb-articles/Pages/latest-catalyst-windows-beta.aspxNow running smooth cant say the same for the pool am assuming its under ddos. Glad you got it working, nope, no DDoS on suprnova, running fine. I see too many reconnects to your pool. About 10% time my miners do nothing waiting for auth. It didn't happen with mbk's pool. Yep, thats when your scratchpad.bin is invalid/too old.. As explained also on the Pool header. It's a common bug of some clients, it works fine with bbr-cudaminer though. Well am not nvidia am amd here maybe client needs to be fixed and updated to pan out the plagued bugs. And too add 2 miner threads started, using 'wildkeccak_ocl' algorithm. Starting Stratum on stratum+tcp://bbr.suprnova.cc:7777 Stratum authentication failed ...retry after 10 seconds Stratum authentication failed ...retry after 10 seconds Same here Stratum authentication failed ...retry after 10 seconds add -P to your cmdline and you'll see it's the error with the old scratchpad.
|
|
|
Any advise on how to resolve following error when using gpu to mine with. [GPU1] share doesn't validate on CPU, hash=8d04abf7, target=000018da [GPU1] share doesn't validate on CPU, hash=fb933a2c, target=000018da minerd -a wildkeccak_ocl -o stratum+tcp://bbr.suprnova.cc:7777 -u iLikecoin.med -p x -l scratchpad.bin -k http://bbr.suprnova.cc/scratchpad.binAny advise on how to fix this please. Using miner cpuminer-multi-opencl CPU miner works fine when suing the comnds and taking out ocl however using gpu gives the error above hoping someone can resolve this problem for me. I get the same error Resolved my problem after back tracking in this thread. Found was drivers for gpu. use catalyst 15.12 or lower Uninstall all your gpu drivers and install http://support.amd.com/en-us/kb-articles/Pages/latest-catalyst-windows-beta.aspxNow running smooth cant say the same for the pool am assuming its under ddos. Glad you got it working, nope, no DDoS on suprnova, running fine. I see too many reconnects to your pool. About 10% time my miners do nothing waiting for auth. It didn't happen with mbk's pool. Yep, thats when your scratchpad.bin is invalid/too old.. As explained also on the Pool header. It's a common bug of some clients, it works fine with bbr-cudaminer though. Have an issue on supernova I can't with draw any coins keep getting this . Failed to update your account: Invalid coin address 1Gpf3BHEvo92GF3agYAbFFbBEtvqv2HqwitYSx6ZxFbzg9aFUNZx3vpczUKsnYhbPF78ofdcMNcupHj UZ1PenCsaAa23KKc .Wallet address is good That address is 1 char too long
|
|
|
is it currently under DDOS ? Why does BBR mining come under DDOS? Its not even that valuable at the moment. Why is someone even doing this? It is probably mined by small group with FPGAs, and they are responsible for DDoS attacks. As someone said earlier this is private coin... can't we make it more expensive for them to do this, more machines to DDOS? The network has rate has more than doubled since my announcement and subsequent price increase, so keep up the public fight Are there code upgrades that could/will make setting up and maintaining mining pools easier? clintar2 mentioned there seems to be memory leak in the miner, I wonder if other communities encountered this, or if it could be a unique problem with the wild keccak algorithm I did? I don't remember saying that. Maybe you are referring to my old post about the experimental keepalive version of my miner that was having issues? that's fixed up in the repos now. I had no time to look deeply yet, but there are at least a few miners around who do not increment scratchpad.bin correctly, they always request n + x blocks without adding the latest blocks to their scratchpad. So while the good miners are always just requesting the last block, those miners request at first the last block, then the last two, then the last three, the last four and so on.. I had one miner on the pool who requested 35000 Blocks ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Any advise on how to resolve following error when using gpu to mine with. [GPU1] share doesn't validate on CPU, hash=8d04abf7, target=000018da [GPU1] share doesn't validate on CPU, hash=fb933a2c, target=000018da minerd -a wildkeccak_ocl -o stratum+tcp://bbr.suprnova.cc:7777 -u iLikecoin.med -p x -l scratchpad.bin -k http://bbr.suprnova.cc/scratchpad.binAny advise on how to fix this please. Using miner cpuminer-multi-opencl CPU miner works fine when suing the comnds and taking out ocl however using gpu gives the error above hoping someone can resolve this problem for me. I get the same error Resolved my problem after back tracking in this thread. Found was drivers for gpu. use catalyst 15.12 or lower Uninstall all your gpu drivers and install http://support.amd.com/en-us/kb-articles/Pages/latest-catalyst-windows-beta.aspxNow running smooth cant say the same for the pool am assuming its under ddos. Glad you got it working, nope, no DDoS on suprnova, running fine. I see too many reconnects to your pool. About 10% time my miners do nothing waiting for auth. It didn't happen with mbk's pool. Yep, thats when your scratchpad.bin is invalid/too old.. As explained also on the Pool header. It's a common bug of some clients, it works fine with bbr-cudaminer though.
|
|
|
Any advise on how to resolve following error when using gpu to mine with. [GPU1] share doesn't validate on CPU, hash=8d04abf7, target=000018da [GPU1] share doesn't validate on CPU, hash=fb933a2c, target=000018da minerd -a wildkeccak_ocl -o stratum+tcp://bbr.suprnova.cc:7777 -u iLikecoin.med -p x -l scratchpad.bin -k http://bbr.suprnova.cc/scratchpad.binAny advise on how to fix this please. Using miner cpuminer-multi-opencl CPU miner works fine when suing the comnds and taking out ocl however using gpu gives the error above hoping someone can resolve this problem for me. I get the same error Resolved my problem after back tracking in this thread. Found was drivers for gpu. use catalyst 15.12 or lower Uninstall all your gpu drivers and install http://support.amd.com/en-us/kb-articles/Pages/latest-catalyst-windows-beta.aspxNow running smooth cant say the same for the pool am assuming its under ddos. Glad you got it working, nope, no DDoS on suprnova, running fine.
|
|
|
Actually the miners just have to update the scratchpad correctly.. currently it only seems some are doing it correctly, this one for example: https://github.com/tpruvot/bbr-cudaminerIs using the initial scratchpad.bin which you download and then increments that scratchpad with the new hashes which are given by the pool when a new block starts. So this miner is just requesting the last block and works well, other miners start with the scratchpad.bin you've downloaded and with every round the request more and more blocks.. because they are not incrementing the .bin... The longer they run, the more blocks are requested up to a certain point where its so slow that the connection drops
|
|
|
is it currently under DDOS ? Why does BBR mining come under DDOS? Its not even that valuable at the moment. Why is someone even doing this? It is probably mined by small group with FPGAs, and they are responsible for DDoS attacks. As someone said earlier this is private coin... can't we make it more expensive for them to do this, more machines to DDOS? The network has rate has more than doubled since my announcement and subsequent price increase, so keep up the public fight Are there code upgrades that could/will make setting up and maintaining mining pools easier? clintar2 mentioned there seems to be memory leak in the miner, I wonder if other communities encountered this, or if it could be a unique problem with the wild keccak algorithm No DDoS, but the clients get "out of sync" over time.. They seem not to update the scratchpad.bin - it should be incremented with every new block, but the miners keep requesting the last X blocks when they started.. Which reaches a certain level a some point where it fails - you need to redownload the scratchpad.bin and it works again until its outdated.
|
|
|
I get so many booos! it is frustrating. why do I get so many booos. I run on mbk, I tried supernova, same stuff. I got a r7 370 and 2 cpu's but my share % is in the 70-75% range. I should be in the 800 khash range but I running in the 300 khash range because of all the boos and disconnects. this is very frustrating.
That only happens when your scratchpad.bin is outdated usually, did you download a fresh copy off my server before starting to mine? https://bbr.suprnova.cc/scratchpad.bin
|
|
|
What a pity, nice name here
|
|
|
|