kamikaza
|
|
April 28, 2017, 01:34:24 PM |
|
Matejbilahora, I have a question for you since you have been active with zoin from almost the beginning. Do you know if there is a new dev team behind the revival of zoin? They should really consider to enlist it to more exchanges etc. Perhaps it will happen in 3 days, but they should not wait too long. signs of activity and communication are the most important to keep the currency going and flowing.
|
|
|
|
|
|
"The nature of Bitcoin is such that once version 0.1 was released, the
core design was set in stone for the rest of its lifetime." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
StelioKontos
Sr. Member
Offline
Activity: 839
Merit: 267
Chad Hodler since 2013
|
|
April 28, 2017, 01:41:25 PM |
|
Yup no problems anymore:p However, it is a little too optimistic about the amount of ZOI i am able to earn in one day haha
Haha, true. - Rank User Name KH/s ZOI/Day BTC/Day 1 leggo 1,757 471,976.130 4.7198 I WISH 4.7 BTC a day! My Hashrate 111.30 KH/s are we sure this pool is legit?
|
|
|
|
Palm
Newbie
Offline
Activity: 10
Merit: 0
|
|
April 28, 2017, 01:50:34 PM |
|
zoi.digger.work Stop maining - I will explain later!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! What is it? anybody stopped?
|
|
|
|
kamikaza
|
|
April 28, 2017, 01:58:25 PM |
|
zoi.digger.work Stop maining - I will explain later!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! What is it? anybody stopped? Was did on the pool? I stopped because i got these errors again...
|
|
|
|
Deff
Sr. Member
Offline
Activity: 939
Merit: 261
Data HDD Repair - Recovery of lost information
|
|
April 28, 2017, 02:28:23 PM |
|
I have corrected on the run.
|
|
|
|
matejbilahora
Sr. Member
Offline
Activity: 1414
Merit: 275
Community built, Privacy driven
|
|
April 28, 2017, 02:45:33 PM |
|
Matejbilahora, I have a question for you since you have been active with zoin from almost the beginning. Do you know if there is a new dev team behind the revival of zoin? They should really consider to enlist it to more exchanges etc. Perhaps it will happen in 3 days, but they should not wait too long. signs of activity and communication are the most important to keep the currency going and flowing.
Hey Kamikaza, current dev is new team. First let the boys do code work and wallet. The rest will be after relaunch. We have the neccessary info for now. Do you know what is it to have few more days patience? It won´t kill us. Ann is 1st of may 2017, that is clear. Who knows what will come. Maybe price will climb, maybe will fall down, but wait as the rest of us is waiting. I wan´t zoin to be good so I let the devs do what can thay do. And by the way with exchanges you can have even the best but if project is not good it dies as cheap and everyone is going to get rid of it. So my advice: two more days +- patience, we can make it..
|
|
|
|
spirea
Member
Offline
Activity: 74
Merit: 10
|
|
April 28, 2017, 03:37:59 PM |
|
Guys, anyone tried to mini zoin solo, via wallet? I set generation true, set 4 cpus, but there is very small hashrate, and i dont even know, if ill get anything with that kind of mining..
Very hard to find a block in solo mining mode unless you have at least 10KH/S or equivalent of 10 servers X1 Amazon AWS witch cost 1000 USD/Month Each Zoin is now very cheap even at 10000 satoshi per ZOI.
|
|
|
|
degxtra1
Member
Offline
Activity: 228
Merit: 46
|
|
April 28, 2017, 03:48:29 PM |
|
zoi.acc pool not working
getting this errors
[2017-04-28 23:44:55] Stratum authentication failed [2017-04-28 23:44:55] ...retry after 10 seconds [2017-04-28 23:45:05] Stratum difficulty set to 0.0005 [2017-04-28 23:45:06] Stratum authentication failed [2017-04-28 23:45:06] ...retry after 10 seconds [2017-04-28 23:45:16] Stratum difficulty set to 0.0005 [2017-04-28 23:45:16] Stratum authentication failed [2017-04-28 23:45:16] ...retry after 10 seconds
|
|
|
|
spirea
Member
Offline
Activity: 74
Merit: 10
|
|
April 28, 2017, 03:50:41 PM |
|
zoi.acc pool not working
getting this errors
[2017-04-28 23:44:55] Stratum authentication failed [2017-04-28 23:44:55] ...retry after 10 seconds [2017-04-28 23:45:05] Stratum difficulty set to 0.0005 [2017-04-28 23:45:06] Stratum authentication failed [2017-04-28 23:45:06] ...retry after 10 seconds [2017-04-28 23:45:16] Stratum difficulty set to 0.0005 [2017-04-28 23:45:16] Stratum authentication failed [2017-04-28 23:45:16] ...retry after 10 seconds
Stratum authentication failed : means wrong user.worker or wrong password
|
|
|
|
degxtra1
Member
Offline
Activity: 228
Merit: 46
|
|
April 28, 2017, 03:52:00 PM |
|
i checked this few times.... before posting about
|
|
|
|
om83
|
|
April 28, 2017, 03:56:34 PM |
|
The price is low, it is better to buy For me it is necessary to hold for a long time min 1 year
|
Zoin Marketing & Communication
|
|
|
matejbilahora
Sr. Member
Offline
Activity: 1414
Merit: 275
Community built, Privacy driven
|
|
April 28, 2017, 04:26:36 PM |
|
The price is low, it is better to buy For me it is necessary to hold for a long time min 1 year
Well there will be one thing, price will sky rocked up and than slowly will fall down somewhere to stabilize and last for some time. That was in most cases, who knows what comes after relaunch.
|
|
|
|
degxtra1
Member
Offline
Activity: 228
Merit: 46
|
|
April 28, 2017, 05:42:50 PM |
|
zoi.acc pool not working
getting this errors
[2017-04-28 23:44:55] Stratum authentication failed [2017-04-28 23:44:55] ...retry after 10 seconds [2017-04-28 23:45:05] Stratum difficulty set to 0.0005 [2017-04-28 23:45:06] Stratum authentication failed [2017-04-28 23:45:06] ...retry after 10 seconds [2017-04-28 23:45:16] Stratum difficulty set to 0.0005 [2017-04-28 23:45:16] Stratum authentication failed [2017-04-28 23:45:16] ...retry after 10 seconds
Stratum authentication failed : means wrong user.worker or wrong password Now it seems to be connected but is rejecting all [2017-04-29 01:40:24] CPU #0: 656 H, 19.25 H/s [2017-04-29 01:40:24] Rejected 36/36 (100.0%), 73.19 kH, 1193.90 H/s, 60C [2017-04-29 01:40:24] reject reason: unauthorized worker [2017-04-29 01:40:25] CPU #11: 1571 H, 25.31 H/s [2017-04-29 01:40:26] CPU #30: 1245 H, 24.52 H/s [2017-04-29 01:40:26] Rejected 37/37 (100.0%), 73.02 kH, 1192.03 H/s, 60C [2017-04-29 01:40:26] reject reason: unauthorized worker [2017-04-29 01:40:27] CPU #45: 1537 H, 28.45 H/s [2017-04-29 01:40:28] CPU #1: 1405 H, 25.00 H/s [2017-04-29 01:40:29] CPU #43: 1439 H, 25.65 H/s [2017-04-29 01:40:29] CPU #38: 1631 H, 27.56 H/s [2017-04-29 01:40:29] CPU #4: 1470 H, 23.90 H/s [2017-04-29 01:40:30] CPU #5: 1469 H, 24.81 H/s [2017-04-29 01:40:31] CPU #28: 1533 H, 25.59 H/s [2017-04-29 01:40:32] CPU #15: 1518 H, 25.03 H/s [2017-04-29 01:40:33] CPU #26: 1492 H, 25.34 H/s [2017-04-29 01:40:33] CPU #41: 1556 H, 28.92 H/s [2017-04-29 01:40:34] CPU #42: 1594 H, 27.88 H/s [2017-04-29 01:40:35] CPU #9: 1489 H, 23.49 H/s [2017-04-29 01:40:36] CPU #2: 1248 H, 21.44 H/s [2017-04-29 01:40:36] CPU #34: 1532 H, 26.42 H/s [2017-04-29 01:40:36] CPU #18: 1516 H, 24.32 H/s [2017-04-29 01:40:36] CPU #24: 1473 H, 26.39 H/s [2017-04-29 01:40:37] CPU #16: 1388 H, 25.16 H/s [2017-04-29 01:40:37] CPU #25: 1535 H, 25.85 H/s [2017-04-29 01:40:38] CPU #20: 1600 H, 24.38 H/s [2017-04-29 01:40:38] CPU #3: 418 H, 23.95 H/s [2017-04-29 01:40:38] Rejected 38/38 (100.0%), 71.73 kH, 1203.67 H/s, 60C [2017-04-29 01:40:38] reject reason: unauthorized worker [2017-04-29 01:40:38] CPU #13: 1470 H, 24.47 H/s [2017-04-29 01:40:38] CPU #7: 1503 H, 24.08 H/s [2017-04-29 01:40:39] CPU #8: 1495 H, 24.49 H/s [2017-04-29 01:40:39] CPU #29: 1506 H, 25.09 H/s [2017-04-29 01:40:39] CPU #19: 1425 H, 24.17 H/s [2017-04-29 01:40:40] CPU #44: 1511 H, 26.48 H/s [2017-04-29 01:40:41] CPU #14: 1494 H, 22.95 H/s [2017-04-29 01:40:41] CPU #17: 1429 H, 22.73 H/s [2017-04-29 01:40:41] CPU #35: 1610 H, 26.78 H/s [2017-04-29 01:40:42] CPU #6: 1431 H, 23.13 H/s [2017-04-29 01:40:47] CPU #41: 395 H, 29.82 H/s [2017-04-29 01:40:47] Rejected 39/39 (100.0%), 68.87 kH, 1201.17 H/s, 60C [2017-04-29 01:40:47] reject reason: unauthorized worker [2017-04-29 01:40:47] CPU #12: 1405 H, 22.94 H/s [2017-04-29 01:40:47] CPU #39: 1463 H, 23.30 H/s [2017-04-29 01:40:47] CPU #37: 1510 H, 22.22 H/s [2017-04-29 01:40:49] CPU #22: 1548 H, 23.54 H/s [2017-04-29 01:40:50] CPU #21: 1336 H, 20.85 H/s [2017-04-29 01:40:50] CPU #32: 1516 H, 26.08 H/s [2017-04-29 01:40:51] CPU #13: 456 H, 34.96 H/s [2017-04-29 01:40:51] Rejected 40/40 (100.0%), 67.17 kH, 1204.35 H/s, 60C [2017-04-29 01:40:51] reject reason: unauthorized worker [2017-04-29 01:40:58] CPU #18: 513 H, 22.91 H/s [2017-04-29 01:40:58] Rejected 41/41 (100.0%), 66.17 kH, 1202.94 H/s, 60C [2017-04-29 01:40:58] reject reason: unauthorized worker [2017-04-29 01:41:00] CPU #11: 939 H, 26.26 H/s [2017-04-29 01:41:00] Rejected 42/42 (100.0%), 65.54 kH, 1203.88 H/s, 60C [2017-04-29 01:41:00] reject reason: unauthorized worker [2017-04-29 01:41:04] CPU #46: 1488 H, 29.23 H/s [2017-04-29 01:41:05] CPU #16: 633 H, 22.80 H/s [2017-04-29 01:41:05] Rejected 43/43 (100.0%), 64.78 kH, 1205.97 H/s, 60C [2017-04-29 01:41:05] reject reason: unauthorized worker [2017-04-29 01:41:06] CPU #27: 1511 H, 26.13 H/s [2017-04-29 01:41:09] CPU #33: 1582 H, 27.28 H/s [2017-04-29 01:41:12] CPU #0: 1155 H, 24.29 H/s [2017-04-29 01:41:13] CPU #10: 1476 H, 25.15 H/s [2017-04-29 01:41:13] CPU #23: 1392 H, 26.13 H/s [2017-04-29 01:41:15] CPU #47: 1661 H, 26.09 H/s [2017-04-29 01:41:18] CPU #43: 1540 H, 31.33 H/s [2017-04-29 01:41:21] CPU #31: 1529 H, 26.02 H/s [2017-04-29 01:41:22] CPU #40: 1508 H, 24.68 H/s [2017-04-29 01:41:23] CPU #30: 1471 H, 26.07 H/s
|
|
|
|
StelioKontos
Sr. Member
Offline
Activity: 839
Merit: 267
Chad Hodler since 2013
|
|
April 28, 2017, 05:47:31 PM |
|
Thanks for transition to cpuminer-opt-3.6.3 Could you do anything about this? Maybe try tweaking to better allow more connections form single IP? I have 3 PCs behind a router and 2 of them often are in that situation.
|
|
|
|
kamikaza
|
|
April 28, 2017, 06:09:10 PM |
|
Thanks for transition to cpuminer-opt-3.6.3 Could you do anything about this? Maybe try tweaking to better allow more connections form single IP? I have 3 PCs behind a router and 2 of them often are in that situation. Still have the same problem, with only one PC.... please fix it! For now i am gonna use zoi.acc-pool, no problems with that one
|
|
|
|
crazycarlo
Newbie
Offline
Activity: 12
Merit: 0
|
|
April 28, 2017, 06:29:33 PM |
|
zoi.acc pool is not working for me, on separate computers on separate networks
getting this errors
Stratum authentication failed
|
|
|
|
StelioKontos
Sr. Member
Offline
Activity: 839
Merit: 267
Chad Hodler since 2013
|
|
April 28, 2017, 06:30:40 PM |
|
zoi.acc pool is not working for me, on separate computers on separate networks
getting this errors
Stratum authentication failed
which OS are you in? post the miner command line you use
|
|
|
|
crazycarlo
Newbie
Offline
Activity: 12
Merit: 0
|
|
April 28, 2017, 06:40:34 PM |
|
zoi.acc pool is not working for me, on separate computers on separate networks
getting this errors
Stratum authentication failed
which OS are you in? post the miner command line you use Same issue on both Win7 and Win10 ********** cpuminer-opt 3.6.3 *********** A CPU miner with multi algo support and optimized for CPUs with AES_NI and AVX extensions. BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT Forked from TPruvot's cpuminer-multi with credits to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d, Wolf0, Jeff Garzik and Optiminer. CPU: Pentium(R) Dual-Core CPU E5800 @ 3.20GHz CPU features: SSE2 SW built on Apr 17 2017 with GCC 4.8.3 SW features: SSE2 Algo features: SSE2 AES AVX AVX2 Start mining with SSE2 [2017-04-28 14:38:37] Starting Stratum on stratum+tcp://zoi.digger.work:3031 [2017-04-28 14:38:37] 2 miner threads started, using 'lyra2z330' algorithm. [2017-04-28 14:38:37] stratum_recv_line failed [2017-04-28 14:38:37] ...retry after 10 seconds [2017-04-28 14:38:48] stratum_recv_line failed [2017-04-28 14:38:48] ...retry after 10 seconds
|
|
|
|
StelioKontos
Sr. Member
Offline
Activity: 839
Merit: 267
Chad Hodler since 2013
|
|
April 28, 2017, 06:53:11 PM |
|
I can't see the command line. (mask your username and worker password if you want but let me see exactly where you put them with the correct spaces)
And there is not an authentication error, but some generic connection error only - which seems to be not only your issue on zoi.digger.work but mine too.
|
|
|
|
|
|