Did some more improvements on the backend, also wrote a blogpost about this piece: Read it on the Wizb.it blog. If you want to be the first to know, make sure you subscribed on the site so you'll get updated as soon as we have new stuff. |
|
|
|
Here is one for FRK
frk.cryptocoinexplorer.com
and one for other coins
coinplorer.com
It's a realtime visualization which has quite specific requirements Blockchain.info is the only party I found yet that is able to offer it. What I need is: - Latest unconfirmed transactions - Latest block finds Blockchain offers it through a websocket which is ideal, though a REST api would also be fine (if I can hit it once every ~2 seconds). If I would opensource the code how would you solve this problem? |
|
|
|
A better fit with the color scheme would be blue and green.
I'll experiment with it for a bit. All blocks were green before but the problem was that they were hard to see when zooming out because the whole globe is blue/green already. |
|
|
|
This is awesome, now all you need is something like Listentobitcoin in there and you will have the ultimate experience haha
Thanks. I'll give adding sounds on transactions / blocks a priority, I'm thinking of making multiple (sound) themes, like sci-fi / relax / etc. But first need to find decent sounds. |
|
|
|
|
After lots and lots of complains about people getting headaches, the auto zoom en each transaction is now a toggle. It's off on default. Also some improvements on the backend & the blocks are now different sizes depending on transaction size (only the orange ones for transactions, the yellow ones for blocks are all the same size).
|
|
|
|
Why don't you make blocks a different color, and add information about the transaction on mouseover/click
Good idea, blocks are now yellow and transactions are orange. Still think the colors can be improved (they don't really fit the sci-fi interface I think). So the last transaction info is displayed on the right, the last block info on the left. I've chosen to not do anything on mouse click because of the speed the globe is auto rotating as new transactions come in (now less than in the weekend for some reason). I think it would be frustrating to do anything on click as you can already use the mouse to rotate the globe and it auto rotates about every second (on average, depends on bitcoin transactions ofcourse). ---- Just a tip: this looks great on a projector. I sometimes give presentations about Bitcoin and have put this in my presentation to showcase the global network. If you're thinking on doing the same but don't like some things let me know and I can alter it / put live a different version specific to your needs. |
|
|
|
Wow, very impressive! Found another thing to endlessly stare at!  Thanks! --- Does anybody know where blockchain.info is located? A lot of transactions are relayed from them (all the Costa Rica based transactions on the globe) and this is the best I could find (based on the main IP of their website). --- I am still tweaking it a little based on feedback I received on twitter: - I'm going to proper lighting to the blocks and transactions, possibly also add glows. - The sizes of transactions will depend on the transaction sizes. - Going to add sounds (especially on new blocks). If anybody has suggestions let me know! |
|
|
|
The Realtime Bitcoin Globe shows (almost) all transactions happening in the bitcoin network in realtime. It also shows freshly minted blocks. Realtime Bitcoin Globe- This is meant as a fun datavisualization / experiment. - The locations are the relay IPs as reported by blockhchain.info. - Since the network has more and more transactions the globe might auto rotate extremely fast. You can disable auto rotation in the bottom right. I am still smoothing it out some bugs on different platforms. If something is not working (on platforms where WebGL is) please let me know! Feedback is highly appreciated! --- This project is part of Wizbit, an upcoming service providing insights in financial data around crypto currencies. -- This project in the press: - Wizbit blog- The Next Web- Hackernews- Adafruit- bittercoin- launch.co- omicrono- pejcz |
|
|
|
I got "registry error parsing json". How to fix that if it happens in the stable version update?
That's weird. So Gekko runs on Nodejs which is a platform for developers, I'm sorry I can't offer a more user friendly solution at this moment. To troubleshoot: - What OS are you running? - What's the output of running: node -v - What's the output of running: npm -v |
|
|
|
Also hey @whydifficult I was figlet-ing some big ASCII text for something unrelated and I thought maybe you'd like a splashier splashscreen? .d888888 .d8888b. 88 .dP 88 .dP .d8888b.
88' '88 88ooood8 88888" 88888" 88' '88
'8888P88 '8boood' 88 '8b.88 '8b.'88888P'
.88
d8888P I'm gonna make you rich, Bud Fox. This looks awesome! Will look into this thanks  Hi
I recently installed the latest version your bot using the windows guide but i have troubles when i want to use kraken, i get a "Cannot find module 'kraken-api' "
But at least the bots works for other platform like MtGox where it can connect. So i guess its just a problem with kraken
Im using node v0.10.25.
If someone can give me an advice ? Thanks
Every time you pull the latest version of gekko you need to run: okey i success to make it run on my computer finnally...
this bot is not really as "intuitive" to make it run as others like butter bot,
any way, is the tutorial data updated? because i use LTC asset and i get an error as its not supported at btc-e...
i am also trying to find the code:
config.tradingAdvisor = {
enabled: true,
method: 'DEMA',
candleSize: 5,
historySize: 20
}
as i read in the tutorial and it does not exist at config.js...
So altcoin support is only available in the latest unstable build: we changed a lot of things in Gekko and don't know for 100% everything works. You can find the latest version here: https://github.com/askmike/gekko/tree/localDBYou can only download this unstable nightly build through git. First download git than: git clone -b localDB --single-branch git://github.com/askmike/gekko (As soon as this version is stable you can download normally) and the configuring docs: https://github.com/askmike/gekko/blob/localDB/docs/Configuring_gekko.md-- So you are looking at the docs for the new version, though you are trying to run it on the old version. |
|
|
|
I'm not sure, but does Gekko simulation take transaction fees into account? That might be the reason for your discrepancy. I also find it surprising you trade succesfully at cex. I thought that market only had one direction... down...
Yes, Gekko also takes fees into account. Though CEX.io doesn't have any trading fees. The different either comes from a calculation bug (I'm skeptical about this) or fees + slippage. Currently the simulator assumes it's able to buy/sell at current market price (which is last trade price, does not look at the book) - fees - slippage. If the spread is large and the trade was on the other side of the book this is far removed from reality if slippage is not set accordingly ( don't trust the defaults as this is way to market specific). The reason it doesn't look at the book now is because the system is agnostic to any live market: if you feed it a stream of trades it is able to simulate new trades according to the configured trading method. Eg. this also works for backtesting as is. I want to move to a system where we also save a historical ticker data. Note that only having ticker data does not prevent not being accurately able to calculate slippage, just the part up to the spread (difference between last price and best ask in case of long), but if you are a whale slippage will eat in your profits hard after the top ask (which is the only information the ticker provides). |
|
|
|
Kraken support has been added to the unstable version, we are currently fixing the last remaining kinks out of the cable. --- Those stats were running CT, with gekko simulating trading with same settings on the side. They approximately agreed, and what you said about gekko's candles not being from 00sec to 60sec explained (some) variance. Today I've started running just gekko, letting it trade and simulate at the same time. 1m period, Default DEMA & slippage. so far simulation says: 2014-01-24 19:05:54 (INFO): (PROFIT REPORT) simulated profit: -0.00385 BTC (-0.62741%) Which is about right. Hard to measure exactly since I'm currently holding GHS, plus it's been a lame day on the cex curve for dEMA. (edit: Now I'm back in BTC. Simulated: 0.61022 / Actual: 0.61072 ) (edit again: few hours later Simulated: 0.60987 / Actual: 0.61094 ) increase mostly mining. Trades happened, but variance tiny. And tiny loss bothers me not a jot, since the bot is there to make sure massive lurches in the graph get acted on quickly. (basically, so I can sleep ever.) I can take a little hit to the balance on flat days that trick EMA slightly, 'cuz the days with movement in the graphs make up for it, and the mined BTC from holding GHS @ cex balances out little hiccup losses. EMA values to 'prefer' holding GHS in flatline and very slow drift situations would be better for cex though to maximise mining. I'm specifically running sim and real trading at the same time because of the mining from GHS held at cex; sim will show me what I'd have made just trading, whereas actual will in theory be higher due to mining rewards. (edit: knew it.) It's entirely possible at cex that's it's more profitable to sell less often in order to keep mining. Awesome let me know how it goes. You can always set the sell threshold higher so that only really steep downtrends would trigger a sell. Now I've seen it run and trade, more output suggestions! 'cos as it is now you can see simulation balances but not your actual balance... So: after every trade, something like "Bought XX<asset> for XX<currency>" would help clarify. And: a portfolio report with % gain/loss much like that of simulated trading would also be good after every trade. Also: Successful has one L  Thanks will look at this. EDIT: someone requested that we output the trades into a CSV file. Is this also something you would use? One more thing: CT ignores amounts below 0.001, (i think) so there was always a bit of balance left in what one doesn't want to be holding. Word on CT's messageboard said that was a cex API limitation. Guess not, cos no such problem with gekko. Nice.
Another difference is that CT will sell mining rewards as they build up, often for unfavourable prices. Because gekko waits until the *beginning* of an EMA upswing, mining reward BTC are sold for GHS at the appropriate time, when they're (relatively) cheap. Double Nice.
Give it a day or two and I'll post how my graph looks after gekko's played with it!
Also: post your cex.io referral link already! Donations are nice but a referral is forever. Plus it's an utter delight having bot-wielding referrals in your cex charts, seeing them rise and fall as their bots trade the EMAs alongside one's own.
I'm interested in all your feedback! Here is my [reflink]( https://cex.io/r/0/askmike/0/) btw. Uh oh! Semi-critical error: 2014-01-26 11:15:30 (ERROR): cancel order failed: Nonce must be incremented I've noticed an identical error in cryptrade, so I'm guessing the actual error string is from cex itself, so maybe cex skips the odd nonce. Difference is: when this happens, cryptrade carries right on regardless, but gekko hangs. What it (probably) needs is to increment the nonce again and retry. Also: this happened when there was an order open, which got left hanging. When gekko started, it interpreted this as which obviously is weirdass, and makes things like this happen: wanted to buy GHS but the amount is to small (-1.0696497) at cex.io A "cancel / ignore open orders on start" line in the config and a tweak to the startup maths would help such confusion. Edit: Once the order was cancelled by hand and gekko restarted, it traded it as usual. So this error has probably to do with you using the same API keys for both CT and Gekko. The nonce has to do with security around the API: in every request applications do to the API they have to send a counter and this counter always needs to be higher than the last one. This is easy if you do all the requests (just write down the last counter everytime and up it by one). Though if you have the same keys for both Gekko and CT they will clash because they are unaware of eachothers counter. Gekko and CT use the same library to connect to CEX.io, Pulsecat was the author (though he copied it from my Bitstamp code). A fix for this particular issue has been suggested almost 2 weeks ago. Unfortunately pulsecat needs to accept this fix and has not done this yet. Edit again: having restarted gekko a few times, it's clear that a "get trading sim start balance from real balance" option would help lots.
Great idea Thanks! looking for help..
i installed node.js
try to follow the installation steps and i get this once i put npm install
------------
C:\Users\Lenovo\Desktop\gekko-master>npm install
npm ERR! install Couldn't read dependencies
npm ERR! package.json ENOENT, open 'C:\Users\Lenovo\Desktop\gekko-master\package
.json'
npm ERR! package.json This is most likely not a problem with npm itself.
npm ERR! package.json npm can't find a package.json file in your current directo
ry.
npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nod
ejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! cwd C:\Users\Lenovo\Desktop\gekko-master
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.24
npm ERR! path C:\Users\Lenovo\Desktop\gekko-master\package.json
npm ERR! code ENOPACKAGEJSON
npm ERR! errno 34
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\Users\Lenovo\Desktop\gekko-master\npm-debug.log
npm ERR! not ok code 0-
-----------
Could you list the contents of the gekko-master folder on your desktop? (screenshot for example). |
|
|
|
anyone actively using this atm with good experiences? gonna try it out soon. Looks great. Was looking into cryptotrader but this bot seems a good alternative and its free I'm using cryptrade which is free and works with the candles stored at cryptotrader (but with no backtesting) at cex.io using the exact same EMA settings gekko uses by default, and that's working out well. 0.55BTC being flipped between GHS and BTC has grown to 0.6 in under a week BUT an instance of gekko doing simulated trading alongside it is (theoretically) making more, athough it's hard to count what with the mining that also occurs @ cex. Now that gekko-localdb can trade, I'll be switching over to it anyminutenow. Here's about 3 days of gekko simulating trading: 2014-01-23 21:43:31 (INFO): (PROFIT REPORT) original simulated balance: 0.58611 BTC
2014-01-23 21:43:31 (INFO): (PROFIT REPORT) current simulated balance: 0.62616 BTC
2014-01-23 21:43:31 (INFO): (PROFIT REPORT) simulated profit: 0.04005 BTC (6.83275%) cryptrade logs differently so the best I got from that is: 2014-01-23T22:16:17.819Z - verbose: updatePortfolio: { btc: 0.6083721, ghs: 0.00034388 }and here's 2ish weeks in GHS. Obviously, pay attention only to the peaks. Methinks a little too twitchy.  So you are using the cryptrade for real trading right now? Let me know if the profit reporting is wrong (though note you have to set slippage level yourself, was added a couple of days ago). Though the implementation DEMA is not 100% the same at CT compared to Gekko's version. |
|
|
|
What I failed to mention, is I had Gekko working fine on my Windows PC at home. I wanted to move it to a server for stability, my internet connection is pretty dodgy. I'll have a look re-migrating across to Ubuntu in a few hours, I appreciate your input Awesome, I'm pretty sure we can run it on ubuntu as well. I'm currently running ~25 gekkos across different linux servers (centOS and ubuntu), also running Gekkos on OS X. Most errors you posted came from NPM and I can't really make that more clear. But I just pushed an update to the localDB branch that will log an error when you try to run Gekko with an old, outdated node version: Your local version of nodejs is to old for Gekko. You have v0.8.4 and you need atleast >=0.10.x I'm actually more curious about your trading rules. I've been tweaking them to see if I can match different tolerance levels to risk. It's pretty experimental in itself, and I'm happy to lose the funds I'm trading with, in the name of art/science/finance.
I'm hoping to get to a point similar to CT where users can design / tweak their own methods. To do that we first need a bunch of indicators (and ta-lib, the library CT plugged in, will remain an optional choice for multiple reasons which means we need to write indicators ourselves). If you have specific questions about the current DEMA, MACD or PPO implementation and what makes them trigger let me know! |
|
|
|
Great job on the scripting. I just threw $20 into MtGox and started it up, so I could see it work in action. I'd love to see Cryptsy support, so I can tailor the script to my trading style, and essentially automate what I'm currently doing manually. You get a gold star from me. Maybe a DogeCoin too First lets get Gekko working I might have missed it through the pages, but is anyone else having issues installing modules from npm?
I just created a new VPS instance, still Ubuntu 12.04.3 x64
[..]
Same error, however it fails at lodash. Is this a NPM server/connection issue?
To bad you are having trouble installing Gekko. The problems all have to do with the fact that the nodejs package shipped with the default ubuntu repos are heavily outdated (nodejs is being really actively updated and Gekko requires a newer version). To install the proper nodejs that won't cause any problems: sudo apt-get update
sudo apt-get install -y python-software-properties python g++ make
sudo add-apt-repository ppa:chris-lea/node.js
sudo apt-get update
sudo apt-get install nodejs
( from the nodejs docs) -- Note that Gekko is open source and I encourage everyone to give it a try. Though in the current state it's not focused on end users, it requires installing developer tools and a command line / configuration file style interface. I am working on a webbased (hosted) backtesting platform similar to CT as well as hosted real traders (far far future). |
|
|
|
The new version (localDB branch) is nearing a stable release. Real trading now works (except Bitstamp, they banned my main IP so will come in an hour or so). To sum it up: There is a new version of Gekko which has trading methods for EMA (called DEMA), MACD and PPO on all markets on BTC-e, Mt. Gox, CEX.io. This includes all altcoin markets for BTC-e! So you can now trade LTC and other altcoins with Gekko.currently enjoying the localdb branch, cos i dig cex.io and gekko is, as far as I know, the only free backtesting game in town for cex since cryptotrader went paid-only. Plus i can actually run gekko in macosX without wrapping it in a VM. And also the only one where you can verify yourself that nobody tinkered with any data. Interestingly, I'm still running the cryptrade opensource bot alongside gekko with identical EMA settings, but they're not giving identical advice. In fact, it's barely only similar. But though they differ, gekko hasn't given any bad advice. It's just a bit different to how the cryptrade bot behaves. I'll try the 'traditional' 10/21 and see if they agree then. Hmm.
So I know of a implementation difference: if you set Gekko to use hourly candles it won't start at full hours, but as soon as it got the history it needs (can be at :41 for example). This way the candles / data / triggers can all be off. If you find any other differences let me know. ANYHOO. I keep gekko open in a terminal, but in the usual procession of 2014-01-21 00:44:43 (INFO): Processed trades, sleeping for a minute... messages, it would be nice if every line, the last buy advice was repeated. It's sometimes a marathon of scrolling to see what the last advice was, and it's often scrolled out of buffer. Those processed trades messages are only logged in debug mode since a couple of days now. Let me know if that helps. This would be easily visible also if COLO(u)RS got involved, too. Imagine: 2014-01-21 00:44:43 (INFO): Trading advice: Long - BUY | Processed trades, sleeping for a minute... 2014-01-21 00:44:43 (INFO): Trading advice: None - WAIT | Processed trades, sleeping for a minute... 2014-01-21 00:52:34 (INFO): Trading advice: Short - SELL | Processed trades, sleeping for a minute... Then even one line would be enough to be advised with a quick glance. It would also be pretty sweet to have an option to have a verbose line of the current algo. Cryptrade's EMA algo rocks it like this, if enabled: 2014-01-21T00:55:04.253Z - verbose: EMA difference: 0.01209289 price: 0.05 at Tue Jan 21 2014 01:50:00 GMT+0100 (CET) A bit of that action would be good for judging those "maybe it's time for human trading intervention" moments. Good idea, will improve this. And much as i'm on the localdb branch, so it's not trading for me, it would be most beneficial to be able to easily toggle trading/watching with a keystroke. When a market lurches oddly and you have to jump in to do something, got to be able to disable a bot real quick!
It is auto trading now, read above! So as a med student with a weak technical background in this script, I am having some trouble configuring everything. Honestly, I am struggling immediately beyond the stage of [node gekko]. Is there somewhere you can point me for further (simple) reading, that'll hopefully clarify the process of getting the trading bot up and running for me?
We have a new version which is almost stable now. This one has way more clear documentation: https://github.com/askmike/gekko/blob/localDB/docs/Configuring_gekko.mdThe new one is almost considered stable (we need to make sure it doesn't make mistakes, etc, which we almost are). You can download that one by running: git clone https://github.com/askmike/gekko.git --single-branch localDB For both versions it works like this: you edit everything you want in `config.js` and you type `node gekko` to launch it, `ctrl c` to stop it. |
|
|
|
Thanks for the reply! I didn't get it though, will trailing stop be included along with new stuff or it isn't actually on your to-do list? I couldn't find it here https://github.com/askmike/gekko/issues/114In my backtests EMA strategies with a trailing stop outperformed strategies that don't use one by at least 20% in profit. Is there any estimated time of arrival for a new stable version? So after stabilizing and verifying this new version and adding the real trader (0.1.0) I'll start working on some things already planned for 0.1.1, a trailing stop is not part of this yet. Though I have a couple of things planned for after that, these include: - More indicators (RSI, Ichimoku, Heikin Ashi, trailing stop losses, etc). - More exchanges (bitfinex, kraken, etc) - webbased interface -- I don't have any ETA as this is an open source project unfortunately. Though you can always support the project by adding the algo you want yourself. |
|
|
|
whydifficult, thanks for sharing your bot!
I was desperatly trying to backtest my EA on btc-e's MT4, but I fail due to strategy tester wrong commission calculation on every data older then 24 november 2013.
So, right now I am looking towards using your bot and I have several question I hope someone will answer
1) does Gekko counts broker commission while backtesting?
2) does it have any kind of a trailing stop?
3) in all the programming world I am slightly familiar with C++, nothing more, how long will it take me to implement those features listed above in the Gekko bot if they are not already on board? (of course I am not seeking for a precise answer, just an estimation like - a day, a week, several months?)
1. Gekko connects straights to exchanges, no brokers involved. Though exchanges also charge fees (which most of the time depends on the amount of volume). The backtest simulates buying / selling directly at the exchange. With Gekko you can configure this fee and the backtester will take it into account, the default is 0.6% (the default fee on mt. gox). 2. At this moment not, the version you are looking at only support the method EMA as described here. We are working on a new (but not yet stable) version of Gekko which currently supports DEMA, MACD and PPO and we are trying to include more asap. Gekko saved my life, thanks again for sharing. Amazing new developments, and great suggestions to include Kraken (really the most professional exchange so far) and Bitfinex too EDIT: Now I got many errors and warnings when installing Gekko on one laptop (after several entirely unsuccessful attempts) but after this most recent attempt it seems like it successfully installed, and it started calculating EMA on historical data. Regardless of that, should I try again until it's a totally clean install? I'm new to almost any type of coding, please help! Awesome thanks! -- I have spawned a mini chart website where you can watch the following markets in semi realtime (updates automatically about every minute): - bitstamp-USD-BTC - mtgox-USD-BTC - cexio-BTC-GHS - btce-USD-BTC - btce-USD-LTC - btce-BTC-LTC - btce-RUR-BTC - btce-BTC-NVC data.wizb.it. All the data is delivered by 8 gekkos (of the new version) running in parallel across all those markets. |
|
|
|
i've made a small web interface for it. screenshot: https://www.dropbox.com/s/od0ac7djvvdyrps/gekkoweb.pngsource: https://www.dropbox.com/s/54y2crazfnyghnd/gekko.zipi am not familiar with npm or node. so you have to install a few dependencies by hand (eg npm install express). there are currently some drawbacks: - portfolio is only updated after a successfull buy or sell - web interface does work as soon as a the first advice is made. - only ema does work as the web if does show some internal data from it i use it in "advanced mode" using data from mtgox and trading on mtgox and btce (but only with small amounts) i did not test it with other configurations, so use it at your own risk (i am not responsiple for any losses etc). as this is a pure personal project i dont think i'll make other extensions, but i am always open for suggestions regards flower Woow this looks great! I am pretty sure we can use a lot of your code and put it into Gekko (if you don't mind). So we are working on a new version for Gekko that has a plugin system which makes it easy to build stuff on top of Gekko. The demo server I built uses this system already. It also uses websockets in favor of a rest style API. Though I am pretty sure we can leverage your code quite a bit (especially the frontend stuff) Awesome stuff! |
|
|
|
|
Show Posts
