Data Analytic Investments
RIPPLE book coverRIPPLE — the book·numbered first edition·$29Buy now
Research

Bithumb lifts the trading-caution designation on Injective (INJ), 22 September: deposits resume at 16:00 KST — what the notice says, and what it does not

Bithumb's notice of 22 September 2026, 16:00 KST, removes Injective (INJ) from its trading-caution list and resumes deposits the same day. The notice gives one sentence of reasoning and no history. We put it next to the exchange's 21 September notices on FET, EGLD and ACX, and list what the text leaves out.

D
Data Analytic Investments
••6 min read
Bithumb lifts the trading-caution designation on Injective (INJ), 22 September: deposits resume at 16:00 KST — what the notice says, and what it does not

Yesterday we read the Bithumb notices that placed three tokens under a trading-caution designation. Today the same exchange published the opposite kind of notice for a fourth token: the designation on Injective (INJ) is lifted, and deposits resume. The two documents come from the same policy and use the same template, so they can be read as a pair — and the pair shows how little the template says about why anything happens.

🎧 Audio edition — the full article read aloud, 8 minutes, MP3: bithumb-injective-caution-lifted-2026-09-audio-EN.mp3

The notice, as posted

Bithumb's notice feed carries the item under number 1654993, with the title "인젝티브(INJ) 거래유의종목 지정 해제" — "Removal of the trading-caution designation on Injective (INJ)". The posting time shown on the page is 2026-09-22 16:00:00, which is Korea Standard Time; the same moment is 07:00 UTC and 09:00 in Budapest.

The body opens with the sentence that appears in every notice of this family: "빗썸은 투자자 보호를 위한 거래지원 정책의 일환으로 거래지원 중인 가상자산에 대한 지속적인 모니터링 및 감독을 시행해 오고 있습니다." In English: as part of its listing policy for investor protection, Bithumb continuously monitors and supervises the virtual assets it supports. The notice then states that, under the exchange's trading-caution designation policy, it announces the removal of a designation, and gives one line under the heading of the affected asset and the reason: "거래유의 지정 사유가 해소되었다고 판단하여 거래유의 지정 해제를 결정합니다." That is: having judged that the reason for the trading-caution designation has been resolved, the exchange decides to remove the designation.

The schedule has two lines. The removal date is 2026.09.22, a Tuesday. The resumption of deposits is scheduled for 16:00 on the same day. A footnote says the schedule may change for internal reasons. The closing paragraph repeats the exchange's commitment to a sound and transparent trading environment, "외부 전문가, 재단과의 커뮤니케이션을 통해" — through communication with external experts and the foundation.

That is the whole document. It names one token, one date, one hour, and a reason described only as "resolved".

What the notice does not say

The text does not state why Injective was placed under trading caution in the first place. It does not state when the designation was imposed. It does not describe what was checked, who checked it, or what changed between the designation and its removal. It does not say whether withdrawals were affected, or whether any trading condition remains in place after 16:00. We did not open the earlier notice that imposed the designation, so the date and grounds of the original designation are, for this article, [UNVERIFIED].

This is not a criticism of the exchange; it is a description of the document type. A trading-caution notice on Bithumb is a status change with a template around it. The template has a slot for the asset and a slot for the reason, and in the removal notice the reason slot is filled with a single formula: the reason has been resolved.

The same template, the other direction: 21 September

On 21 September the exchange used the same template to add three tokens to the caution list. We documented those notices yesterday. For FET and EGLD the stated ground was a category of the policy that covers unresolved security incidents, quoted in the Korean text as "가상자산 지갑 또는 가상자산이 발행·전송·저장되는 분산원장 등에 원인이 밝혀지지 않거나 치유되지 않은 해킹 등 보안사고" — security incidents such as hacks, on a wallet or on the distributed ledger where the asset is issued, transferred or stored, whose cause has not been identified or remedied. For ACX the ground was a different category, concerning the reality and sustainability of the business. Those notices also gave review windows: the fourth week of October for FET and EGLD, the third week for ACX.

Put side by side, the two days show the mechanism. A designation notice names a policy category and a review window. A removal notice names neither; it only records that the category no longer applies. The reader who wants to know what happened to Injective between the two states has to go outside the notice — to the project's own communications, to the ledger, or to the exchange's earlier post — and the notice itself does not point to any of these.

The list around it

The notice listing for 21 and 22 September, as we read it this morning, also contains deposit-and-withdrawal pause notices for several other assets and a notice on multichain support for USDC. We read the titles of those items on the listing page; we did not open each one, and the exact posting times of those secondary notices are [UNVERIFIED]. We mention them only to place the INJ item in context: on a large Korean exchange, the caution list moves in both directions within the same day or two, and each move is announced with the same short form.

Why we read notices like this

The Kripto Akadémia teaches that an exchange notice is a primary source in the narrowest sense: it is the exchange's own statement of its own action, with a timestamp. It is not evidence about the token, the project, or the price; it is evidence about the exchange's list. Reading it for what it is — and writing down what it omits — is the discipline we practise in The Analyst Room on longer documents, and in the Uncle Sunny Academy on the method itself. The market data we publish under Market Observation is sourced from exchanges in the same way: as recorded values with timestamps, not as opinions. Earlier notes in this series are collected under Research, and the team that reads the Korean texts is introduced on the About page.

Sources

Bithumb, notice 1654993, "인젝티브(INJ) 거래유의종목 지정 해제", feed.bithumb.com/notice/1654993, posted 2026-09-22 16:00:00 KST — the title, the body text, the removal date, the deposit resumption time.

Bithumb, notices 1654962 and 1654956 (21 and 20 September 2026), as documented in our article of 21 September — the FET, EGLD and ACX designations, the policy categories quoted, the review windows.

Bithumb notice listing page, feed.bithumb.com, read 22 September 2026 morning — the titles of neighbouring notices; the individual notices were not opened.

We did not open the notice that originally placed INJ under trading caution, did not contact the exchange or the Injective project, and did not consult any price data for this article.

Educational content. Not investment advice. This article documents an exchange notice; it contains no instruction to buy, sell or hold any asset.

Explore Topics

#Bithumb#Injective#INJ#trading caution#Korea#exchange notices#listing policy
D

Written by

Data Analytic Investments

Content creator and writer sharing insights and stories.

Share · Megosztás:XFacebookLinkedInWhatsAppTelegramE-mail

Related Research

Bithumb designates FET, EGLD and ACX as trading-caution assets on 21 September; Upbit does the same for EGLD — the reasons as written, the review dates, and what the notices do not say
Research

Bithumb designates FET, EGLD and ACX as trading-caution assets on 21 September; Upbit does the same for EGLD — the reasons as written, the review dates, and what the notices do not say

At 16:00 Korean time on 21 September 2026 Bithumb posted a notice designating Fetch.ai (FET), MultiversX (EGLD) and Across Protocol (ACX) as trading-caution assets. For FET and EGLD the stated reason is an unresolved hacking or security incident; for ACX it is doubt about the reality and continuity of the underlying business. Deposits stop at 16:00; the designation is to be reviewed in the fourth week of October for FET and EGLD and the third week for ACX. Upbit posted an EGLD caution notice the same hour. We quote the notices and mark their limits.

•6 min read•Data Analytic Investments
#Bithumb#Upbit#FET
Binance Futures changes the leverage and margin tiers of 16 USDⓈ-M perpetual contracts on 25 September, 06:30 UTC — what the announcement says, and what it leaves to the reader
Research

Binance Futures changes the leverage and margin tiers of 16 USDⓈ-M perpetual contracts on 25 September, 06:30 UTC — what the announcement says, and what it leaves to the reader

Binance's announcement of 22 September 2026, 07:00 UTC, schedules new leverage and margin tiers for 16 USDⓈ-M perpetual contracts in four groups, all effective 25 September at 06:30 UTC. The text states that existing positions will be affected and that running grid strategies may expire. It does not say why, or in which direction. We document the announcement and its silences.

•5 min read•Data Analytic Investments
#Binance#futures#margin tiers
Bank of Korea starts the 24-hour offshore won settlement pilot on 21 September with four banks — what the announcements document, and what they do not say about crypto
Research

Bank of Korea starts the 24-hour offshore won settlement pilot on 21 September with four banks — what the announcements document, and what they do not say about crypto

On Monday 21 September 2026 at 09:00 Korean time the Bank of Korea began the pilot run of its BOK Won International Wire Network with KB Kookmin, Woori, Hana and Shinhan; the first test transaction, about 1.4 billion won, went through around 09:30 between two of them. The network runs 24 hours on business days and is scheduled for full launch in January 2027. Crypto headlines carried the story this morning; the official material contains no crypto or stablecoin component. We set the documents side by side.

•6 min read•Data Analytic Investments
#Bank of Korea#won#settlement