Topic: [POOL] YAAMP.COM multipool multialgo profit switch with exchange - page 73. (Read 181320 times)

Feathercoin is down at cryptsy.

And yaamp does not implement exchanges to btc-e or bter yet.

So there's no way for us at this time to exchange FTC to BTC.

Is there any update, yaamp?  It seems the neoscrypt pool is not behaving properly...

Why FTC is not beeing mined , just phoenixcoin?

Any plan for EU server?

Thanks for the info.

Blocks are being found now...  

FTC fork in 111 blocks, which should be in about 2 hours, but will probably be longer because of the high difficulty at the moment.

minerd -a neoscrypt -o stratum+tcp://yaamp.com:4233 -u XXXX -p x

Try this  

I'm connected but no blocks found  

Good question:  What is the port for neoscrypt?  It's not indicated (yet) on the homepage.

The FTC fork is coming soon...

neoscrypt port?

Hello yaamp.
is it possible to use valid JSON format for your API?
For example instead of "name": scrypt use "name": "scrypt" and instead of "port": - use "port": "-".
Thanks
Jiri

{"scrypt": {"name": scrypt, "port": 3433, "coins": 11, "fees": 0.5, "hashrate": 211448220, "estimate_current": 0.00048872, "estimate_last24h": 0.00039709, "actual_last24h": 0.00032679}, "x11": {"name": x11, "port": 3533, "coins": 9, "fees": 1.4, "hashrate": 9644617930, "estimate_current": 0.00036116, "estimate_last24h": 0.00032790, "actual_last24h": 0.00028979}, "x13": {"name": x13, "port": 3633, "coins": 2, "fees": 2.6, "hashrate": 473805025, "estimate_current": 0.00042750, "estimate_last24h": 0.00033953, "actual_last24h": 0.00031533}, "x14": {"name": x14, "port": 3933, "coins": 1, "fees": 2.3, "hashrate": 347490647, "estimate_current": 0.00029718, "estimate_last24h": 0.00071879, "actual_last24h": 0.00068974}, "x15": {"name": x15, "port": 3733, "coins": 3, "fees": 3.6, "hashrate": 164421263, "estimate_current": 0.00058283, "estimate_last24h": 0.00041256, "actual_last24h": 0.00040174}, "nist5": {"name": nist5, "port": 3833, "coins": 2, "fees": 4.4, "hashrate": 253087139, "estimate_current": 0.00006981, "estimate_last24h": 0.00007988, "actual_last24h": 0.00007841}, "quark": {"name": quark, "port": 4033, "coins": 3, "fees": 0.5, "hashrate": 3393799, "estimate_current": 0.00000122, "estimate_last24h": 0.00000134, "actual_last24h": 0.00046477}, "fresh": {"name": fresh, "port": -, "coins": 1, "fees": 0.5, "hashrate": 0, "estimate_current": 0.00030648, "estimate_last24h": 0.00026540, "actual_last24h": 0.00000000}, "neoscrypt": {"name": neoscrypt, "port": -, "coins": 0, "fees": 1, "hashrate": 0, "estimate_current": 0.00000000, "estimate_last24h": 0.00000000, "actual_last24h": 0.00000000}}

More API problems.  Tried running the output through JSONLint and it won't pass there now.



This of course kills Miner Control being able to update prices for YAAMP.

Best pool on the scene, hands down.
Great job guys!

Best DIFF for Zeusminers = 1024

Any higher, or vardiff it's set to high and my hashrates drop like a brick.

Normally my 22,28 and 42 Mh/s miners run minimum this rates.
In yaamp they are all off...

20 gridseed blade's > max 16
22 zeus x3 thunder > max 20
28 zeus x6 thunder x 2 > max 23
42 zeus x6 lightning > max 33


That's to low to keep them in the pool.

If you can set a fixed diff i will put the 140 Mh/s total back in the pool, if not i'm keeping them out.

Hello yaamp,
it seems you have a mistake in your API response...
The comma character (",") is missint in front of  "quark" key and one extra comma character (",") is at the end.
Jiri

{"scrypt": {"coins": 11, "fees": 0.5, "hashrate": 607429810, "estimate_current": 0.00051858, "estimate_last24h": 0.00035363, "actual_last24h": 0.00026115}, "x11": {"coins": 9, "fees": 1, "hashrate": 6092170077, "estimate_current": 0.00032853, "estimate_last24h": 0.00036990, "actual_last24h": 0.00030759}, "x13": {"coins": 3, "fees": 2.8, "hashrate": 274630171, "estimate_current": 0.00048429, "estimate_last24h": 0.00039910, "actual_last24h": 0.00039864}, "x14": {"coins": 1, "fees": 3, "hashrate": 719758605, "estimate_current": 0.00146507, "estimate_last24h": 0.00102093, "actual_last24h": 0.00082590}, "x15": {"coins": 3, "fees": 3.5, "hashrate": 1595931044, "estimate_current": 0.00038518, "estimate_last24h": 0.00052909, "actual_last24h": 0.00049546}, "nist5": {"coins": 2, "fees": 3.5, "hashrate": 321896502, "estimate_current": 0.00008219, "estimate_last24h": 0.00008784, "actual_last24h": 0.00008632}"quark": {"coins": 1, "fees": 0.5, "hashrate": 3520501, "estimate_current": 0.00000147, "estimate_last24h": 0.00000150, "actual_last24h": 0.00003645}, "fresh": {"coins": 1, "fees": 0.5, "hashrate": 0, "estimate_current": 0.00028505, "estimate_last24h": 0.00021687, "actual_last24h": 0.00000000}, }

Connected with titan !
but ..

 [2014-10-23 12:43:42] Coinbase check: multiple inputs in coinbase: 0xfe
 [2014-10-23 12:43:42] Pool 2 misbehaving (coinbase check), disabling!

I do not understand why ?

And enabled .. Titan is sick miner.

Unfortunately, I have to go to another pool. Until knc fix this isue.

Thanx for help yaamp

We've made some tests yesterday with a bfgminer/4.9.0-titan-1.04. Thanks to unitedminers. It appears to be good now although it needs to be confirmed that it's working well.

Thanks for reporting LTCD.

The diff should adjust to a good value automatically to have something around 5-20 shares per minute (max 5120). What value do you get after a little while?

----------

If anyone with a TITAN (or any miner that doesnt work) wants to help debugging, please go to this chat:

http://webchat.freenode.net/?channels=#yaamp

I'll try to hang around and give you a debug stratum port number to make a few tests.

Great pool.

If possible, please ad a feature for setting DIFF.

Like : username = bitcoinadres paswoord = diff=1024 or diff=2048 etc...

It's now Vardiff, and getting slower hash then they normally have when i use a pool when i can set diff=1024

Also, today i heard some multipools were on the wrong chain with LTCD.
I received mail from Cryptsy when my ltcd was not deposited there, and lost a lot of LTCD coins.

Is Yaamp on the correct chain ?

How is it with the pools?
I get a lot of rejects, because pool 0 is not responding!

Still problemm -> Pool 3: Unknown stratum msg: {"id": 4, "result": true, "error": null} when try to connect with TITAN ASIC miner.

Trying with bfgminer/4.9.0-titan-1.04 .. with no chance.

our web server is slow and unresponsive. too many requests. we're looking for solutions.

mining and payments are not affected.