I'm COLE (also known as Anh Ba Cong in Vietnam).
EA Expert with 4 years in Funds.
20K followers on YT and Binance.
Mastering automated trading together!
BITMINE IS JUST 0.2% AWAY FROM ITS 5% ETH SUPPLY TARGET 🟣 Tom Lee’s Bitmine has purchased another 9,926 ETH, lifting its total holdings to 5.82 million ETH, equal to 4.8% of Ethereum’s supply and worth about $11 billion. Based on that ratio, a 5% position would equal roughly 6.06 million ETH, meaning Bitmine needs about 242,500 more ETH. The percentage gap is small, but the amount remains substantial. More than 5 million ETH has already been staked, with estimated annual rewards of about $287 million. This creates recurring income and makes the accumulation strategy less dependent on ETH price movements alone. The downside is significant: Bitmine’s ETH portfolio currently carries about $8.4 billion in unrealized losses. The company is also repurchasing its own shares under a 4 billion program. Tom Lee expects asset tokenization, AI demand, and easier financial conditions to keep supporting crypto markets. Still, macro optimism does not remove concentration risk as one company approaches control of 5% of ETH supply. Could Bitmine’s 5% ETH target become a strategic advantage, or make concentration risk a bigger concern? Please do your own research carefully before making any transactions (DYOR). $ETH $BNB $FTM
STRATEGY RAISES $333.7 MILLION FROM MSTR, BUT DOES NOT TOUCH ITS BITCOIN 🟠 Strategy has taken a noticeably different step this week. Between August 10 and August 16, the company transferred 3,458,866 shares of MSTR and generated approximately $333.7 million in net proceeds. The notable part is that Strategy neither acquired nor transferred any Bitcoin during the period. The proceeds were allocated across three main uses. Strategy spent $52.4 million on dividends for its STRC preferred shares, used $132.2 million to repurchase STRC, and placed another $149.1 million into its USD reserve. Following these transactions, the company's USD reserve reached approximately $4.8 billion, providing liquidity to support preferred-share dividends and interest expenses. Strategy currently holds 840,447 BTC. The decision to leave its Bitcoin position unchanged is notable because the company has become widely associated with raising capital to expand its BTC holdings. This time, the immediate priority appears to be strengthening liquidity and maintaining the ability to meet financial obligations. This could form part of the broader strategy Michael Saylor is developing around STRC. If a larger cash reserve reduces financial pressure, STRC could become more attractive, potentially allowing Strategy to raise capital at a lower cost if the preferred shares trade around or above $100. New capital could then potentially be directed toward additional Bitcoin purchases. However, that remains a potential scenario rather than a confirmed sequence of actions. The model still depends on BTC prices, future capital-market access, and the premium investors are willing to assign to MSTR. Is Strategy temporarily holding back on BTC purchases to build a large enough cash buffer for its next capital-raising cycle? 🤔 Please do your own research carefully before making any transactions (DYOR). $BTC $ACE $EDEN
Late last month, my withdrawal schedule was stuck between an invoice and a stablecoin position that had not matured. I opened several fixed rate markets and saw the highest rates sitting in orders too thin, while deeper orders offered lower levels. The problem was not missing choice, but choice chopped into fragments.
TermMax Order Aggregator goes straight at that fragmentation. It scans multiple orders and builds an execution path around size, interest rate, maturity, market depth, and gas cost. In fixed rate markets, a 9 percent quote looks attractive, but if it fills only 20000 USDC, the rest still has to pass through other orders.
What is worth analyzing in TermMax is that the aggregator sits at the core of V2, not as a cosmetic interface layer. With 49.18 million dollars in TVL, 55.56 million dollars including borrowed value, 17000 daily active users, and more than 100 markets, liquidity is no longer a flat screen number. It lives inside range orders, atomic orders, limit orders, and Smart Unwind, so checking by eye can fail at execution.
The paradox is that fixed rate markets promise certainty, yet hunting rates often makes users less certain. TermMax does not replace users in assessing risk, it gathers operational noise into a route they can judge. That difference is small, but practical.
Before TGE, TMX has a total supply of 1 billion, with about 20 percent circulating at launch. That is enough to draw attention, but attention will not last without a reason to open the app after the points season. For TermMax, that reason has to be the aggregator saving real effort, not a token story running by itself.
I still keep the necessary doubt. A good route can turn bad if orders change quickly, depth is thin, or gas eats the spread. The project’s problem is specific, not creating more rates to display, but helping users choose rates with less self deception. #termmax @TermMax
SafePal has confirmed a security incident affecting approximately 39,798 customers after a vulnerability in its order-tracking system allowed unauthorized access to purchase information. According to SafePal's disclosure, the incident involved orders placed between March 2, 2025 and April 11, 2026. The exposed information included names, email addresses, phone numbers, shipping addresses, and order details. While this may appear less severe than a direct wallet compromise, the information is particularly sensitive in crypto because it can establish a link between a specific individual and ownership or use of a hardware wallet. The most important distinction is that SafePal says the incident did not affect seed phrases, private keys, wallet passwords, or crypto assets. Bank account information, payment card numbers, and government-issued identification were also not part of the exposed data. SafePal says the vulnerability has been fixed and additional security measures have been implemented. However, the absence of private-key exposure does not eliminate the security risk. The more immediate concern is phishing and impersonation. Once attackers know someone's name, address, phone number, and purchase history, they can create highly convincing messages that appear to come from SafePal, potentially referencing an actual order, device update, or security verification. SafePal has emphasized that seed phrases, private keys, and passwords should never be shared with anyone. The company says affected customers were notified individually and that a mechanism is available for checking whether an account was impacted. The incident is a useful reminder that crypto security does not stop at protecting a private key. Personal information surrounding the ownership of a wallet can also become a valuable target. Is targeted phishing becoming almost as serious a threat as direct private-key compromise in crypto security incidents? 🤔 (DYOR). $ACE $EDEN #Colecolen #anhbacong #anh_ba_cong $SAFE
I was looking through Dusk’s explorer when one number made me stop. 136,246 DUSK. That was the amount shown next to a provisioner that had been soft-slashed. My first thought was pretty simple: “That’s a painful mistake.” Then I looked closer. Dusk has two different kinds of penalties, and they aren't really the same thing. Soft slashing is for failed participation. A provisioner can lose active eligibility and have part of its stake moved into a locked state, but the DUSK isn't actually destroyed. Hard slashing is different. That’s where things get serious. Invalid blocks, double voting or double block production can result in part of the stake being burned. I actually like this distinction. Being offline or failing to participate isn't the same as deliberately trying to break consensus. A network that treats both exactly the same would be pretty crude. But there’s another side to it. When I saw that 136K number on the explorer, I started wondering how much of the staking economy is sitting behind these penalties. Because the theoretical staking reward is the easy part. The harder question is what happens when operators make mistakes. And apparently, Dusk has thought quite a bit about that. I’m still not sure how often these penalties matter at network scale. The explorer certainly shows they aren't just theoretical — there are recent soft-slash events visible there. Maybe that's a good sign. A security mechanism that never gets used is difficult to evaluate. Or maybe it means operators have a very real reason to keep their nodes healthy. Either way, I didn't expect a random number on an explorer to lead me into the economics of running a Dusk node. That's probably why I keep checking these things. #dusk $DUSK @Dusk $DUSK