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

[OverP]

who wonna mine sibcoin with,let's make it profitable again!!

[1715217269]

1715217269

[1715217269]

1715217269

[1715217269]

1715217269

[1715217269]

1715217269

[1715217269]

1715217269

[tbonetony]

i am a newbie to zpool. just curious if zpool supports worker id appended to wallet address? such as [walelt_addr].worker1

[joblo]

i am a newbie to zpool. just curious if zpool supports worker id appended to wallet address? such as [walelt_addr].worker1

Use the password "-p worker1".

[Mario241077]

#OrBitcoinLove https://bitcointalk.org/index.php?topic=586674.0 Hard fork coming!(Block # 2 million, ETA 27-Sep-2016) update clients to v1.6.0.0 in time!

https://github.com/ghostlander/Orbitcoin/releases/

integration of BIP65 and BIP 66
Orbitcoin v1.6.0.0 is ready for release. BIP65 and BIP66 will be mandatory after the hard fork for all blocks and payments (BIP66 is forced on mempool only right now by v1.5.1.x clients).
+ index rebuilder after crash of pc system
+ now including the official Abe powered block explorer. Although most people should be fine with the in-wallet block explorer. It's much faster.

[joblo]

All the fee's in the config are set at 2

https://github.com/tpruvot/yiimp/blob/next/web/serverconfig.sample.php#L18-L20

I do mention on the main page:

You can also use any valid wallet address from any of the coins we mine. This feature has had minimal testing so use at your own risk

But I'm not really sure why I did that, I've had it there since the beginning...

doesn't matter, the same with btc, ~25%:

The problem occurs regardless of the payout coin and fees are not the issue.

I'm trying to understand the code and it looks like it stores all block results in the SQL database. That should make it possible to
query the database to get all blocks for a coin/user to check the data. The coin's price (BTC))  is also stored. I'm not sure if it is used
when the payout coin is the same as the mined block.

My point is it can help narrow the problem definition some more. The problem exists even if the mined coin is the same as the payout coin
so it exists in code that is common with a different payout coin. Since a block of the same coin as payout doesn't require calculating an
estimate it can bypass all the estimate code and simply copy the coin amount as the payout estimate. If it does this the estimate code
is eliminated as the source of the problem. If the estimate is calculated regardless if the mined coin is the same as the payout the estimate
code is still suspect.

Unnecessary estimate calculations by themselves may introduce some error but in no way would it be so high unless there is a bug.

The key data points at this time is verifying the share percentage of a block at generation time, to ensure all users add up to 100%.
The second critical data point is finding where the value of a block suddenly decreases by ~20%. This is after the coin is "cleared" but
before it is displayed in the balance.

[felixbrucker]

hmmm, why should i believe that public code is used as it is ?

because you *trust* those who say it


so basically all crackfoo has to do is look in these sql tables and check the values, right?

[scryptr]

hmmm, why should i believe that public code is used as it is ?

because you *trust* those who say it


so basically all crackfoo has to do is look in these sql tables and check the values, right?

i wouldn't post all those test results if there were any trust left.
he had several months to "look in these sql tables"

THE POOL OPERATOR IS NOT A DEVELOPER OF CODE--

He owns and operates the pool.  He is responsible for the operation and the results of the pool's operation.  Whether or not he understands the code within the pool, the results are his responsibilty.  It is sort of like driving a car, and not knowing the brake from the clutch, perhaps.

Unless, a hacker installed maicious code.  I dunno, I could download and try to actually set up a YIIMP pool for myself.       --scryptr

[felixbrucker]

Has anybody verified it only happens on zpool and does not happen on tpruvots ccminer yiimp pool?

Afaik they have most code in common

[scryptr]

Has anybody verified it only happens on zpool and does not happen on tpruvots ccminer yiimp pool?

Afaik they have most code in common

I MINE AT TPRUVOT'S POOL--

But he has it set up to NOT auto-switch, or auto-exchange.  The whole exciting thing about YAAMP/YIIMP is auto-switching for nVidia cards.  If Tpruvot's pool says you have 21 coins, you get 21 coins.  Your percentage of the take is dependant on hash rate.  Some not-so-popular coins are like solo-mining for a 2% fee.  You just mine, and if the net difficulty is really low, you get 98% of every block that you solve.  As for "time on the books", two months (or so) after I stopped mining Yescrypt for Global Boost-Y (BSTY), I received about 2/3 of a block because my residual share contribution was still valid when a new miner solved a block in my absence.

You only get paid in the coin that you mine at "yiimp.ccminer.org".  It usually runs well.  Maybe the code should be inspected where the percent of total share data is stored.  Whether the market value fluctuated over the time I stopped mining BSTY was not an issue.  My share contribution was still valid without decay.  The other miner could have started mining on the same day that I stopped, and my share would have been the same.       --scryptr

[joblo]

Has anybody verified it only happens on zpool and does not happen on tpruvots ccminer yiimp pool?

Afaik they have most code in common

I MINE AT TPRUVOT'S POOL--

But he has it set up to NOT auto-switch, or auto-exchange.  The whole exciting thing about YAAMP/YIIMP is auto-switching for nVidia cards.  If Tpruvot's pool says you have 21 coins, you get 21 coins.  Your percentage of the take is dependant on hash rate.  Some not-so-popular coins are like solo-mining for a 2% fee.  You just mine, and if the net difficulty is really low, you get 98% of every block that you solve.  As for "time on the books", two months (or so) after I stopped mining Yescrypt for Global Boost-Y (BSTY), I received about 2/3 of a block because my residual share contribution was still valid when a new miner solved a block in my absence.

You only get paid in the coin that you mine at "yiimp.ccminer.org".  It usually runs well.  Maybe the code should be inspected where the percent of total share data is stored.  Whether the market value fluctuated over the time I stopped mining BSTY was not an issue.  My share contribution was still valid without decay.  The other miner could have started mining on the same day that I stopped, and my share would have been the same.       --scryptr

Everything you said is correct and I would like to add that the loss also occurs on zpool when mining the same coin as payout. Between the
time it's status changes to "cleared" in the last 50 list to being transferred from the wallet's "pending" to "balance" it drops in value. If no
exchange is required it should be identical to yiimp. But apparently it isn't.

[Spiffy_1]

I don't know how easy this suggestion would be to impliment, but when we click on our wallet, and then show details, would it be possible to sort the coins based on the value of btc we will receive?  its a minor issue, but would be a nice one to track wether its worth mining a certain algo or not.  Thanks again for running this pool.

[berron]

If anyone is interested, new simplified scrypt based in JK's one for Nvidia 960 cards. Hashrates calculated with slight overclocking to the card. Displayed version (-V) of the miners used is this:

ccminer1.8
ccminer v1.8
pthreads static 2, 9, 1, 0
libcurl/7.38.0 OpenSSL/1.0.1i zlib/1.2.8

ccminer181
ccminer v1.8.1
pthreads static 2, 9, 1, 0
libcurl/7.38.0 OpenSSL/1.0.1i zlib/1.2.8

ccminer176
ccminer v1.7.6
pthreads static 2, 9, 1, 0
libcurl/7.38.0 OpenSSL/1.0.1i zlib/1.2.8

ccminer1580
ccminer v1.5.80-git(SP-MOD)
pthreads static 2, 9, 1, 0
libcurl/7.40.0
Attention, this one displays all the help menu after the version when parameter -V used.

@echo off
SETLOCAL EnableExtensions
PATH=C:\Minado
SET ADDY=33R52ceGSXxWUbZvW7iVsNA3Wj2keoCfCM
SET ID=960,
SET A=ccminer18.exe
SET B=ccminer181.exe
SET C=ccminer176.exe
SET D=ccminer1580.exe
SET POOL1=stratum+tcp://
SET POOL2=.mine.zpool.ca
SET COUNTER=0
SET A16=skein
SET A05=lyra2v2
SET A06=neoscrypt
SET A14=x17
SET A18=lbry
SET A20=x11evo
SET A19=myr-gr
COLOR 0B
:start
SET /A COUNTER=%COUNTER%+1
SET PASS=%ID%,c=BTC,skein=186,lyra2v2=15.0,neoscrypt=0.405,x17=3.32,lbry=96.0,x11evo=4.89,myr-gr=27.1,stats
ECHO Starting miner processes....
ECHO off
%D% -r 0 -i 20.5 -a %A16% -o %POOL1%%A16%%POOL2%:4933 -u %ADDY% -p %PASS%,d=0.5 -c ccminer180.conf
%A% -r 0 -i 19.5 -a %A05% -o %POOL1%%A05%%POOL2%:4533 -u %ADDY% -p %PASS%,d=8 -c ccminer180.conf
%A% -r 0 -a %A06% -o %POOL1%%A06%%POOL2%:4233 -u %ADDY% -p %PASS%,d=72 -c ccminer180.conf
%C% -r 0 -i 19.5 -a %A14% -o %POOL1%%A14%%POOL2%:3737 -u %ADDY% -p %PASS%,d=0.008 -c ccminer180.conf
%B% -r 0 -a %A18% -o %POOL1%%A18%%POOL2%:3334 -u %ADDY% -p %PASS%,d=52 -c ccminer180.conf
%A% -r 0 -i 20 -a %A20% -o %POOL1%%A20%%POOL2%:3553 -u %ADDY% -p %PASS%,d=0.012 -c ccminer180.conf
%A% -r 0 -i 19 -a %A19% -o %POOL1%%A19%%POOL2%:5433 -u %ADDY% -p %PASS%,d=0.06 -c ccminer180.conf
ECHO -------------------------------------------------------------------------------
ECHO Total number of round robins:  %COUNTER%
GOTO start

Remember to replace your PATH to the path in which you have your mining software installed. Only algos with estimate profit consistently over 125000 sat/day has been added. Blake2s could be also included, maybe in some days when I found time to get a good hashrate read from it. Decred is not included because the associated impossibility of control diff of the algos due to the (d)ecred bug.

If you find faster miners, better intensity parameters or any of that, please share. Ah, my afterburner conf is +100 core clock, +125 memory clock. I'm playing with it for the moment (not very concerned about burning an already old card) so if you know, you think you know a better conf, please share.

Salute

[denravonska]

Does yiimp's earning estimation match that of the exchanges? It should be trivial to check if you have access to the DB, and it'll probably help locating where things go haywire.

[denravonska]

Does yiimp's earning estimation match that of the exchanges? It should be trivial to check if you have access to the DB, and it'll probably help locating where things go haywire.

there's no question about exchanges and estimates anymore.
you mine a coin with payout to same coin on a single coin pool and it takes 20% (or more).
i doubt the op needs any help here

Aaaah, true. Didn't think about that. I've been absent from this thread for too long

Edit: If it was my pool I would start looking here: https://github.com/tpruvot/yiimp/blob/35220977ef209ced403f1c4c82efb65561cc9493/web/yaamp/core/backend/payment.php#L44

[c_demian]

Are you sure it's taken by the pool? There may be other losses...
And if the difficulty is oscillating then earnings will be less...

[c_demian]

may be residual shares... ?

[crackfoo]

may be residual shares... ?

maybe anything you want,
i'm no longer here, last run was c11 test today,
it shows the same and this is just boring

Where did you go?

take it elsewhere please, this isn't your discussion thread

[joblo]

may be residual shares... ?

maybe anything you want,
i'm no longer here, last run was c11 test today,
it shows the same and this is just boring

Where did you go?

Anywhere. I reduced zpool estimates by 20% in my profit switching and rarely switch to zpool
and my daily revenue has increased. I've now completely removed zpool from my rotation.

I was willing to give the pool op the benefit of the doubt but his denial of the problem suggests
something more sinister than simple ignorance. The losses are real and must be going somewhere.

I spent many hours pouring though unfamiliar code trying to figure out what's going on but the pool op
won't even acknowledge there is a problem.

I'm done.
 

[joblo]

Edit: If it was my pool I would start looking here: https://github.com/tpruvot/yiimp/blob/35220977ef209ced403f1c4c82efb65561cc9493/web/yaamp/core/backend/payment.php#L44

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.

[denravonska]

Edit: If it was my pool I would start looking here: https://github.com/tpruvot/yiimp/blob/35220977ef209ced403f1c4c82efb65561cc9493/web/yaamp/core/backend/payment.php#L44

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.

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