nitrocs
Newbie
Offline
Activity: 47
Merit: 0
|
|
July 17, 2014, 09:02:05 PM |
|
+40gh on x11 youch!
|
|
|
|
poolwaffle (OP)
|
|
July 17, 2014, 09:18:40 PM |
|
Some things we publish because of the potential for me doing something nefarious, for example, we publish all of the blocks we find, which can easily be matched up to the work we send for miners, and you can easily see I'm not skimming blocks (a large number of other pools don't publish this info). We certainly have no requirement to publish anything, but I try to publish as much as possible to make sure everyone understands I'm being as transparent as possible (within reason), and that we're all on the same team.
If you published the following, Goldie can figure out if he is being paid about the right amount: 1) Add "pool hash rate" to the recently found blocks stat. I presume my approximate share would be (my average rate)/(pool rate) 2) Coin Conversion transactions: Coin, time, # of coin converted, Net # of BTC received) So, if 12 urocoin were mined when the pool hash rate was 93GH, and my hash rate is 6GH, then I should be allocated about .77 urocoin (ignoring pplns effects). That number can then be compared to the earnings log. If 24 urocoin are then converted to .18 BTC, then I should get about .00578 btc. So, the only piece that Goldie is missing is a log of conversion transactions. Although, if I recall correctly, gains and losses are allocated to current miners at the time received (coins got stuck at exchange, price went up, and people currently mining benefited). So, Goldie can figure out for himself if he has the right payout by: Using the Recently Found Blocks to estimate his share of the payout (he would have to pull the pool has rate, and use his own average hash rate). Compare that to Earnings Log for his miner, with slight differences (averaging to 0 over time) likely due to PPLNS effect. Pull the spot price for the coin. Compare that to the Earnings Log. PW would then have to somehow disclose the allocation of conversion gains/losses. With that adjustment, he should be close to the actual payout. Everything you mention is already listed on the site. He's asking for the data regarding WHY we switched to a coin (the price/etc that made us consider it the right choice), not the data once mined (which is all public already).
|
|
|
|
poolwaffle (OP)
|
|
July 17, 2014, 09:28:23 PM |
|
Is WP under DDoS attack? I'm seeing a huge amount of "stratum connection interrupted". None of my X11 miners are getting shares accepted and diff keeps reseting to 0.160 I've tried uswest, useast and same problem I don't see anything on my side. SEA server has a tiny bit higher load than normal (but still working fine). Nothing on the graphs showing a noticible drop in hashrate, and no alerts went off... Are you still seeing it? Yep still getting interrupted and had been working fine for weeks. *snipped a bunch* So, after looking into it, I think I've got the issue. Urocoin became extremely profitable, so that's basically the only thing X11 has been mining today. Uro also has a 3min average block time. Since we send work immediately upon connection (instead of waiting for auth data) we send a default difficulty of 0.16 (probably too high), and as soon as block data changes (new coin, new block) we tell you to start using the difficulty you sent. Unfortunately, since we're not switching coins very often today, and the avg block time is higher than a normal TCP connection timeout (2min), and the default difficulty is high (you're unlikely to find a block in those 2min), theres an extremely high chance of a small miner (76khs is very low) getting disconnected in that 2min time. Easy solution won't work (dropping default difficulty by much) because looking at the logs, a LOT of people use it, and it would absolutely destroy our logging to drop it much (overwhelming number of shares), or at least dropping it to the point where you'd get a share in that 2min with a 75khs rig. Mid solution is to apply difficulty on startup (rather than on work switch), I'll look into it. When we originally added the difficulty adjustment, it was just much easier to put it where it is now (work switch), I don't think I checked too deep on applying it earlier. Best solution is to have vardiff working again. Which I'd love to do (better all around for everyone), but thats a bit off. Pool is smaller than it was when we removed it, and our database is a good bit stronger, so its possible its an option again I'll have to check it out
|
|
|
|
utahjohn
|
|
July 17, 2014, 09:44:53 PM |
|
Yep that sounds like a plausible explanation ... vardiff would be the best solution for all.
MP set my diff to .001 immediately and is currently on URO so I guess they are vardiff now.
|
|
|
|
richmke
|
|
July 17, 2014, 10:40:52 PM |
|
I finally got x13 working. My hash rates stats for a pair of r9 280x are: x11 is 4.2x scrypt, and x13 is 3.1x scrypt.
Since WP assumes 4.0x and 3.5x, I actually need x13 to be estimated to be 20% more profitable than x11 to break even.
|
|
|
|
richmke
|
|
July 17, 2014, 10:46:16 PM |
|
He's asking for the data regarding WHY we switched to a coin (the price/etc that made us consider it the right choice), not the data once mined (which is all public already).
Ok. I thought he wanted to confirm he was being paid the right amount (not cheated by the pool). If he wants to know why WP mines a particular coin, then that's a secret you have a right to keep. once again im not asking the pool owners to describe the methods, but i do want the hard line profit numbers. If he wants "hard line profit numbers", the only missing data is the actual conversion rates to BTC.
|
|
|
|
nitrocs
Newbie
Offline
Activity: 47
Merit: 0
|
|
July 18, 2014, 01:20:32 AM |
|
+40gh on x11 youch!
Someone brought a lot of hash to bear on X11 today...almost 60-70gh/s How does this affect the partitioning of hash amongst relatively small coins? Do we just crush them and drive up diff like mad or is there a method in place to promote long term profitability?
|
|
|
|
poolwaffle (OP)
|
|
July 18, 2014, 02:35:28 AM |
|
+40gh on x11 youch!
Someone brought a lot of hash to bear on X11 today...almost 60-70gh/s How does this affect the partitioning of hash amongst relatively small coins? Do we just crush them and drive up diff like mad or is there a method in place to promote long term profitability? We don't do anything in anticipation of the market, only splitting of hashrate to not hurt ourselves (may hurt the coin's difficulty).
|
|
|
|
xrobesx
|
|
July 18, 2014, 09:43:00 AM |
|
is there anyplace to see worker stats and earnings before payout threshold is reached?
|
|
|
|
|
Undefeatable
|
|
July 18, 2014, 10:09:07 AM |
|
+40gh on x11 youch!
Someone brought a lot of hash to bear on X11 today...almost 60-70gh/s How does this affect the partitioning of hash amongst relatively small coins? Do we just crush them and drive up diff like mad or is there a method in place to promote long term profitability? The huge hashrate would definitely cause x11 profit to drop.
|
|
|
|
utahjohn
|
|
July 18, 2014, 10:28:24 AM |
|
IMO the huge hashrates being provided by proxied pools using WP as a backend are the problem and only improve profit for PW but not the dedicated WP miners because they take large amounts of shares away from us ... much like what ASIC are doing to scrypt.
|
|
|
|
nitrocs
Newbie
Offline
Activity: 47
Merit: 0
|
|
July 18, 2014, 03:19:55 PM |
|
IMO the huge hashrates being provided by proxied pools using WP as a backend are the problem and only improve profit for PW but not the dedicated WP miners because they take large amounts of shares away from us ... much like what ASIC are doing to scrypt.
this is along the lines of my previous question X11 is still a relatively new algo & has few coins in the ecosystem. I see this huge hashrate jump as nothing more than a smash & grab which causepushess us "regular" miners around
|
|
|
|
duboisi
|
|
July 18, 2014, 04:51:18 PM |
|
Profit dropping. Time to "speculate" on new X11 and X13 coins again.
|
|
|
|
poolwaffle (OP)
|
|
July 18, 2014, 04:55:44 PM |
|
IMO the huge hashrates being provided by proxied pools using WP as a backend are the problem and only improve profit for PW but not the dedicated WP miners because they take large amounts of shares away from us ... much like what ASIC are doing to scrypt.
Its just more hash-power, its bound to happen for every algorithm. If they weren't mining X11 on WP, they'd be mining X11 somewhere else, and having the exact same effect on WP.
|
|
|
|
sharkbyte093
|
|
July 18, 2014, 05:31:53 PM |
|
You guys have nearly 50% of the DRK hashrate. Miners please move to another pool!
|
|
|
|
Zels
|
|
July 18, 2014, 05:40:56 PM |
|
Same problem as Utahjohn Pool keep reseting my dif to 0.168 and connection timeout like every 5 or 10min ccminer -r 3 -R 5 -a x11 -o stratum+tcp://eu.wafflepool.com:3331 -u 1G5BiEDSaEmoHHDFqG2EhbpJvhdx8JvSYW_750ti -p d=0.008"
|
|
|
|
poolwaffle (OP)
|
|
July 18, 2014, 05:51:18 PM |
|
Same problem as Utahjohn Pool keep reseting my dif to 0.168 and connection timeout like every 5 or 10min ccminer -r 3 -R 5 -a x11 -o stratum+tcp://eu.wafflepool.com:3331 -u 1G5BiEDSaEmoHHDFqG2EhbpJvhdx8JvSYW_750ti -p d=0.008" Yep, should hopefully be fixed today/tomorrow. Its not an actual problem, just default difficulty too high (mining is working fine, you'll just have a ton of variance due to long times between shares).
|
|
|
|
alienesb
|
|
July 18, 2014, 09:58:23 PM |
|
Same problem as Utahjohn Pool keep reseting my dif to 0.168 and connection timeout like every 5 or 10min ccminer -r 3 -R 5 -a x11 -o stratum+tcp://eu.wafflepool.com:3331 -u 1G5BiEDSaEmoHHDFqG2EhbpJvhdx8JvSYW_750ti -p d=0.008" Dude, I'm only getting like 2100 for my 750tis what version/setting are you using?
|
|
|
|
Zels
|
|
July 18, 2014, 10:16:45 PM |
|
Dude, I'm only getting like 2100 for my 750tis what version/setting are you using?
Core clock +135 Memory clock +575 with msi afterburner
|
|
|
|
|