___ _ ___ _ _
/ __\___ (_)_ __ / __\ |__ ___ ___| | _____ _ __
/ / / _ \| | '_ \ / / | '_ \ / _ \/ __| |/ / _ \ '__|
/ /__| (_) | | | | / /___| | | | __/ (__| < __/ |
\____/\___/|_|_| |_\____/|_| |_|\___|\___|_|\_\___|_|
v0.0.4 October 2016 | http://www.fuzzbawls.pw
Report Date: Tue Jan 10 23:29:58 PST 2017
Checking Host OS... MAC
Creating temp folder to clone remote repository...
Cloning https://github.com/ChicksCoin/chicks-source.git...
-= Repository Information =-
============================================================
Number of commits: 35
Last commit date: Tue Jan 10 08:28:54 PST 2017
Days since last commit: .62 Days
-= Build System Information =-
============================================================
Build Type: QMAKE/Makefile
Build Version: 1.0.7.0
Qt Bin: chicks-qt
Daemon Bin: chicksd
-= Coin Specifications =-
============================================================
Coin Name: chicks
Client Version: 1.0.0.0
Client Name: /Satoshi:1.0.0.0/
Default P2P Port: 10123
Default PRC Port: 10124
Message Start String: 0x7c 0xcf 0x0e 0x80
Protocol Version: 60013
-= Coin Information Checks =-
============================================================
Matching P2PPORT in init documentation: [OK]
Matching RPCPORT in init documentation: [OK]
Build & Client Version Match: [!!]
-= Library Version Compliance Checks =-
============================================================
Miniupnpc v1.9 (API 14): [!!]
OpenSSL v1.0.1k+ (Strict DER Signatures): [!!]
Boost v1.58+ (boost::get): [OK]
-= Security Standards Checks =-
============================================================
Free of IRC related files: [!!]
IRC based peer fetching: [!!]
Contains signature malleability patch (PPCoin): [!!]
-= Connectivity Checks =-
============================================================
Contains unique ClientName: [!!]
Contains DNS seeder addresses: [OK]
Contains Hex-Encoded seeder addresses: [!!]
Has at least ONE default connection method: [**]
Number of DNS Seeds: 1
Listing DNS Seed addresses...
* node.walletbuilders.com
95.211.57.108 [OK]
-= OS Specific Checks =-
============================================================
Mac OS X Native Notification Support: [!!]
Mac OS X Deployment Script: [OK]
Mac OS X Application Icon: [OK]
Mac OS X Dock Icon Menu (Qt5): [!!]
Windows Installer Script: [**]
Windows Installer Header Image: [!!]
Windows Installer Logo Image: [!!]
Windows Installer Icon: [!!]
============================================================
* IRC based peer fetching has long since been depreciated!
* Developer should remove it and use DNS Seeding instead.
* Windows deployment script is using an incorrect name!
* Deployment build won't have the correct metadata!
* Windows deployment sript is using an incorrect version!
* Deployment build won't have the correct metadata!
Results should be manually verified and you should NOT rely
on any automated scripts (including this one) before running
or compiling any crypto wallet.
============================================================
Also, "total" supply is unlimited. Total coin supply 884211 coins Which one is correct? Fuzzbawls is correct, there is no max supply |
|
|
|
Thanks for the help !  |
|
|
|
Hey OC, it seems that the zec dashboard broke, we don't have any datas showing.  thanks  Hmm, works for me, I can see my balance, my workers etc.. Maybe log out / close the browser and log in again ? Ok working again, had tried logout/login with no success, had to purge cache & cookies and all good, sorry man will try this the next time Interesting, I've heard that two times now, are you using Firefox ? Im using chromium. Something i noticed on the dashboard, the unit for the current pool sol hashrate should be ksols and not sols. Also why personnal hashrate marked as H/s and not sols/s is there a reason ? Fixed and fixed  |
|
|
|
Hey OC, it seems that the zec dashboard broke, we don't have any datas showing. thanks Hmm, works for me, I can see my balance, my workers etc.. Maybe log out / close the browser and log in again ? Ok working again, had tried logout/login with no success, had to purge cache & cookies and all good, sorry man will try this the next time Interesting, I've heard that two times now, are you using Firefox ? |
|
|
|
Hey OC, it seems that the zec dashboard broke, we don't have any datas showing. thanks Hmm, works for me, I can see my balance, my workers etc.. Maybe log out / close the browser and log in again ? |
|
|
|
Getting a lot of "low lifficulty shares" warnings...
I use r9 390.
start.bat:
SETX GPU_MAX_ALLOC_PERCENT 100
SETX GPU_USE_SYNC_OBJECTS 1
SETX GPU_FORCE_64BIT_PTR 1
optiminer -s zec-eu.suprnova.cc:2142 -u login.worker -p mypw
pause
Pool registers 0 H/s.
What am I doing wrong?
It's probably easier for testing if you mine with your wallet address. Generate an address at your favourite exchange, then do: optiminer -s zec-eu.suprnova.cc:2142 -u WALLETADDRESS.rig1 -p x And access the anondashboard: https://zec.suprnova.cc/index.php?page=anondashboard&user=WALLETADDRESSand you should see some shares etc. (be sure to set a rigname when mining.. so WALLETADDRESS. rig1 |
|
|
|
Wat ? No ICO ? Looks like the best coin ever  |
|
|
|
|
I finally found the error which lead to a defunct dashboard for Anonymous users (mining with your wallet address) - fixed now and dashboard/payouts etc all working agian
|
|
|
|
|
Coin algo is Script... Yes .. Right..
|
|
|
|
and here for suprnova @ windows: SETX GPU_MAX_ALLOC_PERCENT 100
SETX GPU_USE_SYNC_OBJECTS 1
SETX GPU_FORCE_64BIT_PTR=1
optiminer -s zec-eu.suprnova.cc:2142 -u youraddress.rig1 -p x -i 4
pause
have fun |
|
|
|
Disconnect still occurring according to your dashboard page but worker page shows workers still connected. Monitoring emails of idle workers being sent out. Hashrate on dashboard almost zero. Issues today?
I've just restarted the stratum because of the nicehash fix so that should have caused a small disconnect but that was all, nothing else should have happened and your workers should be working again. |
|
|
|
Disconnected. Pool difficulty too low. when trying to send some rented power thrugh nicehash port  (((( getting disconnect like crazy... fix?! Thanks for your Info, found the error and fixed it. |
|
|
|
Thanx, but it leads me to a couple questions, I checked "My Account" -> "Edit workers" and the hashrate reading is much smaller than the reading from Claymore, which one is accurate? In the dashboard, your contributors hashrate is measured in H/s and ZEC/Day, and I'm unable to do so much ZEC/Day per H/s. For example, right now I'm supposed to get 0'073 ZEC/day with 411 H/s (Dashboard reading) but actually I'm doing like 0'13 ZEC/Day with 1300 H/s (Claymore reading). There is a huge difference, because with the Dashboard ratio I should be doing 0'23 ZEC/Day instead of 0'13 @armazingerz:
Check "My Account" -> "Edit workers". You should see the full hashrate there, the Dashboard is cached for performance.
OVH seems to have a bigger issue at the moment, some routes are broken and the servers unreachable, I hope they'll fix it ASAP. From Suprnova's side everything is okay.
Hi ! if your hashrate on "Edit Workers" is much smaller than what you're worker is actually reading there's something wrong. Maybe try to switch to another stratum server (zec.suprnova.cc:2142 instead of zec-eu.suprnova.cc:2142 (or vice versa)) and see if its better than. The Dashboard is knowingly a bit slower and "lazier" in refreshing, but Edit Workers should match pretty close.. maybe +- 10 % |
|
|
|
|
People still don't seem to see the obviousness... Bumping
|
|
|
|
I indeed found a bug where some unintended ip banning on stratum happened in case you've used claymore over ssl.
Fixed now!
17 seconds later and the problem is solved. I'm back. How is the payment address + ID coming along? I'd say I'm at 80%... Some checks need to be implemented that users don't enter false payments ids or no id at all. Also the id has to be removed when the user changes to a kraken address with integrated ID etc.. It's not as easy as thought first, but I'm pretty far already |
|
|
|
|
I indeed found a bug where some unintended ip banning on stratum happened in case you've used claymore over ssl.
Fixed now!
|
|
|
|
|
Hi !
Usually 15 Min as padawan stated already, but make sure your mailbox allows those mails, they often falsely get into spam folders.
Also make sure you're using the worker not on another suprnova pool as those mails are global i.e. if you're mining ZEC at zec.suprnova.cc and have yourworker.1 running there but are using another physical machine under the same workername on xmr.suprnova.cc you will NOT get notifications as the system thinks the worker was just switched to another pool.
|
|
|
|
having same issue with low difficulty on a few workers that are hashing over 4k. Worst part is that worker gets banned even though the server is still accepting work for suprnova.
On top of that, when the worker gets banned, it doesn't send an email of an idle worker. Tested by taking a worker not banned offline and still no email 1 hour later. Block emails come in just fine.
Low difficulty means invalid work, that can happen with some overclocking settings. Banning should not happen at all unless you send ONLY invalid shares for a certain amount of time. I'll check banning again though. |
|
|
|
Suprnova im still waiting for yu to add the polo wallet id so i can use your pool any update
Very soon, I'm testing currently. |
|
|
|
|
Show Posts
