Topic: [ANN][POOL] ZERGPOOL.com - Multialgo, autoexchange, 0.5% fee, 250+ coins - page 12. (Read 57849 times)

Argon 2dyn

[14:46:37] INFO  - Received new job #cd
[14:46:47] INFO  - 1/0 Accepted : diff=0 : 631,1KH/s
[14:46:49] INFO  - 2/0 Accepted : diff=0 : 685,0KH/s
[14:46:53] INFO  - 3/0 Accepted : diff=0 : 749,0KH/s
[14:46:59] INFO  - 3/1 Rejected : diff=0, reason: Invalid job id
[14:47:00] INFO  - 3/2 Rejected : diff=0, reason: Invalid job id
[14:47:02] INFO  - 3/3 Rejected : diff=0, reason: Invalid job id
[14:47:03] INFO  - 3/4 Rejected : diff=0, reason: Invalid job id
[14:47:08] INFO  - 3/5 Rejected : diff=0, reason: Invalid job id
[14:47:09] INFO  - 3/6 Rejected : diff=0, reason: Invalid job id
[14:47:11] INFO  - 3/7 Rejected : diff=0, reason: Invalid job id
[14:47:12] INFO  - 3/8 Rejected : diff=0, reason: Invalid job id
[14:47:15] INFO  - 3/9 Rejected : diff=0, reason: Invalid job id
[14:47:17] INFO  - 3/10 Rejected : diff=0, reason: Invalid job id
[14:47:18] INFO  - 3/11 Rejected : diff=0, reason: Invalid job id
[14:47:19] INFO  - 3/12 Rejected : diff=0, reason: Invalid job id
[14:47:19] INFO  - 3/13 Rejected : diff=0, reason: Invalid job id
[14:47:19] INFO  - 3/14 Rejected : diff=0, reason: Invalid job id

UPDATE

1. Tremendous work improving mining experience and mostly aiding "Invalid jobs" has been completed. Changes are effecting on all CPU algos, and we are rolling out to other gradually.

Yes

Yup, same problem.The problem is the pool isn't sending new jobs properly
so the miner keeps hashing the old stale job.

As I demonstrated in a previous post I collected data showing the miner received
a job that was already stale and the pool had already rejected shares submitted using it.
That's just plain wrong.

Would be nice to get it fixed.

and not only. happens on x16, neoscript, often with the password mc = "coin". I feel that one of the miners is connected to the pool with the wrong settings.

12:39:02] INFO  - 24/32 Rejected : diff=0.00606529, reason: Invalid job id
[12:39:06] INFO  - 24/33 Rejected : diff=0.0100769, reason: Invalid job id
[12:39:07] INFO  - 24/34 Rejected : diff=0.0122791, reason: Invalid job id
[12:39:07] INFO  - 24/35 Rejected : diff=0.0233635, reason: Invalid job id
[12:39:11] INFO  - 24/36 Rejected : diff=0.0117603, reason: Invalid job id
[12:39:11] INFO  - 24/37 Rejected : diff=0.00913617, reason: Invalid job id
[12:39:11] INFO  - 24/38 Rejected : diff=0.0159683, reason: Invalid job id
[12:39:11] INFO  - 24/39 Rejected : diff=0.00591861, reason: Invalid job id
[12:39:14] INFO  - 24/40 Rejected : diff=0.01579, reason: Invalid job id
[12:39:18] INFO  - 24/41 Rejected : diff=0.0143914, reason: Invalid job id
[12:39:22] INFO  - 24/42 Rejected : diff=0.0097482, reason: Invalid job id
[12:39:22] INFO  - 24/43 Rejected : diff=0.0596705, reason: Invalid job id
[12:39:22] INFO  - 24/44 Rejected : diff=0.00616638, reason: Invalid job id
[12:39:26] INFO  - 24/45 Rejected : diff=0.0130139, reason: Invalid job id
[12:39:26] INFO  - 24/46 Rejected : diff=0.00646398, reason: Invalid job id
[12:39:27] INFO  - 24/47 Rejected : diff=0.00700622, reason: Invalid job id
[12:39:28] INFO  - 24/48 Rejected : diff=0.00715171, reason: Invalid job id
[12:39:31] INFO  - 24/49 Rejected : diff=0.0338959, reason: Invalid job id
[12:39:32] INFO  - 24/50 Rejected : diff=0.0072279, reason: Invalid job id
[12:39:33] INFO  - 24/51 Rejected : diff=0.00604158, reason: Invalid job id
[12:39:37] INFO  - Setting new difficulty: 768 (0.0117188)
[12:39:37] INFO  - Block height 386980 : Network difficulty 0.666345
[12:39:37] INFO  - Received new job #9d418
[12:39:37] INFO  - 24/52 Rejected : diff=0.00732371, reason: Invalid job id
[12:39:46] INFO  - 25/52 Accepted : diff=0.0216072 : 9630KH/s
[12:39:57] INFO  - 26/52 Accepted : diff=0.0237028 : 9631KH/s
[12:40:06] INFO  - 26/53 Rejected : diff=0.014315, reason: Invalid job id
[12:40:13] INFO  - 26/54 Rejected : diff=0.015676, reason: Invalid job id
[12:40:18] INFO  - 26/55 Rejected : diff=0.0122919, reason: Invalid job id

If it's stale shares it's the same problem I reported previously and still hasn't been fixed.
It happens on the new power2b also.

Ratio 20/80% (80 - rejected) Delay of norms 50 ms. There are no such problems with Suprnova.

How many is many? What's the reject reason? Does it look anything like this problem?

https://bitcointalksearch.org/topic/m.52287385

If you get a run of stale shares it could be the problem above. A stale share occasionally is
normal. How's your network latency? You'll get more stale shares with higher latency.

very many rejected on DYN (argon2d-dyn) CryptoDredge.

x16rv2   -   also FPGA

Thanks, updated!

UPDATE

1. New CPU Power2b algo with Microbitcoin (MBC) available for mining
2. DOGE is now among guaranteed payout currencies

veil
x16s
skein
lyra2v3

also FPGA

Noticing New York Coin Wallet is missing?   Had some waiting to receive on this coming Sunday now it's missing.

Thanks, I will get config updated!

for example

https://news.fpga.guide/hardware-spotlight-cvp-13-by-bittware/

Hey miners! Good
iece Good news for you! 💡

Whitefire990's latest X16 bitstream for CVP13 has been released with related updates! 🔥
Adding Cubehash partial bitstreams (401/576 partials are now available)
X16S support for Pigeoncoin and X16RT for Gincoin
The possibility of mining 25% of the blocks
PC has a 16 hour limit and no development fee
24 hour average hash rate of 50MH / s
"Note" ⚡️
X16Rv2 is expected in 2-3 days! ⚡️

Hello.

FPGA a long time ago:

x17
bcd
skunk
neoscrypt
nist5
keccakc
honeycomb
x16rt
verushash
bmw512
equihash125
equihash96
equihash192
equihash144
Dmd-groestl
Blake2b

This is just what we know.
Feel free to specify.

Almost nothing was left for the GPU, all markets are dead. FPGA broken pre-consensus rake everything from the markets.

@pinpins

There appears to be a stratum difficulty problem with x16rv2.

I tried to set a lower diff using "-p d=2" (default is 5) but the pool reports diff 2.5.
As a result I occasionally submit low difficulty shares (between 2 and 2.5 presumably)
which are rejected.

I tried d=2, d=2.5, d=3 but all three result in 2.5 at the pool and 2 at the miner.

Using the default both pool and miner report diff 5.

Possibly an issue with fractions?

 Hello!
Please tell me, on your pool I can mine any coins with automatic conversion to lightcoin LTC (to receive payments LTC)
If so, how to do this operation using the Avesome miner software (if possible using screenshots)?
Thank you - I'm not a magician, I'm just learning ))

THANK YOU FOR MARKING MERGE-MINED COINS--

ZergPool has begun designating merge-mined coins in the Scrypt algorithm.  This makes it very easy to see from where the "other coins" are coming on a miner's dashboard.

Just a note:  merge-mined coins do not cost extra effort or power on the miner's part.  They simply share the same algorithm's hash, and are generally of lower difficulty than the primary coin(s).  A lower difficulty block solution may earn a block of merge-mined coins while it does not solve a block for a primary coin.  That is why a miner may see multiple blocks of merge-mined coins between blocks of primary coins.

I still have one question:  Is Scrypt the only algorithm where merge-mining is currently taking place on ZergPool?       --scryptr

EDIT:  I received an answer on Discord.  Scrypt and Sha256 have merge-mined coins.       --scryptr

ARE MERGE-MINED COINS MERGE-MINED BY DEFAULT? --

I want to know if merge-mined coins are 100 percent merge-mined.  If I set "mc=abc", and coin "abc" has merge-mined pairs, will the merge-mined pairs be mined by default?  Or, would I need to specify the merge-mined pairs "cde" and "fgh" in the "mc=abc/cde/fgh" parameter?

Basically, I want to mine the merge-mined pairs of any coin that I mine, but I do not want to mine low value coins within an algorithm set that cannot be merge-mined.

I would also like to see merge-mineable coins designated with a special color, or punctuation.  I want my hash to be efficiently engaged while mining.

--scryptr