[POOL] YAAMP.COM multipool multialgo profit switch with exchange

[Txslady]

I see how to buy hashing power but how do you sell it?  I am setup to autoswitch to the most profitable and would like to add this to my options.

[1713271439]

1713271439

[1713271439]

1713271439

[1713271439]

1713271439

[1713271439]

1713271439

[MeteoImpact]

I see how to buy hashing power but how do you sell it?  I am setup to autoswitch to the most profitable and would like to add this to my options.

I assume that renting just functions like another coin as far as miners are concerned. Hashpower seems to get routed to rentals (which have to pay competitive rates) the same way it gets distributed across coins. No changes should be required on the miners' end as far as I'm aware, except that the rental page makes the point that miners need to support extranonce subscribe to be used in rentals (though you'd still end up getting paid for other people's work on the rentals anyhow just from mining on that algo).

Note: I'm just another miner and this is all speculation based on how it appears to be working, but I'm quite certain that YAAMP's approach to rentals requires no extra configuration on the seller's end.

[yaamp]

I see how to buy hashing power but how do you sell it?  I am setup to autoswitch to the most profitable and would like to add this to my options.

I assume that renting just functions like another coin as far as miners are concerned. Hashpower seems to get routed to rentals (which have to pay competitive rates) the same way it gets distributed across coins. No changes should be required on the miners' end as far as I'm aware, except that the rental page makes the point that miners need to support extranonce subscribe to be used in rentals (though you'd still end up getting paid for other people's work on the rentals anyhow just from mining on that algo).

Note: I'm just another miner and this is all speculation based on how it appears to be working, but I'm quite certain that YAAMP's approach to rentals requires no extra configuration on the seller's end.

exact!

we encourage everyone to get a miner that supports extranonce.subscribe, but for now, you get same results without.

[rednoW]

Hello yaamp,
all coins in all protocols looks like immature for last two hours. What happends?
Jiri

again  (((

[12gaFacelift]

Look like the pool is offline.

[Zels]

Look like the pool is offline.

No, everythings working here, hashing and website up for me

[12gaFacelift]

just try to refresh the webpage....maybe its only here but big doubt about that.

[Zels]

it's only you everythings work ^^

http://www.downforeveryoneorjustme.com/http://yaamp.com/

[MeteoImpact]

It's not a major issue, but would it at some point be possible to modify the front-end such that (at least) the api page doesn't go down for a bit when payouts are being made? I realise that the stratum servers stay up during these periods, but since my miners base their decisions on the api, they always end up switching off the pool when they can't get their numbers. Granted, this only happens for ~20 minutes a day, but even so, it'd be nice if my miners could just stay on YAAMP instead of running off to another pool offering half the profitability.

[MeteoImpact]

Hmm, a bit bigger issue here. Not sure if it used to do this or not, but it seems like the pool is getting, "stuck", on profitability estimates for extended periods of time, which causes it to report numbers that can be very inaccurate.


Here's a screenshot of the x15 pool reporting rather old and inaccurate numbers for KoboCoin (sorry it's so large ). The pool at this point was reporting the difficulty of KoboCoin a whole 26 blocks--a good 8 minutes--behind the last block mined by the pool. In those 26 blocks, the mining difficulty had risen to nearly 3x what the pool was estimating--you can see how this would make the profitability estimate more than a little inaccurate.

Though I hadn't been paying it particularly close attention in the past, I get the impression that the pool didn't used to take this long to re-target; could some recent change perhaps be messing with the profit estimates?

It might also be worth noting that at one point during this stretch the difficulty in the top-left box corrected to report it at ~29 diff, but the profit estimate didn't change, and soon after (within a minute) it went back down to the incorrect 13.534 diff. Makes me think even more that something must be acting up. Variances between estimated and actual 24 hour profitabilities also seem unusually high for the algos with, "spiky", profitabilities (X15, X13, Quark, etc...).

EDIT: Just caught it being goofy with the estimates even after getting the proper difficulty.


Looks like the profitability estimates on the coins updated properly, but the change wasn't applied to the current estimate for the algorithm, which seems to be stuck at what it was for the lower difficulty of KoboCoin (as is the rental price). Everything unstuck itself after maybe a couple minutes, but I'd imagine that the current estimate isn't supposed to end up getting desynchronised with the coin stats for any length of time (I could be wrong, of course).

[yaamp]

Hmm, a bit bigger issue here. Not sure if it used to do this or not, but it seems like the pool is getting, "stuck", on profitability estimates for extended periods of time, which causes it to report numbers that can be very inaccurate.

thanks for reporting. i saw that too yesterday. we'll have to add some more bigger servers i guess. our backend loop that updates found blocks, prices and everything else has problems to keep up with the work.

[Oscilson]

There are many rejects recently, mostly invalid shares or job id. I have to restart the miner to get accepted shares. But it will become invalid again soon. That was not a problem before. The difficulty was auto. After I changed 0.05, there are still invalid shares.

[Bombadil]

There are many rejects recently, mostly invalid shares or job id. I have to restart the miner to get accepted shares. But it will become invalid again soon. That was not a problem before. The difficulty was auto. After I changed 0.05, there are still invalid shares.

Which miner are you using (software AND hardware) and which algo?

[Oscilson]

There are many rejects recently, mostly invalid shares or job id. I have to restart the miner to get accepted shares. But it will become invalid again soon. That was not a problem before. The difficulty was auto. After I changed 0.05, there are still invalid shares.

Which miner are you using (software AND hardware) and which algo?

sgminer 4.2.2-310-g8985f-dirty, AMD 7970. X11.

There are very few rejects now. The 100% rejects on all my miners some times recently.

[Bombadil]

Works fine with my ccminer though :s

[MeteoImpact]

thanks for reporting. i saw that too yesterday. we'll have to add some more bigger servers i guess. our backend loop that updates found blocks, prices and everything else has problems to keep up with the work.

Thanks for looking into it. Hope this gets fixed soon; right now algo switching is ending up less profitable than picking a single algo with higher average profitability and just running with it 

Odd that this only started happening very recently though, as a few days ago it seemed to be working just fine--my profits from the 19-22nd switching algos on the pool were great.

[yaamp]

we're broken.

we'll shutdown for a little while

[MeteoImpact]

we're broken.

we'll shutdown for a little while

Thanks for the heads up. Hope you get whatever's been clogging the pipes cleaned up and come back online soon; pool's been a great switch from TradeMyBit after that shut down (YAAMP has generally been more functional and proactive in pretty much every way).

[Eastwind]

we're broken.

we'll shutdown for a little while

Do you mean the tech side of the pool not finance side?

Are you financially broken?

[yaamp]

we're broken.

we'll shutdown for a little while

Do you mean the tech side of the pool not finance side?

Are you financially broken?

technically

our little hobby project became hard to maintain