Called this one early at 16k. Decided to ape the dip too, figuring it'd help stabilize things, but ended up taking an L on that position. Only made under 1k total, nothing significant. My wallets are public for anyone to verify.
The token actually dumped to 14k when the team moved coins—they admitted it themselves. Tried some top buys to support the price action, but the math didn't work out in my favor. Still, watched it recover to 54k eventually. 16k to 54k wasn't a bad call on timing, even if the execution got messy.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
12 Likes
Reward
12
4
Repost
Share
Comment
0/400
PriceOracleFairy
· 9h ago
ngl the 16k→54k call was clean but that "support the price" part got me thinking... team dumps, you catch the knife, market recovers anyway. classic market inefficiency theatre lmao
Reply0
CryptoTarotReader
· 9h ago
Damn, daring to buy the dip at 16k, you must have a huge heart... Turns out I still got trapped, haha
View OriginalReply0
TheMemefather
· 9h ago
From 16 to 54, the perspective is correct, but that middle L is a bit uncomfortable.
View OriginalReply0
DefiOldTrickster
· 9h ago
16k precise bottom-fishing, 54k top-selling, this wave of timing is extremely tight... Unfortunately, the division of shares in the middle was messed up, and it's not always possible to bet correctly on whether teammates are clear-headed or not, haha
Called this one early at 16k. Decided to ape the dip too, figuring it'd help stabilize things, but ended up taking an L on that position. Only made under 1k total, nothing significant. My wallets are public for anyone to verify.
The token actually dumped to 14k when the team moved coins—they admitted it themselves. Tried some top buys to support the price action, but the math didn't work out in my favor. Still, watched it recover to 54k eventually. 16k to 54k wasn't a bad call on timing, even if the execution got messy.