[POOL][Scrypt][Scrypt-N][X11] Profit switching pool - wafflepool.com

[suchmoon]

according with the statistic i have sended a media of 5 mh/s during 6 hours (that is excluding the hashrate rejected).

if the server have accepted the hash where are my coins?

can you please look at it?

http://wafflepool.com/miner/1LXh74pXQ94wpFF3QC3H6VSk32mbVGCrHe

Can you specify in more detail what you're looking for? You seem to have been paid on 9/28, and have some unpaid balance remaining, which you should receive next weekend (not enough for the daily threshold of 0.005). What seems to be the problem?

[ryukamiho]

according with the statistic i have sended a media of 5 mh/s during 6 hours (that is excluding the hashrate rejected).

if the server have accepted the hash where are my coins?

can you please look at it?

http://wafflepool.com/miner/1LXh74pXQ94wpFF3QC3H6VSk32mbVGCrHe

Can you specify in more detail what you're looking for? You seem to have been paid on 9/28, and have some unpaid balance remaining, which you should receive next weekend (not enough for the daily threshold of 0.005). What seems to be the problem?

Okay



01/10/2014

I have rented the rig  you see in the image.

for 6 hours. as you can see i got a lot of hash rejected. but still some hash worked.  but in the end my profit was 0.00000100 (100 satoshi)

Because before renting the server i have writed how much i had and it was

Earned (not yet sent)   0.00052002   
Unconverted (approximate)   0.00000000   
Earned+Unconverted   0.00052002



After the period i got

Earned+unconverted 0.00052102.


what i am asking how 6 hours with 8 mh/s even with reject hash got me only that?

To where went my hashpower?

I did contacted Betarigs, and they gave me a refund of 20% based on the rejected hashs but they confirmed that i have sended the rest of the hash power to wafflepool was working as intended.


If you check wafflemonitor, you will see that amount of hash in the chart.


But still i can't understand why 0.000000100

[phzi]

Every difficulty i am using its always the recomended at Faq.

If you want less variance on your hashrate charts, drop the difficulty.  Pretty simple, higher difficulty = more variance.  But in the end, both will average out to the same productivity, so the idea of "unstable hashrate" is silly and irrelevant.

[poolwaffle]

We're having some problems with our database (contacting the host right now) looks to be hard drive related.  But mining is disabled for now (should failover to backup pools) until it is sorted out.

Edit: Everything should be fine now.

[Stalker2]

under Current miners, it shows 0...
I can't see my miners, so I have pulled them until this issue is resolved.

[StuffOfInterest]

Can someone please post a sample of the output from the WafflePool wallet API (http://wafflepool.com/api/miner?address=XXXXXXXX) for an addresses that has been mined to.

I'm trying to integrate WafflePool into Miner Control.  I haven't mined to this pool yet so when I put in an address like this:

Code:

http://wafflepool.com/api/miner?address=1PMj3nrVq5CH4TXdJSnHHLPdvcXinjG72y

I get back this:

Code:

{"error":"Address not found!"}

Also, could whoever created the stats API (http://wafflepool.com/api/stats) please consider adding a sliding window earning number in addition to the date windows.  The current day numbers loose currency as the day progresses.  Having a set window, perhaps one hour or even three hours, would give a better view of how earnings change throughout the day and make it easier to determine when WafflePool is paying better than other pools.

Thanks.

[jpouza]

Mining: darkcoin   vsLTC: 666%

So evil and beautiful at same time 

[Zels]

Can someone please post a sample of the output from the WafflePool wallet API (http://wafflepool.com/api/miner?address=XXXXXXXX) for an addresses that has been mined to.

I'm trying to integrate WafflePool into Miner Control.  I haven't mined to this pool yet so when I put in an address like this:

Code:

http://wafflepool.com/api/miner?address=1PMj3nrVq5CH4TXdJSnHHLPdvcXinjG72y

I get back this:

Code:

{"error":"Address not found!"}

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}}}

Not really usefull for Minercontrol.  Would be better if we could get api to return value in http://wafflepool.com/stats

[StuffOfInterest]

Can someone please post a sample of the output from the WafflePool wallet API (http://wafflepool.com/api/miner?address=XXXXXXXX) for an addresses that has been mined to.

I'm trying to integrate WafflePool into Miner Control.  I haven't mined to this pool yet so when I put in an address like this:

Code:

http://wafflepool.com/api/miner?address=1PMj3nrVq5CH4TXdJSnHHLPdvcXinjG72y

I get back this:

Code:

{"error":"Address not found!"}

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}}}

Not really usefull for Minercontrol.  Would be better if we could get api to return value in http://wafflepool.com/stats

Oh, this is very useful for MinerControl.  I'm already parsing the output from the stats call to get earnings per algo.  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
        }
    }
}

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.

Now, a question.  There are three numbers: sent, confirmed, unconverted.  I want to see if I understand this correctly:

• 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?

[Zels]

Now, a question.  There are three numbers: sent, confirmed, unconverted.  I want to see if I understand this correctly:

• sent - BTC transferred from the pool to the address.
• confirmed - BTC earned and converted.
• unconverted - approximate BTC of unconverted coins.

• Yes, total of payout done to address since day 1
• Yes
• yes ^^

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?

Same stat but in image

[StuffOfInterest]

Now, a question.  There are three numbers: sent, confirmed, unconverted.  I want to see if I understand this correctly:

• sent - BTC transferred from the pool to the address.
• confirmed - BTC earned and converted.
• unconverted - approximate BTC of unconverted coins.

• Yes, total of payout done to address since day 1
• Yes
• yes ^^

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?

Same stat but in image

Yea, that confirms it.  Thanks.  I'll hopefully have this done in a day or two based off of the existing per day earning breakdown.  Hopefully the pool owner will add a sliding window earning later so the numbers will be more accurate.

Oh, and how in the heck does a coin have a negative BTC value?  If the exchange rate is so bad that the feeds exceed the value then I hope their engine would just leave it unconverted until there was a positive value.

[poolwaffle]

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
        }
    }
}

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:

• 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.

[poolwaffle]

Oh, and how in the heck does a coin have a negative BTC value?  If the exchange rate is so bad that the feeds exceed the value then I hope their engine would just leave it unconverted until there was a positive value.

Thats a bit odd.  For a number of the stats we use floats (since most of the time approximates are fine) and there might be a rounding error.  Can you post the address you're looking at and I'll check it out?

[Zels]

Oh, and how in the heck does a coin have a negative BTC value?  If the exchange rate is so bad that the feeds exceed the value then I hope their engine would just leave it unconverted until there was a positive value.

Thats a bit odd.  For a number of the stats we use floats (since most of the time approximates are fine) and there might be a rounding error.  Can you post the address you're looking at and I'll check it out?

1KSTYGj25RRQ5i1GNVUGTjUsSyZr4uSPiz

You can see negative for canabis & hidden

[phzi]

Oh, and how in the heck does a coin have a negative BTC value?  If the exchange rate is so bad that the feeds exceed the value then I hope their engine would just leave it unconverted until there was a positive value.

Thats a bit odd.  For a number of the stats we use floats (since most of the time approximates are fine) and there might be a rounding error.  Can you post the address you're looking at and I'll check it out?

Isn't this from when blocks confirm but are later orphaned, or orphaned blocks are missed? It isn't a negative exchange rate, it's a negative coin balance because coins were paid out but later orphaned. No?

[poolwaffle]

Oh, and how in the heck does a coin have a negative BTC value?  If the exchange rate is so bad that the feeds exceed the value then I hope their engine would just leave it unconverted until there was a positive value.

Thats a bit odd.  For a number of the stats we use floats (since most of the time approximates are fine) and there might be a rounding error.  Can you post the address you're looking at and I'll check it out?

Isn't this from when blocks confirm but are later orphaned, or orphaned blocks are missed? It isn't a negative exchange rate, it's a negative coin balance because coins were paid out but later orphaned. No?

This is correct, but thats normally (or at least I thought - I haven't looked into it in a while) listed under confirmed.  They get moved from unconfirmed --> confirmed --> paid --> negative confirmed.  Its most likely that a re-process of the block chains during maintenance changed that (we wipe tables and rebuild them from blockchains, which would see them as orphaned immediately, instead of immature --> confirmed --> orphaned).  I'll check it out.

[StuffOfInterest]

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.

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
        }
    }
}

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:

• 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.

[hans yolo]

Who in the seven kingdoms has joined wafflepool  ?? those are over 32 gh/s (and it's going up..) ... those HAVE to be asics ...

[utahjohn]

cannabiscoin    124.07676974    0.00031114    -0.25827761    -0.00000414

[cyclonereverb]

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?