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

[crackfoo]

...........

EDIT: Might have got the two prices the wrong way around above.

But WTF - In all my years of working on financial trading systems I have never come across any kind of arbitrary logic like this, and I am really having difficulty understanding the reason for the price manipulation:

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

Code:

function AverageIncrement($value1, $value2)
{
	$percent = 80;
	$value = ($value1*(100-$percent) + $value2*$percent) / 100;
	return $value;
}

Code:

		$price2 = ($ticker->result[0]->Bid+$ticker->result[0]->Ask)/2;
		$market->price2 = AverageIncrement($market->price2, $price2);
		$market->price = AverageIncrement($market->price, $ticker->result[0]->Bid);

Why not just run of the bid price? That's how long financial market positions are typically valued. Thats the price you will get if looking for a quick exchange.

Disabled c11 for now to see how profitability goes not being stuck on that algo.

Another EDIT: Perhaps it is trying to provide some kind of market price change smoothing function?

Yeah I'm not too sure why it is the way it is. Sounds like you are about right, just some way to maintain some price flexibility? Unfortunately I'm not really capable of re-coding all that and I'm reluctant to starting muddling with it not understanding the full impact of changes.

[AngryDwarf]

Yeah I'm not too sure why it is the way it is. Sounds like you are about right, just some way to maintain some price flexibility? Unfortunately I'm not really capable of re-coding all that and I'm reluctant to starting muddling with it not understanding the full impact of changes.

It is quite a large system to try and understand, so I can understand concerns over what impacts any small change might apparently have elsewhere. From further investigation it looks like profitability should be calculated somewhat from the bid price (with the big exchanges such as Poloniex and Bittrex taking priority unless another priority exchange is specified on a per coin basis), otherwise best bid price from the other exchanges. The trading functions do seem to attempt to rip up the buy order book, after cancelling any orders found above ask price. So apart from a few oddities it does seem to be attempting to do what I think it should.
The profitability in the pool stats page are always significantly higher than the profitability stated on the wallet page. The former is what seems to cause my miner switches. The latter shows my miner has been heavily weighted on what is not the most profitable algo.
If I look at this code any more I'll probably go mad and try to write my own system from scratch. Since I noticed that you are on github, maybe you could submit some of the issues found by the users here to be looked at by the maintainer?

[MeteoImpact]

The 80% maximum shares bug definitely appears to be a thing. I tried testing by solo-mining blake with some cards for a while; once I found a block, it cleared all shares from the last miner (who probably stopped mining more than 24 hours ago) and set my share to 80% when it should be 100% (or 98% if fees are subtracted).

Pics:


Will definitely keep my estimates for this pool lowered for the time being; basically need to account for a 20% pool fee at the moment.

EDIT: Uhh, then this happened (solo-mined all these blocks).


So 74.97%? That's not 100% either. In fact, it's not even 80%.

[AngryDwarf]

Earnings results seem to happen here:

https://github.com/tpruvot/yiimp/blob/yiimp/web/yaamp/modules/site/results/user_earning_results.php

Code:

<?php
function WriteBoxHeader($title)
{
	echo "<div class='main-left-box'>";
	echo "<div class='main-left-title'>$title</div>";
	echo "<div class='main-left-inner'>";
}
$algo = user()->getState('yaamp-algo');
$user = getuserparam(getparam('address'));
if(!$user || $user->is_locked) return;
$count = getparam('count');
$count = $count? $count: 50;
WriteBoxHeader("Last $count Earnings: $user->username");
$earnings = getdbolist('db_earnings', "userid=$user->id order by create_time desc limit :count", array(':count'=>$count));
echo "<table class='dataGrid2'>";
echo "<thead>";
echo "<tr>";
echo "<td></td>";
echo "<th>Name</th>";
echo "<th align=right>Amount</th>";
echo "<th align=right>Percent</th>";
echo "<th align=right>mBTC</th>";
echo "<th align=right>Time</th>";
echo "<th align=right>Status</th>";
echo "</tr>";
echo "</thead>";
$showrental = (bool) YAAMP_RENTAL;
foreach($earnings as $earning)
{
	$coin = getdbo('db_coins', $earning->coinid);
	$block = getdbo('db_blocks', $earning->blockid);
	if (!$block) {
		debuglog("missing block id {$earning->blockid}!");
		continue;
	}
	$d = datetoa2($earning->create_time);
	if(!$coin)
	{
		if (!$showrental)
			continue;
		$reward = bitcoinvaluetoa($earning->amount);
		$value = altcoinvaluetoa($earning->amount*1000);
		$percent = $block? mbitcoinvaluetoa($earning->amount*100/$block->amount): '';
		$algo = $block? $block->algo: '';
		echo "<tr class='ssrow'>";
		echo "<td width=18><img width=16 src='/images/btc.png'></td>";
		echo "<td><b>Rental</b><span style='font-size: .8em'> ($algo)</span></td>";
		echo "<td align=right style='font-size: .8em'><b>$reward BTC</b></td>";
		echo "<td align=right style='font-size: .8em'>{$percent}%</td>";
		echo "<td align=right style='font-size: .8em'>$value</td>";
		echo "<td align=right style='font-size: .8em'>$d ago</td>";
		echo "<td align=right style='font-size: .8em'>Cleared</td>";
		echo "</tr>";
		continue;
	}
	$reward = altcoinvaluetoa($earning->amount);
	$percent = mbitcoinvaluetoa($earning->amount*100/$block->amount);
	$value = altcoinvaluetoa($earning->amount*$earning->price*1000);
	echo "<tr class='ssrow'>";
	echo "<td width=18><img width=16 src='$coin->image'></td>";
	echo "<td><b>$coin->name</b><span style='font-size: .8em'> ($coin->algo)</span></td>";
	echo "<td align=right style='font-size: .8em'><b>$reward $coin->symbol_show</b></td>";
	echo "<td align=right style='font-size: .8em'>{$percent}%</td>";
	echo "<td align=right style='font-size: .8em'>$value</td>";
	echo "<td align=right style='font-size: .8em'>$d ago</td>";
	echo "<td align=right style='font-size: .8em'>";
	if($earning->status == 0)
		echo "Immature ($block->confirmations)";
	else if($earning->status == 1)
		echo 'Exchange';
	else if($earning->status == 2)
		echo 'Cleared';
	echo "</td>";
	echo "</tr>";
}
echo "</table>";
echo "<br></div></div><br>";

Earnings population seems to happen here:

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

Code:

function BackendBlockNew($coin, $db_block)
{
//	debuglog("NEW BLOCK $coin->name $db_block->height");
	$reward = $db_block->amount;
	if(!$reward || $db_block->algo == 'PoS' || $db_block->algo == 'MN') return;
	$sqlCond = "valid = 1";
	if(!YAAMP_ALLOW_EXCHANGE) // only one coin mined
		$sqlCond .= " AND coinid = ".intval($coin->id);
	$total_hash_power = dboscalar("SELECT SUM(difficulty) FROM shares WHERE $sqlCond AND algo=:algo", array(':algo'=>$coin->algo));
	if(!$total_hash_power) return;
	$list = dbolist("SELECT userid, SUM(difficulty) AS total FROM shares WHERE $sqlCond AND algo=:algo GROUP BY userid",
			array(':algo'=>$coin->algo));
	foreach($list as $item)
	{
		$hash_power = $item['total'];
		if(!$hash_power) continue;
		$user = getdbo('db_accounts', $item['userid']);
		if(!$user) continue;
		$amount = $reward * $hash_power / $total_hash_power;
		if(!$user->no_fees) $amount = take_yaamp_fee($amount, $coin->algo);
		$earning = new db_earnings;
		$earning->userid = $user->id;
		$earning->coinid = $coin->id;
		$earning->blockid = $db_block->id;
		$earning->create_time = $db_block->time;
		$earning->amount = $amount;
		$earning->price = $coin->price;
		if($db_block->category == 'generate')
		{
			$earning->mature_time = time();
			$earning->status = 1;
		}
		else	// immature
			$earning->status = 0;
		if (!$earning->save())
			debuglog(__FUNCTION__.": Unable to insert earning!");
		$user->last_login = time();
		$user->save();
	}
	$delay = time() - 5*60;
	$sqlCond = "time < $delay";
	if(!YAAMP_ALLOW_EXCHANGE) // only one coin mined
		$sqlCond .= " AND coinid = ".intval($coin->id);
	dborun("DELETE FROM shares WHERE algo=:algo AND $sqlCond",
		array(':algo'=>$coin->algo));
}

So the fee should be deducted from the amount in the earnings column.
I think you should see 100% mining share, and 98% earning share.
It's beginning to look like some of the issues stem from the shares table, and perhaps the blocks table (since 80 * .98 != 74.97), both of which I think are populated from the stratum processes.
When Turguy has finished adding decred to the system, I hope he looks at some of this sht with high priority.

[AngryDwarf]

zpool @_xpool_
We've increased the minimum payouts from 0.001 to 0.005 and payouts ever 3 hours instead of 2.

When I mine alt coins (either for exchange or not), it takes a few hours before the coin maturity kicks in. I then get a dribble of longer maturity coins coming in. The payout period could probably be increased to 6 hours.
5mBTC is a bit steep of a minimum payout for some, and is the kind of value which makes me look for pools which don't want to keep my coins. Glad to see the 100 uBTC Sunday payout remains.
Perhaps 2mBTC/6 hours would be a better compromise for all?

[AngryDwarf]

Hello Crackfoo

LTC payments?  

They should be sent out but I'd suggest using another currency since we're no where near enough hashrate to be hitting and ltc blocks

Perhaps some of the popular POW coins could be setup similar to how the new POS payout coins have been added? I've noticed the system is saying we are around 5.0 short on dash. That's 2 blocks needed. And I bet plenty of people are still mining it.

The system is now 6.5 short on dash, and ttf is currently 10 hours.

[crackfoo]

zpool @_xpool_
We've increased the minimum payouts from 0.001 to 0.005 and payouts ever 3 hours instead of 2.

When I mine alt coins (either for exchange or not), it takes a few hours before the coin maturity kicks in. I then get a dribble of longer maturity coins coming in. The payout period could probably be increased to 6 hours.
5mBTC is a bit steep of a minimum payout for some, and is the kind of value which makes me look for pools which don't want to keep my coins. Glad to see the 100 uBTC Sunday payout remains.
Perhaps 2mBTC/6 hours would be a better compromise for all?

How about 0.0025 every 3 hours.

[AngryDwarf]

zpool @_xpool_
We've increased the minimum payouts from 0.001 to 0.005 and payouts ever 3 hours instead of 2.

When I mine alt coins (either for exchange or not), it takes a few hours before the coin maturity kicks in. I then get a dribble of longer maturity coins coming in. The payout period could probably be increased to 6 hours.
5mBTC is a bit steep of a minimum payout for some, and is the kind of value which makes me look for pools which don't want to keep my coins. Glad to see the 100 uBTC Sunday payout remains.
Perhaps 2mBTC/6 hours would be a better compromise for all?

How about 0.0025 every 3 hours.

It's about balancing the requirements of the higher hash rate miners with that of the lower hash rate miners, whilst also taking into consideration those who also periodically mine alt coins. I'll leave it to others to suggest what they think is best for them.

EDIT: but at least 6 2mBTC/2.5mBTC lumps can be combined using coin control into a free transaction to oneself, where 1 mBTC chunks can't without having a bigger lump to start with.

[jds1119]

Tried usuing this pool today for the first time and I run my machines through MRR, but I kept losing workers and hashrate. Is that normal? Was today a bad day for the pool? I had about 30TH put on it

[crackfoo]

Tried usuing this pool today for the first time and I run my machines through MRR, but I kept losing workers and hashrate. Is that normal? Was today a bad day for the pool? I had about 30TH put on it

We're still looking into an issue where sometimes the stratum server will reset if there was not a timely response from a wallet.

[jds1119]

Tried usuing this pool today for the first time and I run my machines through MRR, but I kept losing workers and hashrate. Is that normal? Was today a bad day for the pool? I had about 30TH put on it

We're still looking into an issue where sometimes the stratum server will reset if there was not a timely response from a wallet.

Thanks, that's understandable. I will be keeping and eye on it and hope it all works out well. Im user " 1rkBkzmKfZ11wUBH3L2JGv1rRVPL6gPtD "

[djoser]

How about 0.0025 every 3 hours.

That's a reasonable payout threshold.

But more important:
You should make sure that the sunday payout of amounts below that threshold are only paid once on sunday.
In the past there were 3 or even 4 payouts of small amounts on sundays.

Regards, djoser.

[AngryDwarf]

Meanwhile, over on hashpower.co, we don't seem to have this 80% share limit problem. I can't say conclusively for sure as there is no algo to solo mine, and even if it had I would need luck to push through blocks solo. Unfortunately it seems to be a pool in decline, with problems removed rather than resolved and an admin who no longer seems to provide support. But, considering a bit of luck variance, the percent share figures seem to be correct. I might be on a bit of a lucky run, but even with the additional 2% BTC fee, profitability appears to be outstripping zpool by quite a margin. At least on this flavour of yaamp, the percent share calculations look more reasonable.

It looks like tpruvots reference yaamp pool is here:
http://yiimp.ccminer.org/
BTC payment exchange is disabled on this pool, and it looks more like a test pool than a production pool. Plenty of opportunity for someone to solo mine an algo if they have the hash power to push blocks through. Then we can determine if the 80% cap issue is present in the reference version.

If not then there is a problem in zpools customisation of the pool. Perhaps a trigger on the share table not behaving as it should. It does look like it may be effecting out profitability though. I would like to see this issue resolved as the active development and support of this pool should make it one of the best pools to use.

[patinencomun]

Hello,
for one of my rigs I have a constant message

 Waiting for work to be available from pools.
 Work available from pools, resuming.
 Waiting for work to be available from pools.
 Work available from pools, resuming.

between any accepted share.
Any suggestion to fix that?

Thank you in advance.

Can't say I've seen this error before. Are you setting your own diff?

No, I have to setting my own diff?
I have also the problem mentioned by tolazy user https://bitcointalk.org/index.php?topic=632503.msg13862922#msg13862922
random stops with no error.

Now my temps are low, set lower voltage and engine frequency. Still same results, message "waiting for work..." and random stops with no error.

[AngryDwarf]

Hello,
for one of my rigs I have a constant message

 Waiting for work to be available from pools.
 Work available from pools, resuming.
 Waiting for work to be available from pools.
 Work available from pools, resuming.

between any accepted share.
Any suggestion to fix that?

Thank you in advance.

Can't say I've seen this error before. Are you setting your own diff?

No, I have to setting my own diff?
I have also the problem mentioned by tolazy user https://bitcointalk.org/index.php?topic=632503.msg13862922#msg13862922
random stops with no error.

Now my temps are low, set lower voltage and engine frequency. Still same results, message "waiting for work..." and random stops with no error.

I use sgminer 5.2.1 and rarely experience issues on the multi algo ports. Only sha256 port is giving periodic drop outs and share resets for me. Which version of sgminer are you using?

EDIT: I assume you are using 5.1.0-optimised. I went from 5.1.1 to 5.2.1 and got a considerable X11 performance boost, so I would try that. It's a NiceHash fork of sgminer.

[MeteoImpact]

Meanwhile, over on hashpower.co, we don't seem to have this 80% share limit problem. I can't say conclusively for sure as there is no algo to solo mine, and even if it had I would need luck to push through blocks solo. Unfortunately it seems to be a pool in decline, with problems removed rather than resolved and an admin who no longer seems to provide support. But, considering a bit of luck variance, the percent share figures seem to be correct. I might be on a bit of a lucky run, but even with the additional 2% BTC fee, profitability appears to be outstripping zpool by quite a margin. At least on this flavour of yaamp, the percent share calculations look more reasonable.

Yeah, hashpower has been spotty when it comes to pool management, but most of the time (aside from when stuff breaks) the returns tend to meet or exceed my conservative estimations, so if there is a problem with their calculations, it's fairly negligible. While it was alive, ffpool seemed fine in this respect as well. zpool on the other hand seems to miss its targets even after a significant reduction in my estimates on its returns, probably mostly due to the bug with shares.

[jkminkov]

what types are those cards, it seems they throttle, set temp target to 75C and see how it goes.

[patinencomun]

Ok, now seems stable mining with sgminer5.1.0_optimized (nicehash fork) (6 hours, still running)
sgminer.conf (rig 1)

{
"pools" : [
   {
      "name" : "Z pool BTC X11",
      "url" : "stratum+tcp://mine.zpool.ca:3533",
      ...
   }
]
,
"intensity" : "20,17",
"worksize" : "64,64",
"gpu-threads" : "1,1",
"gpu-fan" : "34,32",
"gpu-powertune" : "15,15",
"kernel" : "x11mod",
"thread-concurrency" : "0,0",
"gpu-powertune" : "20,20",
"temp-target"   : "75,75",
"temp-cutoff"   : "85,85",
"temp-overheat"   : "88,88",
"api-allow": "W:127.0.0.1",
"api-listen": true,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "1",
"failover-only": true,
"failover-switch-delay" : "300",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"hamsi-expand-big": "4",
"log": "5",
"no-pool-disable" : true,
"no-client-reconnect": true,
"queue" : "0",
"scan-time" : "1",
"tcp-keepalive" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}

Underclocked cards:
Rig 1:
0 280x 10.4MH
1 7950 7.36MH

Rig 2:
0 7950 7.4MH
1 7970 (master 7990) 9MH
2 7970 (slave 7990) 9MH

Seems better use intensity instead of xIntensity.
Use latest drivers.
Bios mod for underclocking.
Do not mix graphic cards in same pc (2x7790 with 7950 dont work...)

Still some random message
" Waiting for work to be available from pools.
 Work available from pools, resuming."


EDIT
After 9 hours Rig 2 stops without any error / change from I=18 to I=17 at 7950, change fan settings as sugested by jkminkov restart again
Rig 1 10 hours and still up.

EDIT 2
Changed "tcp-keepalive" : "30" to "tcp-keepalive" : "60" and restarted both rigs.

[jkminkov]

edit: "gpu-fan" : "34-100,32-100",
add: "auto-fan" : true,

[tmpwhore]

Tried usuing this pool today for the first time and I run my machines through MRR, but I kept losing workers and hashrate. Is that normal? Was today a bad day for the pool? I had about 30TH put on it

We're still looking into an issue where sometimes the stratum server will reset if there was not a timely response from a wallet.

Thanks, that's understandable. I will be keeping and eye on it and hope it all works out well. Im user " 1rkBkzmKfZ11wUBH3L2JGv1rRVPL6gPtD "

Thats probably what I was experiencing. On the SHA256 protocol occasionally it will just dump everyone and when the miners re-connect they are stuck at 64 difficulty. I'll throw one of my s7's on there again and see if it's resolved.
'

Edit: It's not, dumps everyone then gets stuck at 64 difficulty. If you reconnect it manually it goes back to normal. This is with extronance or without. I guess I'll have to manually mine to get any benefit out of the pool. This is a potential deal breaker for those on SHA256. If you get the bugs worked out you'll have one awesome pool. Maybe increase the timeout time on the stratum server to the wallet? It does this every couple of hours. Next time it goes tits up, I'll leave it for a good 10 min and see if it corrects itself.