█▓▒░-< [ZPOOL.CA][BTC Multipool] The miners multipool >-░▒▓█ Paid 925+ BTC

[ComputerGenie]

@joblo

You're right in that it is out of context; however, this type of board isn't really the right space to provide the 9 different pages that form to create the graphed estimates. That being said, you're still missing the point that since the estimates are calculated on a time and hashrate basis, by definition, they include the notion of continued mining. No one on Earth is going to create an estimate formula for on-again/off-again mining; the entire notion is ridiculous.

@everyone crying about the feken graph

Stop blaming the pool op because you don't like 1 small function of the 12 bajillion lines of prewritten code he employs. Suck it up, buttercup, and mine on. If you don't like it (and every yiimp pool on the planet), then write your own!

[Megaquake]

 What was the reason to remove Bitboss sha256, it seems now we need to take advantage of its current value

[ComputerGenie]

What was the reason to remove Bitboss sha256, it seems now we need to take advantage of its current value

Blockexplorer:  http://blocks.ypool.ga:2003

Dead 

Hi,

We've added BOSS to the miners multipool: www.zpool.ca

Cheers

And the amount of Orphans is insane!! Not to mention 36 unconfirmed (some "8d ago").

Why u still pushing this?
Dev left a long long time ago.

[Megaquake]

What was the reason to remove Bitboss sha256, it seems now we need to take advantage of its current value

Blockexplorer:  http://blocks.ypool.ga:2003

Dead 

Hi,

We've added BOSS to the miners multipool: www.zpool.ca

Cheers

And the amount of Orphans is insane!! Not to mention 36 unconfirmed (some "8d ago").

Why u still pushing this?
Dev left a long long time ago.

I just saw it on yobit is all lots of pump on that coin right now, went up from 5k sat to 7k sat in 10 minutes

[joblo]

@joblo

You're right in that it is out of context; however, this type of board isn't really the right space to provide the 9 different pages that form to create the graphed estimates. That being said, you're still missing the point that since the estimates are calculated on a time and hashrate basis, by definition, they include the notion of continued mining. No one on Earth is going to create an estimate formula for on-again/off-again mining; the entire notion is ridiculous.

@everyone crying about the feken graph

Stop blaming the pool op because you don't like 1 small function of the 12 bajillion lines of prewritten code he employs. Suck it up, buttercup, and mine on. If you don't like it (and every yiimp pool on the planet), then write your own!

Continued mining disguises the problem by adding another cariable. It's very simple actually. Mine lbry until you get a block. Now your
wallet has a share of one block of one coin. Stop mining imediatelty. If everything was static the value would remain the same, ie the
graph would be perfectly flat. But the coin's exchange price isn't static because you will notice the value fluctuate. Then the coin matures
and gets exchanged and 20% is lost.

If the value of the coin was not being updated the graph would stay flat as the coin matures because there are no other coins being added
or exchanged, just a share of one block of lbry. If that was the case there could be a significant difference between the hours-old estimate and
the current rate. But a consistent 20% no matter the coin is too much of a stretch. But that's not what I see.

I see the value fluctuating as the coin matures. Why is it doing that? I still have the same number of lbry so why is the value changing. Obviously
the exchange rate is being updated. If the exchange rate is regularly updated there should be no reason for a large discrepency when the coin
is ultimately sold.

Continued mining, which you're hung up on, just complicates things so it's harder to see the problem. I think crackfoo realizes there is an issue
but doesn't know what to do about it. But you're just in denial. Why are your denials so forceful yet so superficial without any supporting evidence.
Why are you so sure you're right? Why are you so sure I, and others, are wrong?

I've explained my position in great detail and anyone with the tools and the data can prove me right or wrong. I am willing to help in any way I can.
If there is a problem we all will benefit from getting it fixed, except maybe someone who is profiting from it.

[Epsylon3]

also remember the coin price = buy orders ... only

[joblo]

also remember the coin price = buy orders ... only

Yup, already considered that. A 20% spread might be possible for a couple of very very low volume coins
but it can't explain a consistent 20% bias. Also the quoted price is based on the last trade so if the
last trade was at the buy price there would be no spread discrepency.

Do you have any tips for data collection to trace the process from the time a block is found until it is sold?

Until we have real data it's all just speculation based on superficial observations. The question of what is causing
the apparent loss of 20% needs to be answered one way or another.

[crackfoo]

also remember the coin price = buy orders ... only

 Also the quoted price is based on the last trade so if the last trade was at the buy price there would be no spread discrepency.

Is it? The estimates are, AFAIK, based off the ASK price. The pool sells into the BIDs.

[joblo]

also remember the coin price = buy orders ... only

 Also the quoted price is based on the last trade so if the last trade was at the buy price there would be no spread discrepency.

Is it? The estimates are, AFAIK, based off the ASK price. The pool sells into the BIDs.

Most exchanges quote the last price as the price of the last trade. They can also quote bid and ask. If the pool is
specifically requesting the ask price it's misleading if you are selling into the bid. If you are placing market sell
orders you will always be getting the bid price so it would be more appropriate to use the bid price in your
estimates. Can you change it?

Edit:

The choice of exchange could also be a factor. If the pool is choosing among all the connected exchanges
how does it choose? If quoting ask prices and choosing the highest ask price it woul dfurther distort the estimate
from the actual trade, particularly if quoting a low volume exchange where higher price spreads are likely.

Quoting the highest bid, or the bid with the most volume, seems the best approach as this is most likely going
to be the trade price.

[JaredKaragen]

I may write myself a program to take the pool's share percentage and calculate that into what algo to mine;

When I switch my miners to 100% an algo that is profitable but I get 15%+ share on a low number of miners;  I seem to get crazy wicked profit spikes.

I want an app that will take advantage of this.

Sitting on XRE for the last 24 hours has been very nice...  Seeing 10%-25%+

[Lercker]

Anyone else notice that a lot of coins are taking an abnormally long time to go from New to Immature and actually show up that you mined them?

[berron]

There are weird things happening in the pool rigth now. I'm minning algos which theoretically are not finding blocks, so I'm accumulating shares



But when I enter in that algo tab, the pool is getting coins, but it's not able to confirm them.



Hope you can solve this fast, crackfoo. I will stop mining till then.

[joblo]

also remember the coin price = buy orders ... only

 Also the quoted price is based on the last trade so if the last trade was at the buy price there would be no spread discrepency.

Is it? The estimates are, AFAIK, based off the ASK price. The pool sells into the BIDs.

Most exchanges quote the last price as the price of the last trade. They can also quote bid and ask. If the pool is
specifically requesting the ask price it's misleading if you are selling into the bid. If you are placing market sell
orders you will always be getting the bid price so it would be more appropriate to use the bid price in your
estimates. Can you change it?

Edit:

The choice of exchange could also be a factor. If the pool is choosing among all the connected exchanges
how does it choose? If quoting ask prices and choosing the highest ask price it woul dfurther distort the estimate
from the actual trade, particularly if quoting a low volume exchange where higher price spreads are likely.

Quoting the highest bid, or the bid with the most volume, seems the best approach as this is most likely going
to be the trade price.

I did some of the grunt work.

Here is a sample for Poloniex. Other exchanges have similar code.  It looks like the estimate is based on either the bid price
or the average of the bid and ask price, depending on whether it uses price or price2. I don't know what AverageIncrement does.
It also appears to look for the best market. It doesn't look like this is the problem.

https://github.com/tpruvot/yiimp/blob/next/web/yaamp/core/backend/markets.php

Code:

		$price2 = ($ticker['highestBid']+$ticker['lowestAsk'])/2;
		$market->price2 = AverageIncrement($market->price2, $price2);
		$market->price = AverageIncrement($market->price, $ticker['highestBid']);
		$market->pricetime = time();

[joblo]

Anyone else notice that a lot of coins are taking an abnormally long time to go from New to Immature and actually show up that you mined them?

It happens sometimes but 2 hours behind is unusual. Something must be stuck.

[crackfoo]

Anyone else notice that a lot of coins are taking an abnormally long time to go from New to Immature and actually show up that you mined them?

It happens sometimes but 2 hours behind is unusual. Something must be stuck.

There was a block record that was corrupted so block processing was down until it was removed. It running through now, but there was about 6000 blocks to process.

[Epsylon3]

price2 is the ask (sell) price which is there for information and/or initial sale orders in auto exchange mode. A big difference between both generally means the exchange is not used enough.

The used one for estimations is price. And the "avg increment" is there to prevent some instant peaks, that make the curve more "flat"

[berron]

Anyone else notice that a lot of coins are taking an abnormally long time to go from New to Immature and actually show up that you mined them?

It happens sometimes but 2 hours behind is unusual. Something must be stuck.

There was a block record that was corrupted so block processing was down until it was removed. It running through now, but there was about 6000 blocks to process.

But all that blocks where not valid or what? I have lost my share in the algos I mined during the stuck time without receive any payment. So if the blocks where valid I have been mining two hours for the pool for free. Not fair. 

[berron]

EDIT: Taking a more close look there is a jump in my balance graph that seems to be that share being paid, but without blocks mined being shown in the found blocks list. Is anyone seen something similar (so no lack of payment, lack of mined block refresh instead)

[berron]

Stucked again since one hour ago aprox. Please, crakfoo, tell us when definitely solved. Thanks.

[joblo]

EDIT: Taking a more close look there is a jump in my balance graph that seems to be that share being paid, but without blocks mined being shown in the found blocks list. Is anyone seen something similar (so no lack of payment, lack of mined block refresh instead)

This is the problem I am complaining about. When a coin is sold (balance goes up) the total drops representing approx 20% loss.
It's not due to the stuck block, I have never seen losses due to it.

@Epsylon3, thanks for explaing the exchange code. It appears the estimates are based on the bid price which should be close to
the actual trade price. The discrepency must be caused by something else.