How's this for small:



It runs much cooler than the old 65nm BFL hardware I'm going to finally retire after the cold winter months are done with, and without all the hardware errors I had on the BFL --- this is stable at 107-119 GH/s mostly, even when I'm playing flappy bird...

Most of what I've been doing has been OS / rom hacks and stuff like removing the bamc it came with and clearing out to make room for more games and other non-mining stuff.

It might be back to a broken state^* soon.

https://bugs.gentoo.org/show_bug.cgi?id=531634 (new tracker ID for proposed gentoo ebuild)

---

^* broken as defined by the original poster of this thread.

"An easy way" --- Actually, there is -- the only thing needed is an API wrapper.

Both askmike's current design, as well as my fork of Gekko is modular, so all the logic to trade on one exchange with a particular method works the same no matter which exchange or which currencies are being used. (Example: Originally the bot was developed for mtgox, but gekko works the same no matter what API wrapper you use.)

The code to talk to the exchange (API wrapper) really doesn't do much other than providing the abstraction logic which translates the internal names used in gekko's code for doing different things (buy, sell, check balance, etc. etc. etc.) to whatever the names might be for how the developers at the exchanges decided to name it in their API.

Actually, here's a flowchat diagram thingy which might help to understand the concept:

Yeah, for FIAT trades it tries to increase your portfolio value in dollars or whatever currency you're using... It still shouldn't lose so much money like that. Maybe it was because the exchange you're using has high fees? Buy and hold (just holding BTC since the value has increased over the years) is often better in some cases though, particularly in cases where the bot parameters aren't tuned right.

Speaking of fees...

I'm pretty sure askmike never added any logic which checks to make sure the hypothetical gains will be higher than whatever fees the exchange is charging. Actually, this is a major issue since many exchanges charge a percentage based on the size of your trade, and askmike never added a feature to gekko's engine to have the option to do a smaller trade than "buy/sell as much as possible"

I had a talk with askmike the other day on IRC and this came up:


^ we were actually looking at a bug unrelated to fees...
Either way, he's back so there might be new features coming to askmike's gekko repo.

Not sure, I've never seen that error on mine.


^ What version are of node.js are you using?

I'm certain that gekko runs fine on the latest version of node.js built with a recent compiler. With the latest version it's very stable for me (I compiled my node.js binary using gcc 4.9.2... I think an error like that could possibly be related to the ancient compiler toolchain the ubuntu devs use to build packages)

---

Edited to add:

I feel no remorse about disliking ubuntu, but it's not your fault they ship an ancient version of node
(I just checked -- it looks like ubuntu really might include node.js version is v0.10.25 or older...
That's from nearly a year ago so please don't use that with gekko)

If you don't want to manually build node.js from source, there's a handy tool called "node version manager"

Official README for NVM

^ TL;DR

... you can install NVM like this if you just want to use it and don't care how it works:


Afterward, the relevant instructions are here:

"usage" section of the readme

---

I'm sorry for almost saying bad things about ubuntu and not actually helping. That wasn't cool.

... I haven't personally found NVM to be a helpful tool because I just build mine from source and it's easy to get the latest version with gentoo. Ubuntu makes it harder, but there's NVM specifically for making it easier to get a non-ancient version on distros which don't provide a non-ancient version, so hopefully this info helps.

What I think happened was that the market conditions were in a state where your gekko was trying to buy more bitcoin but your portfolio was out of FIAT currency and so it couldn't buy more... I'm pretty sure whenever it says "buy" it's trying to spend money to buy bitcoin.

That specific error message is because there's a minimum amount for trade, but you didn't have enough funds or assets available in your portfolio on the exchange. You can look in exchanges.js for the minimum values on whatever exchange(s) you're planning on trading on.

I don't have any advice on how to configure DEMA...

I recommend switching to MACD.

The standard values which a lot of people have good luck with is:

Short @ 12
Long @ 26
Signal @ 9

If you want to see what those values do, a good way to visualize and look at historical data is by looking at old charts on a site like bitcoin wisdom.

https://bitcoinwisdom.com/markets/bitfinex/btcusd << the default MACD settings are 12 26 9 so just turn on the MACD indicator and have a look (it'll show up at the bottom once you enable it)

Note: bitfinex currently looks like it might be the exchange with the most volume at this time...

askmike just accepted a pull request for bitfinex support too, so you can even use it with gekko

I hope this info helps.

Yes, that's fine. The technical skill required to add it wouldn't be hard.

However...

http://www.gnu.org/licenses/index.html


Copy of the AGPLv3 license as included in my fork

TL;DR / Translation: Please don't steal it; I want my work, and any modifications or derivative version to remain open source...

Specifically, I mention the AGPL license because I expect application service providers who use a modified version of my work comply with the license, and the source code should remain available for any modified versions if it was changed in any way for use as a "hosted application" (cloud service or any other term with a similar meaning)

---

Though as far as my own version is concerned, the modifications for "only reinvest or otherwise buy" could be made configurable. The hardcoded change was a bad idea.

My bad. Sorry about that.

Yeah I know... None of the methods in askmike's version check to make sure trades happen at a better price than the average price over the past periods --- That's why I wrote a trading method which actually tracks to make sure the trades happen at a good price:

The "stats window" functionality of the zero method is explicitly to make sure the price isn't worse than the average trading price over the past periods (candles)

Here's an example of the remote tracked repositories (on github) I've been using for development of my own fork...


^ That "pull" command in the example would fetch the latest version from my own fork.

WARNING:

If you do something like that you're pulling the version from the repository and overwriting whatever you have locally. This will overwrite your config.js and probably shouldn't be used on a live gekko installation (running OR stopped, either one is bad and it doesn't matter which) unless you know how to use git well enough to disable synchronization of certain files...

Your best bet is probably just to download a ZIP from here:

https://github.com/kuzetsa/gekko/releases

Or alternatively, one of askmike's:

https://github.com/askmike/gekko/releases

... oh, that's weird. There aren't any releases / tags in there for some reason.

---

...Actually it looks like he's back, and maybe even accepting pull requests?

https://github.com/askmike/gekko/commits/master

^ maybe he's working on it again.

...I don't know?

Yes, that's normal. That's the way askmike designed it.

---

Someone made a node.js wrapper for the REST APIs for coinswap, but I don't have an account with that exchange so I wouldn't be able to add it to gekko. If anyone wants to look into it, try and add (or find) a NPM module and see if they can get it working in gekko:

https://github.com/defcronyke/NodeJS-Coin-Swap-v2

No worries.

Mine isn't the only fork which is still being updated. Mostly I've seen a lot of other people who have focused on adding new features and exchanges, so hopefully because it's open source, people will continue to share their changes in good faith, and hopefully you'll find a version that does what you want.


Note that most of the active forks are from after askmike left around 8 months ago.

I'm gonna reply to this in reverse order:

#3 When I mentioned server administration, I meant for the purposes of reliable, uninterrupted operation. Technically you could run it on your laptop or home PC or whatever since it's based on node.js and doesn't actually need to be a server environment. The main issue is that the bot REQUIRES uninterrupted historical price data, and if there are any gaps because you turn it off it has to start over and gather another N minutes or hours of non-corrupt gapless history before it can start trading or giving advice again (50 hours for askmike's version, or 39.083 hours for mine --- both versions are configurable, but that's the default for the latest version)

#2 I left all of the original methods from askmike's version, but I added a "zero lag" method which is functionally equivalent to work done by Patrick Malloy from at or around the year 1994 (I changed to a default 1 minute intervals while developing this) Most of the trading methods on gekko are based around math which can be used at 1 minute intervals just as easily as 1 day intervals.

#1 -- I haven't tested any exchanges other than cexio. You can probably use Askmike's version. I think it still works, but there's just a bug or two which isn't in that version.. Another thing to consider is that askmike's version uses a default setting of 60 minute (1 hour) candles, and 50 hours worth of history before it starts trading (the latest version of my fork uses less history, but it's been tested and is based around 1 minute candles and can react faster)


Warning: I decided to intentionally break the code related to SELLING assets. No matter what trading method you use, my version waits for a good price and then buys new GHS (or other assets / currency pairs)

... I made this decision because GHS will continue to mine new coins if you hold. This difference from askmike's version can be made configurable, but for now it's hardcoded. Basically, my version won't work as you expect if you need a bot which both can buy AND sell... At least not until the "sell" logic is fixed (by making the behavior configurable, probably. A lot of the bugs in askmike's version were because each time a change was made, it only ended up tested with 1 or 2 trading methods or exchanges, and caused something to break for other usage cases than the one being tested.)

Mainly it's that askmike's version hasn't been updated (bugfixes, features, or otherwise) in over 8 months. Askmike left and hasn't returned, and hasn't been accepting pull requests or otherwise given anyone commit access to the repo. When I forked gekko a few months ago, I was doing it because I wanted to fix bugs and add features --  One of the main bugs I fixed was related to how the history is stored and used when a history size of greater than 24 hours is used. (askmike's version from 8 months ago had a major bug and can't correctly load history databases if a window of larger than 24 hours is needed)

WARNING: I've only been supporting cex.io automatic reinvestment to buy more GHS. The way I redesigned is for a reinvestment-type "buy and hold" strategy. I've been doing this in my spare time, but the latest version is finally stable and works as intended so I can probably move on to adding other strategies than the current "buy and hold" reinvestment code.

Last difference is that all the changes in my version are AGPL instead of MIT license. Moving forward I'd prefer to keep my fork as AGPL licensed. I really believe in the idea of making sure people have the source code to their trading engine ESPECIALLY in cases where it's hosted as a managed service. (not everyone has the experience or technical knowledge to run and maintain their own server, but that's no excuse to deny them access to audit the changes made to the source code. This is an important feature of the AGPL license which I strongly believe in)

There's a new version...

• https://github.com/kuzetsa/gekko/releases/tag/config_fix

currently same as:

• https://github.com/kuzetsa/gekko/releases/latest

---

^ that new line / comment is a hint which should hopefully help to prevent confusion and misconfiguration

Not much has changed, other than making sure that the settings it ships with are sane and actually work right.

---

The exact changes for anyone who wants to see what they're getting:

https://github.com/kuzetsa/gekko/compare/kuzetsa:427e0373d96a864d3afb7e4c0d8c616c36f0552a...config.fix

No.

You do not need that.

That is not a dependency for gekko.

---

Of the things which ARE dependencies for gekko, you shouldn't even be manually installing any of these:


^ if you're using gekko, all you have to do is unzip the package and type this command:


It installs all the dependencies for you.

The reason for using the "npm" command is because the node.js programming language comes with its own package manger.

The "node package manager" is what npm stands for, hence the command you would use is called: "npm install"

The dependencies are handled automatically because they're configured in the package.json file for use with the install command (you shouldn't need to automatically install any of those in order to use gekko. Just use "npm install" and you're ready to go)

gekko with a standard node.js installation has never required sudo.

ubuntu is doing something wrong to break your node.js if it disabled the node command and changed the command to nodejs

perhaps you should check and confirm that ubuntu isn't adding "node" to your environment / path...

I don't use ubuntu, nor do I know how they like to do things otherwise I'd file a bug with your distro.

---

commands to check and make sure it's in your path:


^ I have no idea what that "nodejs" even is, but if it requires sudo to use I'd recommend fixing your path
(and/or possibly uninstalling the ubuntu nodejs all together, since it's naughty and demands more privileges than it needs)

you SHOULD NOT need to use sudo.

If you chose to use gekko via the the ubuntu-provided "nodejs" command, you're doing so at your own risk.

either a mysterious delay happened with github or your local git repo hadn't been refreshed, or maybe some other reason it wasn't showing up when you looked???

it looks fine to me:


https://github.com/ckolivas/cgminer/releases/tag/v4.7.1

Yes, I can see now why you mentioned potential merge conflicts...

Initially I was more concerned with making it as easy as possible to identify the purpose of various sections of the patch before any attempts could be made at a non-monolithic version.

Even if it's just for auditing and reverse engineering purposes, this still helps a lot.

Thanks.

I haven't checked yet, but is this most of the relevant code from your patch?

https://github.com/luke-jr/bitcoin/compare/bitcoin:0.9.3...0.9.x-ljr?diff=unified