QFL Trade Opportunity - 1.30.2018 - ADAETH - Analysis

in #qfl7 years ago (edited)

Disclaimer: This is not advice, this is just information that can be consumed and used however you may wish - but it is not advice or guidance.

Preface:

See the bottom of the post for my generic methodology - which follows closely the QFL method of trading, however, I have (maybe) added some of my own rules. EDIT: I will post my general methodology/philosophy in a separate post.

Body:

Regarding the recent ADAETH hype, I did some analysis on this potential trade and it is as follows...

Results:

Opportunity percentage gain: 21.56% gain
24 HR BTC Volume: 674.99 BTC (at time of post)
Status of trade: Waiting for buy orders to execute...we'll see! If not, then I will just cancel and take my ETH back.

Chart:


Based on my method of creating a base, this is my base at .00054475
Keep in mind, I only set my alert for 7% below the base - which is 0.0005066 - at this time, I set my buy orders. If it goes above this, then I will cancel and take my ETH back and look at another trade.

Previous data shows me:

16.81% average/median crack
25.29% average/median crack to bounce
6 hours 30 minutes average/median time elapsed between low of crack and high of bounce

This would be a solid coin to QFL

Buy Orders:

Since there is a 16.81% average/median crack; I decided to create buy orders 12.6%, 14.3% and 15.1% below the base to try to "time" the "average/median crack" of 16.81% below the base as best as possible.
So my buy orders are at:
0.00047607 - 20% of order stack
0.00046691 - 30% of order stack
0.00046233 - 50% of order stack

Sell Orders:

Since there is a 25.29% average/median crack to bounce; I decided to create my sell orders at 19.36%, 21.94%, and 23.23% above the average/median crack to ensure I get them off.
So my sell orders are at:
0.00055863 - 50% of order stack
0.00057269 - 30% of order stack
0.00057972 - 20% of order stack

Again, my opportunity for potential profit is 21.56% on this trade.


My basic methodology I will post in a separate post.