WTF?
http://wafflepool.com/miner/112osU8zqMs72oWRRKBDNruZ7qi3dYuHXL
Almost 50% of the pool hash power in X11.
Topic: [POOL][Scrypt][Scrypt-N][X11] Profit switching pool - wafflepool.com - page 7. (Read 465750 times)
October 22, 2014, 10:21:31 AM
October 21, 2014, 01:06:11 PM
Is there some problem with the pool right now?
Had high rejects on eu.wafflepool.com (Job not found errors) switched to useast and it's all goodeu and us are the same for me, getting 30-50% rejects due to job not found, it looks like the same issue from couple of weeks before (some hardware problems if I remember correctly)
October 21, 2014, 09:52:53 AM
Is there some problem with the pool right now?
Had high rejects on eu.wafflepool.com (Job not found errors) switched to useast and it's all good October 21, 2014, 04:43:58 AM
Is there some problem with the pool right now?
October 21, 2014, 01:36:08 AM
But the reject radio is growing big. 
October 20, 2014, 12:21:49 PM
x11 Hashrate: 60.10 GH/s Mining: hidden vsLTC: 678%
So beast, throwing my 30MH/s, doing nicely!
Cheers
So beast, throwing my 30MH/s, doing nicely!
Cheers
October 15, 2014, 12:41:16 PM
Mintpal is gone. How many coin store in there unexchange yet?
Affirmative.
"MintPal is currently down for urgent bug fixes, and is additionally moving to new management (away from Moopay LTD). A statement will follow shortly."
The question is, when will we get paid?
Cheers
I unfortunately don't have a good answer for that. Glancing at the coins right now, it looks like we have approx 2btc in unexchanged coins, these coins were all mined within a few hours of mintpal "upgrading", when everything was explained/looked like they would be down for a few hours for upgrades, and then back to working order. Instead, they have been down (essentially) for a few weeks now, and some of the coins that were sent while they were upgrading still haven't shown up in the account.
At this point, I honestly don't know whats going on over there. The original site was working fine, and then they botch an upgrade pretty majorly, and now they're either closing down, or changing management (@moolah_io on twitter seems like he's saying completely different things about what is happening every few hours).
Essentially if the exchange comes back up and our deposits show up, we'll withdraw the coins and try to manually exchange them on whatever exchanges support those coins (if there are any). If we can't recover those coins (way too early to tell) they'll probably be written off, as there really isn't much we can do there.
tldr; we wait and see for now.
October 15, 2014, 11:16:09 AM
Mintpal is gone. How many coin store in there unexchange yet?
Affirmative.
"MintPal is currently down for urgent bug fixes, and is additionally moving to new management (away from Moopay LTD). A statement will follow shortly."
The question is, when will we get paid?
Cheers
October 15, 2014, 09:40:38 AM
Mintpal is gone. How many coin store in there unexchange yet?
October 14, 2014, 01:44:18 PM
yeah my associate operating EU pool says pretty much the same, don't worry about it 
October 14, 2014, 01:19:37 PM
.. snipped ..
I really wouldn't read much into it. Its most likely just someone scanning around for vulnerabilities and spewing data at random ports/ips around the internet. Its obviously passing a cookie (something that isn't even remotely connected to stratum), you're going down a rabbit hole looking for stuff that probably isn't there... Imagine I pulled up a random SMTP vulnerability for a random SMTP server, and fired it at your stratum server. Your server would say "malformed message", and you can either ignore it (very safely), or spend a ton of time tracking down essentially nothing.
October 14, 2014, 11:03:11 AM
Any idea what this is:
2014-10-13 19:16:37 [Pool] [diamondcoin] (Thread 2) Malformed message from (unauthorized) [117.25.128.139]: �Cookie: mstshash=g
http://www.tcpiputils.com/browse/ip-address/117.25.128.139
Not much help there, but it is in China
is there any way I can examine the malformed message
I suppose I'll have to have some TCP logging of some sort and wait for another one ... only get it a couple times a day ...
2014-10-13 19:16:37 [Pool] [diamondcoin] (Thread 2) Malformed message from (unauthorized) [117.25.128.139]: �Cookie: mstshash=g
http://www.tcpiputils.com/browse/ip-address/117.25.128.139
Not much help there, but it is in China
is there any way I can examine the malformed message
I suppose I'll have to have some TCP logging of some sort and wait for another one ... only get it a couple times a day ...
Looks fine, anything could be a malformed message, as long as it doesn't conform to exactly what NOMP was expecting. So if you connected and just sent "{a:a:a:a:A:a:a:a:a:]" to it, it would probably break and spit out the same line of text (malformed message). Assuming there isn't a flaw in how NOMP parses the data coming in, its just garbage data...
OK I'm still gonna block that IP in firewall tho
Got another one from another IP 192.210.53.41, looking at where it came from.
Had similar Cookie: mstshash=a
Domain neighbors for IP: 192.210.53.41
Found 2 websites running on IP address 192.210.53.41.
Domain Pagerank Alexa ranking Quantcast ranking
xuezhao.net
sanlewh.com
Found 65 IP addresses with hosting around 192.210.53.41.
IP address Number of websites Example
192.210.53.3 1 defurid.com
192.210.53.6 1 eucoque.fr
192.210.53.14 1 pdstp.com
192.210.53.18 67 utf8.cn
192.210.53.19 1 689686.com
192.210.53.38 2 yazhoubocaitong.com
192.210.53.39 1 jinguanquanxunwang.com
192.210.53.40 2 yushouzhe.com
192.210.53.41 2 sanlewh.com
192.210.53.45 2 kjiussfiiu.com
192.210.53.46 1 tonkincorp.com
192.210.53.49 2 ucskqq.com
192.210.53.54 1 jingbaominzzmz.com
192.210.53.57 2 jingdongmmzgdool.com
192.210.53.75 4 dlrft.com
192.210.53.77 1 hujita-store.com
192.210.53.98 1 ctom.us
192.210.53.101 8 sengd88.xyz
192.210.53.103 2 borcr.com
192.210.53.107 10 acy.in
192.210.53.108 1 supplierss.com
192.210.53.109 1 yyjiaoyi.com
192.210.53.110 1 yixiuba.com
192.210.53.111 1 beststyledresses.com
192.210.53.113 3 yaoons.org
192.210.53.116 1 342324.com
192.210.53.118 2 2014bikinis.com
192.210.53.119 1 qbochina.com
192.210.53.125 1 superstarwigs.com
192.210.53.131 1 fatswede.com
192.210.53.139 1 qaiai.wang
192.210.53.155 1 fangzhiguan.com
192.210.53.162 1 njhbs.net
192.210.53.163 1 yingtaowang.net
192.210.53.164 1 tonglelebaby.com
192.210.53.165 1 huayaexpo.com
192.210.53.166 1 5use.net
192.210.53.167 1 jsfgold.com
192.210.53.168 1 jxjihong.com
192.210.53.169 1 jxmin.com
192.210.53.170 1 kanituan.com
192.210.53.171 1 lcdycm.com
192.210.53.172 1 lfdahao.com
192.210.53.173 1 szwfl.com
192.210.53.174 1 lzshengfa.com
192.210.53.175 1 mybesa.com
192.210.53.176 1 qianqin.net
192.210.53.177 1 qianyiwang.com
192.210.53.178 1 souney.com
192.210.53.179 1 szrongxing.com
192.210.53.180 1 liupinyan.com
192.210.53.181 1 tzwuxin.com
192.210.53.182 1 wuyetuan.com
192.210.53.183 1 xynhsh.com
192.210.53.184 1 xzy88.com
192.210.53.185 1 zjrjyy.com
192.210.53.186 1 beiyunsi.com
192.210.53.187 1 cimdo.com
192.210.53.188 1 hbhtc.com
192.210.53.189 1 hzzuche.net
192.210.53.190 1 icharmonline.com
192.210.53.194 1 dirpy.com
192.210.53.208 1 hljer.com
192.210.53.210 1 x3x3x3.com
192.210.53.211 2 qyk.cc
China again ... The whois shows California, USA on another web tool ...-
And another one:
2014-10-14 11:49:32 [Pool] [diamondcoin] (Thread 2) Malformed message from (unauthorized) [80.82.70.239]: �Cookie: mstshash=a
have you seen this linux backdoor analysis : https://www.nccgroup.com/en/blog/2014/10/analysis-of-the-linux-backdoor-used-in-freenode-irc-network-compromise/
Thanks
October 14, 2014, 10:22:17 AM
Any idea what this is:
2014-10-13 19:16:37 [Pool] [diamondcoin] (Thread 2) Malformed message from (unauthorized) [117.25.128.139]: �Cookie: mstshash=g
http://www.tcpiputils.com/browse/ip-address/117.25.128.139
Not much help there, but it is in China
is there any way I can examine the malformed message
I suppose I'll have to have some TCP logging of some sort and wait for another one ... only get it a couple times a day ...
2014-10-13 19:16:37 [Pool] [diamondcoin] (Thread 2) Malformed message from (unauthorized) [117.25.128.139]: �Cookie: mstshash=g
http://www.tcpiputils.com/browse/ip-address/117.25.128.139
Not much help there, but it is in China
is there any way I can examine the malformed message
I suppose I'll have to have some TCP logging of some sort and wait for another one ... only get it a couple times a day ...
Looks fine, anything could be a malformed message, as long as it doesn't conform to exactly what NOMP was expecting. So if you connected and just sent "{a:a:a:a:A:a:a:a:a:]" to it, it would probably break and spit out the same line of text (malformed message). Assuming there isn't a flaw in how NOMP parses the data coming in, its just garbage data...
October 13, 2014, 09:10:02 PM
@PW
I need some help here, I know we had exploit probs on wafflepool ages ago, anyway here is what is troubling me, u finally got them resolved :
It has to be something deliberate to my DMD port, some sort of exploit attempt ?
I am running NOMP+MPOS ...
I still mine here too, but minimum X11 d=0.008 is still a bit too high for my lower hashrate cards on X11, any setting below this does not take effect
and diff resets to 0.160 ...
I need some help here, I know we had exploit probs on wafflepool ages ago, anyway here is what is troubling me, u finally got them resolved
:Any idea what this is:
2014-10-13 19:16:37 [Pool] [diamondcoin] (Thread 2) Malformed message from (unauthorized) [117.25.128.139]: �Cookie: mstshash=g
http://www.tcpiputils.com/browse/ip-address/117.25.128.139
Not much help there, but it is in China
is there any way I can examine the malformed message
I suppose I'll have to have some TCP logging of some sort and wait for another one ... only get it a couple times a day ...
2014-10-13 19:16:37 [Pool] [diamondcoin] (Thread 2) Malformed message from (unauthorized) [117.25.128.139]: �Cookie: mstshash=g
http://www.tcpiputils.com/browse/ip-address/117.25.128.139
Not much help there, but it is in China
is there any way I can examine the malformed message
I suppose I'll have to have some TCP logging of some sort and wait for another one ... only get it a couple times a day ...
It has to be something deliberate to my DMD port, some sort of exploit attempt ?
I am running NOMP+MPOS ...
I still mine here too, but minimum X11 d=0.008 is still a bit too high for my lower hashrate cards on X11, any setting below this does not take effect
and diff resets to 0.160 ... October 11, 2014, 02:34:05 PM
why does poolpicker.eu still show Wafflepool as mining X13, and how come WP got most profitable pool a few times at the start of the month (last few days not so good...)?? Where are these stats coming from?
...Quote from: PoolPicker
About PoolPicker
This statistics page works by gathering data from the pools official stats pages and plot then simply plots it in a grid.
Poolpicker is terribad and a totally unreliable way to compare mining pools. They don't use _actual_ income data, they just parse APIs and scrape websites for pool reported profitability. Not to mention their graphs break all the time. This statistics page works by gathering data from the pools official stats pages and plot then simply plots it in a grid.
October 11, 2014, 12:46:22 AM
why does poolpicker.eu still show Wafflepool as mining X13, and how come WP got most profitable pool a few times at the start of the month (last few days not so good...)?? Where are these stats coming from?
If you look at the numbers they're identical to Waffle's Scrypt numbers. Probably some kind of a glitch there.
October 11, 2014, 12:40:32 AM
why does poolpicker.eu still show Wafflepool as mining X13, and how come WP got most profitable pool a few times at the start of the month (last few days not so good...)?? Where are these stats coming from?
October 08, 2014, 04:27:25 PM
cannabiscoin 124.07676974 0.00031114 -0.25827761 -0.00000414
October 07, 2014, 02:14:05 PM
Who in the seven kingdoms has joined wafflepool 
?? those are over 32 gh/s (and it's going up..) ... those HAVE to be asics ...
?? those are over 32 gh/s (and it's going up..) ... those HAVE to be asics ... October 07, 2014, 08:29:38 AM
OK, the information on the API was very helpful. Thanks to both Zels and poolwaffle for the samples and explanations.
Last night I put out Miner Control 1.2.1 (with a fix version 1.2.2 this morning) which now supports WafflePool. With the two API calls it is able to show earning potential along with per algorithm balances and hash rates. If the stats api is tweaked for sliding window later I'll update to support that but for now I'm using the current day prices in the earnings calculator.
Full details and download links are available on the Miner Control thread. Example configurations for supporting WafflePool are also provided.
One more question, what is the deal with X13? It shows in the API but not in the front end. Doesn't appear to have any miners and shows 0 price but is still sending information.
Oh, this is very useful for MinerControl. I'm already parsing the output from the stats call to get earnings per algo.
If possible, please don't parse the output of the stats page, there is an API for that (/api/stats), if theres something missing there, let me know and I can see how tough it is to add.
The piece I'm asking about here is for the balance numbers. Here is the same result reformatted by jsonlint.com for easier reading.
One thing I like here is that we have hashrate and balance per algorithm. Only NiceHash/WestHash gave me that previously. I'm not too happy seeing numbers like this: "2.220345987e-7". Hopefully the C# JSON parser handles this format correctly. It did pass the JSONLint so that is a good sign.
Yep, "e-" and "e+" notation are both valid JSON Since some balances are super low and we're returning them as floats (only other option would be as strings, maybe satoshi integers), they come up with scientific notation.
This is correct. Confirmed is how much you have confirmed BTC. This number should only ever go up (until a payout). Unconfirmed will vary a bit as exchange rates fluctuate. On your next payout (assuming you meet the criteria) you'll be paid the amount in Confirmed.
Last night I put out Miner Control 1.2.1 (with a fix version 1.2.2 this morning) which now supports WafflePool. With the two API calls it is able to show earning potential along with per algorithm balances and hash rates. If the stats api is tweaked for sliding window later I'll update to support that but for now I'm using the current day prices in the earnings calculator.
Full details and download links are available on the Miner Control thread. Example configurations for supporting WafflePool are also provided.
One more question, what is the deal with X13? It shows in the API but not in the front end. Doesn't appear to have any miners and shows 0 price but is still sending information.
Oh, this is very useful for MinerControl. I'm already parsing the output from the stats call to get earnings per algo.
If possible, please don't parse the output of the stats page, there is an API for that (/api/stats), if theres something missing there, let me know and I can see how tough it is to add.
The piece I'm asking about here is for the balance numbers. Here is the same result reformatted by jsonlint.com for easier reading.
Code:
{
"scrypt": {
"hashrate": 0,
"hashrate_str": "0.00 kH/s",
"stalerate": 0,
"stalerate_str": "0.00 kH/s",
"workers": [],
"balances": {
"sent": 0,
"confirmed": 0,
"unconverted": 0
}
},
"nscrypt": {
"hashrate": 0,
"hashrate_str": "0.00 kH/s",
"stalerate": 0,
"stalerate_str": "0.00 kH/s",
"workers": [],
"balances": {
"sent": 0.00177243,
"confirmed": 0,
"unconverted": 0
}
},
"x11": {
"hashrate": 808137,
"hashrate_str": "808.14 kH/s",
"stalerate": 0,
"stalerate_str": "0.00 kH/s",
"workers": {
"1KSTYGj25RRQ5i1GNVUGTjUsSyZr4uSPiz_R9": {
"hashrate": 808137,
"stalerate": 0,
"str": "808.14 kH/s",
"last_seen": 1412611329
}
},
"balances": {
"sent": 0.02127437,
"confirmed": 0.00039378,
"unconverted": 2.220345987e-7
}
},
"x13": {
"hashrate": 0,
"hashrate_str": "0.00 kH/s",
"stalerate": 0,
"stalerate_str": "0.00 kH/s",
"workers": [],
"balances": {
"sent": 0,
"confirmed": 0,
"unconverted": 0
}
}
}
"scrypt": {
"hashrate": 0,
"hashrate_str": "0.00 kH/s",
"stalerate": 0,
"stalerate_str": "0.00 kH/s",
"workers": [],
"balances": {
"sent": 0,
"confirmed": 0,
"unconverted": 0
}
},
"nscrypt": {
"hashrate": 0,
"hashrate_str": "0.00 kH/s",
"stalerate": 0,
"stalerate_str": "0.00 kH/s",
"workers": [],
"balances": {
"sent": 0.00177243,
"confirmed": 0,
"unconverted": 0
}
},
"x11": {
"hashrate": 808137,
"hashrate_str": "808.14 kH/s",
"stalerate": 0,
"stalerate_str": "0.00 kH/s",
"workers": {
"1KSTYGj25RRQ5i1GNVUGTjUsSyZr4uSPiz_R9": {
"hashrate": 808137,
"stalerate": 0,
"str": "808.14 kH/s",
"last_seen": 1412611329
}
},
"balances": {
"sent": 0.02127437,
"confirmed": 0.00039378,
"unconverted": 2.220345987e-7
}
},
"x13": {
"hashrate": 0,
"hashrate_str": "0.00 kH/s",
"stalerate": 0,
"stalerate_str": "0.00 kH/s",
"workers": [],
"balances": {
"sent": 0,
"confirmed": 0,
"unconverted": 0
}
}
}
One thing I like here is that we have hashrate and balance per algorithm. Only NiceHash/WestHash gave me that previously. I'm not too happy seeing numbers like this: "2.220345987e-7". Hopefully the C# JSON parser handles this format correctly. It did pass the JSONLint so that is a good sign.
Yep, "e-" and "e+" notation are both valid JSON
Since some balances are super low and we're returning them as floats (only other option would be as strings, maybe satoshi integers), they come up with scientific notation.Now, a question. There are three numbers: sent, confirmed, unconverted. I want to see if I understand this correctly:
Based on this it looks like a person's current balance would be "confirmed + unconverted" although the amount ready for payout is only "confirmed".
Does this sound correct?
- sent - BTC transferred from the pool to the address.
- confirmed - BTC earned and converted.
- unconverted - approximate BTC of unconverted coins.
Based on this it looks like a person's current balance would be "confirmed + unconverted" although the amount ready for payout is only "confirmed".
Does this sound correct?
This is correct. Confirmed is how much you have confirmed BTC. This number should only ever go up (until a payout). Unconfirmed will vary a bit as exchange rates fluctuate. On your next payout (assuming you meet the criteria) you'll be paid the amount in Confirmed.
Jump to: