nesatom
Newbie
 Offline
Activity: 25
Merit: 0
|
 |
August 30, 2019, 06:07:37 PM |
|
Just tell me who has merged coins mined at your pool? Does admins keep merged blocks?
|
|
|
|
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
|
|
|
|
|
|
|
|
pinpins
|
|
September 01, 2019, 05:10:50 AM |
|
Just tell me who has merged coins mined at your pool? Does admins keep merged blocks?
Hello, No, those are proportionally distributed among all contributors of shares(users) pinpin |
|
|
|
|
scryptr
Legendary
Offline
Activity: 1763
Merit: 1025
|
|
September 03, 2019, 06:42:47 PM |
|
Just tell me who has merged coins mined at your pool? Does admins keep merged blocks?
Hello, No, those are proportionally distributed among all contributors of shares(users) pinpin 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 |
|
|
|
scryptr
Legendary
Offline
Activity: 1763
Merit: 1025
|
|
September 29, 2019, 03:34:36 PM
Last edit: September 30, 2019, 01:23:14 AM by scryptr |
|
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
|
|
|
|
borodaus
Jr. Member
Offline
Activity: 162
Merit: 1
|
|
October 01, 2019, 07:23:34 PM
Last edit: October 04, 2019, 04:26:26 PM by borodaus |
|
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  )) |
|
|
|
|
joblo
Legendary
Offline
Activity: 1470
Merit: 1113
|
|
October 03, 2019, 07:53:38 PM |
|
@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?
|
|
|
|
Siolim
Newbie
Offline
Activity: 106
Merit: 0
|
|
October 03, 2019, 10:22:15 PM |
|
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.
|
|
|
|
|
Siolim
Newbie
Offline
Activity: 106
Merit: 0
|
|
October 03, 2019, 10:23:38 PM
Last edit: October 05, 2019, 09:27:49 AM by Siolim |
|
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! ⚡️ |
|
|
|
|
|
pinpins
|
|
October 05, 2019, 10:20:58 AM |
|
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.
Thanks, I will get config updated! |
|
|
|
|
bitcorning
Newbie
Offline
Activity: 2
Merit: 0
|
|
October 05, 2019, 05:44:11 PM |
|
Noticing New York Coin Wallet is missing? Had some waiting to receive on this coming Sunday now it's missing.
|
|
|
|
|
Siolim
Newbie
Offline
Activity: 106
Merit: 0
|
|
October 08, 2019, 01:44:55 PM
Last edit: October 08, 2019, 06:03:15 PM by Siolim |
|
Noticing New York Coin Wallet is missing? Had some waiting to receive on this coming Sunday now it's missing.
veil x16s skein lyra2v3 also FPGA |
|
|
|
|
|
pinpins
|
|
October 10, 2019, 05:38:55 AM |
|
UPDATE
1. New CPU Power2b algo with Microbitcoin (MBC) available for mining
2. DOGE is now among guaranteed payout currencies
|
|
|
|
|
|
pinpins
|
|
October 10, 2019, 05:42:25 AM |
|
Noticing New York Coin Wallet is missing? Had some waiting to receive on this coming Sunday now it's missing.
veil x16s skein lyra2v3 also FPGA Thanks, updated! |
|
|
|
|
Siolim
Newbie
Offline
Activity: 106
Merit: 0
|
|
October 11, 2019, 03:42:40 PM
Last edit: October 11, 2019, 04:26:04 PM by Siolim |
|
very many rejected on DYN (argon2d-dyn) CryptoDredge.
x16rv2 - also FPGA
|
|
|
|
|
joblo
Legendary
Offline
Activity: 1470
Merit: 1113
|
|
October 11, 2019, 06:13:48 PM |
|
very many rejected on DYN (argon2d-dyn) CryptoDredge.
How many is many? What's the reject reason? Does it look anything like this problem? https://bitcointalk.org/index.php?topic=2759935.msg52287385#msg52287385If 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. |
|
|
|
Siolim
Newbie
Offline
Activity: 106
Merit: 0
|
|
October 11, 2019, 08:14:08 PM |
|
very many rejected on DYN (argon2d-dyn) CryptoDredge.
How many is many? What's the reject reason? Does it look anything like this problem? https://bitcointalk.org/index.php?topic=2759935.msg52287385#msg52287385If 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. Ratio 20/80% (80 - rejected) Delay of norms 50 ms. There are no such problems with Suprnova. |
|
|
|
|
joblo
Legendary
Offline
Activity: 1470
Merit: 1113
|
|
October 11, 2019, 09:36:44 PM |
|
very many rejected on DYN (argon2d-dyn) CryptoDredge.
How many is many? What's the reject reason? Does it look anything like this problem? https://bitcointalk.org/index.php?topic=2759935.msg52287385#msg52287385If 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. Ratio 20/80% (80 - rejected) Delay of norms 50 ms. There are no such problems with Suprnova. 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. |
|
|
|
Siolim
Newbie
Offline
Activity: 106
Merit: 0
|
|
October 11, 2019, 09:56:47 PM
Last edit: October 12, 2019, 09:40:42 AM by Siolim |
|
very many rejected on DYN (argon2d-dyn) CryptoDredge.
How many is many? What's the reject reason? Does it look anything like this problem? https://bitcointalk.org/index.php?topic=2759935.msg52287385#msg52287385If 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. Ratio 20/80% (80 - rejected) Delay of norms 50 ms. There are no such problems with Suprnova. 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. 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 |
|
|
|
|
joblo
Legendary
Offline
Activity: 1470
Merit: 1113
|
|
October 12, 2019, 12:58:45 PM |
|
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
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. |
|
|
|
Siolim
Newbie
Offline
Activity: 106
Merit: 0
|
|
October 12, 2019, 04:07:05 PM |
|
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
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. Yes |
|
|
|
|
|
