The USDJ sunset ended the old system workflow; an old token balance does not establish that minting, redemption or an exchange service is currently available to its holder. This guide helps readers separate a TRON record from dated service instructions and an unverified personal outcome.
We checked the public JUST entry and its current Help Center on November 2, 2026. This is a read-only interpretation guide, not a new shutdown announcement. We did not connect a wallet, submit a claim, register with an exchange, sign a message or execute a conversion. The success standard is a usable evidence note that identifies the record, relevant source and unresolved next question.
Table of Contents
Four checks for a USDJ sunset record
- Identify the record. Is it an address balance, transfer, collateral position, exchange balance or support decision? Keep these categories separate.
- Identify the service date. An older explanation can describe a system that no longer accepts the same operations.
- Identify the source path. Retain the page address and actual link destination, rather than relying on a displayed URL alone.
- Identify the unproved result. A page loading successfully does not prove that a particular holder can complete the stated process.
For the USDJ sunset, these checks are more useful than treating every occurrence of the ticker as a promise of a dollar payment. A public token record answers a narrow chain question. The terms of a service process answer a different question, and personal eligibility may require information we did not collect or verify.
Why an older minting description is insufficient
The JustLend ecosystem overview dated March 2024 describes USDJ as a collateral-based stablecoin associated with TRX and collateralized debt positions. That is useful historical context. It is not evidence of a currently open minting route.
In contrast, the current official entry we opened displays a shutdown notice referring to November 17, 2025, at 21:50 Singapore time. It also presents a USDJ/WTRX panel and a wallet-connection button. We observed those public labels without testing a conversion. A zero balance displayed while disconnected was not a lookup of any reader’s address.
Singapore and Beijing use UTC+8 for this date. We converted the stated boundary to November 17, 2025, at 13:50 UTC. Preserve the timezone with the date: a date-only screenshot loses information needed to distinguish records near a boundary. This conversion does not decide whether a particular acquisition satisfies a service condition.
Our original source and record comparison
| Evidence checked November 2 | What we recorded | What remains unproved |
|---|---|---|
| Older ecosystem article | A 2024 collateral/minting description | Current operation of the old workflow |
| Public entry | Sunset notice and a USDJ/WTRX panel | A personal balance, executable quote or settlement |
| Current support update | Three channel descriptions; signed November 24, 2025 | A fresh acceptance decision for an individual |
| Prior-detail link in that update | Displayed old-host URL; actual relative target on the current support host | A usable detailed article: the tested target displayed a missing-page message |
The table is our own comparison of independently observed pages, rather than a reconstructed account history. The support update has a visible updated-time value of April 16, 2026, while its body is signed in November 2025. Neither date is our November 2026 observation date. Retaining all three prevents an old announcement from being presented as today’s event.
Read the channel descriptions as dated source claims
The current JUST support update describes an official USDJ/CDP channel with documentation and a form, an HTX channel involving verification, and a website fixed-price channel. It also includes an HTX completion note dated November 21, 2025. We did not open or submit the form, verify an account or test continuing acceptance by any channel.
There is a specific unit difference worth preserving. The support text states 1 USDJ to 1.5532 TRX for its website option. Our later loaded entry displayed 1 USDJ to 1.5531 WTRX. These are two source observations, not interchangeable guaranteed proceeds. We did not determine whether wrapping, rounding, timing or another implementation detail explains the difference.
The USDJ sunset worksheet therefore leaves the requested amount, final receiving amount and execution status blank. Copying a displayed rate into those fields would turn a public observation into a fictitious personal quote. A reader with an actual completed record should preserve that record’s own assets and units.
A link that looks familiar can still fail
One prior-announcement link in the support update visibly names the old justorg.zendesk.com host. Its actual href is a relative article path. Resolved on the current page, it points to support.just.network. In our test, that target showed a missing-page message. Separately opening the old-host address led to a closed-help-center destination.
We did not infer that all support was unavailable: the current update and Help Center loaded. The useful fallback was the current official navigation, not a guessed replacement article ID, an unofficial mirror or a private message from a purported agent. A broken earlier detail link remains a limitation in our source record.
When repeating the check, record the actual destination before opening it. On a phone, use the browser’s link preview or address display when available. Avoid changing a host by hand just to make a remembered address look familiar. If the relevant condition cannot be established from a current source, leave it unresolved and use the official support route for clarification.
To reproduce the link check, open the current Help Center from the entry page, choose the update about funds not returned after shutdown, and inspect its earlier-detail link. The working update ends with article ID 52719795613465; the tested missing detail uses 52545197691161. Retain both complete addresses and the access time in your note. These are two different article identifiers, not alternate spellings of one destination. Our check did not recover the missing article or establish whether its conditions had been replaced.
Three synthetic cases: classify before concluding
| Clearly hypothetical case | Supported statement | Unsupported leap |
|---|---|---|
| A reader saves an old wallet balance screen | The screen records what that interface displayed at its saved time | The reader qualifies for a current service channel |
| A reader sees USDJ and WTRX in the entry panel | The panel names those two assets | The displayed number is a completed TRX payment |
| A reader finds an old minting tutorial | The tutorial described a historical workflow | The old system still accepts minting now |
These cases are not real claims, transfers or eligibility decisions. They demonstrate how to keep an observation and its conclusion at the same level. The method also applies when a support agent asks for a record: provide the relevant dated evidence, and avoid filling missing fields with a claim copied from someone else’s case.
Build a useful read-only evidence note
- Write the asset, network and type of record. If it is a token record, preserve the full contract identifier from a trusted source; a ticker by itself is insufficient.
- Write the source address, source date and your check time separately. Preserve a missing-page result as a result, rather than silently replacing the source.
- Copy the units exactly. Distinguish USDJ, WTRX, TRX, USDD and USDT in every field; do not infer a conversion from similar names.
- State the specific question still unanswered: record identity, historical timing, channel conditions, personal acceptance or actual settlement.
Asset / network / full contract, if verified: Record type / address or reference / observation time: Official source URL / source date / current check time: Stated conditions / exact input and output units: Actual destination of relevant links / access result: What was personally verified / what remains unknown: Next official source or support clarification needed:
Keep sensitive account or claim material out of a public post. Our worksheet is an original organization aid, not a downloadable claim form or a replacement for official verification. We retained the original source observations locally; no reader’s credentials or personal documents were involved.
Choose the relevant next guide
If the confusion is WTRX versus native TRX, the WTRX record guide explains that separate asset distinction. For a separate example of a planned lending-service change, the USD1 market offboarding evidence guide compares a dated notice with current public fields. USD1 and USDJ are different assets and service histories; neither notice proves the other asset’s conditions. For a saved historical record, the read-only evidence preservation guide is the next step.
Frequently asked questions
Does an old USDJ balance prove redemption eligibility?
No. It is a record to investigate. The applicable service conditions and any personal acceptance decision require separate evidence.
Did the USDJ sunset happen in November 2026?
The reviewed notices refer to November 17, 2025. November 2, 2026, is our check date.
Did you test the displayed USDJ conversion?
No. We observed public pages without wallet connection, form submission or a financial transaction.
Are the displayed TRX and WTRX numbers equivalent?
We did not establish that. Preserve each asset label and source time; neither observation is a personal settlement receipt.
Does one broken announcement link mean the whole Help Center is closed?
No. The current support page loaded, while the tested prior-detail destination did not. Record the scope of each result.
Independent Tronscan News guide with AI-assisted drafting and primary-source checks on November 2, 2026. Two original diagrams, a four-source comparison, synthetic decision cases and an evidence worksheet support the reading method. No personal eligibility, current exchange execution or recovered funds are claimed. Browse the Tronscan News homepage; use About & Standards for corrections.
Leave a Reply