BinanceがACX、LSK、STXにモニタリングタグを付与、価格急落

,

tags. For the first paragraph: "Binance added three tokens to its Monitoring Tag list on July 24, triggering sharp price drops for Across Protocol (ACX), Lisk (LSK), and Stacks (STX). The exchange uses the tag to flag assets with higher volatility and risk, and tokens that fail to meet its criteria can be delisted. Within hours, LSK hit an all-time low of $0.074, ACX fell to $0.286 — its lowest since March — and STX dropped to $0.143, a level not seen since late 2020." Translation: "Binanceは7月24日、3つのトークンをモニタリングタグリストに追加し、Across Protocol（ACX）、Lisk（LSK）、Stacks（STX）の価格が急落しました。取引所はこのタグを使用して、ボラティリティとリスクが高い資産を警告し、基準を満たさないトークンは上場廃止される可能性があります。数時間のうちに、LSKは史上最安値の0.074ドル、ACXは3月以来の安値となる0.286ドル、STXは2020年末以来の水準となる0.143ドルまで下落しました。" Note: "Binance" is proper noun, keep as is. "Monitoring Tag" - in Japanese crypto context, often "モニタリングタグ" is used. "all-time low" -> "史上最安値". "since March" -> "3月以来". "late 2020" -> "2020年末". Second paragraph: "What the Monitoring Tag means" -> "モニタリングタグの意味" as h2. Then text: "Binance applies the Monitoring Tag to tokens that show signs of elevated risk. The exchange reviews these projects regularly, looking at team commitment, development activity, trading volume, network stability, changes to tokenomics, and any evidence of fraud or negligence. A tag doesn't guarantee delisting, but it's a warning. Previous tokens that received the tag and were later removed include Beefy.Finance (BIFI), Measurable Data Token (MDT), FunToken (FUN), Orchid (OXT), FIO Protocol (FIO), and Wanchain (WAN)." Translation: "Binanceは、リスクが高い兆候を示すトークンにモニタリングタグを適用します。取引所はこれらのプロジェクトを定期的にレビューし、チームのコミットメント、開発活動、取引量、ネットワークの安定性、トークノミクスの変更、不正行為や過失の証拠などを確認します。タグが付与されても必ず上場廃止になるわけではありませんが、警告です。過去にこのタグが付与され、後に上場廃止されたトークンには、Beefy.Finance（BIFI）、Measurable Data Token（MDT）、FunToken（FUN）、Orchid（OXT）、FIO Protocol（FIO）、Wanchain（WAN）などがあります。" Third paragraph: "Why these three tokens got flagged" -> "これら3つのトークンがフラグされた理由" as h2. Text: "Binance didn't specify a single reason for each token. The criteria are broad. For Lisk, a blockchain platform that launched in 2016, the price had already been sliding for months. The Monitoring Tag news pushed it to a record low. Across Protocol, a cross-chain bridge, saw its token drop to levels last seen in March. Stacks, which brings smart contracts to Bitcoin, fell to its lowest price since late 2020. At press time, LSK was down 3.85%, ACX down 1.14%, and STX down 7.05%." Translation: "Binanceは各トークンについて単一の理由を明らかにしていません。基準は広範囲にわたります。2016年にローンチしたブロックチェーンプラットフォームLiskは、すでに数ヶ月にわたり価格が下落していました。モニタリングタグのニュースにより、過去最安値に押し下げられました。クロスチェーンブリッジのAcross Protocolは、トークンが3月以来の水準に下落しました。ビットコインにスマートコントラクトをもたらすStacksは、2020年末以来の最低価格に下落しました。本稿執筆時点で、LSKは3.85％安、ACXは1.14％安、STXは7.05％安となっています。" Note: "STX" is Stacks ticker, keep as STX. "At press time" -> "本稿執筆時点で". "down" -> "安" (down percentage). Fourth paragraph: "What happens next" -> "今後の展開" as h2. Text: "Binance will continue to monitor the projects. If they fail to meet the exchange's standards, they could be delisted — meaning trading pairs would be removed and users would have to withdraw before a cutoff date. The exchange hasn't set a deadline for these three tokens. For now, holders are left watching the price charts and waiting for Binance's next review." Translation: "Binanceは引き続きこれらのプロジェクトを監視します。取引所の基準を満たさない場合、上場廃止となる可能性があります。つまり、取引ペアが削除され、ユーザーは期限までに引き出す必要があります。取引所はこれら3つのトークンについて期限を設定していません。現時点では、保有者は価格チャートを見守りながら、Binanceの次のレビューを待つことになります。" Meta description: "Binance added ACX, LSK, and STX to its Monitoring Tag list on July 24. Prices dropped sharply, with LSK hitting an all-time low. The tag warns of delisting risk." Translate: "Binanceは7月24日、ACX、LSK、STXをモニタリングタグリストに追加しました。価格は急落し、LSKは史上最安値を記録。このタグは上場廃止リスクを警告するものです。" Now assemble JSON. Ensure proper escaping for double quotes in JSON. Use double quotes for strings. The content should be a single string with HTML. We'll write it as a string with escaped quotes if any. But since we are outputting JSON, we need to ensure the HTML content is valid JSON string. We'll use double quotes inside the string, but they need to be escaped with backslash. However, in the translation, we have double quotes in the original? No, the original HTML has no double quotes inside attributes? It has

and

tags, no attributes. So we can just put the translated HTML as a string without escaping internal double quotes because there are none. But to be safe, we can use single quotes for the JSON string? No, JSON requires double quotes for strings. So we'll just write the HTML with double quotes for tags, which are fine because they are not inside the string? Actually, the string content will contain double quotes in the HTML tags like

etc. In JSON, the string value is enclosed in double quotes, so any double quote inside the string must be escaped with backslash. For example, "

" becomes "

" but the double quotes around the attribute? There are no attributes. So the only double quotes are the angle brackets? No, angle brackets are not double quotes. The HTML tags use < and >, not double quotes. So no need to escape. However, if there were attributes like class="something", then we'd need to escape. But here there are none. So we can just write the string as is. But to be safe, we can use backslash escapes for any double quotes that might appear. In our translation, we have no double quotes. So fine. Let's write the JSON. Note: The original content had

and