GoldBit89
|
|
July 16, 2014, 11:37:00 AM |
|
I honestly don't think poolwaffle should be asked to show everything behind the scenes to miners. There is zero reason for him to publish what he does to everyone. In fact you could consider his profitability code to be proprietary and no company is going to release proprietary data for free. He provides a service that he is paid for and we are not paying him for his source code, simply his ability to generate profit for our equipment. It's very unreasonable to expect someone to go and spend a lot of time creating something and then give it away for nothing. When you purchase commercial off the shelf software, you are purchasing a license for use, not a license for the release of the source code. I feel that this is a similar situation.
wasnt asking poolwaffle to give his source code.simply to display 2 numbers that should already be apart of the profitability formula. and yes when my equipment and time are involved and it involves any kind of finances, then yes i do want to know what the profitability is and how it is achieved.If you rented out a building to someone, you would want to know what they are doing or else you could end up with some kind of child porn business that could ultimately effect you. I know totally different subject but same principle.
|
FTC 6nvzqqaCEizThvgMeC86MGzhAxGzKEtNH8 |WDC WckDxipCes2eBmxrUYEhrUfNNRZexKuYjR |BQC bSDm3XvauqWWnqrxfimw5wdHVDQDp2U8XU BOT EjcroqeMpZT4hphY4xYDzTQakwutpnufQR |BTG geLUGuJkhnvuft77ND6VrMvc8vxySKZBUz |LTC LhXbJMzCqLEzGBKgB2n73oce448BxX1dc4 BTC 1JPzHugtBtPwXgwMqt9rtdwRxxWyaZvk61 |ETH 0xA6cCD2Fb3AC2450646F8D8ebeb14f084F392ACFf
|
|
|
GoldBit89
|
|
July 16, 2014, 11:39:04 AM |
|
I honestly don't think poolwaffle should be asked to show everything behind the scenes to miners. There is zero reason for him to publish what he does to everyone. In fact you could consider his profitability code to be proprietary and no company is going to release proprietary data for free. He provides a service that he is paid for and we are not paying him for his source code, simply his ability to generate profit for our equipment. It's very unreasonable to expect someone to go and spend a lot of time creating something and then give it away for nothing. When you purchase commercial off the shelf software, you are purchasing a license for use, not a license for the release of the source code. I feel that this is a similar situation.
Agreed. I've tried all the different multipools out there and I always come back to WP. Not only is the profitability great, but my payouts line up with what I expect which can't be said for many other multipools. hence my proposal for a universal wide display of those 2 numbers, not just for waffle pool but for all mining pools.
|
FTC 6nvzqqaCEizThvgMeC86MGzhAxGzKEtNH8 |WDC WckDxipCes2eBmxrUYEhrUfNNRZexKuYjR |BQC bSDm3XvauqWWnqrxfimw5wdHVDQDp2U8XU BOT EjcroqeMpZT4hphY4xYDzTQakwutpnufQR |BTG geLUGuJkhnvuft77ND6VrMvc8vxySKZBUz |LTC LhXbJMzCqLEzGBKgB2n73oce448BxX1dc4 BTC 1JPzHugtBtPwXgwMqt9rtdwRxxWyaZvk61 |ETH 0xA6cCD2Fb3AC2450646F8D8ebeb14f084F392ACFf
|
|
|
adaseb
Legendary
Offline
Activity: 3878
Merit: 1733
|
|
July 16, 2014, 11:49:33 AM |
|
What coin is WP mining right now?
KEYCoin?
The block rewards don't seem to add up.
I dont want to waste my mining power on this.
|
|
|
|
torontominer
Newbie
Offline
Activity: 35
Merit: 0
|
|
July 16, 2014, 11:57:02 AM |
|
go x13 go!
|
|
|
|
utahjohn
|
|
July 16, 2014, 12:40:43 PM Last edit: July 16, 2014, 12:55:23 PM by utahjohn |
|
What coin is WP mining right now?
KEYCoin?
The block rewards don't seem to add up.
I dont want to waste my mining power on this.
Could be KEY ... I have seen 250 blocks earlier and 550 blocks now ... if(pindexBest->nHeight < 400) { nSubsidy = 500 * COIN; } else if(pindexBest->nHeight < 700) { nSubsidy = 450 * COIN; } else if(pindexBest->nHeight < 1000) { nSubsidy = 350 * COIN; } else if(pindexBest->nHeight < 1300) { nSubsidy = 300 * COIN; } else if(pindexBest->nHeight < 1600) { nSubsidy = 250 * COIN; } else if(pindexBest->nHeight < 2000) { nSubsidy = 550 * COIN; } else if(pindexBest->nHeight < 2100) { nSubsidy = 150 * COIN; } else if(pindexBest->nHeight < 3000) { nSubsidy = 100 * COIN; } else if(pindexBest->nHeight < 4000) { nSubsidy = 50 * COIN; }
If this is true, the bonus we are seeing right now will end soon Mine it while reward is at maximum!!!
|
|
|
|
|
utahjohn
|
|
July 16, 2014, 01:13:26 PM |
|
LOL thanks for the confirmation on our guess
|
|
|
|
murraypaul
|
|
July 16, 2014, 01:45:40 PM |
|
and yes when my equipment and time are involved and it involves any kind of finances, then yes i do want to know what the profitability is and how it is achieved.If you rented out a building to someone, you would want to know what they are doing or else you could end up with some kind of child porn business that could ultimately effect you. I know totally different subject but same principle. You know the profitability, as you know how much you are being paid. You have no right to know how it is achieved, that is the IP of the pool owner. If you invested $X in a mutual fund, would you expect them to describe exactly the methods they chose to determine how much of which stock they bought? No, you would get a broad description of how the fund worked, and no view of the details, as they are what give fund A a competitive advantage over fund B.
|
BTC: 16TgAGdiTSsTWSsBDphebNJCFr1NT78xFW SRC: scefi1XMhq91n3oF5FrE3HqddVvvCZP9KB
|
|
|
utahjohn
|
|
July 16, 2014, 02:13:43 PM Last edit: July 16, 2014, 02:31:27 PM by utahjohn |
|
Well so much for the KEY coin 550 blocks I don't see any recent ones now Reward must have switched to 150 now and no longer our most profitable Congrats to those who stuck with X13 for the awesome but too short bonus (I did) EDIT: yep that's it, now only paying 150 blocks ...
|
|
|
|
atomicchaos
|
|
July 16, 2014, 02:18:21 PM |
|
I honestly don't think poolwaffle should be asked to show everything behind the scenes to miners. There is zero reason for him to publish what he does to everyone. In fact you could consider his profitability code to be proprietary and no company is going to release proprietary data for free. He provides a service that he is paid for and we are not paying him for his source code, simply his ability to generate profit for our equipment. It's very unreasonable to expect someone to go and spend a lot of time creating something and then give it away for nothing. When you purchase commercial off the shelf software, you are purchasing a license for use, not a license for the release of the source code. I feel that this is a similar situation.
wasnt asking poolwaffle to give his source code.simply to display 2 numbers that should already be apart of the profitability formula. and yes when my equipment and time are involved and it involves any kind of finances, then yes i do want to know what the profitability is and how it is achieved.If you rented out a building to someone, you would want to know what they are doing or else you could end up with some kind of child porn business that could ultimately effect you. I know totally different subject but same principle. I have a great idea for you, go open your own pool!
|
BTC:113mFe2e3oRkZQ5GeqKhoHbGtVw16unnw2
|
|
|
OPTiK
|
|
July 16, 2014, 02:52:06 PM |
|
If you rented out a building to someone, you would want to know what they are doing or else you could end up with some kind of child porn business that could ultimately effect you. I know totally different subject but same principle.
This is a terrible analogy -- Owning the building does not grant you rights to the IP that is developed on the premises.
|
|
|
|
poolwaffle (OP)
|
|
July 16, 2014, 03:32:22 PM Last edit: July 16, 2014, 03:47:25 PM by poolwaffle |
|
Well so much for the KEY coin 550 blocks I don't see any recent ones now Reward must have switched to 150 now and no longer our most profitable Congrats to those who stuck with X13 for the awesome but too short bonus (I did) EDIT: yep that's it, now only paying 150 blocks ... So many posts while I was asleep Yeah, we jumped on Key within a few minutes of it being exchangable on bittrex, so got in there pretty early, very nice spike in profits indeed I don't actually own/operate that site, they're just using our API, but it looks like I'm obviously not scrubbing it somewhere along the way. I'll see where I missed it Edit: Fixed, thanks for the heads up
|
|
|
|
primer10
|
|
July 16, 2014, 04:01:44 PM |
|
is it just me? Anyone noticed their x11 (maybe x13 too) hashrate graph is quite wild, fluctuating with quite a big variance (like +/- 1mh/s)?
I am using 2x 750ti with ccminer reporting 5100kh/s.
|
|
|
|
atomicchaos
|
|
July 16, 2014, 04:07:33 PM |
|
Well so much for the KEY coin 550 blocks I don't see any recent ones now Reward must have switched to 150 now and no longer our most profitable Congrats to those who stuck with X13 for the awesome but too short bonus (I did) EDIT: yep that's it, now only paying 150 blocks ... Someone was renting a lot of hash power too to point there as it was very profitable elsewhere. So since I cannot wait to rejoin Waffle, I'm just walking through the concept of auto switching and wondering if this is what it takes: 1). Logic to determine which protocol is most profitable using the standard X11 = 5.5x, X13 = 4x, if we assume X15, Nist5, and Keccek won't be thrown into the mix 2). Additional ports to receive the switching clients 3). Ports are shut down based on the logic in item #1, and only the most profitable protocol remains with a port open, and the miner simply uses pool switching as the way it moves from one to another I know there is a lot on the backend that needs to be introduced, and in a custom package, that is pretty complex I imagine, but I just wanted to know if that was the basic concept on how it would be handled. My 50 rigs no have been diagnosed with split-algorithm complex, which is actually a good thing, but it would be better at Waffle!
|
BTC:113mFe2e3oRkZQ5GeqKhoHbGtVw16unnw2
|
|
|
malodin
Newbie
Offline
Activity: 21
Merit: 0
|
|
July 16, 2014, 04:08:57 PM |
|
Primer10
my cgwatcher reports an average between 12-12.9M/hs steady all day long, but my graphs and current stats on wafflepool show peaks clear up to 18Mh/s and valleys down to 8Mh/s, i have noticed that the higher the hash rate shown on wafflepool the higher my reject rate is.
|
|
|
|
poolwaffle (OP)
|
|
July 16, 2014, 04:57:30 PM |
|
So since I cannot wait to rejoin Waffle, I'm just walking through the concept of auto switching and wondering if this is what it takes:
1). Logic to determine which protocol is most profitable using the standard X11 = 5.5x, X13 = 4x, if we assume X15, Nist5, and Keccek won't be thrown into the mix 2). Additional ports to receive the switching clients 3). Ports are shut down based on the logic in item #1, and only the most profitable protocol remains with a port open, and the miner simply uses pool switching as the way it moves from one to another
I know there is a lot on the backend that needs to be introduced, and in a custom package, that is pretty complex I imagine, but I just wanted to know if that was the basic concept on how it would be handled.
My 50 rigs no have been diagnosed with split-algorithm complex, which is actually a good thing, but it would be better at Waffle!
This is almost exactly what we'll do. The biggest thing unaccounted for is how to handle users who either prefer (electricity, etc) a specific algorithm (aka, add +25% weight to x13), and users who have cards that switch at rates outside our standard (eg, having a card that does X13 at 6x instead of our calculated 3.4x). Doing the first part (algo switching) shouldn't be too terribly difficult, some tech additions (turning on/off ports), and some minor switcher logic (choosing which port to open). Doing the second part (per user config of weights) is a lot tougher, and will likely get pushed back for a while (no one else is doing that yet either, so its not like we're playing catchup)
|
|
|
|
Zels
|
|
July 16, 2014, 05:08:51 PM |
|
This is almost exactly what we'll do. The biggest thing unaccounted for is how to handle users who either prefer (electricity, etc) a specific algorithm (aka, add +25% weight to x13), and users who have cards that switch at rates outside our standard (eg, having a card that does X13 at 6x instead of our calculated 3.4x). Doing the first part (algo switching) shouldn't be too terribly difficult, some tech additions (turning on/off ports), and some minor switcher logic (choosing which port to open). Doing the second part (per user config of weights) is a lot tougher, and will likely get pushed back for a while (no one else is doing that yet either, so its not like we're playing catchup) Nicehash even if it's not really a pool like waffle mining coin but rent hash is already doing that, you can define f= and c= as your factor and cost Something like p=x;fx11:4;fx13:6 and pool accept or reject connect
|
|
|
|
atomicchaos
|
|
July 16, 2014, 05:14:35 PM |
|
So since I cannot wait to rejoin Waffle, I'm just walking through the concept of auto switching and wondering if this is what it takes:
1). Logic to determine which protocol is most profitable using the standard X11 = 5.5x, X13 = 4x, if we assume X15, Nist5, and Keccek won't be thrown into the mix 2). Additional ports to receive the switching clients 3). Ports are shut down based on the logic in item #1, and only the most profitable protocol remains with a port open, and the miner simply uses pool switching as the way it moves from one to another
I know there is a lot on the backend that needs to be introduced, and in a custom package, that is pretty complex I imagine, but I just wanted to know if that was the basic concept on how it would be handled.
My 50 rigs no have been diagnosed with split-algorithm complex, which is actually a good thing, but it would be better at Waffle!
This is almost exactly what we'll do. The biggest thing unaccounted for is how to handle users who either prefer (electricity, etc) a specific algorithm (aka, add +25% weight to x13), and users who have cards that switch at rates outside our standard (eg, having a card that does X13 at 6x instead of our calculated 3.4x). Doing the first part (algo switching) shouldn't be too terribly difficult, some tech additions (turning on/off ports), and some minor switcher logic (choosing which port to open). Doing the second part (per user config of weights) is a lot tougher, and will likely get pushed back for a while (no one else is doing that yet either, so its not like we're playing catchup) What I'm doing is using custom variables that are being set in the password field to control my own formula as to how I want to mine. So I can give my own custom defined weight to each algo, or I can use the defaults. Then the pool is taking those and applying them. In thinking that through, that means the port opening and closing simplicity is not there, as some will be mining different coins based on custom settings, so I'm not clear how they are doing that (keeping in mind I have no knowledge of the backend of a pool, but just was trying to better understand it). For me, I'm fine with using default calculations if it speeds up implementation and makes it easier on the back end. Based on your past, I would certainly trust your profitability calculations, as I have on a per coin basis, this simply makes a multi-pool even more multi.
|
BTC:113mFe2e3oRkZQ5GeqKhoHbGtVw16unnw2
|
|
|
poolwaffle (OP)
|
|
July 16, 2014, 05:57:49 PM |
|
So since I cannot wait to rejoin Waffle, I'm just walking through the concept of auto switching and wondering if this is what it takes:
1). Logic to determine which protocol is most profitable using the standard X11 = 5.5x, X13 = 4x, if we assume X15, Nist5, and Keccek won't be thrown into the mix 2). Additional ports to receive the switching clients 3). Ports are shut down based on the logic in item #1, and only the most profitable protocol remains with a port open, and the miner simply uses pool switching as the way it moves from one to another
I know there is a lot on the backend that needs to be introduced, and in a custom package, that is pretty complex I imagine, but I just wanted to know if that was the basic concept on how it would be handled.
My 50 rigs no have been diagnosed with split-algorithm complex, which is actually a good thing, but it would be better at Waffle!
This is almost exactly what we'll do. The biggest thing unaccounted for is how to handle users who either prefer (electricity, etc) a specific algorithm (aka, add +25% weight to x13), and users who have cards that switch at rates outside our standard (eg, having a card that does X13 at 6x instead of our calculated 3.4x). Doing the first part (algo switching) shouldn't be too terribly difficult, some tech additions (turning on/off ports), and some minor switcher logic (choosing which port to open). Doing the second part (per user config of weights) is a lot tougher, and will likely get pushed back for a while (no one else is doing that yet either, so its not like we're playing catchup) What I'm doing is using custom variables that are being set in the password field to control my own formula as to how I want to mine. So I can give my own custom defined weight to each algo, or I can use the defaults. Then the pool is taking those and applying them. In thinking that through, that means the port opening and closing simplicity is not there, as some will be mining different coins based on custom settings, so I'm not clear how they are doing that (keeping in mind I have no knowledge of the backend of a pool, but just was trying to better understand it). For me, I'm fine with using default calculations if it speeds up implementation and makes it easier on the back end. Based on your past, I would certainly trust your profitability calculations, as I have on a per coin basis, this simply makes a multi-pool even more multi. Right, it means it wouldn't be closing ports at all, they'd all be open, it just probably wouldn't be giving out work on the ports that would normally be closed (and also based on those weight factors). I assume sgminer sees those as "down" or not giving work fast enough, and ignores them (otherwise, what would it work on?). So that shouldn't be too tough actually. Again, haven't started the implementation, but been thinking about it a good bit
|
|
|
|
suchmoon
Legendary
Offline
Activity: 3850
Merit: 9090
https://bpip.org
|
|
July 16, 2014, 06:49:51 PM |
|
Right, it means it wouldn't be closing ports at all, they'd all be open, it just probably wouldn't be giving out work on the ports that would normally be closed (and also based on those weight factors). I assume sgminer sees those as "down" or not giving work fast enough, and ignores them (otherwise, what would it work on?). So that shouldn't be too tough actually. Again, haven't started the implementation, but been thinking about it a good bit Here is the NH implementation: https://nicehash.com/multialgo/#finetuningSince it's based on the password, authorization will fail on all ports except the one that's most profitable ATM. This works not only with sgminer5, but with some additional scripting with other software (with some loss of performance due to slower switching of course), so even though it's quite hacky it's still a decent stopgap solution. In addition to allowing to set custom multipliers, they also allow to set the power cost, and exclude certain algos - e.g. if I don't have my rig set up for X13 I can set f4=0 and the pool will authorize me on the next most profitable algo.
|
|
|
|
|