Well this sucks a bit.

So, care to share how much of the 'would-be-dividends' are actually being kept now as a result of this impromptu payout limit?

Well, one reason mine isnt doing well is that it was not intended to be running on a 4 hour time scale.  I had it running on 15 minutes specifically.

I'll throw this mess into the pile of fun 

https://cryptotrader.org/backtests/etFTmediwTGYDBfed

im in again.

lol  ouch 

I like to watch the 15 minute charts, but base my technicals on 1 or 4hr.  9/21 EMA -> 36/84 sort of thing, using a multiplier. 

the difficulty with beating the market currently is the fact that most of the substantial jumps and losses were caused by huge volume swings with no real precursors.  There's no good way to predict someone coming along in a slow moving market and in one swoop making a huge purchase/sale.  No trend gets established, just BAM, huge change.

the sharper the angle of the upswing or downswing, the harder to 'trend'.  the more curvy, the easier.

the shorter your timescale, the more you can see the curve to a mass purchase / sell, but then you also subject yourself to other issues.

tis a balance between looking at big picture, missing finer detail, vs looking in close, seeing details, but also being thrashed by false signals



If you click on the "settings" tab next to the "log" tab, you will see that the bot defaults to 0.55 trading fee. One step up from the 'base' gox fee.

That buy'n'hold link appears to actually be going to the EMA crossover example.

Edit:  LoL buy'n'hold looks like it'll be the winner yet again... unless we get a big slide back down.
2013-08-18 17:00 Simulation started. Balance: 1000.00 USD
2013-08-18 17:00 BUY 8.770 BTC at 113.39
2013-08-27 16:00 Simulation completed. Balance: 8.770 BTC (1141.63 USD)

anyone else having an issue getting the graphs to display?  It does the loading circle animation for me, but when it finishes, it's still just a blank graph section.  the code and backtest simulation areas appear working, just the graph is broken.

edit : problem appears to have gone away.  havent had any issues the past couple days... except with my fail contest entry :-P

for what it's worth, the following is the same as my actual entry for the contest, but with added round debug info.

https://cryptotrader.org/traders/q75spqHf6SWTDaid9

Strategy is the same, but I found being able to step through the rounds and review what it was doing for each was enlightening.

example:
013-08-19 09:30 Trader started. Balance: 1000.00 USD
2013-08-19 09:45 ROUND ==> 1 | HOLDING: usd=1000  btc=0
2013-08-19 09:45 cciValue =13.65474704470624
2013-08-19 09:45 highRocValue = -8.403361344537785 | lowRocValue = -9.888532448760534
2013-08-19 09:45 high =118 | low =117.25 | close =117.39002
2013-08-19 09:45  @ @ hold  cci @ @
2013-08-19 09:45 *************
2013-08-19 09:45 *************
2013-08-19 10:00 ROUND ==> 2 | HOLDING: usd=1000  btc=0
2013-08-19 10:00 cciValue =9.35064812180757
2013-08-19 10:00 highRocValue = -9.075714285714298 | lowRocValue = -7.711210914329358
2013-08-19 10:00 high =117.91999 | low =117.1 | close =117.25
2013-08-19 10:00  @ @ hold  cci @ @

I'm enjoying seeing the variety of styles people use, both from a technical standpoint, and methodology standpoint.  Also nice being able to see real examples of specific methods in use.

Where's the case from?  Didn't see it on adafruit.  I like the buttons 

https://cryptotrader.org/backtests/qyYudoimmtTEupchJ


CCI enable with [high|low]-value ROC trigger

mostly learning how to use talib functions in coffeescript :-)


edit : damn    forgot about including a method for stop-loss lol

As far as I understand it, all addresses 'already exist', so to speak.  It's just a matter of having a private key.  If you 'generate' a key, youre not magically making it appear, youre just doing the math that gives a private key that happens to correlate to whatever its address is.  Same way you could just smash in some keys (within constraints that would make a valid address) and send coin off to the nethers of a random address, lost unless someone happened to come upon a private key for that address.  'Generating' a vanity address is really just spam checking random address/private key combos until you happen to find an address you deem interesting.

I'll throw my mess in again, whether or not I get it cleaned up at all 

Oh, dont interpret my post as some form of 'pro-bitvanity'.  just reports of the issue are enough to make me avoid it like the plague.

That being said, I think vanitygen is a different author, different program.  I dont keep any btc on the machine I use to generate vanity addresses, but I do have a wallet on it, and havent had any issues.

as always, always a good idea to review something yourself (like source) to evaluate the risks.

im definitely not an 'expert' in code review, but https://github.com/samr7/vanitygen seems ok.

lol not gonna lie one bit... I kinda feel a bit dense and ham-fisted comparing mine to the others submitted 

Some day I'll write decent code... some day

Any idea how to stop the vanity miner from stopping on this error?
It runs for a while, but inevitably, it halts.
Win7 64-bit.  driver @ 320.49


C:\Users\xxxx\Desktop\vanitygen>oclvanityminer64.exe -u https://vanitypool.appspot.
com/ -a 1NfaEu8CC84dCpJnQEwjoLFvuE57UbZpAU
Searching for pattern: "17Strykes" Reward: 0.088000 Value: 0.000006 BTC/MkeyHr
Difficulty: 50656515217834
[22.58 Mkey/s][total 192538214400][Prob 0.4%][50% in 17.9d]                    clWaitForEv
ents(NDRange,1): CL_OUT_OF_RESOURCES
clEnqueueUnmapMemObject(0): CL_INVALID_COMMAND_QUEUE
vg_ocl_context_callback error: CL_INVALID_COMMAND_QUEUE error executing CL_COMMAND_UNMAP_M
EM_OBJECT on GeForce GTX 570 (Device 0).

Device: GeForce GTX 570
Vendor: NVIDIA Corporation (10de)
Driver: 320.49
Profile: FULL_PROFILE
Version: OpenCL 1.1 CUDA
Max compute units: 15
Max workgroup size: 1024
Global memory: 1342177280
Max allocation: 335544320
Device: GeForce GTX 570
Vendor: NVIDIA Corporation (10de)
Driver: 320.49
Profile: FULL_PROFILE
Version: OpenCL 1.1 CUDA
Max compute units: 15
Max workgroup size: 1024
Global memory: 1342177280
Max allocation: 335544320
clEnqueueMapBuffer(4): CL_INVALID_COMMAND_QUEUE
ERROR: Could not map row buffer for slot 0
ERROR: allocation failure?

Ok, I'll throw mine in now.  Didnt have as much time as I thought to play with it   

Anyway, half arsed attempt at following a really short ema slope's rate of change, and direction change.
Thought process was the rate of increase / decrease would have to slow down before it switches direction.  Watch for the slow-down in the rise or fall and buy/sell when the direction change happens.

30 min window.

https://cryptotrader.org/backtests/dQy9CXc5CLiqadvsn