Topic: █▓▒░-< [ZPOOL.CA][BTC Multipool] The miners multipool >-░▒▓█ Paid 925+ BTC - page 5. (Read 217698 times)

Surely you no what you are doing by now. Nobody cares if you are taking 2% fee or 22% fee, just state it on the home page. What ever it is, you are getting plenty of money coming in so you should know how the pool works and be able to diagnose problems when they arise (or at least work with those that do).

You're missing it? Like... you love it and can't sleep without it?

If you need help, you can create support tickets. support.zpool.ca. But I can't help with your feelings from missing links.

My pools have been running 3-4 years now, call it what you will.

You forgot to add that there is a support link now... and c11 & myr-gr are gone.

If you're not having a technical issue, there's no need to post.

I'm missing a forum link on zpool site.

is this going to be like scam or what?

Zpool profit estimates are way off! It seems only for sha256 coins!

Yiimp fork:

https://github.com/crackfoo/yiimp

The link to this forum has been removed from zpool.ca

It's probably a case of querying the earnings table, but I don't want to drive myself crazy looking at the code again. It probably does add up to 100%. So like the 80% share issue, it is either a case of fixing it in a few more places, or there is an address which likes to collect a rather predictable 20%.

Wouldn't it be simple to just query the database to get every user's share of a particular block and add them up? The percentage should
add up to 100 and the value should match the block reward.

I think it is the case that the pools fee is accumulated in the BTC hot wallet, and then sent to a BTC cold wallet once a threshold is reached, but it is a long time since I took a look at this. So yes, it will have gone through an exchange. The other coins hot wallets just hold a reserve for people who want to be paid in that coin. That is how I think it works.

EDIT: So basically all coins in a wallet above the reserve level are sent to exchange for BTC.

It is essentially a calculation based on difficulty, last block reward, and best market bid price (although the latter was manipulated from what I can best call a market price smoothing function that I don't agree with). Once the coin has matured, obviously the market price may have moved. But the best market price might not be the exchange where the coin is sent. A preferred market route might be set up, or it might send it to the big exchanges (bittrex, poloniex) in preference to the exchange with the best market price.

EDIT: Also the exchange with the best market price might not have the market depth to fill a large order at that price, so the price attained may be lower.

crackfoo, I have a way to help you try and figure it out based on what the guys are piecing together...

disable a single coin port, such as sib... what was used in the example.  Perfect choice because it's a solo port, and rarely used compared to the rest.

change the port and don't advertise it.   Have only one person/wallet mine to it for one to five full payout cycles.

From there it should be easy enough to track down what's going where as far as the sql logs they speak of (I never got much into databasing, I was more interested back then on the meat of programming code).  All records would be for the same account, I would assume that the server would keep a record of the wallet that the generated coins appear in (is it static?) and it could be verified in the host coin's blockchain to verify the wallet is going empty and to where (should only be two payouts, one to wallet of miner, one to pool/sent to exchange yes?  Is there a way for you to verify the exchange wallet matches the one in the blockchain).  Just save a copy of the logs/database at that moment and you can spend more time studying a static dataset.

Also dont forget to include/count TX fees when applicable.

Also: I am wondering, does the pool's 2% go to the exchange and paid out to BTC the same as the rest of us?  or are you holding your remains in the hot-wallets that generated coins are created in and selling later on exchange?  I can't help but wonder if a code snippet in there could be changing a value that's only supposed to be read....

This came to mind... so I thought I would share.

When you actually think about what needs to happen here... its no small task... not in the slightest....

yes it would be up to crackfoo to check the logs.. it would be time consuming but possible to go through all the users and add up the payouts to make sure the block is 100% accounted for..

there could be something hidden in the code he doesnt even know about sending a small amount of coins to someone..

I don't promote any specific pools, but most have threads in tis forum.

I would like to know how the real time profit estimate is calculated...

I was going to write a brainstorming post trying to dig further into the mystery, but what's the point? The operator is apparently not interested.

@joblo, please drop me a PM for a hint where I can point my miners. I cannot PM you since I cannot see the captcha images.

I agree, I've given it my best shot and narrowed the problem as you quoted above. It looks like the user data for each block
is stored in SQL and the payout data is taken from SQL. They should match. The next step seems obvious although I've stated
it many times already.

Yiimp vs yaamp might be part of the problem. The original yaamp supported auto-exchange of mined coins but when TPruvot forked it
he dropped auto-exchange for his yiimp pool. Somewhere along the way Zpool came out and supported auto-exchange using
the yiimp fork.

Although the problem appears not to be related to exchange (ie the loss also occurs when mining same coin as payout)
it is possible the exchange code is still being run and performning a null-exchange of some kind when calculating the
balance. But that's just speculation.

Unfortunately, I make the same observation. I rented SHA256 Miner for 0.0013 and got back less than my investment, despite higher profitability

So checkt it please, i like your pool, but there is something wrong

With this much information it should be a matter of 1-2 hours to track down the 20%. Is zpool running yiimp or yaamp?

The error first appears in the balance, this is before the payment. It is correct when a block is "cleared" but the balance
is short. Then the payment just pays out the already short balance.