The UNCX Smart Token Vesting V2 report describes an October 14, 2026 incident in which share-accounting errors allowed excess withdrawals from pooled tokens across four networks. A scheduled vesting amount and tokens already received in your wallet are different records. Start by establishing which record you own before treating the headline as a loss estimate for your account.
Begin with the claim, not the displayed total
UNCX's vesting documentation distinguishes time-locking regular tokens from locking liquidity-provider tokens. The product and manager contract therefore matter. A vesting schedule shown beside a token is not proof that the full scheduled amount has already been delivered to the beneficiary's address.
Write down the network, token contract, vesting manager, beneficiary and position reference. Use the affected-manager list in the incident report as the comparison source. A symbol alone is too broad: a wallet-held token, a claim against a manager and a liquidity position can appear beside the same project name while requiring different evidence.
Two amounts can be correct and still answer different questions
Consider a fictional schedule for 100 units, with 20 units released earlier and 80 still scheduled. The wallet may no longer hold the released 20 if the owner subsequently transferred them. Adding the original 100 to today's wallet balance would count some history twice. None of these example quantities describe an affected UNCX holder or establish a claim amount.
| Record | What the quantity describes | How to avoid a false total |
|---|---|---|
| Original schedule | The allocation recorded when the position was created | Do not add it to releases as if both were new assets |
| Historical release | A transfer attributed to an earlier position action | Separate delivery then from the current wallet balance |
| Remaining claim | What the position still records as due | Do not assume a display proves available pooled backing |
| Current wallet holding | Tokens held at that address now | Separate other receipts and transfers from vesting history |
This is an editorial bookkeeping example, not the report's internal share formula. It does not tell a holder how to exploit or repair the contract. Its purpose is to make an enquiry precise enough that the issuer or service can reconcile the same position rather than debate an unexplained total from a screenshot.
Why the report's dollar figure needs its label
The currently read version 2.0 reports approximately $807,609 as realized or routed economic value, replacing an earlier mark-to-market aggregate. It lists returned assets separately by quantity. These are different accounting measures, not interchangeable estimates of what each beneficiary will receive. UNCX says individual outcomes and a timetable cannot yet be confirmed.
When comparing an older headline with this report, first compare the valuation methods and version. Do not subtract a returned token's current market value from a differently valued aggregate to manufacture ‘the remaining loss’. The dates, assets and measurement basis would need to match. A report-level return also does not identify a payment to your particular beneficiary.
Build a short position file before contacting the project
- Locate your original position reference through a trusted record, then identify the network, manager and beneficiary.
- Compare that manager with the official incident report. Keep ‘matched’, ‘different’ and ‘not established’ as separate findings.
- Collect public references for earlier releases and later transfers without mixing them with the original scheduled allocation.
- State the amount or action you cannot reconcile, in the token's own units; distinguish your observation from an estimated loss.
- Use the contact route reached from the official report and ask what evidence is needed for that position. Keep your secrets and funds out of the correspondence.
You do not need to recreate the attack, test contract actions or approve a new spender to prepare this file. If you do not know whether an action released tokens, say so and supply the public reference. A claim that remains unresolved is more accurate than assigning every unexplained wallet movement to the same incident.
An audit description is not a post-incident resolution
The general UNCX documentation describes several services. It should not be used as a live status page for this specific V2 manager. Nor does a generic description of a time lock prove that an individual position still has the backing needed for release after an incident. Read the dated report and product-specific updates together.
This review has not independently replayed the report's transactions, measured the backing of an individual claim or established a beneficiary's compensation. It does not infer that ordinary tokens held outside the affected manager were stolen through the same mechanism. Any broader account problem needs evidence specific to that address and action.
Only delivered, supported assets belong in a later swap
A future vesting entitlement cannot be treated as spendable funds in a normal exchange order. Once an asset is actually under your control, check the supported coins and exchange instructions for its exact network. This does not establish KOT.CASH support for any affected token or vesting claim. Review the incident page again before relying on its accounting and recovery statements, which may change.
FAQ
Does an UNCX vesting schedule equal tokens already in my wallet?
A schedule records a position's allocation and timing, while wallet holdings reflect delivered assets and subsequent transfers. Reconcile releases separately before calculating a total.
Does UNCX token vesting identify the manager affected in this incident?
The product name alone is insufficient. Match the network and manager contract against the official report before treating a particular position as part of the case.
Does UNCX Network's vesting security documentation prove a payout?
General product documentation is not evidence that a beneficiary received funds. Look for the position-specific explanation and the relevant public receipt, keeping an unresolved result explicit.