 Show Posts
|
|
Pages: [1] 2 3 »
|
The coin is completely dead  |
|
|
|
|
Hi,
I have a (broken) Antminer D3 without PSU.
Is it possible to power up its controller board without blades, with an ordinary PC PSU ?
(I understand it can't mine this way, I only need to access its web interface dashboard)
|
|
|
|
It seems I got my 0.0015 bitcoin crumbs from the pool.  ) |
|
|
|
Hmmm, the pool is gone?  I liked its multi-algo system, thare's no other pool like that, afaik... However, going silently without paying off is not good at all.  |
|
|
|
Hello. Why do not you put your miner on githab? It looks suspicious. Probably because Github.org doesn't want devs who f*ck GPL license. I downloaded the latest release and didn't find there any source code. Maybe there's some place where I can get it? If zFastminer is build upon Tanguy Pruvot's ccminer (or any fork of Christian Buchner's original ccminer) -- it is under GPL v.3 |
|
|
|
UPDATE.
1. VERGE clearnet version was installed to reduce amount of orphans blocks found. It is safe to mine with less orphans now.
Hopefully it will improve accuracy as well!
Does it mean that orphan rate is not included in profit prediction? This would explain a lot, as suggested before. Hope clearnet helps, because these orphans are anoying. However, I thought that ist due to relatively low hashrate in comparison to whole network, am I wrong? I think wrong estimates were caused by worsen connectivity via darknet, hence orphans, hence lower end result. Now have fixed it, see it is much better already for last blocks in x17 Verge. The issue is not fixed at all. There are 10 Orphan blocks on zergpool for the past 10 hours and each block is found every 45 minutes and this means a loss of 10% caused by orphan blocks and because of the terrible "DARKNET" network you are using. Wtf is this "darknet network"?? |
|
|
|
The owner takes 0,5% pool fee even if it advertises everywhere, even in the title of this thread that the pool is 0% and this is not true : ZERGPOOL.com - NEW!Multialgo, autoexchange, 0% fee, <<< not true, and disappointing late action taken after 6 hours It was explained several times why this 0.5% was introduced -- for hardware upgrade. I hope it was upgraded decently and solved disconnect problem, at least. Also such a sh*t can happen with _any_ sh*tcoin, at _any_ time. Whoever is not ready to take this risk -- those shouldn't mine sh*tcoins, first of all. Actually, they shouldn't go into mining at all, for that matter -- mining is not a "business", and even less it's a "set-and-forget passive income", it's more like gambling with your money on stake. Anyway, I hope the pool-owner will fix that XVG issue pretty soon or drop that coin forever. |
|
|
|
We're glad to introduce a new NEOSCRYPT pool with over 40 coins already with more being added on a daily basis. Payouts happen each 2 hours, fee is 0.5%. No auto-exchange to BTC. https://althash.ruThe website doesn't work. |
|
|
|
If a pool with high minimum payout stops servicing a coin (XVG), is has to payout the miners in the same moment or... Each and every sh*tcoin around can be hacked, forked or f*cked up some other way or simply die forever, at any arbitrary moment, taking along all its earnings, payments, wallets, etc. It's a part of the current cryptocurrency gambling. No sane pool-owner would guarantee the opposite or take any responsibility of that unlucky sh*tcoin's devs. However zergpool's owner could deactivate that XVG coin a bit earlier, not waiting for several hours. |
|
|
|
Do you know why this problem only happened to zergpool and the other pools had no issues like this ? What was the problem, in simple words? XVG coin suddenly got f*cked, it forked, and the miners who was mining that coin on zergpool.com lost what they thought they earned on it? |
|
|
|
Can you please tell me exactly what the " 24 Hours Actual*** " column represents? Does that mean that if I started mining exactly 24 hours earlier , that's the actual real profit I would have made?
Yep, it's the actual profit made from the past 24 hours. It's what we call a "lagging indicator". Do you mean "last 24 hours back starting from right now" or "24 calendar hours, e.g. last 0:0 AM -- 12:0 PM period"? |
|
|
|
|
x16s doesn't work? No miners, no hashrate, no estimates.
|
|
|
|
|
"xevan" algo seems to be down.
[2018-03-29 21:59:16] Starting on stratum+tcp://xevan.mine.zpool.ca:3739
[2018-03-29 21:59:26] stratum_subscribe timed out
[2018-03-29 21:59:26] ...retry after 30 seconds
However, most other algos seem Ok.
|
|
|
|
|
Frontend bug: at a BTC wallet page it says ** bitstamp $usd USD/BTC, looks like a variable doesn't expand.
|
|
|
|
UPDATE
1. HW upgrade with associated downtime is planned for 14:00 CET-14:30 CET 24.03.2018(today). And you are safe to mine until then
Good luck. When the upgrade will be over, please put a note here. |
|
|
|
1) "connection refused" - that I noticed a lot for many RIGS ( DDOS protection is too restrictive or server is overloaded ) ;
2) many orphaned blocks caused by too late coin being disabled or bad configuration when there is a chain split
I believe the root of evil is the same for both: the hardware is too weak to handle more than a certain number of miners connections -> when this limit is reached, the stratum server falls off and miners start getting "connection refused" -> when stratum server goes up and miners resume working on the block, that block comes too late and the network refuses it (i.e. it becomes "orphan"). However, it's just my theory, I don't know what actually goes there. |
|
|
|
Looks like something up with Tribus consistently for the past half hour to hour:
*** ccminer 2.2.4 for nVidia GPUs by tpruvot@github ***
Built with VC++ 2013 and nVidia CUDA SDK 9.0 64-bits
Originally based on Christian Buchner and Christian H. project
Include some kernels from alexis78, djm34, djEzo, tsiv and krnlx.
BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)
[2018-03-18 20:37:38] Starting on stratum+tcp://mine.zergpool.com:8533
[2018-03-18 20:37:38] NVML GPU monitoring enabled.
[2018-03-18 20:37:38] NVAPI GPU monitoring enabled.
[2018-03-18 20:37:38] 2 miner threads started, using 'tribus' algorithm.
[2018-03-18 20:37:39] API open to the network in read-only mode on port 4028
[2018-03-18 20:37:41] ...retry after 30 seconds
[2018-03-18 20:38:15] ...retry after 30 seconds
[2018-03-18 20:38:48] ...retry after 30 seconds
[2018-03-18 20:39:21] ...retry after 30 seconds
Seeing this on multiple systems. Anyone else having this issue?
Yes. Same issue. There are still connection issues when the number of simultaneous miners for a single algo is above 1000. When can you install a much powerful server with many CPU cores ? Installing many small servers is not helping because the number of miners can go very fast from 100 to 2000 while total number of miners remains almost the same and miners are never distributed to all algos, miners are like "a swarm of bees" that go from one algo to another all driven by Awesome Miner.When will you have a very powerful server installed ? He says about the coming weekend https://bitcointalk.org/index.php?topic=2759935.msg32505901#msg32505901 |
|
|
|
API at http://api.zergpool.com:8080/api/currencies doesn't match with what's on the website. e.g. currently SGL is marked as "no-autotrade", but the API says "noautotrade=0" also there're problems there with estimates, hashrate, etc. I wonder which figures are correct. |
|
|
|
UPDATE
1. We need to purchase more powerful servers, so enabling 0.5% fee for a week or so
It's not fees that drive people away from your pool. Look at other pools, nearly everyone there has a fee, 0.5-2% is pretty standard. If you put similar fees and arrange better stability and better service and better features, you'll catch them up. |
|
|
|
Sorry for any inconveniences encountered with any pool issues.
For the more reliable earning estimates, I would recommended to refer to 24h estimated and 24h actual data at the pool. To maximize earnings using any profit switching software you should use current estimate. However it is indeed changing as network difficulties and coin prices do. Current estimate figures in API sometimes (often enough) don't match the figures on the website (about 24h figures I'm not sure). Besides, the pool have connection issues. Why wouldn't you put, say, a 1% fee and rent a better server or hosting plan, etc. |
|
|
|
|
