Created at 8pm, Jan 4
DnzDGRLOther
1
Price Action Concepts
d38K0uIkiky82RZ90wPauPq4hoT-eSKgzprMtQ2wMdM
File Type
PDF
Entry Count
32
Embed. Model
jina_embeddings_v2_base_en
Index Type
hnsw
Looking for Bullish Orderblocks: 1. Ensure that HTF M.S (according to your timeframe matrix) is bullish (explained at the end of the doc) 2. Start looking for areas of interest in your directional bias (S/R levels) 3. Drill down to your entry TF and begin to look for orderblocks around those levels 4. A bullish OB is identified as the last down candle before the impulsive move up IT HAS TO FIT THE DEFINITION a. b. Once it meets the basic criteria you validate it with the characteristics stated above
id: 68ecca5b6eb5e6e208f92156d33baae2 - page: 11
Looking for Bearish Orderblocks: 1. Ensure that HTF M.S (according to your timeframe matrix) is bearish (explained at the end of the doc) 2. Start looking for areas of interest in your directional bias (S/R levels) 3. Drill down to your entry TF and begin to look for orderblocks around those levels 4. A bearish OB is identified as the last up candle before the impulsive move down IT HAS TO FIT THE DEFINITION a. b. Once it meets the basic criteria you validate it with the characteristics stated above But this isnt as easy it seems; the validity of the OB is key to its execution. Lets add some visual examples and further develop on the criteria
id: 9af389a4f11ef0a489874798773077d2 - page: 11
Valid Orderblocks: What makes this Orderblock valid? 1. 30k is a SSR for BTC a. That makes it a high-interest level 2. It was the last down candle before the impulsive move up that broke market structure 3. The rally (imbalance) away from the OB is larger than 2x the OB a. This adds tremendous interest to the OB Once it meets the validity criteria, we look forward to executing it Invalid Orderblocks: What invalidates this Orderblock? Even though it fulfills most of the criteria, the OB isnt the last down candle before the impulsive move up. As you can see, in the next candle price went lower than our marked-out OB, this automatically invalidates the OB. However, there certainly was a rally after that down candle, so we proceed to do the following: 1. Drill down to LTF to find the correct OB that preceded the move 2. Mark it out This was on CRV/USD 1D Chart, so we proceed in the following order: 1. 12h 2. 8-6h 3. 4h
id: f036b1ef65d51aeaedef568e27d2255e - page: 11
Tw: mgvcapital We drilled all the way down to the 6H chart until we found the correct Orderblock. It previously met most of the criteria, but it was invalidated due to the lower wick in the following candle. Now that we found ourselves a proper Orderblock, the next question is: how to execute them? Our orderblock should contain a considerable number of orders waiting to be filled. If the orderblock is valid then price shouldnt be able to go lower than our marked-out zone. Therefore, here is one conservative way to play Orderblocks: Bullish OB: entry at the top of the OB, invalidation below the lowest price of the OB o Target next swing highs / liquidity areas Bearish OB: entry at the bottom of the OB, invalidation above the highest price of the OB o Target next swing lows / liquidity areas This is how we would wait for price to retrace with our limit orders set.
id: 19c5d1a90ba03d43d0f6e41d576ba845 - page: 11
How to Retrieve?
# Search

curl -X POST "https://search.dria.co/hnsw/search" \
-H "x-api-key: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{"rerank": true, "top_n": 10, "contract_id": "d38K0uIkiky82RZ90wPauPq4hoT-eSKgzprMtQ2wMdM", "query": "What is alexanDRIA library?"}'
        
# Query

curl -X POST "https://search.dria.co/hnsw/query" \
-H "x-api-key: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{"vector": [0.123, 0.5236], "top_n": 10, "contract_id": "d38K0uIkiky82RZ90wPauPq4hoT-eSKgzprMtQ2wMdM", "level": 2}'