Been like this all day today ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fi63.tinypic.com%2F29626fc.jpg&t=663&c=s8ZuLjouqAL8rA) I had some DDoS in Suprnova today, but it's all fixed since about 4 hours now EDIT: Ah I just found a bug, fixed !
|
|
|
ETC network issues discussion
The ETC network appears to be facing memory usage attacks. The issue is likely related to the latest attacks on the ETH network. •Both parity and geth nodes are affected by the attack. •For miners, it is recommended to use nodes with 16GB and above, and increase swap size to 64GB. •More info and advice on how to deal with this attack may be available in the #mining channel of the ETC Community Slack.
https://etc.suprnova.cc is all updated now
|
|
|
I'm wondering if there are GPU miners already available... I guess only the Suprnova owner can tell for sure.. ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) OC, if that is not a secret, could you please tell if you see any workers with big hashrate coming from a single IP? Suprnova GUI is extremely slow btw. Servers seem to be overloaded... Pool.mn is ok though. I don't see anything suspicious to a gpu miner yet. I'm working on some load balancing but the server is indeed a bit crowded at the moment, should be better soon Load is fixed - server is fine
|
|
|
I'm having intermittant stratum connection problems at suprnova: connection refused, subscribe timeout. Retry is usually successful, the servers are probably straining under the load.
Exactly, try pool.mn an and the other pools there are also still lots of people trying to mine with wrong algos and it takes a bit until they are banned
|
|
|
I see that the pool xzc.suprnova.cc has got problem it doesn't show the worker hashrate in my account and it seems that the payout is not shown on dashboard . Please check it
Well, if your worker isn't shown on the dashboard that also means you get no payout as there is no hash on the pool ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Try to look at the "My Workers" page if the hashrate is displayed there.
|
|
|
my cpu is at 200% with the gui client and setgenerate true 2 but gethashespersec = 0. wtf?
I think now only the enterprise CPUs are able to mine the Zcoin. With every single block the hashrate drops... Not yet. You can easily mine with i3/i5/i7 or even with older Core2Quad or Core2Duo CPUs for now. Hashrate will not be big, but decent enough, so you can get few coins per day with few machines. Depending on what they will cost, it could be reasonable. I wonder where these guys are getting their CPU power from? This is on Suprnova: Rank Donor User Name KH/s XZC/Day 1 paulscreen 112 9,458.737 2 huber 84 7,057.705 3 iflyplane 55 4,659.601 4 anonymous 34 2,874.489 5 anonymous 32 2,659.563 6 anonymous 26 2,192.228 112 Khash/s? Botnets or GPU miner? The Supernova numbers are way off. I think the calculations are based on a different coin. ZCoin's entire network hashrate is 88.5 kH/s at the moment. It's not KH/s but H/s OC, with all the respect those numbers cannot be hash/s. Just one of my machines shows 17.95 hash/s locally, but all the machines combined show just about 1.2 something/s at Suprnova (in average). That could be KH/s or something else, but it cannot be hash/sec. Now we have miner with 204 something/sec!!! That should be about 1000 CPU cores working, when estimated compared with my hashrate and shown number! ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Yes, you're right, it's indeed kh/s, i'm a bit confused sorry.
|
|
|
my cpu is at 200% with the gui client and setgenerate true 2 but gethashespersec = 0. wtf?
I think now only the enterprise CPUs are able to mine the Zcoin. With every single block the hashrate drops... Not yet. You can easily mine with i3/i5/i7 or even with older Core2Quad or Core2Duo CPUs for now. Hashrate will not be big, but decent enough, so you can get few coins per day with few machines. Depending on what they will cost, it could be reasonable. I wonder where these guys are getting their CPU power from? This is on Suprnova: Rank Donor User Name KH/s XZC/Day 1 paulscreen 112 9,458.737 2 huber 84 7,057.705 3 iflyplane 55 4,659.601 4 anonymous 34 2,874.489 5 anonymous 32 2,659.563 6 anonymous 26 2,192.228 112 Khash/s? Botnets or GPU miner? The Supernova numbers are way off. I think the calculations are based on a different coin. ZCoin's entire network hashrate is 88.5 kH/s at the moment. It's not KH/s but H/s
|
|
|
At pool last block 2394, miner show 2417 ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Server is at capacity limit currently, frontend is slow, i'm working on it.
|
|
|
If you guys have some free time you can easily port a GPU miner for this coin. Search for CPUMINER with OpenCL and modify the kernel to mine this Lyra2 algo with the current parameters.
Just look at the other algorithm C source codes and opencl kernels and make the necessary changes, you can use debug the program to make sure you are on the right path.
However at this moment it seems like a waste of time because nobody knows what speeds GPUs will hash at because of the matrix issue, and nobody knows when the algorithm will be changed. Maybe if it got listed on Poloniex or Bittrex and had large buy support.
This won't work, because the input for the algo is 80 bytes, not 64 bytes as in all the current available gpu miner implementations. Current implementations use lyra2 as a chained algo, input is 64 bytes because it's in the middle of the chain. ZCoin uses pure lyra2, so it's the only algo or the first in the chain and it needs to hash 80 bytes. Yes I am just noticing this, the height is the extra part. Wouldn't the fastest and easiest way to do this is just to re-use the current Lyra2rev2 algo and just null the blake256,keccak,skein,cubehash, bmw256 hashes and transfer the target argument from the last hash to the lyra2 part? This way you don't have to rewrite everything from scratch. Still won't work.. you need a GPU function for Lyra2 that hases 80 bytes, not 64 bytes Example: Hashin: 80bytes80bytes80bytes80bytes Using a correct, 80 bytes hash results in: adasebadasebadasebadasebada Using a wrong 64 bytes hash results in: adasebadase The result is incomplete.
|
|
|
If you guys have some free time you can easily port a GPU miner for this coin. Search for CPUMINER with OpenCL and modify the kernel to mine this Lyra2 algo with the current parameters.
Just look at the other algorithm C source codes and opencl kernels and make the necessary changes, you can use debug the program to make sure you are on the right path.
However at this moment it seems like a waste of time because nobody knows what speeds GPUs will hash at because of the matrix issue, and nobody knows when the algorithm will be changed. Maybe if it got listed on Poloniex or Bittrex and had large buy support.
This won't work, because the input for the algo is 80 bytes, not 64 bytes as in all the current available gpu miner implementations. Current implementations use lyra2 as a chained algo, input is 64 bytes because it's in the middle of the chain. ZCoin uses pure lyra2, so it's the only algo or the first in the chain and it needs to hash 80 bytes.
|
|
|
hey folks, i'm delisting Neva from https://neva.suprnova.ccPlease withdraw your remaining funds and switch to other pools. Thanks Sorry to hear that. But anyway thank you for all the support to Nevacoin since day 1 ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) I find it funny that he says he is closing it due to low interest when it is/was the largest Neva pool and had 98 miners around the time of his posting. That's more miners than about half of Nova's pools... It's more about pool hash vs net hash, not minercount.
|
|
|
Im trying to feed the noonce loop into an opencl kernel so we can finally GPU mine this coin however upon looking at the code its messed up.
LYRA2 is a matrix, usually of 2 or 4. However for this coin the matrix = height; so with every new block the matrix gets bigger and bigger and it will get harder and harder to solve. Pretty much like the difficulty bomb with ETHEREUM.
This is exactly what I was posting in the first thread already, mining will come to an end sooner or later... With every new block it gets harder to mine
|
|
|
Ugh.. so many error in the code... unbelievable
Ugh so many damns not given omg... wow bud is this all you do? Run around threads and complain? This was something we made for the Dev quickly as a fun token. Nothing more nothing less. If there's issues we'll fix it for the dev. 1. I'm not your "bud", dude. Fuzzbawls Script is doing well as it's an easy checker for obvious things in code which should nowadays be fixed on launch. I've had a quick look, it wouldn't compile because it's missing several objects in the Makefile and I've also noticed no dnsseeds in the code and the provided addnode is/was hosted obviously on a home/residential connection.. So if someone cannot even afford a $3 VPS to host his node I didn't even look further but maybe this is the next zcash 2.0 ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) Good luck with your attitude and your "project(s)"
|
|
|
how long I'll be able to catch a unit on suprnova, and if I can do this is to do with 0.4-0.5 Kh/s ? or have to settle for accepted shares
Use the ultra low port You think: stratum+tcp://xzc-low.suprnova.cc:5595 ? yes
|
|
|
how long I'll be able to catch a unit on suprnova, and if I can do this is to do with 0.4-0.5 Kh/s ? or have to settle for accepted shares
Use the ultra low port
|
|
|
hey folks, i'm delisting Neva from https://neva.suprnova.ccPlease withdraw your remaining funds and switch to other pools. Thanks
|
|
|
Okay, I've added a "super-low-diff-port":
stratum+tcp://xzc-low.suprnova.cc:5595
Initial difficulty is lowest possible there, however, you should see the same low diff after a few minutes on the other ports as well when Vardiff retargets.
|
|
|
120 confirmations for this coin ...on supernova all nigth nothing in confirmed .... @ocminer fix that and set much lower vardiff ...this is not gpu coin man...and we have another option to mine on pool.mn but this pool is to slow ...
Block time is 10 minutes, I can't do anything about confirmations but I'll add a low diff port for you guys Edit : if you just wait a bit after you've connected vardiff automatically turns your diff down btw I second that port. The problem on my Celerons is fixed. They just needed a very long time to turn in because of the high entry difficulty I think. Exactly. It should take about 2 to 3 mins after initial connect until you see accepted shares, I had to bump up initial diff because lots of people still try to mine with wrong algos and flood the pool with invalid shares, the higher diff makes it a bit better
|
|
|
120 confirmations for this coin ...on supernova all nigth nothing in confirmed .... @ocminer fix that and set much lower vardiff ...this is not gpu coin man...and we have another option to mine on pool.mn but this pool is to slow ...
Block time is 10 minutes, I can't do anything about confirmations but I'll add a low diff port for you guys Edit : if you just wait a bit after you've connected vardiff automatically turns your diff down btw
|
|
|
|