Author

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

legendary
Activity: 3486
Merit: 1126
Might be worth looking at adding decred quick, just launched on the blake256 algo.

It's a blake256 algo with custom headers so not the same as the others. Also, it's not a BTC compatible wallet and takes quite a bit of coding to get into the backend.

Ah, I assume that also makes BCN derived coins difficult to add too?

yes that right, for now anyway.
sr. member
Activity: 476
Merit: 501
Might be worth looking at adding decred quick, just launched on the blake256 algo.

It's a blake256 algo with custom headers so not the same as the others. Also, it's not a BTC compatible wallet and takes quite a bit of coding to get into the backend.

Ah, I assume that also makes BCN derived coins difficult to add too?
legendary
Activity: 3486
Merit: 1126
Might be worth looking at adding decred quick, just launched on the blake256 algo.

It's a blake256 algo with custom headers so not the same as the others. Also, it's not a BTC compatible wallet and takes quite a bit of coding to get into the backend.

sr. member
Activity: 476
Merit: 501
Might be worth looking at adding decred quick, just launched on the blake256 algo.
newbie
Activity: 4
Merit: 0
legendary
Activity: 3486
Merit: 1126
X15 issue again...

I use the algo switching option with my gpu and don't understand why the worker shuts down completely if one algo has issues.
It should simply switch to the next profitable one, but it just stops mining completely until the dead algo returns.
That's not very good at all!

djoser.

This should be fixed now.

Hello crackfoo,

Sorry, but it seems not to be fixed.
Exactly the same issue again right now.
X15 disappears from pool stats and miner stops working.

Cheers, djoser.

hrmm ok. It did remove the x15 from api properly:

{"sha256": {"name": "sha256", "port": 3333, "coins": 14, "fees": 2, "hashrate": 33496182008846, "workers": 107, "lastbloc": 14123, "timesincelast": 100, "estimate_current": 0.00000529, "estimate_last24h": 0.00000561, "actual_last24h": 0.0041, "rental_current": 0.00666071}, "scrypt": {"name": "scrypt", "port": 3433, "coins": 20, "fees": 2, "hashrate": 1464838953, "workers": 82, "lastbloc": 1846761, "timesincelast": 85, "estimate_current": 0.00011482, "estimate_last24h": 0.00011483, "actual_last24h": 0.0924, "rental_current": 0.15102283}, "lyra2v2": {"name": "lyra2v2", "port": 4533, "coins": 5, "fees": 2, "hashrate": 57378542, "workers": 21, "lastbloc": 129737, "timesincelast": 440, "estimate_current": 0.00020055, "estimate_last24h": 0.00018627, "actual_last24h": 0.3092, "rental_current": 0.25533888}, "neoscrypt": {"name": "neoscrypt", "port": 4233, "coins": 4, "fees": 2, "hashrate": 4159291, "workers": 78, "lastbloc": 418728, "timesincelast": 298, "estimate_current": 0.00304056, "estimate_last24h": 0.00301735, "actual_last24h": 3.0825, "rental_current": 4.10643842}, "quark": {"name": "quark", "port": 4033, "coins": 6, "fees": 2, "hashrate": 141206613, "workers": 14, "lastbloc": 249956, "timesincelast": 164, "estimate_current": 0.00017863, "estimate_last24h": 0.00017330, "actual_last24h": 0.1154, "rental_current": 0.20224336}, "qubit": {"name": "qubit", "port": 4733, "coins": 4, "fees": 2, "hashrate": 24247896, "workers": 16, "lastbloc": 41878, "timesincelast": 653, "estimate_current": 0.00013865, "estimate_last24h": 0.00019881, "actual_last24h": 0.1866, "rental_current": 0.18973258}, "c11": {"name": "c11", "port": 3573, "coins": 2, "fees": 2, "hashrate": 19879170, "workers": 6, "lastbloc": 675100, "timesincelast": 177, "estimate_current": 0.00058914, "estimate_last24h": 0.00050852, "actual_last24h": 0.2105, "rental_current": 0.74885460}, "x11": {"name": "x11", "port": 3533, "coins": 11, "fees": 2, "hashrate": 467468364, "workers": 127, "lastbloc": 89726, "timesincelast": 130, "estimate_current": 0.00012794, "estimate_last24h": 0.00018134, "actual_last24h": 0.1462, "rental_current": 0.18369703}, "x13": {"name": "x13", "port": 3633, "coins": 3, "fees": 2, "hashrate": 283923223, "workers": 35, "lastbloc": 770627, "timesincelast": 171, "estimate_current": 0.00027667, "estimate_last24h": 0.00034950, "actual_last24h": 0.3412, "rental_current": 0.39964410}, "groestl": {"name": "groestl", "port": 5333, "coins": 1, "fees": 2, "hashrate": 0, "workers": 0, "lastbloc": 960491, "timesincelast": 5194, "estimate_current": 0.00007836, "estimate_last24h": 0.00006379, "actual_last24h": 0.1501, "rental_current": 0.08795759}, "myr-gr": {"name": "myr-gr", "port": 5433, "coins": 3, "fees": 2, "hashrate": 0, "workers": 0, "lastbloc": 582401, "timesincelast": 35381, "estimate_current": 0.00004098, "estimate_last24h": 0.00006489, "actual_last24h": 0.0118, "rental_current": 0.05007796}, "yescrypt": {"name": "yescrypt", "port": 6233, "coins": 1, "fees": 2, "hashrate": 197194, "workers": 62, "lastbloc": 70815, "timesincelast": 285, "estimate_current": 0.03111918, "estimate_last24h": 0.02479419, "actual_last24h": 25.2836, "rental_current": 42.41434436}}

Will look into it more again.
member
Activity: 122
Merit: 16
X15 issue again...

I use the algo switching option with my gpu and don't understand why the worker shuts down completely if one algo has issues.
It should simply switch to the next profitable one, but it just stops mining completely until the dead algo returns.
That's not very good at all!

djoser.

This should be fixed now.

Hello crackfoo,

Sorry, but it seems not to be fixed.
Exactly the same issue again right now.
X15 disappears from pool stats and miner stops working.

Cheers, djoser.
legendary
Activity: 1470
Merit: 1114
Hi Crackfoo,

Since you have been so active adding new algos and coins I'm surprised cryptonight hasn't hit your radar. Any particular
reason? I've got a shiny new cpu miner I'd like to put to work.
legendary
Activity: 3486
Merit: 1126
Looks like the rental has been temporarily disabled.

But yes, I was also getting lots of extranonce change requests and delays getting work on algos with active rentals.

I'm away all weekend and can't look into it right now. Rentals was the only changed recently so we disabled it for the time being. Seems it was the problem.
sr. member
Activity: 476
Merit: 501
Looks like the rental has been temporarily disabled.

But yes, I was also getting lots of extranonce change requests and delays getting work on algos with active rentals.
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
Same with X11 mining ... no response

Mine hasnt switched to X11;  been popping between qubit, X13 and X15 mostly.   X15 seems to be working fine;  X13 is all crazy to hell;  mostly no response from stratum or a million nonce changes in 2 seconds time.

scrypt seems to have come back;  and the other issue with scrypt is resolved;  the stratum was sending work restarts faster than my diff level would submit a share. (low diff coin most likely).

sha256 dropped off for a moment but came back as well.

But for sure;  something is foul with X13.   every time my pc switches to it theres barely any accepted shares.


Crackfoo:  is there any way we can "opt out" of rental?  such as a password flag like r=yes/no ?
member
Activity: 92
Merit: 10
Same with X11 mining ... no response
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
anyone else being sent a million nonce change requests from x13?  And Scrypt seemed to stop sending my pc data...
newbie
Activity: 34
Merit: 0
Well today I keep getting server no response after a few mins of running. So I shut my miners off untill the issue is fixed  Undecided

Sucks. Although, glad to hear it's not just me.
newbie
Activity: 53
Merit: 0
Well today I keep getting server no response after a few mins of running. So I shut my miners off untill the issue is fixed  Undecided
legendary
Activity: 1470
Merit: 1114

I have a nagging suspicion it has to do with the major difference between pool hashrate % and share reward % that I can see on my zpool wallet page.

I expected to loose out from the start;  so I wasn't disappointed if I did loose coin;  its not that much of a loss to help the pool try and see if there truly is an issue with the calculations somewhere.

I just dont have any way else to explain away the difference between pool hashrate % (on left side where total share amount from each algo is displayed), and the share value of the coins on the right pane where it lists found blocks and credit for them.


I had difficulty seeing the small text but it looks like you were credited the same percentage as expected. So I guess
the question really is is what happened between then and you were paid. Alot can happen.

Luck can affect the profitability a lot. It works both ways bbut most people don't complain when it works in their
favour.

orphaned block occur and are a direct loss.

Time usually works against profit for many reasons. Coins are mostly mined when they are most profitable. it's
almost certain they will be lower by the time they mature and are exchanged. Profit switching and autoiexchange
exacerbate this effect with their dramatic and rapid shifts in hash volume. The resulting flood of new coins on the
exchanges also pushes prices down. maing mmoney with rentals is not an easy game. The only time there is any
kind of assurance of profit is when the rental has a distinct advantage with nore efficient mining equipment and
software and the fees are less than the advantage leaving a guaranteed profit for both.

I don't know if ay of this will help but ity's what i've observed. YMMV
full member
Activity: 232
Merit: 100
yes;  but when all coins/shares are coming out under your pool hashrate....   there is a missing percentage in the end.

100% in == 100% out in the end.

it's consistently lower;  not varying.

If I am putting half of the pools hashrate into mining the coins;  I should get half minus the 2% no matter what coins are mined.

I understand it will give more or less hashrate between coins while mining;  but in that case I should have at least one coin that has a higher percentage than the others.

Instead;  (guessing) my coin reward varies on the total pool hashrate up on the top right pane (not pictured);  not my input hashrate on left.

If I can see what parts of my hashrate are pointed towards what coins; and a percentage thereof;  it would be easier to track down where that percentage is missing from.

very very easy ... XD
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
yes;  but when all coins/shares are coming out under your pool hashrate....   there is a missing percentage in the end.

100% in == 100% out in the end.

it's consistently lower;  not varying.

If I am putting half of the pools hashrate into mining the coins;  I should get half minus the 2% no matter what coins are mined.

I understand it will give more or less hashrate between coins while mining;  but in that case I should have at least one coin that has a higher percentage than the others.

Instead;  (guessing) my coin reward varies on the total pool hashrate up on the top right pane (not pictured);  not my input hashrate on left.

If I can see what parts of my hashrate are pointed towards what coins; and a percentage thereof;  it would be easier to track down where that percentage is missing from.
full member
Activity: 232
Merit: 100
for all my rentals they have usually rented at 0.0044-0.0048 or so;  spending ~26mBTC.  Generating 19-21mBTC after the rental is up....  which is close to the amount the share reports are off by;   and thats also with an extra S3 running that consistently generated 2.2mBTC/day.

The hashrate reporting is almost nominal;  within a few percent; so I know those per-share hashrate calcs are good =)
sorry you pay 26 mBTC for earn 19-21?

yes.

Each time I calculated based on profitability reports from the pool through the day;  the estimates should have been to earn 1-3mBTC after 24 hours.    They obviously kept falling way short.   Even on a days when rental was a lot cheaper than the previous day.

I have a nagging suspicion it has to do with the major difference between pool hashrate % and share reward % that I can see on my zpool wallet page.

I expected to loose out from the start;  so I wasn't disappointed if I did loose coin;  its not that much of a loss to help the pool try and see if there truly is an issue with the calculations somewhere.

I just dont have any way else to explain away the difference between pool hashrate % (on left side where total share amount from each algo is displayed), and the share value of the coins on the right pane where it lists found blocks and credit for them.

Example:

ah ok
however the shares aren't the % of the new block
legendary
Activity: 1848
Merit: 1166
My AR-15 ID's itself as a toaster. Want breakfast?
for all my rentals they have usually rented at 0.0044-0.0048 or so;  spending ~26mBTC.  Generating 19-21mBTC after the rental is up....  which is close to the amount the share reports are off by;   and thats also with an extra S3 running that consistently generated 2.2mBTC/day.

The hashrate reporting is almost nominal;  within a few percent; so I know those per-share hashrate calcs are good =)
sorry you pay 26 mBTC for earn 19-21?

yes.

Each time I calculated based on profitability reports from the pool through the day;  the estimates should have been to earn 1-3mBTC after 24 hours.    They obviously kept falling way short.   Even on a days when rental was a lot cheaper than the previous day.

I have a nagging suspicion it has to do with the major difference between pool hashrate % and share reward % that I can see on my zpool wallet page.

I expected to loose out from the start;  so I wasn't disappointed if I did loose coin;  its not that much of a loss to help the pool try and see if there truly is an issue with the calculations somewhere.

I just dont have any way else to explain away the difference between pool hashrate % (on left side where total share amount from each algo is displayed), and the share value of the coins on the right pane where it lists found blocks and credit for them.

Example:
Jump to: