I have some sad news. Tradewave will be shut down by End of March (~ 30 days). New signups and payment pages will be shutdown effective immediately. Your bots will continue to run till 30 days from now, after which we will shutdown all running bots and wind down the service by mid April. We are planning to purge authored strategies across all storages. If you have any questions re: your strategy, please DM me.
Unfortunately we couldn't secure funding to continue the operations and with recent exits from the founders, it became difficult to achieve sustainability.
One thing I am very proud about is the community of passionate traders who helped each other with code samples, help build the platform and so many other contributions that would be difficult to summarize here. All these contributions were critical for our growth.
If you are aware of any other platforms the traders can switch over to, please list them in this thread.
Once again, thank you for your business and support in growing Tradewave.
I'm at firstname.lastname@example.org if anyone would like to stay in touch.
Sorry to hear that, Mike. Just wonder how things are turning down... Is it the monetising model, the product or the team that goes wrong?
btw, I'm personally developing an algorithm-based trading platform for cryptocurrencies. Hindsights are welcome, and your help are really appreciated.
that's sad news indeed.
As you are now winding down everything, is there any plan for the code the bot platform is/was running on?
Would you consider making it opensource or is there any plan for it, which the bot authors here could benefit from?
I am sure that within the community you managed to build over time there are people willing and capable to pick up the pieces and let at least the core idea live on.
So many people (including myself) have put hundreds of hours of their lives into crafting python bots to work with tradewave, it would be a great thing if we had the oportunity to keep our own work from losing its value practically over night with the end of march.
It would be highly appreciated if you could take some time to consider a solution concerning this hard hit for the users who stayed with you for so long, even if it is currently a breaking point in your own careers.
I will keep my farewells for some time and hope to hear from you soon.
is it possible to crowdfund/own/invest?
www.botvs.com is also a awesome quant-platform for bitcoin.
Is it possible to download historical data / will you make it possible?
Eg. I would like to download the data from bitstamp USD, so I can continue doing backtests after I rewrote my strategy script to work without tradewave.
also, via poloniex.com API you can get chart data for all their coins back to the beginning in resolution as fine as 5m
I have no access to my live bots this morning.
No logs, no charts, no stop button.
I have access again this morning. Not sure what that was about.
Curious to know where everyone is moving to now that TW is shutting down.
@litepresence - are you migrating your bots to another site where we can follow you too?
this is a truly bad news... What about considering to open source the whole project. I think the community here is committed and faithful and it might work on that kind of base. What do you think of it? Also curious where everyone is moving.
I'm building my own platform based on poloniex candle data as they're the only exchange that provides live historical array data from their API
I have a backtest engine.
I have a live engine.
I've ported the Honey Badger to my new engine.
I've created an altcoin algo.
I'm working on an API.
When my API is live, next goals:
Set up a lease architecture for badgers; even if I'm doing it manually at first.
Open source my backtest / live trade engine.
Then I will look into open sourcing my altcoin algo.
Then I'll get the badger pushing signals from polo to bitfinex and btce.
Keep in touch rpfpresence@gmail.
Tradewave is dead. Long live Honey Badger!
upon release the new platform will be called
In a ruined wasteland
amid the wreckage of shattered bot systems.
all hope was lost....
It is time for a reckoning
Love it! I hope you progress towards opensourcing the backtest engine!
Also i sent you a quick mail. Would love to help out in any way possible!
Can we get the code for the backend please? It would be marvelously useful, and a great contribution to the community.
I can't see it as being much of a saleable asset on your end. It would just be sitting there slowly rotting not doing anyone any good as API changes and a lack of maintenance render it unusable and obsolete in very little time.
If you release it then someone may take up the banner and maintain it as an open source project or spin of a corporate venture based on it and it will at least do some good in the world. Good karma doesn't pay the bills, but it can't hurt.
the issue with a platform like "tradewave" is all it takes is for a few members to write some silly blip of computationally intensive useless code and "tradewave" is on the hook for the cpu cycles required to run it.
if 9**9**9 > 8**8**8:
simple real world example... how many people here probably called:
data(PAIR).warmup_period('high') #250 candle array
when all they ever actually used each tick was
data(PAIR).period(2, 'high') #2 candle array
...and how many recalled that array from the engine time after time instead of storing it to a variable in their script?
I'm convinced the correct model is backtest engine and live engine being open to the user and run either on desktop or self funded cloud server. This way every knows what resources their burning.
Sales should be of "signals" not server time; so that the "tradewave" is only on the hook for the cpu time required to receive a signal and share it with other parties; not actually crunch it. the monetization model here was flat fee for endless number crunching server time; which can quickly spiral upwards in cost. It should have been cost plus for hosting botsmith's proprietary signals.
Or possibly "tradewave" could host the candle data in an API but still not crunch the numbers; then charge based on how many arrays get called per month instead of charging for "10 bots". Then costs would match customers better.
Clearly whatever was happening; the maintainace of this place left no place for dev in the budget.