I tried https://data.mtgox.com/api/0/bitcoin_tx.php

and pulled off a bunch of ids and couldn't find them in the block chain.

It's symbolic of a what happens if you don't change, adapt, and eventually evolve....you die.  Also they are traditionally considered slow, lumbering, ancient and doomed to die.

Too bad this guy didn't know to bring his dinosaur.

http://www.reddit.com/r/Bitcoin/comments/1x9gue/my_protest_at_mtgox_offices_5_to_7th_february/

I'm not sure what your point is.  If you believe this then it doesn't matter what age people are, they are all technically clueless whether they play angry birds or pong.  My point is the OP has a superiority complex about technology based falsely on his youth that is probably not going to go over well with people he wants to press his ideas upon.

If he regurgitates Ty13rDerden's points, they are going to turn glossy eyed and dismiss him because the only one that isn't just PR fluff is the rate of return on $15.  If they are shrewd investors then they'll probably keep him talking about Bitcoin to extract what he knows about it.  Then they would think, why don't I just spend the money and buy it directly myself? And that would probably return more than buying a bunch of gear to mine at the current difficulty rates while letting the OP take 75% to 90% for himself.

They only way to pitch this is to show them the mining profits vs. investment vs time and give them a good rate of return that would beat just buying bitcoin themselves with their own money.  If you absorb some of the initial startup costs and pitch in with some real money towards their real costs (rent), then they might start to listen.

Two things.  No one in their 40's knows technology in spite of the fact many grew up writing code in assembly on 8 bit processors with 16K of RAM?  Adjust your attitude or you won't get any respect if you don't give it.

Secondly, you're going to need to make it worth their while.  You want them to buy the equipment and then only give 25% plus you are going to run your own hardware and maybe give them 10%?  Meanwhile they are paying the rent and buying equipment for nothing?  If you want this to work, you should buy all the equipment, pitch in on rent, and promise them a larger share once the gear is paid off.  Otherwise your intentions to use them look pretty obvious.

I have also seen suspicious trades occur way off the mean like your chart shows a few price spikes, yet the volume in the order book seems unchanged.  It seems the only way for this to happen is for a coordinated buy/sell with someone in control of both accounts.  I have seen some exchanges (btc-e) report trades out of order (based on time stamp) and sometimes several minutes later.  I have not tried to track their order book vs. trades to see what gets filled and if it looks real.  There could also be a significant delay in the book depth as well.

The thing that is most suspicious about these events is the price seems unaffected.  If the book depth was truly eaten into then the price should rise at some point even if it is delayed.

Just now you are hashing?  Let me guess MD5?  No salts/peppers?

Anyway you have a great idea!  Invite a bunch of people to test your insecure service.  Experience a security problem, then have them bad mouth your service before you've even launched because you want to focus on your algorithm.

This smells like a scam to me.  You don't need users to test your trading algorithms.  That's the benefit of automation and the whole point of a bot.

Wow.  As someone who does website design SSL implementation is easy and should be a priority for this type of site.  If you don't have enough "resources" to do about 4 hours of work, then you're in trouble.

Secondly, what would an attacker steal that is valuable?  Crikey.  What world do you live in?  First off, it would crush your "business".  Secondly there are lazy users that reuse account names and passwords which could lead them to major theft on other sites, but then it appears you don't really care about their security anyway.  Based on that I have to assume your database is probably not even hashed or secured properly.

Lastly if someone steals your API keys they could sell off everything you have in your account just to drive prices down for their own amusement and possibly profit.

FWIW
http://www.reddit.com/r/BitcoinMarkets/comments/1rhtv1/eli5_how_do_cryptocurrency_pump_dumps_work_how_do/

I think this is different than interval to interval close-opens.  The trades that accumulate when the market is closed is dealt with the opening cross.  However I believe candles are supposed to line up with either the top or bottom depending on the trend interval to interval.

It seems to me method 1 would be more accurate and a time average seems more natural to me than discrete jumps.

I've been wondering what is the standard method for determining and open and close price for a time interval?

Here's two methods I've been investigating:

1.  Interpolate around both start and stop points to get estimated price at exact time intervals.
2.  Take first and last trades inside the time interval as open and close

The first method can be slower because you need to bracket the intervals and sometimes trading can be slow so it takes a while to determine the close price.  However this seems like a more realistic way to estimate the end point of the price during that time interval.

The second just shifts trade values in time (which is faster) to estimate the open and close.  The problem here (and I've seen this on some internet charting tools) is that the intervals might not match up between close and open of the next interval.

Thanks for taking the time to clear that up for me.  I understand why the open/closes/etc. are not working for me when I compare them.  And now I understand better how your cool charts work.

I am curious how you group the trades.  I've found 3 cases that occur with BTC-e:

1.  Multiple trades at the same time with same time stamp.  (Just add volumes together.)
2.  Multiple trades at different prices with same time stamp. (I have just been sequencing them assuming that the newest trade is always on top even if the time stamp is the same).
3.  Multiple trades at different prices and same prices all with the same time stamp (confusing but I only combine volumes of trades of the same price that are in a sequence together, if there is a different price in between the two same prices I treat them separately).

Are you doing something different to group them and which time stamps do you designate to them?  I have been trying to preserve their time data 100% because I re-sample the values with linear interpolation to even out the time base into a per second basis to do my time averages.  Is this a good approach?

There is a bug somewhere.  The volumes seem to get swapped around and the time stamps are different.  And there are trades that I don't know where they came from.  I don't have time to go through them line by line, but all the data is posted if someone wants to try.

The second question is BCW using the API or are they getting a different feed from BTC-e?

Wow it is worse than I thought.  Their own reported trade data is all messed up.  I captured their own "trade" list and the API and their chart values all at once.  Since their chart data seems to be wrong too this might be a systemic problem rather than just how bitcoinwisdom.com prints out the display.

From Chart 3m period
17:39:00 - 17:36:00
open: 23.55
High: 23.60
close: 23.58  (not according to btc-e API)
Low: 23.50 (not according to btc-e API)

From the chart's trade list it never hits 23.50, or 23.58 during this time frame. 

For some reason BCW is modifying the time stamps and it appears their volume data is often very wrong and there are missing trades!  And I understand combining trades at similar times at same prices, but changing the times?

From bitcoinwisdom's trade window:
17:40:11 23.551 70.6785 (real time stamp from API shows 17:39:59)
17:39:59 23.551 0.25 (time stamp shows this should be 17:39:56 )
17:39:56 23.551 0.4008 (this is two trades combined that were 1 seconds apart)
17:39:52 23.551 0.2004 (really 17:39:49)
17:39:49 23.551 0.2004 (??!  This trade never occurred!)
17:39:44 23.5999 1.18955 (at 17:39:44)
(missing a trade here?  17:39:44  23.511 0.98915 )
17:39:44 23.551 0.25038 (is this the missing trade with wrong volume?)
17:39:37 23.5999 0.23395 (really is at 17:39:42 and volume is wrong!  0.25038!  See above trade vol.)
17:39:21 23.6 0.2004 (volume is wrong here too)
17:39:18 23.6 70 (never happened at 70 shares....errors go on and on)
17:39:15 23.551 38.2491 (vol is really 63.2996)
17:38:28 23.6 0.38036
17:38:11 23.6 0.11827
17:37:38 23.6 0.15
17:37:34 23.6 0.32719 (this volume actually traded at 23.5996)
17:36:56 23.5996 3.44501
17:36:21 23.5997 0.1
17:35:59 23.5998 0.10360

From BCT-e api for comparison:

{"date":1389757199,"price":23.551,"amount":70.6785,"tid":27194971,"price_currency":"USD","item":"LTC","trade_type":"ask"}, ** 2014-01-14 17:39:59 **
{"date":1389757196,"price":23.551,"amount":0.25,"tid":27194970,"price_currency":"USD","item":"LTC","trade_type":"bid"}, ** 2014-01-14 17:39:56 **

{"date":1389757192,"price":23.551,"amount":0.2004,"tid":27194965,"price_currency":"USD","item":"LTC","trade_type":"bid"}, ** 2014-01-14 17:39:52 **
{"date":1389757191,"price":23.551,"amount":0.2004,"tid":27194964,"price_currency":"USD","item":"LTC","trade_type":"bid"}, ** 2014-01-14 17:39:51 **

{"date":1389757189,"price":23.551,"amount":0.2004,"tid":27194963,"price_currency":"USD","item":"LTC","trade_type":"ask"}, **  2014-01-14 17:39:49 **

{"date":1389757184,"price":23.5999,"amount":0.2004,"tid":27194962,"price_currency":"USD","item":"LTC","trade_type":"bid"}, **  2014-01-14 17:39:44 **

{"date":1389757184,"price":23.551,"amount":0.98915,"tid":27194961,"price_currency":"USD","item":"LTC","trade_type":"ask"}, **  2014-01-14 17:39:44 **

{"date":1389757184,"price":23.551,"amount":0.2004,"tid":27194960,"price_currency":"USD","item":"LTC","trade_type":"ask"}, **  2014-01-14 17:39:44 **

{"date":1389757177,"price":23.5999,"amount":0.25038,"tid":27194948,"price_currency":"USD","item":"LTC","trade_type":"bid"} **  2014-01-14 17:39:42 **

,{"date":1389757161,"price":23.6,"amount":0.233955,"tid":27194943,"price_currency":"USD","item":"LTC","trade_type":"bid"},{"date":1389757158,"price":23.6,"amount":0.2004,"tid":27194940,"price_currency":"USD","item":"LTC","trade_type":"bid"},{"date":1389757155,"price":23.551,"amount":63.2996,"tid":27194939,"price_currency":"USD","item":"LTC","trade_type":"ask"},{"date":1389757155,"price":23.552,"amount":6.5,"tid":27194938,"price_currency":"USD","item":"LTC","trade_type":"ask"},{"date":1389757155,"price":23.552,"amount":0.2004,"tid":27194937,"price_currency":"USD","item":"LTC","trade_type":"ask"},{"date":1389757108,"price":23.6,"amount":38.2491,"tid":27194927,"price_currency":"USD","item":"LTC","trade_type":"bid"},{"date":1389757091,"price":23.6,"amount":0.380361,"tid":27194925,"price_currency":"USD","item":"LTC","trade_type":"bid"},{"date":1389757058,"price":23.6,"amount":0.118274,"tid":27194894,"price_currency":"USD","item":"LTC","trade_type":"bid"},{"date":1389757054,"price":23.6,"amount":0.15,"tid":27194892,"price_currency":"USD","item":"LTC","trade_type":"ask"},{"date":1389757016,"price":23.5996,"amount":0.327193,"tid":27194874,"price_currency":"USD","item":"LTC","trade_type":"bid"},{"date":1389756981,"price":23.5997,"amount":3.44501,"tid":27194779,"price_currency":"USD","item":"LTC","trade_type":"bid"},{"date":1389756959,"price":23.5998,"amount":0.1,"tid":27194723,"price_currency":"USD","item":"LTC","trade_type":"bid"},{"date":1389756945,"price":23.5998,"amount":0.103609,"tid":27194713,"price_currency":"USD","item":"LTC","trade_type":"bid"},

I've tried a few time slices and the example I posted is typical.  The BCW site shows numbers that are not in the API trade data.  However I have not checked it against other time intervals.  Perhaps a 3min interval posted at 9:45 does not mean 9:45 to 9:42 but something else.  Since I've run into a lot of weird problems with the btc-e trade data I thought someone here might be familiar with it or BCW methods.  Maybe I should run it over 1 min intervals to reduce any errors in how the time frames are defined.

I'm using python with a sqlite3 database and matplotlib modules.

I am looking for something to test my numbers against and what you describe is what I'm doing (see data in first post).  But it doesn't appear to be how BCW does it.  Since I don't know technical trading I'm trying to figure out what is going on.

Also the btc-e api has many issues that are complicating the calculations so I'm trying to see how pros like BCW handle the data.  It seems like the example I'm illustrating with the raw data vs. their charts shows that they are doing something that I don't understand or are getting data from somewhere other than the API.

I wrote my own program to pull the trade data for the selected period, which is what you see in the orginal post.

@DCP.  I'm really interested in understanding what is going on with the TRADE api vs bitcoinwisdom and how the calculations compare.  It appears they are not working from exactly the same data, or I don't understand their algorithm correctly.  I could be looking at the time periods wrong or there could be something else I don't know about going on.  So I thought I would ask if there are others who have noticed discrepancies or have done these type of calculations before for some insight.

Thanks.

Thanks for getting back to me.  I've been doing a lot of work with their API.  I'm pulling these trades I posted (for LTC) via https://btc-e.com/api/2/ltc_usd/trades

I can't seem to duplicate some of BCW numbers for their time intervals as you can see by my example I posted.  Is it correct to assume a 9:45 data point spans trades between 9:45 and 9:42?  I took a screen shot from BCW from the above example and I've attached it:

http://i.imgur.com/lK7WTh0.png

I also can not duplicate their indicators.  Are their parameters based on intervals?  For example a SMA of 10/20 on a 3min chart is that 10 moving sample once every 3 minutes or are they doing something different?  Their lines are much smoother than I am able to duplicate for the same settings.

I've been working on a trading bot for BTC-e and I was comparing 3min intervals with bitcoinwisdom and my software.  I noticed the bitcoinwisdom (BCW for short) produced some odd numbers.

For example here is the trades that take place according to btc-e's API:

date               timestamp      price      trade id   seqId      amount
2014-01-13 09:41:59   1389642119   23.0611   27081938   42874   6.4243
2014-01-13 09:42:01   1389642121   23.0045   27081939   42875   7
2014-01-13 09:42:02   1389642122   23.09      27081940   42876   0.22634
2014-01-13 09:42:12   1389642132   23.09      27081942   42877   0.1
2014-01-13 09:42:12   1389642132   23.09      27081943   42878   0.1
2014-01-13 09:42:59   1389642179   23.1378   27081972   42879   1
2014-01-13 09:43:39   1389642219   23.1376   27082018   42880   0.64829
2014-01-13 09:43:39   1389642219   23.1377   27082019   42881   11.2153
2014-01-13 09:43:50   1389642230   23.1373   27082027   42882   100
2014-01-13 09:44:37   1389642277   23.0046   27082041   42883   0.64826
2014-01-13 09:44:54   1389642294   23.0046   27082053   42884   0.134273
2014-01-13 09:45:18   1389642318   23.0045   27082064   42885   0.922397

These time bracket the interval from 9:42 to 9:45 for computing a 3min interval.  If you compare this to BCW report for the same time (9:45 with 3min interval)

open   23
close   23.1
high   23.1
low   22.97

While it seems ok until the Close and LOW, which are not correct.  I've noticed other odd things on BCW like the volume not adding up correctly.  Has anyone spent time looking at BCW's numbers?  Is there something I'm not getting here?