
Price Predictive innovation in Orderbook states analyses. US session on $QQQ and #lowfloats l criticism of common reads l not financial advice.
Grand Casablanca, Morocco
Joined April 2024
- Tweets3.7K
- Following690
- Followers374
- Likes333
Replying to @R3G5B7 @AndrewTradesNQ
1. There are no dark pools in futures
2. I don't use "warm maps" and my intention from reading orderbook is not to see where buyers are because buyers location doesn't impact price.
3. I am a loving person by nature but I hate it when poeple on the one hand promote and execute on prop-firms like Vest which is at the same time a prop, a broker, and exchange executing orders against client orders. And on the other hand, wonder about conflict of interest in sweeping retail. $QQQ
Option gamma is not predictive simply because executed orders bear no significance in predicting future prices. And that is if the many farfetched and imaginary assumtion of GEX guys are true. Like heding in an underlying say a $QQQ, $BTC or a $TSLA .Problem is you still need to make sure when the hedging must occure, how the hedging must occut and where the hedging must occur, how much of it must occur and is it that hedging and only hedging alone that moves prices. So volume based traders are wrong for normal reasons. GEX guys even more wrong than volume based guys.
Replying to @TraderPoko
Option gamma is not predictive simply because executed orders bear no significance in predicting future prices. And that is if the many farfetched and imaginary assumtion of GEX guys are true. Like when the hedging must occure, how the hedging must occut and where the hedging must occur, and is it that hedging and only hedging alone can move price. So volume based traders are wrong for normal reasons. GEX guys even more wrong that volume based guys. Here is recorded evidence of price moving on zero volume. Where is the hedging in this move?
Replying to @Abu_Cartel
Not really...
1. here is video recorded evidence of a 10% move occuring in miliseconds on no volume. No limit orders to execute.
2. You provided one senario to accomulate a large position. I have video recorded evidence of large positions executing at the same / within a tight price range. That is because the liquidity at that time event was such that it was capable of absorbing that large order. Likewise, a massive order is also exacutable at favorable prices or any which other way.
3. The fascination with large orders talk is vacious because that's not what moves price and definetely not what can be used to predict it. The only thing that can is the actual liquidity state of the day. And that non-agentic and need to be studied as is with no further interpretations or goals.
Heatmap display is the worst introduction to orderbook reading especially on $BTC . First mistake
1. If dense limit areas represent support and resistence why do you need to add absorption and pull and orders adding?
2. Why would dense limit areas represent a magnet and repeller at the same time. Logical contradiction.
3. The entire display is made out of repeated same unimportant information. Why you need adsoption indicator of you have volume bubbles and volume profile. Why have a price ladder on the side if you already print limit orders on the map.
4. The entire rationale behind build similar heatmap platfroms is flawed because it tries to make orderflow fit into the box of a static technical analysis style world view when in fact orderflow is dynamic in time and sensitive to data completeness and quality. When $BTC and crypto there is no wildely known quality datafeed provider.
Replying to @VestExchange
@VestExchange is yet another American scam platform that claims having no rules to payout. But as soon as their algos spots a you are trading successfully,once you ask for payout, they ban you as per their terms of use bellow.
The Vest team has reviewed the recent posts and will be enforcing an affiliate ban for Lanto. Under our guidelines, earned commissions will be paid but Lanto is no longer eligible to receive commissions going forward. We appreciate the cooperation from @thebrianstonk in enforcing this via their shared entity code.




