[KR KOL Index] Apr 22 | Top Trending Topics on Global & KR Timelines

The notice “Pharos pALPHA Withdraw application available” was widely shared, and a practical checklist spread quickly across communities. As the application window, the actual withdrawal processing schedule, and the next deposit (lock-up) opening period were compiled together, an interpretation followed that “if you don’t apply, your withdrawal may be pushed back until after the next lock-up.” It was repeatedly emphasized that withdrawal requests can only be made on the Pharos network, and users holding assets only on ETH were cautioned that bridging would be required.

pALPHA withdrawal window “6/17–7/1” shared… bridging requirement also highlighted

Channels such as “Pagu Information (DeFi Info)” circulated a detailed schedule for when pALPHA withdrawal requests can be submitted. According to the guidance, applications are accepted from June 17 to July 1, and actual withdrawals are slated for July 20–27 (with July 23 as the target completion date). Communities also amplified a logical estimate that “if you miss applying within the window, you may not be able to withdraw until after the next lock-up.” In particular, because withdrawal requests are only possible on the Pharos network, the note that bridging is necessary for users who only have assets on ETH drew attention. A withdrawal-request link (ember.so) was also shared and saw rapidly increasing views.

Next deposit schedule and lock-up terms—portfolio allocation and APY summarized “all at once”

Alongside withdrawal discussions, demand for “when the next deposit opens” rose, leading deposit calendar information to be consumed together. The shared content stated that the next deposit opens between July 10 and July 16 with a three-month lock-up, and the following deposit is guided for September 17 to October 1. The deposit allocation was described as 70% vrPCQ / 30% JTRSY, with a target APY of 14%; the line “if the target yield is not met, PROS incentives may be added” attracted attention. Community reactions focused less on price outlooks and more on execution checkpoints such as timing, chain movement, and lock-up risks.

Market-side topics: STRC “peg breakdown” and exchange delistings/watchlists… heightened risk alertness

Meanwhile, the broader market discussed news that MicroStrategy’s STRC preferred share lost its peg and fell to $85, prompting reactions warning of “structural risk.” At the same time, the phrase “exchange cleanup season” spread alongside bundled lists of delistings and watchlist designations across major exchanges. Mentions included Bybit delistings (multiple tickers), Binance watchlist designations (ACT, BLUR, PIVX, QKC), and Upbit watchlist designations (AQT, AERGO). The mood suggested that beyond individual tickers, the overarching “watchlist/delisting trend itself” needs to be monitored.

Overseas-exchange asset reporting and post-FOMC rate-bet shifts also mentioned

From a practical standpoint for Korean users, guidance about “reporting if you hold 500 million KRW+ on overseas exchanges” was repeatedly circulated across multiple channels. On the macro side, changes in FedWatch probabilities after the FOMC were cited, with interpretations that bets on the timing of rate hikes within the year moved forward. Other one-off items—such as Binance listing news ($RE), token listing notices (Solstice on Bullish), and offline event announcements—were also consumed, but the day’s attention skewed more strongly toward checklist-type risk management topics like “withdrawal/deposit schedules” and “delisting/watchlist” issues.

The top community topics that day were led by hands-on guidance centered on the pALPHA withdrawal schedule and network requirements (bridging). Simultaneously, rules and risk issues—such as exchange delistings/watchlists and overseas-exchange asset reporting—overlapped, reinforcing a sentiment that “verifying information comes first.” This content was written based on Telegram messages collected using DataMaxiPlus’s community analysis technology.