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

[yaamp]

VTC addys recognised as VIA, SPA as SYS, and so on... i'm out.
technically it's impossible to tell VTC addr from VIA
if they are identical and both exist, and i have such example.
why not make an option to tell the pool explicitly what coin,
maybe in user field as "vtc=************"

We just added an option to choose the payout currency. It's using the password on the miner command line, again:

-u your_address -p c=VIA

But it just works the first time you use an address on the pool. Once an address has been used with the pool, it cant be changed to another currency.

[yaamp]

Quark pool seems to have broken and isn't handing out work properly, probably when C-Note was added. When first connecting, the pool seems to hand out work fine, but then seems to stop giving out work (or hand it out only very sporadically), causing all shares after a short period to be rejected since the job being worked on has expired and the miner isn't being sent new work. Seeing this across my rigs, and by the looks of the pool hashrate, it looks like many other miners seem to be affected as well.

+1

Thanks for reporting, we'll be looking at that issue.

[jimbojons]

Tell me why your pool permanently bans my IP address? Should I just get a new one for the provider as 30-40 minutes after switching to another miner algorithm ceases to my OED packages to your pool and your site does not open yaamp.com. Explain what is it?

[yaamp]

VTC addys recognised as VIA, SPA as SYS, and so on... i'm out.
technically it's impossible to tell VTC addr from VIA
if they are identical and both exist, and i have such example.
why not make an option to tell the pool explicitly what coin,
maybe in user field as "vtc=************"

We just added an option to choose the payout currency. It's using the password on the miner command line, again:

-u your_address -p c=VIA

But it just works the first time you use an address on the pool. Once an address has been used with the pool, it cant be changed to another currency.

this option doesn't work when i place smth after, like this: "c=MUE,x11=***, x13=***,..."
but works as charm in the end "x11=***, x13=***,...,c=MUE"

that's right. we just fixed that so it can now be in any order. we also changed it so you can set the payout currency not only the first time, but anytime. your address will be validated against your currency and your balance converted. i was worried that someone else could change your setting, but i guess it's more practical that way.

[yaamp]

yaamp, u'r on the wrong fork of quarkcoin
and soon you'll be on the wrong fork of MUE 

thanks for reporting

[yaamp]

Tell me why your pool permanently bans my IP address? Should I just get a new one for the provider as 30-40 minutes after switching to another miner algorithm ceases to my OED packages to your pool and your site does not open yaamp.com. Explain what is it?

well.... we always do some sort of filtering to block malicious ip. because there are. but they eventually get unblocked. i just double checked and the ip you gave me in PM arent blocked at this time. it's still a work in progress to fine tune these filters and we're adjusting.

[probel]

your pool permanently bans my IP address

[jimbojons]

I would like to know when finally will function normally switch between algorithms according to prescribed miner complexity in the "pass". Just at the moment of every 2 minutes miner switches to a different algorithm., And idle time of switching from 3 to 15 seconds. Waiting for an answer.

[B.T.Coin]

I would like to know when finally will function normally switch between algorithms according to prescribed miner complexity in the "pass". Just at the moment of every 2 minutes miner switches to a different algorithm., And idle time of switching from 3 to 15 seconds. Waiting for an answer.

Algo switching works fine as far as I can see on my rigs.

[jimbojons]

I would like to know when finally will function normally switch between algorithms according to prescribed miner complexity in the "pass". Just at the moment of every 2 minutes miner switches to a different algorithm., And idle time of switching from 3 to 15 seconds. Waiting for an answer.

Algo switching works fine as far as I can see on my rigs.

I understand that it basically works, but not so. I ordered for example,
"pass": "x11=6,x13=3,x14=2,x15=2,neoscrypt=0.15,quark=2,lyra2=1"
A miner still switches between algorithms me every 3 minutes in a circle. And I told him clearly sets the priority of X11. I ask to clarify that it may have changed, and now we have a different register settings in the "pass" ??

[jimbojons]

I would like to know when finally will function normally switch between algorithms according to prescribed miner complexity in the "pass". Just at the moment of every 2 minutes miner switches to a different algorithm., And idle time of switching from 3 to 15 seconds. Waiting for an answer.

Algo switching works fine as far as I can see on my rigs.

I understand that it basically works, but not so. I ordered for example,
"pass": "x11 = 6, x13 = 3, x14 = 2, x15 = 2, neoscrypt = 0.15, quark = 2, lyra2 = 1"
A miner still switches between algorithms me every 3 minutes in a circle. And I told him clearly sets the priority of X11. I ask to clarify that it may have changed, and now we have a different register settings in the "pass" ??

from yaamp.com:
"Note that the password parameter must be all together, that is no spaces."

Of course, no spaces.

[jimbojons]

Hmmm ...... Now everything works fine ..

[yaamp]

do you guys suggest a longer time between switched? right now, i understand it's now switching a bit too often.

[B.T.Coin]

do you guys suggest a longer time between switched? right now, i understand it's now switching a bit too often.

Optimal would be if the time to switch would be dynamic and calculated based on the difference in profitability.
So if you are mining X11 and X13 is more profitable by 2% then there is no need to switch fast. If X13 would become more profitable by 100% then it makes sense to switch quickly to X13.

[scotte]

do you guys suggest a longer time between switched? right now, i understand it's now switching a bit too often.

Optimal would be if the time to switch would be dynamic and calculated based on the difference in profitability.
So if you are mining X11 and X13 is more profitable by 2% then there is no need to switch fast. If X13 would become more profitable by 100% then it makes sense to switch quickly to X13.

When I 1st started on yaamp last week it seemed to switch through the algos quite alot then slowed down and switched between a few less frequently. I assumed that my hashrate was being measured and then it moved to switching based on profitability. If thats the case I dont understand the need for an option to provide a "factor to normalize profitability" as documented on your yaamp's multi algo page? Anyway I have input my own factors as they are a bit different than the defaults just in case, eg my hashrate on quark is about 15 times what it is on lyra2.
Also my miner had a "sleep 10" on exit which delayed switching so I have comented that out and recompiled it, now for me switching incurrs little overhead.

before asking for change it would be handy to know what the current switching methodology is?
for reference this is what I use on linux:

while :
do
./ccminer -r 0 -a x11   -o stratum+tcp://yaamp.com:3533 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
./ccminer -r 0 -a x13   -o stratum+tcp://yaamp.com:3633 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
./ccminer -r 0 -a x14   -o stratum+tcp://yaamp.com:3933 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
./ccminer -r 0 -a x15   -o stratum+tcp://yaamp.com:3733 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
./ccminer -r 0 -a lyra2 -o stratum+tcp://yaamp.com:4433 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
../ccminer-1.5.31/ccminer -r 0 -a quark -o stratum+tcp://yaamp.com:4033 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
./ccminer -r 0 -a fresh -o stratum+tcp://yaamp.com:4133 -u 1DQiMcgWVB8wwLWhwGZFkfjF1YhP5gQNFX -p x11=10.4,x13=7.9,x14=7.7,x15=6.8,quark=20,fresh=11,lyra2=1.3
done

As an aside there were some issues with 503 service not available on the website earlier this morning and the miner getting "connection refused", was there a DoS going on?

[Eastwind]

Why is there such a big discrepancy between the estimated and actual profitability of neoscrypt coins?

[enginera]

I'm just pointing my rented rig in your X11 pool.

My username is a CANN wallet
I thought that I will recieve that type of coins but I always see Mysterycoin in my wallet screen.

Is that normal? (I tried othey coin wallets also)

My second question is; which exchange rates you are using to convert?

https://i.imgur.com/Ljrqw2k.jpg

[enginera]

Ok I learned to use c="coinname code" as a password. So we recieve payouts in our preffered coin type.
You should add these info, changing difficulties and anyother type of codes that to be used in password area; into homepage of Yaamp

[MeteoImpact]

Why is there such a big discrepancy between the estimated and actual profitability of neoscrypt coins?

I get the impression that there was some sort of coordinated attack against mining pools going on yesterday; both the YAAMP and Nicehash websites were going up and down intermittently (though staying down more than not), and even the stratum servers looked like they were crapping out every once in a while. The lower scores across the board probably reflect the turbulence.

[yaamp]

do you guys suggest a longer time between switched? right now, i understand it's now switching a bit too often.

Optimal would be if the time to switch would be dynamic and calculated based on the difference in profitability.
So if you are mining X11 and X13 is more profitable by 2% then there is no need to switch fast. If X13 would become more profitable by 100% then it makes sense to switch quickly to X13.

we're now trying this implementation for algo switching:

- below 2%, no switch
- 2% ~15 minutes
  ...
- 50% ~2 minutes

----------

we just fixed that problem that caused many rejected submits. it appeared a few days ago. the same ntime was sent over in some situations.