Someone of you knows Mintpal Admins? and could contact them to ask about APIV2 Relase?

I don't know much about API's and coding, but since my wallet is properly displayed I would say the problem with an exact 0.00002% difference is within the program.

Yes, that might be why i thought it to be broken in the first place: my windows machine is has a 6350. Looks like the hamsi implementation by sph is not compatible with those boards. Is there a lot of people using those boards around? Is it worth it to try to port another hamsi implementation just for those boards?

Before do something like that i think i need to write some MACD calculator inside C.A.T.

You know that a function like that is VERY VERY VERY RIsky? We are on Cryptocurrency Market, some "classic" market rules doesn't work in this world  

I am secretly on Sampeys payroll 

You are totally right about simply buying a lot of coins, holding, and then selling high, BUT your exposure to the market is much higher. That is one of the advantages of C.A.T. - the fact that instead of risking a large bet on a market rising, you bet much smaller amounts, and hope to make many smaller margin trades as it rises. If the market crashes, well you have only lost your small bet. Plus, if the market is fairly stable and not really going anywhere (ideal conditions for C.A.T.!), you can still make plenty of trades on the buy/sell margins.

Damn. Also have you had any issues with trade amounts. I am always getting issues and the bot gets stuck. I tried all three settings and i get an invalid trade amount all the time. I also for somereason get "Reading fee percentage has failed, falling back to 10%.". This might be the cause as adding a 10% fee would throw off everything, when the real fee is like .15%.

You could do this, but who knows how long to wait before a market has finished its dump and is ready to pump again ? Better to wait until a low price limit is met I think.

Heres another thought....

I think most people should have realised that Ping Buy/Pong Sell only works well on a rising (pumped) market, and Ping Sell/Pong Buy only works well on a falling (dumped) market.

To get the most gains, you can run Ping Buys whilst its rising, and then when the market starts a dump cycle (and you have some too high Pong Sells), cancel these orders, take a small loss on the difference, and then use the coin balance to start Ping Sell orders which should make good gains on the downward trend.

Then again, when the market looks like it has fallen its most and will start a pump again, similarly cancel your (too low Pong Buys), take a small loss, and restart these orders as Ping Buys, making the most gains again on the pump.

If you judge the market flips correctly, the losses should be zero or minimal. If you wait too long for the price trend to reverse, they will be more.


If people agree that this is a good method of making the most out of market cycles, I'd like to suggest the following :

• Have a button in CAT which works out and displays any loss to flip the market, and also tells you which way CAT is working i.e. Rising/Falling
• Pressing the button does the steps above and also adds the losses to the gain sheet, toggling between Rising/Falling
• Next step might even be to automate this with options like Set Market to Rising when a (low) price is met & Set Market to Falling when a (high) price is met.

Comments pls ! 

My bot sometimes seems to stop tracking data from Cryptsy. The prices it was trying to use were hours old. Also what happens when the bots order gets burried by other orders. Does it cancel the order and reevaluate or does it just sit there hoping the price returns.

Good news.
Just some more suggestions, though I know you spend a lot of time on fixes 

• Would be nice to have Never PING Buy Over / Never PING Sell Under
  Reason : If you're trading coins with very close limits, Never Buy Over will sometimes block stop your Pong Buys and similarly Never Sell Under will sometimes block your Pong Sells. Really you never need to block Pong buy/sells as they will always only work within your min. gains. You only really need to price limit PINGs as this is your set starting point.
  
  
• Halt Ping Buying once market hits a (high) price / Resume Ping Buying once market hits a (low) price
  Reason : Most markets are cyclical. Live traders often follow these cycles with pump/dump trades. If we leave CAT running at the start of a pump (with a never buy over limit set), it will run fine and make some good trades, then stop when it hits the limit. Problem is when the market starts to dump, CAT will start rebuying once the price limit is crossed again and you will usually have a stuck trade at the top of the cycle as the market continues to fall. What we really want to do is predict the upper & lower price points of cycles and have CAT only work on the pump, then wait for the dump to finish, then restart buying from a much lower price.
  
  
• Halt Ping Selling once market hits a (low) price / Resume Ping Selling once market hits a (high) price
  Reason : same as above but for Ping sells.
  
  
• Any chance we could have one colour per action type in the general log to make it more readable ? I still get totally lost looking for items sometime.
  e.g.
  Yellow - Check My Active Trades
  Orange - Trade recalculation
  Green - Make a new trade
  Red - A trade has occured
  etc...
  And also the buy / sell pool balances displayed on each cycle before actions ? Currently we just get a 'balance left in pool'
  
  

Thats all ideas I can think of for now !!

I have modified my strategies at Crypsy to not care about the inability to cancel.

ex. Using EarningsOnProcentagetrade,  it doesn't matter if it doesn't fill because you are going to buy/sell at once price anyway. Down side is that it might sit for a bit and then have to be manually fixed / poked at. In good volume ( DRK right now ), it works well. For a general devaluing set the down % higher than up. Reverse that for a coin gaining value.

Hope that helps.

How can you cancel unfulfilled orders manyally from Crapsy? My 'cancel order' button says that "order cancelling not supported for Cryptsy".

What would be a good trading strategy to not to get orders stuck all the time?

I wonder why there were hanging so many unfulfilled trades on Cryptsy, so I start to experimenting with my own (very basic java) bot and found out something strange and very annoying.
There are 3 ways how to connect to Cryptsy API. One is only for pushing realtime trading data (and probably not used by Haasbot), second is for various market and trading data, its public and don´t require API keys (and probably not used by Haasbot either, because without API keys You can´t even read prices with Haas) and third is for ordinary API access to get all possible data and to be able to trade and it requires API keys. This is most probably the one Haasbot use and suddenly worst of them - no matter how often You call API commands, last trade price is cached on server and updates once in about 15 minutes, furthermore inacurrate to actual price. Other data like open orders and recent trades are updated correctly, just this last price is somehow screwed.. Seems to me like some filthy Cryptsy game and I am curious how Haasbot is getting last price.