Bitcoin Forum
April 11, 2021, 09:23:08 AM *
News: Latest Bitcoin Core release: 0.21.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 [103] 104 105 106 107 108 109 110 111 »
  Print  
Author Topic: [ANN][POOL] ZERGPOOL.com - Multialgo, autoexchange, 0.5% fee, 250+ coins  (Read 54114 times)
pinpins
Member
**
Offline Offline

Activity: 971
Merit: 18


View Profile WWW
August 16, 2019, 04:34:33 AM
 #2041

<SNIP>
I mean seriously I used to make 0.0025 a week.

Am I'm just having the worst luck ever or is there something up.

THERE MAY BE SOMETHING UP--

Recently, there was a network problem of some sort.  I think it affected some of the profitablity calculations for the worse.  The miner population shifted in response, and some of the top mining algos were actually providing little profit even if the coins at the market had a steady value. The number of miners and hash rate had dropped.

Your continual reports of solo-mining problems may have their own merit as well.  Personally, I'd like to know when any coins within an algorithm are being merge-mined versus individually mined with only portions of the total hash rate.  There are low value coins that I would not like to waste hash power on unless they are being merge-mined.  I use the "mc=COIN" flag in my password string to focus my hash, but would like to know if that focus is actually necessary.  If coins are being merge-mined, the "mc" flag is not necessary, as the low value coins  are mined with no separate effort.  On the other hand, if the pool software is portioning out the mining hash, I want my hash focused on the valuable coins.

And, as for solo-mining, there are some good algos where my hash is enough for mining blocks solo.  I just keep reading your reports and have not experimented, as I can't afford to waste hash.

Perhaps pinpins will respond...       --scryptr

Just clarify solo and non solo is just matter of reward distribution in case your miner was identified as finder. Hashing and block finding logic is the same in a pool.

When it comes to hashing and mc= option, I always recommend to put alternative coin in mc set, like mc=DGB/GAME. Giving example, as pool is autoswitch when DGB appears on top of list, all free hash(not locked with mc=) is moves to DGB and all of sudden DGB becomes full of hash, until next diff raise it receives more hash that it can consume, pool logic then moves extra hash to next coin in your list based on profitability, say GAME, and you have chance to find block there and utilizing left overs in better manner.

Hope this helps or clarifies a bit.

pinpin




Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1618132988
Hero Member
*
Offline Offline

Posts: 1618132988

View Profile Personal Message (Offline)

Ignore
1618132988
Reply with quote  #2

1618132988
Report to moderator
1618132988
Hero Member
*
Offline Offline

Posts: 1618132988

View Profile Personal Message (Offline)

Ignore
1618132988
Reply with quote  #2

1618132988
Report to moderator
Wolf_Tech
Jr. Member
*
Offline Offline

Activity: 64
Merit: 2


View Profile
August 16, 2019, 09:40:57 PM
 #2042

Actually some company has released new scrypt miners and is not selling them to the public. Nicehash and all the other pools in the last week has seen scrypt tripled in hashrates.

Sucks that us little guys cannot get them.
Brondal
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
August 18, 2019, 05:30:57 PM
 #2043

Hello, first: you have a good pool. Now my question: how can i mine with a StrongU STU-U2 on the blake2b algorithm at your pool?

Thank you for a answer.
scryptr
Legendary
*
Offline Offline

Activity: 1763
Merit: 1025



View Profile WWW
August 20, 2019, 12:25:15 AM
 #2044

Actually some company has released new scrypt miners and is not selling them to the public. Nicehash and all the other pools in the last week has seen scrypt tripled in hashrates.

Sucks that us little guys cannot get them.


THERE IS AN OLD, RESPECTED POOL THAT PAYS YOU TO MINE LITECOIN--

I can't remember its name just now, but it pays more than 100% for your hashrate. Seriously!

The secret?  It merge-mines so many scrypt-algo coins that the other scrypt coins result in a more-than-100% scrypt yield for the pool.  The miner can only get LiteCoin (LTC), all the merge-mined scrypt coins go for the profit margin.  The miner gets a fixed percentage, 1% or 2% or something.  That is to say the miner gets more than he would make mining LTC solo with no fee at all.  And, this is while pool mining and submitting shares.

That is why I asked pinpins about merge-mining.  No extra effort or energy is necessary to merge-mine multiple coins of the same algorithm.  VertCoin (VTC) was the first to introduce this, and some scrypt coins and X11 coins are merge-mineable by design.  It does take extra effort to code and set-up a pool for this.  I'd like to know if YIIMP pools are compatible.

I hope that pinpins might answer...       --scryptr

TIPS:  BTC - 1Fs4uZ6a9ABYBTaHGUfqcwCQmeBRxkKRQT    DASH - XrK81tW31SLsVvZ2WX9VhTjpT6GXJPLdbQ
          SCRYPTR'S NOTEBOOK: https://bitcointalk.org/index.php?topic=5035515.msg46035530#msg46035530
          GITHUB: "github.com/scryptr"  MERIT is appreciated, also.  Thanks!
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1113


View Profile
August 20, 2019, 04:12:12 AM
 #2045

yaamp/yiimp has had merged mining for a long time. Take a look at scrypt, all those coins at the
bottom of the list with the hashrate in gray are merge mined.




AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
scryptr
Legendary
*
Offline Offline

Activity: 1763
Merit: 1025



View Profile WWW
August 20, 2019, 04:09:30 PM
 #2046

yaamp/yiimp has had merged mining for a long time. Take a look at scrypt, all those coins at the
bottom of the list with the hashrate in gray are merge mined.


THANKS FOR THE ANSWER--

The question has been on my mind for some time.  What I don't like about YIIMP is that it can portion my hash away from a high-value coin and mine a low-value coin with my hash instead of merge-mining both with the same hash.  When this happens, I lose out on building "hash-equity" (or contributing and accumulating shares) for the high-value coin.

--scryptr

TIPS:  BTC - 1Fs4uZ6a9ABYBTaHGUfqcwCQmeBRxkKRQT    DASH - XrK81tW31SLsVvZ2WX9VhTjpT6GXJPLdbQ
          SCRYPTR'S NOTEBOOK: https://bitcointalk.org/index.php?topic=5035515.msg46035530#msg46035530
          GITHUB: "github.com/scryptr"  MERIT is appreciated, also.  Thanks!
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1113


View Profile
August 20, 2019, 06:59:28 PM
 #2047

I've been trying to follow but I'm lost. I can't figure whether you're compaining about
allocating hash to coins in the multipool or merged mining. They aren't related.

A clear problem definition would help.

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
scryptr
Legendary
*
Offline Offline

Activity: 1763
Merit: 1025



View Profile WWW
August 20, 2019, 08:26:43 PM
Merited by vapourminer (1)
 #2048

I've been trying to follow but I'm lost. I can't figure whether you're compaining about
allocating hash to coins in the multipool or merged mining. They aren't related.

A clear problem definition would help.

NO FLAG TO SET MERGED MODE MINING--

I mine lyra2v3, and it features 3 coins.  VertCoin (VTC) has a solid value, the other two are less valuable by at least an order of magnitude.

If I set "mc=VTC" in my password string, I mine VTC, and accumulate shares for VTC while waiting for a block.  If I do not set a mining coin (i.e. "mc"), the pool directs my hash to any of the three coins, but not necessarily to VTC.  I loose out on VTC shares when mining the less valuable coins.

If there was a merge-mining flag, "mg=VTC/HANA", or just "mg" to merge-mine all merge-mineable coins within an algo, I would accumulate shares on VTC at the same rate as if I were mining only VTC, and still receive shares for the merge-mined coins and earn BTC for payout.

Apparently, YIIMP portions out hash based on difficulty.  The less valuable coins often have frequent blocks, but it may take more than a day of mining less valuable coins to equal the value of a single VTC block, which currently has blocks found every few hours.

Not all coins and algorithms support merge-mining.  VTC was designed for merge-mining.  SHA256 and Scrypt allow merge-mining.  More earnings could be mined by the miners if merge-mining were a flag option at the pool.  I don't think the pool would loose any earnings, likely it would gain earnings with a greater coin turnover on the market.       --scryptr



TIPS:  BTC - 1Fs4uZ6a9ABYBTaHGUfqcwCQmeBRxkKRQT    DASH - XrK81tW31SLsVvZ2WX9VhTjpT6GXJPLdbQ
          SCRYPTR'S NOTEBOOK: https://bitcointalk.org/index.php?topic=5035515.msg46035530#msg46035530
          GITHUB: "github.com/scryptr"  MERIT is appreciated, also.  Thanks!
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1113


View Profile
August 20, 2019, 09:04:11 PM
Merited by vapourminer (1)
 #2049

You misunderstand, you can't choose the merged coins, the coin devs do. One coin is primary and you mine
that, Any coins merged with it also receive your hash.

Merged mining is only supported for coins designed for it.

The available parasite coins are always listed at the bottom and always have hash assigned to them.
The hash display is gray to indicate merged hash.

In most cases you can identify the host coin because the hash rates match, but scrypt is more complicated
because there are multiple hosts and multiple parasites. It would be nice to be able to identify which
parasites merge with which hosts.

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
scryptr
Legendary
*
Offline Offline

Activity: 1763
Merit: 1025



View Profile WWW
August 20, 2019, 09:55:21 PM
Last edit: August 21, 2019, 12:25:39 AM by scryptr
 #2050

You misunderstand, you can't choose the merged coins, the coin devs do. One coin is primary and you mine
that, Any coins merged with it also receive your hash.

Merged mining is only supported for coins designed for it.

The available parasite coins are always listed at the bottom and always have hash assigned to them.
The hash display is gray to indicate merged hash.

In most cases you can identify the host coin because the hash rates match, but scrypt is more complicated
because there are multiple hosts and multiple parasites. It would be nice to be able to identify which
parasites merge with which hosts.


THE MERGE FLAG WOULD ONLY APPLY TO MERGE-MINEABLE COINS--

Merge-mining must be implemented at the pool, as well as designed into the coins.  I don't know which coins are merge-mineable in the three Lyra2v3 coins available at ZergPool.  Looking at the scrypt algo list, I do see "coins at the bottom", but I see no color or shade difference.  I do see 4 or 5 coins there with identical hash rates.  The hash rates are less than the total given for the algo, however.

I'd like to see merge-mineable coins available as an flag option.       --scryptr

TIPS:  BTC - 1Fs4uZ6a9ABYBTaHGUfqcwCQmeBRxkKRQT    DASH - XrK81tW31SLsVvZ2WX9VhTjpT6GXJPLdbQ
          SCRYPTR'S NOTEBOOK: https://bitcointalk.org/index.php?topic=5035515.msg46035530#msg46035530
          GITHUB: "github.com/scryptr"  MERIT is appreciated, also.  Thanks!
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1113


View Profile
August 21, 2019, 04:46:16 AM
 #2051

You misunderstand, you can't choose the merged coins,

THE MERGE FLAG WOULD ONLY APPLY TO MERGE-MINEABLE COINS--

I'd like to see merge-mineable coins available as an flag option.       --scryptr

Sigh!

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
somaton
Jr. Member
*
Offline Offline

Activity: 130
Merit: 3


View Profile
August 23, 2019, 01:59:48 PM
 #2052

pinpin

You still think that this is normal starting/lower difficulty for x25x coin? really? 7 shares in 12 min?

https://cdn1.imggmi.com/uploads/2019/8/23/77d60e4afb4305b5d6a931018c9dd96e-full.jpg
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1113


View Profile
August 24, 2019, 03:24:22 PM
 #2053

pinpin

You still think that this is normal starting/lower difficulty for x25x coin? really? 7 shares in 12 min?

https://cdn1.imggmi.com/uploads/2019/8/23/77d60e4afb4305b5d6a931018c9dd96e-full.jpg

+1,

A high default starting diiff can be tolerated but the bigger problem is the minimum diff is too high for
a single GPU, even worse for CPU. The ability to set a lower starting diff or automatic adjustment
to a reasonable diff would be greatly appreciated.

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
scryptr
Legendary
*
Offline Offline

Activity: 1763
Merit: 1025



View Profile WWW
August 26, 2019, 10:54:04 PM
 #2054

You misunderstand, you can't choose the merged coins,

THE MERGE FLAG WOULD ONLY APPLY TO MERGE-MINEABLE COINS--

I'd like to see merge-mineable coins available as an flag option.       --scryptr

Sigh!

MERGE-MINEABLE COINS SHOULD BE MARKED--

At the very least it should be obvious which coins are merge-mineable.  They should have punctuation (superscript, subscript, asterisk) or a special color or special color underlining.

I don't know which coins are capable of merge-mining, and I don't know if all merge-mineable coins are merge-mined by default.

Further, these coins are not parasitic, they are value-added, or symbiotic, at the worst.  As I stated recently, there is at least one pool that earns its profits by merge-mining LiteCoin and scrypt-algo symbiont coins.  Those profits are shared with the miners (1% or better), who then pocket a better yield of LTC than they would if solo-mining at a 0% fee.       --scryptr

TIPS:  BTC - 1Fs4uZ6a9ABYBTaHGUfqcwCQmeBRxkKRQT    DASH - XrK81tW31SLsVvZ2WX9VhTjpT6GXJPLdbQ
          SCRYPTR'S NOTEBOOK: https://bitcointalk.org/index.php?topic=5035515.msg46035530#msg46035530
          GITHUB: "github.com/scryptr"  MERIT is appreciated, also.  Thanks!
Melfyce
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
August 27, 2019, 01:25:43 PM
 #2055

Hey guys I need your help.
So I've setup my miner to mine Dynamic [DYN] on zergpool.

This is what it looks like and it seems to be working:
sgminer.exe -k argon2d -o stratum+tcp://argon2d-dyn.mine.zergpool.com:4239 -u myDYNwallet -p c=DYN,mc=DYN

However, I havent gotten any payouts yet, but accumulated some DYN and they show up under "balance" and "total unpaid". What is the default threshold for DYN?

joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1113


View Profile
August 27, 2019, 07:29:46 PM
 #2056


MERGE-MINEABLE COINS SHOULD BE MARKED--

At the very least it should be obvious which coins are merge-mineable.  They should have punctuation (superscript, subscript, asterisk) or a special color or special color underlining.

I don't know which coins are capable of merge-mining, and I don't know if all merge-mineable coins are merge-mined by default.


[sarcastic]

Don't be so pig headed, it's not that complicated. The profit of the parasites is near zero anyway.
Just mine LTC for a few minutes and see what other coins pop up in your pending list.

Whining about the design of the pool software is unproductive. Make a feature request to the devs
if it's that important to you.

[/sarcastic]

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
joblo
Legendary
*
Offline Offline

Activity: 1470
Merit: 1113


View Profile
August 28, 2019, 01:50:16 AM
 #2057

I have been investigating a problem of invalid job id rejects mining various algos at zergpool.

It looks to me like like the miner never receives the new block from the pool. I have opened a
git issue (https://github.com/JayDDee/cpuminer-opt/issues/193) to investigate from the miner
side but it llso needs o be investigated from the pool side.

I haven't found any delays in the miner detecting a new block, it appears the message was never
received and the miner continued to submit shares for the old block until the next block was
sent by the pool.

Did the pool fail to send the block to that miner or did it get lost?

I did some more testing and it seems I'm receiving stale data from the pool. I'm getting data
regularly but sometimes it has an old job id.

There are no errors reported, I copy the data from the socket and it has the same job id

In the following you can see the sequence with a couple of debug printfs and annotations.

Code:
[2019-08-27 17:13:08] Starting Stratum on stratum+tcp://yespowerr16.mine.zergpool.com:6534
[2019-08-27 17:13:08] 16 miner threads started, using 'yespowerr16' algorithm.
[2019-08-27 17:13:09] Stratum difficulty set to 0.5
newjobcheck (null)   (null)
newjobcheck 7e61   (null)            <----------------------------------------------------------------- first job received
newjob
[2019-08-27 17:13:09] yespowerr16 block 463840, job 7e61, network diff 0.0072
newjobcheck 7e61   7e61             <----------------------------------------------------------------- second job, same job id
[2019-08-27 17:13:41] Share 1 submitted by thread 1, job 7e61.   <------------------------ share submitted with provided job id
[2019-08-27 17:13:41] Rejected, diff 1.41e-05, 32.665 secs, A/R/B: 0/1/0.
[2019-08-27 17:13:41] reject reason: Invalid job id.          <------------------------------------ share rejected as expected

I hope this provides a clue of what's going on so it can be solved.

AKA JayDDee, cpuminer-opt developer. https://github.com/JayDDee/cpuminer-opt
https://bitcointalk.org/index.php?topic=5226770.msg53865575#msg53865575
BTC: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT,
pinpins
Member
**
Offline Offline

Activity: 971
Merit: 18


View Profile WWW
August 28, 2019, 03:30:14 PM
 #2058

pinpin

You still think that this is normal starting/lower difficulty for x25x coin? really? 7 shares in 12 min?

https://cdn1.imggmi.com/uploads/2019/8/23/77d60e4afb4305b5d6a931018c9dd96e-full.jpg

+1,

A high default starting diiff can be tolerated but the bigger problem is the minimum diff is too high for
a single GPU, even worse for CPU. The ability to set a lower starting diff or automatic adjustment
to a reasonable diff would be greatly appreciated.

Ok, this is changed now to accommodate 1 GPU level.
pinpins
Member
**
Offline Offline

Activity: 971
Merit: 18


View Profile WWW
August 28, 2019, 03:38:44 PM
 #2059

Hey guys I need your help.
So I've setup my miner to mine Dynamic [DYN] on zergpool.

This is what it looks like and it seems to be working:
sgminer.exe -k argon2d -o stratum+tcp://argon2d-dyn.mine.zergpool.com:4239 -u myDYNwallet -p c=DYN,mc=DYN

However, I havent gotten any payouts yet, but accumulated some DYN and they show up under "balance" and "total unpaid". What is the default threshold for DYN?



Please let me know your wallet address by PM or discord
dede021385
Newbie
*
Offline Offline

Activity: 5
Merit: 2


View Profile
August 29, 2019, 05:28:15 PM
 #2060

Hello everyone,
there is a problem with the pool?
My L3 + tell me the dead server and look at the graph of the pool, the hashrate is much lower today.
Pages: « 1 ... 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 [103] 104 105 106 107 108 109 110 111 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!