Bitcoin Forum

http://i1037.photobucket.com/albums/a457/rollerbot/logofull_zpsb7e320b1.png (http://s1037.photobucket.com/user/rollerbot/media/logofull_zpsb7e320b1.png.html)

Hello

I have written what I think is the most advanced trading bot available anywhere for Bitcoins and Altcoins.  While it is still in the early stages, it has already shown enormous success in my own personal testing.  
I am now at the point where I will be needing alpha and beta testers to get valuable feedback and thoroughly test the features and operation of RollerBot.

With that out of the way,  

Let me tell you what differentiates RollerBot from every other bot that I could find.  Keeping in mind that I am in early stages, RollerBot already supports many features that traders have been waiting for over a year with other commercial bots.  Here are the current features (with many more on the way):

• RollerBot was designed from the ground up as a completely abstracted system.  In layman's terms, exchange logic is abstracted from trade logic.  RollerBot doesn't need special instructions to handle different exchanges, different trade pairs, etc.  Logic is executed the same regardless of the exchange or currency used.  This isn't an amateurish attempt to commercialize an open-source bot or implement some algorythm that I read about in a post.
• Rollerbot will be running on an enterprise-level infrastructure that will ensure scalability, uptime and processing power is never an issue.  Rollerbot will be running on the Amazon EC2 elastic web, just like major companies like Netflix do.
• RollerBot currently supports MtGox, BTC-e, Bter, Cryptsy, Crypto-Trade, Coins-e, CoinEx, Bitstamp, C-Cex.io, Bittrex, Poloniex and Vircurex. I have current plans of adding OKCoin, BTCChina, LiteTree, Cryptonit, McxNow, Kraken, and The Rock Trading Ltd. (As well as any other exchange that exposes a full trading API). These are actually very easy to implement because of the level of abstraction provided by Rollerbot's platform.
• Because of the level of abstraction, and because adding an exchange does not affect other logic, new additions cannot break the trading logic already implemented. No special cases need to be programmed when new exchanges are added.  Nobody wants to sacrifice stability and reliability at the expense of new features, and Rollerbot was designed with exactly this in mind.
• RollerBot uses a full MySQL backend and keeps full trade records of all pairs being traded at all exchanges.  I do not rely on external services to provide information!  This is also part of what allows Rollerbot to run multiple trade plugins simultaneously without them stomping on eachother's feet.  Mark my words, other bot authors will see this and try to implement running multiple trading algorithms side-byside and learn the hard way that it's an insanely complex thing to do! (I.e. what happens when another algorithm loses funds that would be needed to complete the sell end of an EMA order?) Luckily, this is all managed automatically behind-the-scenes with Rollerbot!
• RollerBot uses a very advanced API daemon cache system that always has the freshest data from available exchanges.  Furthering that, it has an intelligent retry and throttling system to deal with API's that get flaky during peak throughput.  Rollerbot's API calls are threaded and run in parallel, spreading the load to API providers and ensuring that their query limits aren't exceeded.  This keeps us off the naughty list - I have yet to have my requests rejected from abusing an API provider's service.
• I created the settings engine ground-up specifically for RollerBot.  While this may seem minor, it's a major feature that must be seen to be fully appreciated.  Want to treat the DOGE-BTC market differently in CoinEx vs. Vircurex?  No problem!  Have a feature request to implement a new setting?  Easy - I simply add it to the database and it's done - I don't need to change plugin code or add logic to the UI, it's automatically handled.There is full control over pretty much every aspect of Rollerbot!
• RollerBot itself is not actually a bot at all.  It is a thoroughly though-out trading platform architecture which integrates data aggregation, messaging, plugin capabilities and powerful database functionality.  The trading bot portion of RollerBot is actually provided by individual bot plugins.  Want to run an Arbitrage trading plugin alongside a Variance trading plugin, along with an EMA plugin?  No problem, the settings engine and plugin architecture allow you to diversify however you want to.
• Speaking of diversification..  Run different combinations of plugins on different exchanges (and even different accounts within each exchange)..  A high-risk account, along with a low-risk account, along with  anything else you can think of in between.  The level of abstraction offered by RollerBot is simply unmatched anywhere.  The amount of diversity can really help mitigate risk, and the fact that so many exchanges are supported helps to protect in the unfortunate event that an exchange is hacked (losses would be at least minimized)
• As I already implied, RollerBot supports any currency pair offered by an exchange.  This isn't magic or a bunch of hackery, it's the simple result of having a correctly abstracted architecture for this type of task.  In fact, many of the supported exchanges will automatically pick up newly added currency pairs (if the API in question has methods to get a list of current pairs.  In cases where the API doesn't expose this, it can easily be added through the settings engine). Virtual currency, fiat currency, foreign or domestic - it simply doesn't matter.  With Rollerbot's level of abstraction, it is all simply currency and handled the same regardless.  In fact, nowhere in Rollerbot's code would you find "If($currency=='BTC')" or any similar (which would be horrible programming practice - shame on any bot author using such hacks in their code!).  Rollerbot simply knows if a chunk of data is currency, knows if it's virtual or fiat and knows it's role in the current market.  I can't stress enough that Rollerbot is not just another hackjob bot, this is a fully OOP compliant that has been abstracted and encapsulated in accordance with the best practices in the industry.
• While incomplete, RollerBot has significant time and effort already poured into it.  Quickly approaching 50,000 lines of hand-written code (NOT including external libraries!)
• RollerBot has a complete notification system capable of emails, tweets, and push notifications to iPhone and Android devices.  No need to stare at a screen all day, you can be notified when a trade is initiated, when one end of a trade goes through and when actual profit is made.  Automated daily reports ensure that you are always aware of your investments.
• RollerBot automatically takes trade fees into account.  Rollerbot does not place a trade hoping that it grows enough to offset trade fees - it already knows where these points are when the trade is placed.  Want to pull out of a trade with 0 profit/loss?  Easy, RollerBot will do the math and make it happen.  I have written a full library just for accurate calculation of profit against price or quantity of any trade type.  This also make for very accurate STOPS (having very finite control over controllable losses)
• Full profit allocation system.  What does this mean?  You can choose to try to build the primary currency, secondary currency or split between them at any arbitrary percentage. For example, if you are trading LTC-BTC, you can choose to take full profits as LTC, full profits as BTC, or split somewhere in between.  This is a good way to slowly grow your individual holdings as your accounts grow.  This is in contrast to most other bots, which should be better classified as leveraged sell-off bots.  With most bots, you earn USD while at the same time decreasing your BTC holdings.  Here is a news flash:  this is called "Selling your coins".  Rollerbot is different..  It's for those that believe in Crypto-currency and want to increase their investment, not sell it off! (Though, nothing is stopping you from configuring a plugin to take profits in fiat if that's what you want)
• Rollerbot is a fully hosted web solution.  There is nothing to download, and you don't have to run anything on your own computer.  Most people don't realize it, but running a computer full time to run a bot can easily cost $30-$40 per month in electricity costs.  Not with rollerbot!  You won't have to worry about electricity costs, crashes or maintaining a machine to protect your investments.
• Rollerbot is developed with and executed with leading industry standards.  This isn't a browser plugin - this is a world-class project that leverages some of the best technologies available!

The list is currently pretty impressive, but I do have a long way to go with RollerBot.  As of now, it only has a CLI interface accessible over SSH (no fancy web interface).  This is both good and bad - SSH adds a huge layer of security, while at the same time not being as user-friendly as a flashy GUI.  Of course, all hooks are in place to add a Web GUI, but it has been very low on the priority list.  In fact, I'm waiting for the beta testing group to give feedback, as I have a hunch that a lot of people will really like the appeal of such a simple, clean interface.

Now for some "Pros and Cons":

PRO:
- I am a single developer.  As such I have full decision making power and know the code base like the back of my hand.  You will never hear from me "Let me check with the developer to see if it's possible..."
- RollerBot already has more features than all other commercial bots combined (and then some)
- I am a relational database expert. Having this relational database experience has given me a huge advantage in abstracting RollerBot the way that it has been.  This leads to a stable codebase, faster integration of features, and endless possibilities for the future.
- In the two available trading plugins now (EMA, Arbitrage and Variance), Rollerbot has had about a 90% success rate in placing profitable trades (this is no lie.  Trades made during testing were actually tweeted live as they happened. See https://twitter.com/RollerbotFeed). I openly challenge anyone to prove that I've deliberately misled anyone or made up claims about trade profitability. I will NEVER make claims based on backtesting (because it is inherently inaccurate).  I will only make claims based on actual performance of Rollerbot.
- While I'm not a big name in the Bitcoin community, I have been around for a while.  I also authored SmartCoin https://code.google.com/p/smartcoin/, a miner load balancing system that was pretty popular early on with Bitcoin.  Smartcoin code can be evaluated by anyone that wants to see my credentials as an experienced programmer.
- Simply put, RollerBot offers features that you just can't find anywhere else, and are unlikely to anytime in the future.

CON:
- No fancy GUI.  Interaction happens over SSH to a linux server running RollerBot.  I understand that this can be a turn-off for some people.
- I am a single developer (heard that one already huh?).  Just as it is a pro, it has it's cons too.  I can only develop so fast.  I also have a family and a full time job.  Just disclosing this to be fully transparent. Oddly enough, my development pace puts the development pace of other bots to shame.  I've supported features after my first week of programming that most bots have been working for the last year to implement!
- Still in early stages - I have many plugins to implement and plenty of testing to do.
- CLOSED!  I will not open the source to RollerBot.  I'm coming on 2 months of working on this for every single waking hour of every single day since starting this project.  Some days have been 16-20 hours straight coding, and there has not been a single day that I haven't spent at least 8 hours working on RollerBot.  Aside from that, the architecture is so radically different than anything else available that I don't want "competition" to even see the magic behind the works.  It is the biggest single thing that puts RollerBot in an entirely different league than anything else.
- COST -  While I'm open to suggestions, I do have a good idea of a few pricing models that will probably be supported.  Because of the full feature set, and because of the effectiveness - Rollerbot will come in at the premium end of pricepoints (Believe me, paying for an Amazon cloud infrastructure is not cheap!  This isn't some small shared or even dedicated server).  However, because of the profitability of Rollerbot, it will actually be a great value.  More on this to come...
- I have not yet implemented a backtester or full simulation trading.  I've actually done most of my testing live in the market with my own money.  I may get some flack for this, but the more I think about it, the more that I don't even want to implement one.  While I can talk about this for hours, I'll at least give a few examples why...  First of all, backtesting is very very inaccurate.  Assumptions are made that every trade you place goes through.  In real life, by the time the data is collected, a decision is made and the order is submitted - the current trade price has moved enough that the order would become stale and not execute when expected.  Secondly, backtesting doesn't and cant simulate how your own orders will impact the market.  When an order is placed, it will have an impact on the market (in line with it's volume usually).  This can be compounded, as when you get multiple people trading with bots the impact becomes even more significant.  Backtesting simply can't account for this.  I simply don't want someone to backtest a certain strategy, gain false confidence and then lose on their investment just because a backtesting algorithm told them it was a good idea.  I may revisit this in the future, but as of now I'm pretty certain that I'm not going to waste my time on something with such little added value.


Current Status: (last updated 3-1-2014)
Currently adding support for more exchanges.

Thanks to any who provide feedback!


[/list]

I just fired RollerBot back up after my architecture changes.  Just to give an idea of how things are right now:
I turned the bot back on and within the first hour 4 trades were initiated. Again, the twitter feed is https://twitter.com/RollerbotFeed

Here are a couple of pictures.  One of the output from the Arbitrage plugin, one of the output from the Variance plugin, and a quick screen grab of the push notifications on my Android phone.

http://i1037.photobucket.com/albums/a457/rollerbot/jondecker76rollerbot-var-www-rollerbot_001_zps290522ff.png (http://s1037.photobucket.com/user/rollerbot/media/jondecker76rollerbot-var-www-rollerbot_001_zps290522ff.png.html)


http://i1037.photobucket.com/albums/a457/rollerbot/jondecker76rollerbot-var-www-rollerbot_002_zps93ded3be.png (http://s1037.photobucket.com/user/rollerbot/media/jondecker76rollerbot-var-www-rollerbot_002_zps93ded3be.png.html)

http://i1037.photobucket.com/albums/a457/rollerbot/push_zps8a5458f0.png (http://s1037.photobucket.com/user/rollerbot/media/push_zps8a5458f0.png.html)


If you look closely, you'll see that it only takes each plugin a few seconds to execute!  The arbitrage and variance plugins intentionally sleep to put the frequency at 10-second intervals just to slow things down.  This excellent speed is mainly due to the API cache daemons that do the heavy lifting in the background with the various exchange API's.  Historical data is saved in the database, so if I need to look back for trending, I don't have to do a bunch of complex API calls, I can simply call results up nearly instantaneously from the backend.  In my early testing, I had 10 instances of the arbitrage plugin running, along with 10 instances of the variance plugin running simultaneously without lagging down the system.  Anyone who has had to try to fetch massive amounts of data quickly via API calls will tell you how long it can take - in these screenshots you can see Rollerbot retrieving all the info it needs from multiple exchanges and markets in mere seconds.  Soon I will make a recording so it can be truly be understood just how fast this system is.

Added Bitstamp and C-Cex support today (both still need testing after I send some funds to each of these).  This makes for 10 exchanges now fully supported

More good news.

I played around with the HHVM JIT compiler/runtime today (developed by and used by Facebook for the sole purpose of speeding up PHP code execution to be nearly on the level of compiled C/C++ code).
Early results are simply awesome, with a nearly 8-fold speed increase.  I will be moving RollerBot to HHVM in march when the mysqli extension is fully supported.  This very fast bot is going to get a turbo mode very soon!

I love the idea behind this (especially arbitrage) but is it also taking into consideration the fees for moving funds from one exchange to another?

Trade fees are always taken into consideration with any trading plugin. 
When the logic for the Arbitrage plugin is executed, it only considers opportunities where the profit is above a certain threshhold after associated buy/sell fees are taken into account (there are other things considered for arbitrage as well, such as direction of the slopes in both exchanges as well as the current price in relation to the average upper/lower variances over the last N minutes, adjusting order quantity so that it respects you max_spend_percent setting as well as taking into consideration whether both exchanges have enough of the appropriate funds to pull off the arbitrage)

As far as transfer fees, they are are not put into consideration - mainly because they don't need to be.  When market conditions are right for arbitrage, a buy order is placed in one exchange and a sell order is placed in another.  You keep the profit from the difference of the buy/sell price.  Also, in practice i have found that the direction of the trade will naturally cycle back and forth between exchanges, eliminating the need to actually transfer funds back to the original accounts.  During one-sided times, it is not uncommon for most of your holdings in a specific currency to all end up at one exchange, but over time they almost always seem to find their way back just through natural trading.

In the event that funds don't find their way back naturally, I have an answer for that as well.  I'm currently testing a "mock transfer" plugin, who's responsibility it is to keep fund distribution even across the exchanges.  It simulates transfers by basically running a modified instance of the arbitrage plugin it's self - looking for opportunities to buy in one exchange and sell in another - with the difference being that instead of looking for a minimum profit, it shoots for a zero profit/loss when possible, up to a minimal loss if you have one set ("transfer fee").

Hopefully this answers your question.  Thanks for stopping in

That was actually extremely informative, and it hit on exactly what I needed. This all sounds extremely interesting!

I'll definitely be hanging out to see what happens with this and keep up with the latest information, :).

Wow, very fancy. Good luck with sales jondecker76

CURRENTLY TESTING MY NEW EMA PLUGIN!!!

The plugin will be called REMAP (Real-time Exponential Moving Average Periods) and it is a highly modified version of the standard EMA that most traders are used to.  There are some very unique twists to this plugin and is not even remotely close to being your standard EMA algorythm.

Here are some details:
* First, this thing is FAST, especially when comparing to standard EMA methods.  I am calculating EMA in real time for every chosen market in each exchange (In my test I am tracking 4 different exchanges with about 10 markets each - for a total of 80 total EMA calculations each iteration (one for a short EMA and one for a long EMA on each).  I am able to fly through all 80 calculations in under a minute.  This is without optimizations or compiling through HHVM yet (where I'm sure I can cut this time in half at a minimum).  This means that on-the-fly EMA calculations will be running in the background at a resolution of under one minute while calculating 40 different markets - independent of the period or short/long iterations chosen.  What does this mean?  Rollerbot's REMAP plugin is capable of sensing a market trend change according to the setpoints in under a minute and executing trades immediately.  This is very different from other bots using EMA methods that have to see a Short/Long EMA crossing 2 successive times in a row (sending an alert that a trade is eminent only to have you wait an hour to see if it happens or not...).  The problem with these old EMA methods are that they are suited to a stock market setting where the markets close every day - so calculating once per period worked fine.  With our 24/7 exchanges however, this causes a lot of missed and/or losing opportunities.  The REMAP plugin solves this problem by doing these calculations on the fly, 24/7/

* Infinitely adjustable!  Do you want to do a 10:21 EMA against 14-second periods?  Not a problem!  A 8:18 EMA against 5 minute periods?  Again, not a problem.  You are not locked into pre-defined periods like with other bots.

* Capable of high speed trading and taking advantages of price fluctuations throughout the day (though, only if that's what you want of course)



I will be testing the plugin for the next day or so in simulation mode (I.e. no trades will actually execute - just text output to let me know a trade would happen).  If things look good, I will be trading with it soon (and tweeting the results live of course)

What language is the bot created in? I ask because if it was PHP and you were interested, I could help you improve it.

I appreciate the offer, but Rollerbot source is remaining closed at this time.

But yes, it is mainly written in PHP, with very heavy MySQL integration and the Linux shell via BASH.
It will eventually be run through the HHVM JIT Compiler instead of the PHP interpreter.

Myself being a small time btc earner see btc as a hobby and would vote for a percentage of earnings as a fee to use. I simply dont have enough btc to trade for the program, but if its secure and makes enough profit, I can see it paying off well for you. I wish you luck in your endeavors.

Thanks for the feedback.  This is a pricing model that I'll definitely be considering.

Over the next week I'm slowly going to be migrating RollerBot to Amazon AWS running over an elastic EC2 cloud.  This is a move that will add a lot of scalability for the future!

Are you looking for any beta testers? I'd love to try it out on a semi-larger scale.

I will be accepting applications soon for a very limited batch of beta testers. I will make an announcement when I am ready (moving to Amazon AWS will take a little time).

Off the top of my head though, any linux and cli experience will definitely be helpful, as RollerBot is completely command-line driven at this point.

Put me down on your list for one of the limited batch testers. I do have some linux experience, and can code some too.

I began a round of optimizations on the EMA calculations (specifically on increasing the efficiency of the queries involved).
I am now calculating on-the-fly EMA values at about 10 per second! That's an 800% increase in speed.  This modified EMA plugin is really shaping up!
EDIT: Last round of optimizations complete.  I am now calculating live EMA values at the rate of 100-120 per second.  This is enough speed to iterate through numerous scenarios in the background for dynamic EMA

A quick peek of the debug output:
http://i1037.photobucket.com/albums/a457/rollerbot/jondecker76rollerbot-var-www-rollerbot_006_zps80c5b18e.png (http://s1037.photobucket.com/user/rollerbot/media/jondecker76rollerbot-var-www-rollerbot_006_zps80c5b18e.png.html)
* Note on above - Vircurex data shown is old (I have the cache daemon down while adding features), all other data shown is real-time though.
Settings used: 10:21 EMA short:long, 1800 second period size (periods can be any denomination of seconds)

I'll be working mainly on the REMAP EMA plugin today.  I may have it doing live trades later today.  Things are looking very promising!

If debug output is accurate, there have been countless opportunities within the last day

The REMAP EMA plugin is complete and undergoing testing tonight.
I've shut off other trading plugins so that I can focus on ensuring the accuracy of this plugin.  Should be interesting!

Put me on your beta tester list.
My group has around 1050++ people (on twitter, kakaotalk and newsletter subscribers.)
If it really works, they will love your software.

sounds really good.  Well if your going to sell it.  I would suggest you use someone like me with no coding or even many coins to test it on.  You have to make it user friendly.  Let me know when your ready to test.

Last night's testing went very well. Things that were verified were:
- EMA was generated accurately
- Other plugins could not access funds "locked in" by a current EMA order.  This ensures that the appropriate funds are available when opportunities hit (this is the most complex part to deal with when running multiple different plugins)
- Order compounding and cross-cancellation worked as expected.  This allows for accurate profit calculations
- Sanity checking worked as expected.  This filters out noise from when there is an abnormally high or low order placed that could place a sudden change on EMA calculations.


Today I'll be testing some settings for some high-speed EMA trading as well as adding more configuration options that should help differentiate between variance fluctuation and an actual trend

I have sent PMs to those inquiring about beta testing

I have decided to fully commit to releasing RollerBot commercially.  The first post of this thread has been updated.

Awesome to hear. Can you hint a bit about the pricing models yet?

Can't wait to see this pot in action, note to everyone, consider this an investment.

Yes, there will be a flat pricing model (Per month, Per quarter, per year)
And a percentage pricing model.  Details aren't 100% complete yet, but basically you use rollerbot for 30 days, then you have a 5 day grace period to submit your payment based on the profits from those 30 days.  I'm so confident that profit will be made that I will take the risk - note though that risk comes at a premium. Also, there will only be a limited number of "pay by percent" slots open at a time on a first-come first serve basis.

My guess is that most will want to start out with a pay-by-percent model, but will quickly move to the more affordable up-front options.

Made some good progress today.  The REMAP plugin is shaping up nicely and operating as expected.

Tomorrow will be spent improving on the settings engine even more.  I'm at a critical point where I need to start thinking forward when it comes to supporting multiple users, and now is the time to implement everything needed in the background.  Hopefully I can do this all tomorrow, but my worst case is 2-3 days to get things redone where they need to be.  After that, I'll put a little more attention into the REMAP plugin and then start working on the MTT plugin (Modified Turtle Trader).  Lots of good stuff coming this week!

As far as alpha/beta testers, I'm hoping to have them all running Rollerbot within a month, and a full release in 3 months.

Please add me to beta

Thanks

Cool,,, will check it out.

Yes this sounds fair and I will do a full review for you.  My friend who writes games reviews will be interested as well.  Even if im a tester for you and it works I will probably purchase it as well.  Always good to reward innovation.

Just an update for the day.
I'm working on the settings engine improvements, but I also have a few more things on the slate.

To fully explain, I'll have to describe a concept that Rollerbot uses.
Plugins can operate as DEO (Double-ended orders) or SEO (Single-ended orders). A DEO plugin places both the buy and sell orders at the same time (I.e. they are stored in the database referencing eachother, thus being designated as Double-ended).  With SEO, only one side of the order is actually placed in a market (Either a buy or a sell).  It is stored in the database as being what i call "Uncomplimented", meaning it does not reference an opposite order, because it hasn't been placed yet.  With SEO plugins, they calculate on-the-fly when to complete the order, and the complimenting order is placed when needed.

The nice thing about DEO is that you know when the order is placed how much profit will be made if both sides go through.  The bad thing is, some DEOs go stale and only one side goes through.  It's kind of hard to do a stop loss strategy with a fully committed DEO.  The plus side, is that since both orders are placed, then the funds are put on hold at the exchange level, so you don't have to worry about different plugins stomping on eachother's feet.

With SEOs, uncomplimented orders must be manually tracked in each market, so that the appropriate funds will be available to them when it's time for the complimenting order to go through.  This is a very complex task, and one already handled by RollerBot.  Here is an example that may make sense:
Lets say you start out with 1.00 BTC, and the REMAP EMA plugin buys 100 XCoins for 0.5 BTC (as an SEO).  Eventually to make a profit, you will have to sell those coins (minus the buy fee that was originally taken out).  If another plugin were to have already sold some or all of those XCoins, then your original REMAP SEO buy order will never compliment and become stale.  On top of that, other plugins could possibly sell those XCoins cheaper than what they were bought for, causing a loss instead of a profit.

With the above in mind, I'm going to be improving the SEO logic even more and adding failsafe checking to ensure things like this never happen.  If you've ever wondered why other bots have a hard time supporting multiple trading algorithms and multiple exchanges, this is a big part of the reason.



I will also be changing the Variance trading plugin from a DEO plugin to an SEO plugin so that real STOPS can be put in place, as well as to maximize profits.

Sounds like a fun day

I ran across your bot on twitter (I periodically search for likely outputs from trading bots on twitter so keep tabs on the 'opposition'); this looks like a pretty competent outfit. If I ever find a bot that I think's better than mine, I'd cheerfully switch to using it.

Given that you are going to be opening it up to users, presumably users will simply have to trust you with their API keys?

The twitter feed has been down for a few days so I can test some new features, but glad to hear you found out about Rollerbot through Twitter.

Yes, you are most correct that there will have to be a level of trust from users, this is inevitable.   API keys will be stored in encrypted form in the database to protect them in case the database were ever dumped somehow by a third party (even though security is top priority, I must also consider all possibilities for protection of the userbase). Rest assured that I have no interest in breaking the trust of future users.  Aside from that, most exchanges don't allow withdraws from the API anyways.

Thanks for stopping in

Short term EMA testing is going very well!
I should be posting screenshots soon once a sell occurs, but running realtime 6 minute periods with a 4/8 EMA locked on to a nice FST trend on Cryptsy. I'll post screen shots once the trade completes.
EDIT:  Attaching screenshots

This is nothing amazing but it is a profit.  This was a short spike in FST price at Cryptsy today.  The REMAP EMA plugin would have caught the trend at the beginning, but I didn't even start trying the fast settings until the trend was half way up. Also, since this is a testing period, I purposely limited amount that could be spent in a single buy order.  If I would have had things set up before the uptrend started, and I wouldn't have limited my buy order size, this would have been a nice profit from a very short and fast EMA.

Here is the trend from Cryptsy. 
http://i1037.photobucket.com/albums/a457/rollerbot/Selection_008_zps89ef9200.png (http://s1037.photobucket.com/user/rollerbot/media/Selection_008_zps89ef9200.png.html)
You can see that the trend was pretty short lived, but the realtime EMA of Rollerbot was able to lock onto the trend and ride it up (even though I got in a bit late)

Here are the notifications that were sent to my phone:
(I'm attaching a couple of screen shots so the entire history can be shown)
Initially you will see that the order was placed for 99.13648990 DOGE @ 0.00000873 (at the bottom of the screen)
Next, you can see that I got a notification that the order that was placed was actually executed at the exchange.
Then, at 3:26 you can see that the sell order was placed for 98.9382169202 @ 0.00000879.
Just after that, a separate sell order was created to get rid of extra holdings that I had that weren't part of the first original order.
Shortly after that, I get a full confirmation that a profit of 0.00000247 was made (this is after trade fees)
Lastly, the extra order that was placed to sell off extra FST holding that I had got a confirmation that order executed.
http://i1037.photobucket.com/albums/a457/rollerbot/Screenshot_2014-02-09-15-29-55_zps1546cd9e.png (http://s1037.photobucket.com/user/rollerbot/media/Screenshot_2014-02-09-15-29-55_zps1546cd9e.png.html)
http://i1037.photobucket.com/albums/a457/rollerbot/Screenshot_2014-02-09-15-38-40_zps25892521.png (http://s1037.photobucket.com/user/rollerbot/media/Screenshot_2014-02-09-15-38-40_zps25892521.png.html)

Now, here is a screen grab of the plugin daemon output.  You can see that FST is still dropping in this screenshot, but a message is displayed that there are no FST holdings to sell, so nothing happens at this point.
http://i1037.photobucket.com/albums/a457/rollerbot/jondecker76rollerbot-var-www-rollerbot_007_zpsa5e898a4.png (http://s1037.photobucket.com/user/rollerbot/media/jondecker76rollerbot-var-www-rollerbot_007_zpsa5e898a4.png.html)

I'd be interested in beta testing. I switched to using bots a couple of months back and I'm always on the look out for improvements.

I got it, thank you.

Excellent progress today.

I decided to do some tests of the API cacheing system today.  Up until now, I've only been cacheing the API calls needed to keep fresh data for the currencies that I've been trading.
Now I need to look ahead and start caching the API calls needed to get information on all trade pairs on all exchanges.
With my current system, it takes almost a minute to fetch all API calls from all exchanges.  This is not fast enough moving forward, so I'm going to be overhauling the cache system to spread the load among even more threads, and getting rid of disk-based cacheing all together in favor of a very fast in-memory cache using Amazon's ElistiCache service.  As soon as this is done, I'll start storing all trade data for all trade pairs in all exchanges to start building up historical data for when Rollerbot goes live. (I've currently been only saving trade data to the database for the pairs that I trade).  I'm also going to have to jump right onto implementing the user system, as cache daemons will need to be spawned for each user as well, for each exchange that they have set up.  Since I'll be working on the user system, I'll also go ahead and implement a strategy system so that different stragies (selected plugins and their settings) can be saved or restored at any time.

So for now while I implement these changes, I'm going to take RollerBot down so I can focus on getting these very important changes in.  The twitter feed will remain silent as well - but no worries, I'm sure after a week or so all of these goodies will be implemented and tested.  Hopefully I'll be working on the GUI shortly after that!

It is likely that an entire server will be needed just to handle the API call load, an entire server just to handle the cache system, and an entire server to host the database. A fourth elastic server will be used to spawn individual plugins for each user.  Since almost all of the heavy lifting will be handled by the other servers, I should be able to host hundreds of users per front-end server.
I've also been thinking of methods to have multiple pricepoints.  One method that I'm really liking is that you purchase the rollerbot service buy buying Points.  Each trade pair traded under a plugin will cost one point.  This way, I can have some cheap options for those who only wish to trade a few trade pairs (which can be switched around at will), and for those that wish to trade in many markets at once they will have options too.  This will ensure that I can pay for the provisions needed to host the service (I'd simply have to charge too much if every single user were to trade under 15 different exchanges and every market in each exchange).  This makes it fair for all users, as they will only be paying based on the provisions that I have to provide with the backend.  I'd love to hear everyone's thoughts on this...


Once I am done with the above changes and get some testing in, I will probably start the Beta team testing starting with the REMAP EMA plugin and Variance plugin.

very good work, will follow closely.

This is a good idea in an ideal world, but are the exchanges going to be okay with you hammering the APIs in this fashion? The (public) orderbook APIs are usually more forgiving, but still, especially if


I could see exchanges starting to blacklist IPs.

Also, if it wasn't clear from my first post (likely), I would be interested in beta testing when things get that far.

this is exciting although I did not understand all what you said some off it I did.  Cannot wait to see your baby in motion.  ;D

Jon

All exchanges?
which exchanges are covered by your system?

Maybe you can also charge users per exchange basis
Personally I only use a few main exchanges like Cryptsy, btc-e and Coinex for trading,
and I do not trade all the pairs.

I've got things hashed out a bit more.  The only APIs that I absolutely have to call even if nobody is using a certain exchange/tradepair is the trade data (to maintain my own tradebook on the back end fur the purpose of calculating slopes EMAs, etc against).  Since these tradebook API calls are almost always public calls, and since they normally keep a large span of time, I can call these infrequently when the backend determines that nobody is running a plugin against a specific exchange/tradepair.

Regarding orderbooks, I have no need to keep a local copy, so i can spawn those daemons as needed (In real world, there will be many currency pairs at any given time that simply won't be being used).

So basically, Based on whether a tradepair is being used or not:
-tradehistory daemons will kick into either high speed mode or slow speed mode
-orderbook daemons will either kick on or off as needed

As far as private API calls, all I really need is balance data and a data on the user's current open orders, so these calls will just be treated normally as I do now.

I have already been in talks with many of the exchanges and they know what I am doing and have a list of the IP addresses the daemons run on. I'm quite positive that this shouldn't be a problem.  If ever becomes one, I can simply launch daemons in different AWS zones to spread out among more IP addresses (though I don't foresee needing to happen at all)

I currently support MtGox, BTC-e, Bter, Cryptsy, Crypto-Trade, Coins-e, CoinEx, Bitstamp, C-Cex.io and Vircurex
I have plans of eventually supporting every exchange out there that exposes a full trade API, including some of the big hitters in Asia.

As far as the points system goes, imagine that you get 10 points for a certain fee.  Rules would be like:
*1 point for each exchange to run on
*1 point for each trade pair to run
*1 point for each trade plugin to run

With that example, 10 points could get you:

Cryptsy(1 point) running EMA(1 point) on LTC-BTC(1 point) and DOGE-BTC(1 point)
BTC-e (1 point) running Variance(1 point) and EMA(1 point) on EUR-USD(1 point), PPC-BTC(1 point), and XPM-BTC(1 point)

Basically you could build your strategy with the number of points allotted.  Of course, I will have higher tiers where more points will be included at a better cost-per-point, but I have a lot of details to work out yet.

Also keep in mind that I am building a full "strategy" system.  You could save the above example as "My 10-point BTC-e/Cryptsy strategy", and make one or more entirely different strategies and switch between them at any time.  The point won't be to lock anyone in to one strategy, only con help put a cap on the amount of load it puts on the servers.

I would imagine that most users will be like yourself, wanting to trade their favorite pairs in a few different exchanges.  But I also want to be prepared for the "Big dogs" that want o bite into everything they can.

im also interested if testing spots are available

More great happenings today.

I have purchased the domain name and am hard at work getting the website put together.  I'll post more on this once the website coding is done (probably in a few weeks).  By then I should have the move to Amazon AWS complete and can start working on getting some beta testers started.

As I get closer to starting the beta program, I'll contact more people for testing.

all sounding good to me wish i could offer some help but i am thick lol

points system sounds feasible.
do rope in the beta testers once its online,
thanks.

This looks amazing! Great work!!!

Im up for beta testing also! Sign me up!

Would love to test this and subscribe in the future

Working mainly on the website today.  Just standard HTML5/JQuery stuff, nothing too exciting.  Mainly just working on the basic website template and some of the settings and configuration screens. Hopefully I'll be on Amazon AWS by the end of this week so I can really get busy!

Wrapping up for the night

Got a pretty good start on the website.  I concentrated mostly on Add/Edit/Delete exchange accounts.  This is now mostly finished, a little more to do on it tomorrow then I'll start working on the web interface for building strategies.

Here is a quick screen grab of part of the website showing how the account settings are coming along (API keys blacked out for obvious reasons)
http://i1037.photobucket.com/albums/a457/rollerbot/Selection_009_zps869bcab2.png (http://s1037.photobucket.com/user/rollerbot/media/Selection_009_zps869bcab2.png.html)

thank you for the daily updates.
eager to test your service once it's online.

Bump for Jon. Awesome progress!!

looks clear and concise cooll

Nice!!! It looks amazing! keep the god work m8!!

Just posting a quick update

A lot of stuff going on.
-The move to Amazon EC2 should be complete tomorrow
-I am almost done with all of the CRUD interface code for the website to safely interact with the database. Extra care is being taken to ensure MySQL injection is guarded against. All queries are properly escaped and parameterized and internally generated authentication tokens are also used to ensure passed-in parameters are not tampered with.
- A lot of effort is going into the user authentication and authorization system.  Security is absolutely the number 1 concern and protection is being built-in for just about any attack imaginable.
- Along with security, I made a change to the accounts interaction of the website.  Public and private keys will never be shown once they are entered.  Under public or private keys in the display, it will either show as "<entered>" or <not entered>".  They can be changed, but they will never be viewable after they are entered.
- I've brought in a jquery/jqwidgets expert to help with the interface.  I absolutely hate working with javascript (it's so messy) so this will free my hands to get back into the guts of Rollerbot.  FYI, this second party does not have access to the server or the database, only the the CRUD interface that I have built to allow UI interaction.  On top of that, the CRUD interface is currently pointed to a test database.  Rest assured that I will remain the only person with full access to sensitive information (including database schema, database contents, etc.).  I can't stress enough that security is my number one focus.

I'll post more updates as they come.  I may be quiet for a few days while I wrap up some of these loose ends.  Also, I have to remember the wife on Valentine's day - she's been awful supportive of my full-time dedication to getting Rollerbot out to the community.

Thanks again everybody for the support and interest in this project

Why would you sell access to pairs when you could just make it an investment fund with other people investing money ?
You could earn much faster ( people get 90% of the money made on their investments and you keep 10 %) and it could be simpler.

I have thought of this as well, but I also must ensure I'm complying with local laws.  When you get into supplying actual investments and such the laws get very stringent and it's something that I'd rather not get into at this point.  Legally speaking, it is much easier to ensure full compliance by providing a service rather than directly handling the money of others as an investment.
Perhaps as things progress and I can get proper legal advice on this it may be revisited, but for now this is the model that I am going to follow for the named reasons.

It's not totally out of the question, but I have not received appropriate legal advice on such a setup at this point.

Never forget the missus on Valentine's day.
Mental note.

@jondecker76, Have a good weekend.

yes my wife moans im on the pc all the time lol.

keep up the good work.  cannot wait to see this working

personally that sounds dumb as hell, who on these forums would give btc to someone offering to give them more later?

I'd like to beta test as well. I actively trade on btce and bitfinex.

 :) :) :) :)

Things are still going well with Rollerbot

The servers at Amazon AWS are all set up now.  Over the next week I'll be working on moving the cache system into the Elastiweb Redis in-memory cache, working on imrovements to the API daemon system and getting things running again.

The UI is coming along nicely and there is now full ability to Add/Edit/Delete exchange accounts, and partial support for building strategies.  I'll post some pictures in the next couple of days

Really looking forward to seeing updates, the screenshots specifically!

I have not done as much trading as I would like due to the difficulty in messing around on each exchange so much.
When you are ready for testers I would like to be one for it.

looks fantastic. count me in for testing or any other help you need.

Just posting some shots of the progress so far.
The UI is coming along nicely.  The user registration/authorization/authentication system is up and working.
Exchange accounts can be added/edited/deleted from your profile
Strategy names and descriptions can now be Added/edited/deleted. 

Much of the work now has to go into the strategy system.  This is how setting up your account and strategies will work:
- After registration, you go into your profile settings and add Exchange accounts.  You can setup multiple accounts per exchange, and select from all of the supported exchanges Rollerbot has to offer.
- After you have all of your exchange accounts set up (more can be added at any time), then you will be ready to create your first strategy.  Under the "Strategies" tab you will create a strategy name and description.  Selecting one of these strategies once entered will bring you to an area where the strategy can be configured.  This will be done by selecting one or more of your accounts, defining the trade pairs for each account, then finally which trading plugins you want to run for each trade pair for each account.  You will be able to configure this any way you want - multiple plugins per trade pair (even multiple instances of the same plugin), one plugin per tradepair - whatever you want.
- Manage your settings.  Each plugin instance has it's own settings group.  For every single plugin under every tradepair under every account you have individual settings so that you can fine-tune your strategy.
- Make as many strategies as you want.  Only one strategy can be active at a time, but you can switch between them on the fly.  Switch to a high risk strategy during times of high market volatility, and then to a lower risk hold position during flat market times with one click.


Here are some sneak peeks of the UI so far:

Exchange accounts list:
http://i1037.photobucket.com/albums/a457/rollerbot/Selection_010_zpse0015ea2.png (http://s1037.photobucket.com/user/rollerbot/media/Selection_010_zpse0015ea2.png.html)

Editing existing account:
http://i1037.photobucket.com/albums/a457/rollerbot/Selection_014_zps4e53c757.png (http://s1037.photobucket.com/user/rollerbot/media/Selection_014_zps4e53c757.png.html)

Adding new account:
http://i1037.photobucket.com/albums/a457/rollerbot/Selection_011_zpsc14c085c.png (http://s1037.photobucket.com/user/rollerbot/media/Selection_011_zpsc14c085c.png.html)

Strategies list:
http://i1037.photobucket.com/albums/a457/rollerbot/Selection_016_zps48927df6.png (http://s1037.photobucket.com/user/rollerbot/media/Selection_016_zps48927df6.png.html)

Editing a strategy:
http://i1037.photobucket.com/albums/a457/rollerbot/Selection_017_zpsc6e1a582.png (http://s1037.photobucket.com/user/rollerbot/media/Selection_017_zpsc6e1a582.png.html)


Back to work!

Looks good Jon!

Hi there


Any chance to join the Beta Test, the Tool looks really awesome!

best regards


Hektek

In time I'll go through all of the beta test requests and send out some information.  I'm going to do my best to get as many of you guys as possible into the beta to give things a good test.  My goal is to have things ready by March 15th to kick off the beta.  If things go well, hopefully even sooner :)

This looks awesome! Put me in for beta tester and reseller if you are planning to accept that!

Sounds awesome! Would love to help on the beta tester side at the least

Just popping in real quick.
I spent most of today getting the Amazon AWS redis Elasticache setup.  Everything seems to be working now, so now I need to go through the code that uses the old disk-based cache and update it to use the blazing fast redis cache.  Considering that the cache is normally under a 500+ I/O per second load, this should end up being a tremendous speed-up due to reducing all that disk I/O.

I also have the database fully setup on the new server.  Hopefully these next changes go smoothly and I can actually fire the rollerbot backend up very soon to start storing trade history locally again.

As a software developer of 15 years, your approach and choice of technology sounds spot-on to me, and so I've registered on this forum simply to request to be a beta tester when you're ready.  I have plenty of Linux command line experience (if that's still a concern now that you're building a UI), and I'm excited to see the project progress!


zebaroo

Thanks for stopping in!
It's nice to hear from from someone that understands the choices in underlying technology (as well as the difficulty in implementing some of it). 
It was pretty hard to take a step back from a perfectly running system only to tear it down and implement things properly for a fully scalable commercial system.  It is delaying the launch date, but in the end things will be done correctly and it will be worth it. 

I'll be in touch!

Daily update on the thread.

The new api daemon system (including new cache integration and load throttling) has been the focus for the day.  It's about 75% done at the moment -  all of the backend daemon changes are done (mainly common (public) API calls).  I just have to get the frontend to start it's own daemon process for individual authenticated user API calls.

For now I've limited my tests to cryptsy.  Over 320 API calls have to be cached in the background.  In my tests, this throttled to just under 40 threads, keeping the local cache at 10 seconds of age.  Each additional user only adds 2 API calls to the total - so you can see where the heaviest lifting is done on the backend server and that adding additional users has very low impact on the overall load.  Anyways, in my tests tonight the processor usage was much lower than expected (0.03 as reported by top).

Moving forward, I have to finish adapting the rest of the exchanges to use the new daemon and cache system, and add the ability to the plugin system to have backend plugins (to be used by the Rollerbot Platform, such as plugins to store trade data to the database), as well as frontend plugins (to be used by individual users, such as trade bot plugins).

Lastly, I started drafting a plugin API.  This one is a ways out, be eventually I hope to provide an API to interface the Rollerbot platform for those who wish to code their own plugins.  I'll probably open-source at least one or two of the simpler plugins as examples.  This will let users that have programming experience program their own plugins (and even share them systemwide with Rollerbot users if they want).  In all actuality it will be the same API that I use to make the plugins, but with the plugin includes dynamically included to protect the source code behind Rollerbot (in which case it's more of an issue of documentation).

That should be it for the night.  I'll check back in tomorrow.  There is a good chance that the entire backend should be back up and running tomorrow and I can actually get some real-life benchmarks.

That will be great.
I'm not good at trading on my own and this would be a godsend.
Thanks

march 15th ish sounds good seems you moving pretty well

looking good

Lots of good stuff today.

The new API cache daemon system is running great on the backend.  Right now it's only running against Cryptsy and BTC-e (mainly because I haven't updated the other exchanges yet to use the new system).  Those two exchanges alone are cacheing 542 API calls in real-time effortlessly.  The daemon thread monitor script is doing an excellent job of throttling the API calls(by spawning and removing parallel daemon scripts) to keep the age of the data at the desired setpoint.  
Tonight I should be able to update all the exchanges to use the new methods and get a full load test in.
Next on the plate is to get backend plugins running, at which time I'll be able to start storing trade history to the database again.

I've also drastically reduced the number of database queries.  Up until this point, I was storing the nonce for each account API in the database, querying to retrieve it each call, then querying again to increment the value.  With so many API calls, this was adding up to thousands of queries per second, which are now eliminated due to using a better method based on microtime instead.

The exchange landscape is really looking good lately. I've seen quite a few new exchanges popping up in the last month, almost all of them with a full trade API.  I fully expect to support 20+ exchanges by the time Rollerbot launches!

Other good news is that HHVM recently included mysqli support, so soon I will be running everything through the HHVM JIT compiler for a huge speed boost and better memory management.


Here is a screenshot of one of the daemons running in the background.  If you look across the bottom,  you'll see that the daemon spawned 22 parallel threads, with 5 symbols being queries per thread (this specific daemon is querying cryptsy for trade data).  If the queries take too long, then more threads are spawned until the average execution time is where it should be.
http://i1037.photobucket.com/albums/a457/rollerbot/Selection_019_zpsa4261b5a.png (http://s1037.photobucket.com/user/rollerbot/media/Selection_019_zpsa4261b5a.png.html)

HHVM is now compiling on the backend server.  Hopefully I can test running the Rollerbot code through the HHVM compiler tonight!  I already have benchmarks finished running the code through the PHP interpreter, so this should turn out interesting!

It looks excellent so far.
This could change trading for the better in a short time.
Keep up the great work I cannot wait to try it.

This looks extremely cool, even if I do not yet completely understand all of its potential capabilities. I'm not a programmer, but if you are ever looking for someone to team up with on a web based GUI, feel free to hit me up.

im so excited cannot wait to review this

Not a whole lot to report today.  I was pretty short on time, but the couple of hours I did have went towards testing things out with HHVM.

Unfortunately just a few days ago the HHVM redis support got broken with an update (I'm testing with the nightly builds ATM while waiting for the stable release that includes mysqli support).  I spent some time with one of the devs on IRC and the fix will be pushed out in the next day or two - after which I expect to have a successful test of Rollerbot running on HHVM.

http://oi57.tinypic.com/sv016p.jpg

Newest work I did for RollerBot!

Client: RollerBot
Project: Advanced trading platform
Type of logo:  Simple, professional, memorable and trendy.
Solvation Logo represents a roller, turn-over, never ending profit.  I've used colors and shapes that has associations with robot.

Any feedback is highly appreciated! 8)

Currently I'm working on: 2 projects.
Am I available? YES!
Please write me a PM or email bitcrea@yahoo.com
My official graphic design thread: https://bitcointalk.org/index.php?topic=444106.0

Precise and high quality work guaranteed!

woot!
Awesome job!

Thanks to the excellent work by Bitcrea (https://bitcointalk.org/index.php?topic=444106.0), Rollerbot now has a finalized logo (I only changes some of the color scheme to fit my tastes)!

http://i1037.photobucket.com/albums/a457/rollerbot/logoicon_zpsc920693e.png (http://s1037.photobucket.com/user/rollerbot/media/logoicon_zpsc920693e.png.html)

http://i1037.photobucket.com/albums/a457/rollerbot/logofull_zpsb7e320b1.png (http://s1037.photobucket.com/user/rollerbot/media/logofull_zpsb7e320b1.png.html)

http://i1037.photobucket.com/albums/a457/rollerbot/logofull_zps4d037820.png (http://s1037.photobucket.com/user/rollerbot/media/logofull_zps4d037820.png.html)

Very cool Logo.
I am looking forward to the beta test and to use it.
I am no good at trading this would help so much.
Thanks for the updates.

great logo i like it

Please add me to beta.

Thanks !!

Just checking in while I have a brief moment.

I've done countless tests with HHVM now, and spent a lot of time talking to the HHVM developers.  Unfortunately, HHVM doesn't really fit my use case of having a lot going on in parallel - mainly due to the heavy memory overhead of HHVM.  As it doesn't support threading yet, I would have to spawn many hhvm instances which is just too resource-intensive.  So for now, I'm going to stick to the normal zend PHP interpreter.

I've spent the last few days doing a lot of benchmarking, and it has helped me come up with a plan for moving forward. 
Initially, I wanted to launch fully supporting every exchange out there.  Unfortunately due to resource allocation costs it would just cost way too much up front to provision the resources needed to process so much data.  What I may have to end up doing is launching supporting fewer exchanges so that membership costs help to get the provisions needed to enable the rest of them (I'm thinking of starting with 8-10 of the exchanges enabled, then bringing more in as the userbase grows (which is just basically flipping a switch in the database for each exchange).  This will balance my risk to the point of being manageable in the case of a slower-than-expected startup, while still offering way more than the competition.


With the benchmarking out of the way, I can continue forward with the programming, having a much clearer path ahead.  If anyone has input on which exchanges they would like to see starting up, it will be taken into consideration.

Back to work!

Updating the thread for the day

Today I got my standby daemons working well.  What they do is slow down the api queries for markets that aren't currently being traded.  This lightens the load on the API provider, as well as the Rollerbot servers.
I've also put some work into the plugin system today to support backend plugins, which will run on a separate machine than user/tradebot plugins.  The first backend plugin to run will be the tradedata plugin, which will do nothing but look through the API cache for new trade data on each exchange and each market, and put them into the backend database.  This allows Rollerbot to have instant access to historical data without having to wait for dozens of API calls to complete.

I've also been putting a lot of thought into the best way to hit the market with Rollerbot.  I've decided to go ahead and fire up two more Amazone EC2 instances so that I can launch with every exchange supported (contrary to yesterday's post).  The whole MtGox situation is a prime example of why I wanted to build Rollerbot in the first place - to diversify as much as possible so that if one exchange gets hacked or is dishonest, then my holdings are spread out enough to absorb such a blow.  To that end, I need to be sure to offer as much diversity as possible when Rollerbot launches.  The sooner users can protect their investments (myself included), the better.

That last paragraph speaks volumes as to how many of us feel right now.  GoX was nothing but a ripoff and they are trying to figure out not how to give the BTC back to it's clients but keep it for themselves.

I cannot wait to try this out.

Daily update:

Today was an excellent day of coding.  The plugin system is now reworked and can support plugins as a frontend service, a backend service, or any future service that may be added.  I now have the backend trade data plugin running, and things are working as expected.  I also went ahead and threaded the plugin system.  Each plugin (frontend, backend, etc.) will run in it's own thread and have it's own thread controller.  This will give me tons of flexibility moving forward.  There are still some small additions needed yet, but nothing I can really do much with until I complete the strategy system.  As of today, the rework of the backend services is nearly finished (probably around 90% complete).  The few bits that still need to be done have to do with auto-scaling features that will allow more Amazon EC2 instances to spin up as needed along with demand.

Performance-wise, the backend services are doing very well.  I'm currently running the backend API cache system on 10 exchanges, along with the trade data plugin at about a .25 CPU load.  Not too shabby!

Moving forward starting tomorrow, I'll get back into the website/user interface and get back into the guts of the strategy system.  Once this is done I will mostly only have to concentrate on website and UI work.

That's about it for now.  Things are looking good to meet the March 15th Alpha testing start date!

Hello,

would love to beta test this. Have linux / shell experiance. Also potential customer ;)

Thanks!

very excited about this :) can't wait.

Once I get a user interface slapped on, I will start bringing you guys in slowly.  I haven't forgotten about everyone wanting to help Alpha test - it's a very important part of the development process that will really help me test out capacity of the system.

Thanks for all of your support guys - this has been a lot of work and it's been nice being able to share my development on here without having to deal with the typical negativity and accusations you see fly around here sometimes.

I appreciate you even developing this.  For people like me trading can be a pain trying to keep everything straight to make a bit of profit.
This is something that will help so much and maybe make it a bit easier to increase what little I have.
Keep up the great work.

Nothing too exciting today..  Spending some time implementing support for a few more exchanges that I've had on the backburner for a while.  At the rate new exchanges have been appearing, it's beginning to look like RollerBot will end up supporting 25-30 exchanges at launch time, which is a great thing for diversity as well as arbitrage opportunities (and profitability in general).  I may spend the next couple of days just in this area, getting as many of the new exchanges in that I can.

I'm also looking into adding CryptoStocks support for cryptostock trading.

Cryptostocks is actually really good.  I have some stock over there.

This looks awesome! Keep up the great work. Love all the updates. Would be very interested in being in the alpha/beta test group.

Today's progress:

- Added Bittrex support.  Just have to do full verification tests
- Added  AnxBTC support. Just have to do full verification tests
- Got a good start on Poloniex support.  Will pick back up on this tomorrow.

Running some backend tests tonight with Bittrex and AnxBTC running along with the other API Cache daemons.   So far so good as far as system load

Slow day today

Spent most of the day taking the family to the Museum of Natural History for a little break in the action.
Spoke to several exchanges today about API specifics, many of them newer exchanges just starting out.  Again, my goal is to provide a trading platform that will support as many exchanges as possible to offer a lot of diversity.  All I can say is that things are looking great on the exchange front.  While some seem to hate seeing new exchanges popping up - I personally love it.  Competition not only keeps trade fees in check, but the more exchanges that we have the more we can diversify and reduce our personal risk.

I'll be getting an early start tomorrow and hope to get quite a bit accomplished

I agree on the exchange front.
There are too few that are any good and some of the established one's are slow to pick up new coins that are worth it.
I'm hoping that I can earn a bit more using RollerBot to help me navigate through it all.

I'd be interested in beta testing as well. :) I am already an active trader.

Daily update, 3-2-2014
Current SVN revision: 275

Today I started a round of verifications and general code cleanup.  I'm going through all currently supported exchanges and doing a full functionality verification, as well as general code cleanups.  This is a bit of a tedious process but is coming along nicely.
I also contacted a few more exchanges today about adding certain features to their API that will allow auto-adding of new currencies and markets as soon as they are added to the exchange.  No huge deal if they don't add the features, it just means that I have to enter new trade pairs into the database manually as they appear.
So far everything is looking good on the timeline for testing and full release dates.  There is going to be a huge push this next two weeks on the interface and frontend services.

I'm going to go lay down now, I haven't been feeling good all day.  Just wanted to post a quick update before I got off of here

Feel better soon.
It's been a cruddy winter for getting sick.

Hang in there bud! Lots of sleep and hydration!

Oh the fun times of verification testing all by yourself on 30+ exchanges. I bet that doesn't get dull. Thanks for keeping the updates coming.

Felling pretty terrible today - ended up taking the day off of work.

Today I'm just working from a laptop in bed here and there.  I'm building a verification and testing routine to automate the testing process.  This will make things go much faster in the end but is going to take a little time up front.  It sure beats the tedious process of manually verifying everything!

I'd like to be a beta tester as well! In the past I actively trade on bitfinex.

Daily update, 3-3-2014
Current SVN revision: 395

I actually got quite a bit done today despite being sick and staying in bed for the most part.
I have the Test and Verification functions done, and have fully verified Cryptsy.  The test takes about 5-10 minutes to run and thoroughly tests all aspects of communicating via API.  It also checks for simple things like DEBUG statements and TODO comments in the associated code.  BTC-e is very close to fully passing the new verification testing.  Tomorrow I hope to have most if not all currently supported exchanges fully verified through the new testing system.

I also improved on some lower-level things, such as minimumquantity limits being stored per-market in the database, as well as decimal places per market (BTC-e is currently the only exchange that needs the decimal places, but it is now there for future exchanges as well).

I'm finding more and more exchanges to add support for.  In fact, I have nearly 50 "stubs" (empty source code files), one for each exchange that I've been able to find.  I'm going to post a screenshot of my current directory where individual files are maintained for managing API connections to the exchanges.  Of course, these aren't all supported (YET!), but I'm very confident of being able to start the Alpha testing with 15 or so fully supported and tested, 20+ by the time I get to Beta, and 30+ by launch time, and eventually every exchange out there that exposes a trading API.  If anyone knows of any other exchanges that I'm missing, please bring them to my attention and I'll be sure to create a stub file to make sure I don't forget to add support for it.
http://i1037.photobucket.com/albums/a457/rollerbot/Selection_020_zps859d28a3.png (http://s1037.photobucket.com/user/rollerbot/media/Selection_020_zps859d28a3.png.html)

I was testing the API Cache daemon early in the day, and with 6 exchanges running I was showing 111 currencies being supported in 201 different markets.  I can't wait to get the rest of these exchanges verified through testing so that I can get back to the UI stuff and preparing for Alpha testing.  Hopefully I'll be back on the UI later this week.

That is a beast!
I hope you are starting to feel better.

Good news, I know the team at AnxBTC, buzz me if you need help.

Hello jon. Please add one here as a Beta Tester too! Thanks.

Add me to the list of alpha testers, this looks great!

Daily update, 3-4-2014
Current SVN revision: 458
Number of source code files: ---
Lines of Code: ---
Currencies Supported: 147
Markets Supported: 272
Improving the format of the daily report.  I'm going to start including the number of supported currencies and markets each day. The numbers above are actual numbers - Rollerbot now supports 147 different currencies in 272 different markets! (and that's just with 3 of the exchanges having fully passed the new verification testing!)

Sick in bed today again, but I still got some good things done. Cryptsy, BTC-e and BTer are all fully verified via automated testing.  BTer was a real PITA, as they have a pretty nasty bug in their API which reports a meaningless order_id on placement of a new order.  Luckily I've found a suitable workaround that passed 1000 iterations of full verification testing.
Vircurex is 95% verified with just some small changes to do in the order system to pass the new verification testing.
Coins-e and CoinEx are both very close to passing the new verification testing as well.

The automated testing system is really paying off.  It has already found many small inconsistencies and bugs that would have otherwise made it through to production release.  From now on, any change made to one of the exchange API interface files will automatically trigger a verification test to run to help ensure nothing sneaks through to the production environment.

Tomorrow I will continue to work on getting full verification testing done on more of the exchanges (I have 15 of them technically done when it comes to programming, I just have to run the tests and make any necessary changes)

Daily update, 03-05-2014
Current SVN revision: 522
Number of source code files: 171
Lines of Code: 70,759
Supported currencies: 140
Supported markets: 276


Not a bad day again (feeling quite a bit better finally).  Mostly just work on verification testing  Here is the current status of the verifications:
Cryptsy: Fully tested
BTC-e: Fully tested
BTer: Fully tested
Vircurex: All good except for an issue getting trades. See: https://bitcointalk.org/index.php?topic=49383.msg5527803#msg5527803.  Hopefully they fix it soon.
Coins-e:  All good except for a small problem with their listorders API method.  I have reported the bug to them.
Coinex: Fully tested
Bittrex: All good except for a small bug I found with their market/getopenorders method.  It has been reported as well. Edit: Heard back from them, it will be fixed within a day!

Moving forward I'm going to put some energy into the website and user registration and work on getting the frontend services running

That is allot of exchanges I need to join.  :o
Good to hear you are feeling better.

I'm ready to help you test. Please let me know when to start ...

i am happy to see your feeling better.  I'm feeling pretty awful myself today.   Have you given me a virus lol.  :P

I am very happy to test it. Do you have any performance stats so far? This looks like an incredible system.

I did a lot of benchmarking of the system when I had it running as a personal project, and the results were astounding (making decisions at 10 second resolution across 6 exchanges at 5-10 markets per exchange with very little processor usage).  Things have changed considerably though now that I have started making the platform scalable.  For example, database queries may be a bit slower due to higher load from having multiple users, while at the same time there will be a nice speed-up from having common API calls shared among multiple users.  With that in mind, I can't really predict yet what the performance gain/hit will be from the recent changes until I get things back to a state where I can do new benchmarks.  I do however expect the performance to be on par with what I experienced running it as a stand alone system for myself, and early tests so far seem to support this as well.

The next couple weeks will tell a lot now that the backend system is running and I can see how the newly separated frontend services run.  I'll definitely be sharing my results here either way as I progress

Not a lot to report today

I'm still waiting to hear back from some of the exchanges in which I've identified bugs in their API (currently I've hear back from Bittrex with indication of a fix on the way, and ANX (anxbtc/anxpro) with interest in working on solutions).  Therefore there are no new significant changes for today.  I've also contacted some other potential industry partners in order to open clear lines of communication.

Tomorrow I will mostly work on web frontend stuff, and will report back here tomorrow with my progress

Today I'm mainly going to be working in Amazon AWS console getting things organized (VPC, elastic IP addresses, load balancers, etc), then work on the website starts.  I'll update the thread later with how things go.

Today was a great day.  A lot of progress is being made on final decisions when it comes to the actual specifics behind RollerBot deployment.  I've brought aboard someone with extensive knowledge in system administration and deployment, especially when it comes to AWS.  This weekend will be a pivotal point for RollerBot as the full groundwork is put into place that will empower the scalable architecture that I dreamed for this platform.  There should be some exciting news in the coming weeks as things are nearing being ready for alpha testing.

Stay tuned :)

I am glad it is going so well.
Also glad to hear you are feeling better.
Sounds like you are really rolling along.

I know the ANX team personally. Buzz me if they don't get back to you.

I've hear back from them once and sent another email.  So far they have been great to work with

3-8-2014

No code changes today.  All of today was spend in AWS with configuration.
I've recruited the help of an absolutely awesome system administrator to help guide RollerBot in the best direction possible when it comes to the underlying infrastructure.  Most of today was spent discussing future direction and getting things set up to provide the scalability and reliability needed for the trading platform.  A lot of discussion revolved around security and many things were put in place today to ensure a secure platform to build on.  I wish I could share more, but this is leading to the possibility of an exciting announcement in the near future.

I'll have more updates tomorrow

I'm interested to test it as I have many alt-coins as well as an active trader on many exchanges plus an linux administrator. So this fits very well. I've use AWS and Windows Azure somewhat, just let me know if you need anything.

Just wanted to drop in with some progress updates.

I didn't get as much done as I wanted to over the weekend.  Most time was spent on getting the rest of the infrastructure set up on AWS, which included making some important decisions that took some time to thoroughly evaluate.  I'm not going to release too many details, but as of right now RollerBot consists of 5 ec2 server instances (with more to come) and the important backend services are islanded and isolated from the Internet.  The only server attached to the Internet is the web server, which it's self doesn't even have database access.  Many steps have been taken and decisions made to ensure a secure platform.  Now with that out of the way, I can continue marching forward with the code.

Code-wise, I spent a lot of time yesterday cleaning out the source tree of old/antiquated files and making an effort to improve the documentation (through phpdoc). 
Today will be spend finishing off some of the backend services (daemon spawning and load balancing) and then working on some of the user services (private API call daemons, etc)

Thank you everyone for your continued interest and support.  Things are starting to get exciting as everything is slowly starting to pull together

Killer day today
I did a lot of work tightening up the backend code.  The cache daemons are running fast and smooth, and the backend plugin system is fired back up (just storing trade data ATM)
Made some changes that reduces the number of MySql calls per second dramatically as well.  Letting it run all night to see how things do

3-12-14 Swinging in for a quick update

Getting the infrastructure set up has turned out to be a much larger task than I expected.  Almost the entire last week has been spent testing configurations, running load tests, reconfiguring, testing again, etc.
I'm happy to say that I have finally found the mix of performance, redundancy and cost needed to efficiently and effectively run the platform.  I would even venture to say that I've spent more in server infrastructure so far in development than most (if not all) bots spend in a year.  I'm not quite sure anyone really understands the amount of power it takes to run such a large trading platform (currently 8 servers in total to get through development and alpha testing, and even more when it comes to full release).  I'm beginning to see why something of this scale has not been done yet!

With all that said, things are still moving forward, albeit a bit slower than I originally expected.  Due to costs, RollerBot will launch supporting 10 exchanges.  As a userbase builds, I'll be able to afford more infrastructure to enable support for even more exchanges (in blocks of 10, to keep costs reasonable).

I'll be able to get back into the programming that needs done over the next couple of days now that the final layout for the infrastructure is now set!

Great update! I was very curious how much processing power would be required. Sounds like you need an infrastructure guy to worry about all the easy stuff so you can get back to the coding and development. If you have any immediate needs or desires you should outline them. Perhaps donations to fund more development servers? Would you be interested in having help beyond all us pestering you with "let me be a part of the alpha test team so i can make easy money with all your hard work?"

I've actually been asked about donations a few times now.  I honestly didn't think there would be anyone willing to donate..  I'll get a donation address set up for those interested and post back here.

Regarding infrastructure - I have found at least part-time help with this recently and it has been a tremendous help.  We're actually in talks about the legalities and specifics about retaining him - If we work something out I'll make an announcement.

Regarding other help, there may be a possibility to bring in some limited PHP help just for supporting new exchanges (writing the exchange class files, most of it would be copy and paste)- though to expose even this little bit of the source code to an individual would require some good references and standing in the community.

Another area of help would be someone fluent in the Chineese language (or any foreign language where exchange platforms exist) to help me get accounts set up at these exchanges and do some test trades etc.

Thanks for the great Ideas!

Updated my signature with a BTC donation address.

Thanks for the suggestions guys

I'd like to test your app. It looks much better then most of the existing bots.

Very exciting times ahead :)

all sounds promising must be getting close for release well beta testing anyway.  I know i have not been on much of late but im still here.
keep up the good work.

3-15-14

Bittrex is fully verified and tested now, as is ANX (ANXBtc/ANXPro)
I've been working on the daemon system quite a bit to make it lighter on resources and give it more control over spawning and tracking threads.  The results are excellent.  In my load tests right now, 7 exchanges querying/caching all trade and depth data for every market in each of these exchanges is in the 35%-40% load range on the backend server (1077 API calls are being cached @ a 20 second refresh).  I still have some optimizations to make, but these results are beyond what I was expecting already.

I have about one more day of backend work to do, then I can concentrate on the website stuff.

Those stats look awesome:
(1077 API calls are being cached @ a 20 second refresh).

Keep up the good work and don't forget to rope me in for the beta program.

3-16-2014

The backend services are pretty much complete, leaned out and optimized!
I'm not going to let too much out of the bag, but I'm currently load testing the daemon system and the results are simply blowing me away!

Currencies supported: 164
Markets being queried:729
API calls being cached: 1,948 @ 20 second refresh

There is still a ton of headroom left on the backend server, the database server and the redis cache also.  All of these small optimizations are really adding up!

3-17-2014

Today I sent emails out to Cryptsy, Btc-e, Bter, Coinex, Coins-e, Crypto-Trade, Vircurex, Bittrex, AnxBTC/AnxPro, Bitstamp and Poloniex requesting that the Rollerbot IP address be whitelisted.  This should help avoid interruptions in service in the future, as well as make them aware of why this IP address sends so many requests.

I will update the thread with the status of these requests.

[Edit] Heard back from ANX (AnxBTC and AnxPro).  They have accepted the whitelist request.
[Edit] Heard back from Bittrex.  They have accepted the whitelist request

just awesome work you're doing! I'm really excited to try it once you'll release a beta! can't wait!

This looks really interested, I'll be keeping an eye on this.

Shouldn’t this thread be in Project Development though?

Looks very promising! Will the pricing depend on the volume of trades? It would be very unfair to charge the same monthly amount to the small miner/investor as to the big whales!

Please also add me to the list of betatesters!

This looks great! i would love to be a part of beta testing.

and the ability to have packages for limited exchanges and coin paires available is awesome!
you  would need a lot of coins to fund over 150 currencies at 20 exchanges.
and you need a lot of time to manage all those pairs and the arbitrage an all. that would simply be to much to handle for me and i guess most of us.

if this works as good as you discribe it will, you got an instant subcriber here!

If everything works out as expected then this one could be the best one yet!

Please add me to the beta test list as well.

3-19-2014

Nothing too big to report.  Most of my time has revolved around getting the web server set up so that I can get the interface back up and running, then improve on it.  This is pretty important, as without this step I can't finish the front-end services (user plugins running, authenticated queries, etc)

Thanks again to all showing their support. Progress has been slower than expected, but things are still progressing :)

If you need anything to speed it up, please give a shout-out!

Can I try out the beta please ?

Thanks

This looks good! i'm already using a few other bots and would love to beta this

let me know!

Which ones are you using? Are they good?

Any updates?
i cant wait to get my hands on this and try it out.
so much possibilities!

Just reading through, looks good. Will keep an eye on it.

3-24-14

Checking in to the thread.  I had a very busy weekend and had to work 12 hours shifts all weekend, so I've been a little scarce for the last few days.

Effort right now is being put into the internal API system.  For security reasons, the website its self will not have access to the database.  Instead, it will communicate with a backend server (which is completely isolated from the Internet on a VPC) via a secure internal API that has strict control over what kind of information the web server has access to.  I'ts going to eat up some development time in other areas, but it's important to have the security portions done correctly right from the beginning to ensure the security of user data.

Another area I have been poking around with is the User Interface.  Right now I'm torn between using standard tools like JQuery and JQWidgets (I hate programming in Javascript, so using these would mean hiring out for more work to be done on the interface), and between using a completely custom UI (meaning that the UI is a custom program with all components rendered on a canvas, including text boxes and other standard UI items - more so like a video game).  There are pros and cons to each.  Here is a quick list of the pros and cons of both.

JQuery/JQWidgets

PRO	CON
Industry standard libraries many programmers available to hire Very fast and attractive interface Skinnable via CSS	Standard HTML UI elements are a security risk Javascript is not my strong point, I would hire out Bugs in JQuery/JQWidgets would be out of my control

Custom UI

PRO	CON
Full control over features and appearance I can use a language I'm very fluent in Skinnable via custom graphic files I could use the same base for web via HTML5 and/or Flash, iPhone, Android and desktop UI options Super high security	Would likely take a little more time Not likely to be as fast as standard UI components, as each one is rendered as a graphic (20 FPS target) Not industry standard

So as you can see, weighing these two options is not very easy.  I want to take the project in the right direction so I need to be sure that I make the right choice.  Throughout the week I'll be experimenting with a little of both to help in the decision making (and any feedback from the community considered as well)

Lastly, I know it's a bit early but I've been doing some experiments with porting the framework over to compiled C++, which is not only way faster than interpreted PHP, but will also lower costs in the long run due to being lighter on provisional resources.  This is a very long term thing though, I would finish the framework in PHP first and start serious work on the port only after Rollerbot is up and running (think of it as the "next generation" product).


That's about it for now.  Just wanted to give an update on where things are.  I should be able to put a good dent into the internal API and user registration/login system this week!

Will HackLang.org help you speed up and be a little bit more productive?

Not really unfortunately.  I've already did a bunch of tests with HHVM and the overhead is way too big with all the threads running.

I made some great progress on the API tonight though, and should be finished with the internal API within a day so progress is picking back up :)

great! i love how you provide regular updates.
keeps people excited for your product :)

Been waiting since 4 FEB and still awaiting.
cannot wait to see the beta rollout.

me to. i see more and more oppertunities everytime i log in on an exchange.
and because of the vast possibilities created by so much coins and exchanges there shouldn`t be any problem with saturation.
as long as pricing isn`t unreasnable. we all can make a nice profit and jon will be drowning in customers and making a reall killing on this.

this is just what i`ve been waiting for for sooooooo long lol

still have my support cannot wait to test and do a write up

yeah, we definitely need more bots to throw out humans from exchanges, it's already a joke on cryptsy where you can see bot battles on popular coins cancelling 99% of their orders within seconds
terminator HFT powa :D

Really excited for this!! Can u pls let me know as soon as I'm able to get a copy.

Thanks

jondecker76 has been quiet since 25 March,.....

Right, it was the last time he answered my post!

he's probably super busy, but it would be cool to know what's going on :)

He's still working on Rollerbot, no worries.

so did you managed to talk to jondecker76 ?

another week gone by without an update from jondecker76.
anyone spoke to him yet?

Quite a prob with one person company!

I'm the guy Jon spoke about earlier in this thread who has been helping him with the AWS infrastructure for his bot. Unfortunately, despite a couple of messages now, I haven't heard back from Jon. Not sure what is going on - he was very passionate about this project so I'm hoping he's ok!

still no news?

So pretty much the project is gone!

Unfortunately it appears that way. I haven't seen Jon on Skype for 2-3 months now and he hasn't been logged on here for over a month either. I'm not sure what's happened, but the EC2 instances are still running, which will be costing a pretty penny, along with the collaboration tools we were using.

Hopefully he's ok.

still no news from Jon?

I havent heard anything from Jon in around 2 months now, although he was last active on here after that date. The EC2 instances which were running the code have been stopped so I assume something has come up which is preventing him working on the bot - not sure why or what has happened though. I shame he hasn't dropped by to confirm what's going on.

Damn. Was really looking forward to this.

what happened here? I was really happy for this.

Jon is still missing?

He was getting very interesting results. :/