Delisting L3 e VIC su Bybit: scadenze per spot, bot e prelievi

Timeline at a glance

What changed

The update has one core fact pattern: Bybit is moving L3 and VIC out of its listed-token and Spot-trading environment. The notice names the delisted tokens as L3 and VIC, and names the delisted trading pairs as L3USDT and VICUSDT. Bybit frames the action as part of its regular token and project review process under its Token Management Rules, saying it reviews listed tokens and projects for performance and compliance standards.

That wording matters because this is not just a quiet pair cleanup. The notice includes token names, Spot pairs, deposits, Convert, DCA Bot, Spot Grid Bot, withdrawals and a VIC-specific asset-retirement section. A user who only reads the pair line may miss the operational sequence. Deposits stop before Spot trading stops. Bots need to be closed before the Spot deadline if the user wants control over the close. Convert disappears at the same stated time as Spot trading. VIC has a withdrawal-retirement date three months later, but the notice does not give the same explicit final withdrawal cutoff for L3 in the crawled text.

The other important wording is the conversion caveat. Bybit says VIC tokens may be converted into stablecoins on the user's behalf after the withdrawal function closes, but that this is not guaranteed. Bybit's general Spot Delisting Mechanism gives the broader reason to treat that sentence seriously: after a delisted token withdrawal is suspended, Bybit says conversion into equivalent USDT depends on sufficient OTC liquidity, distribution is proportional after transaction fees, and if liquidity is insufficient no transaction takes place. The help article also says that if the converted asset value is below 0.01 USDT, Bybit will not release the converted USDT to the user's Unified Trading Account.

For a user, that does not mean every VIC balance becomes worthless. It means the exchange is explicitly refusing to promise a post-deadline conversion outcome. The practical control point is still before withdrawal closure, not after.

Why it matters for different users

For a Spot trader, the key issue is not just that a ticker disappears from a menu. The deadline can affect open limit orders, stop logic, portfolio tracking, exports, cost-basis records and the ability to use Bybit liquidity for an exit or transfer decision. Bybit says open orders will be automatically removed after Spot trading ends, so users relying on resting orders should not assume those orders remain pending for later manual handling.

For a bot user, the risk is mechanical. DCA Bots and Spot Grid Bots depend on pair availability. If a bot is still active on L3USDT or VICUSDT at the deadline, Bybit says it will be automatically terminated by the system. That may be acceptable for a user who has already checked the state and understands the consequence. It is a bad surprise for a user who expects the bot to keep managing inventory, average entry, or a grid range after the pair is removed.

For a depositor, the September 16 deposit closure matters because exchange deposits involve more than sending a transaction onchain. A chain transfer can be technically valid while the venue has stopped accepting deposits for that asset. The Bybit notice does not promise late-credit handling in the crawled text. A careful user should treat the stated closure as a hard operational boundary and check the live deposit page, memo/tag requirements and network status before moving anything.

For a holder who wants to leave assets on Bybit, VIC is the sharper case. Bybit gives a final withdrawal-retirement date for VIC. Once VIC withdrawals close, the user no longer controls a normal withdrawal path through Bybit. The notice says later conversion may happen, but it does not guarantee it. The general help article adds more context: conversion depends on liquidity, can take time, can be reduced by fees, and can fail to happen if conditions are insufficient.

For a user watching the broader altcoin market, the decision signal is also limited. A Bybit delisting affects one venue's supported products and liquidity surface. It does not prove that the Layer3 or Viction projects have ended, and it does not prove that every exchange will remove the assets. Layer3's own documentation still describes Layer3 as infrastructure for distribution, identity and incentives. Viction's documentation still describes a network secured by masternodes receiving VIC rewards. CoinGecko still tracked L3 and VIC market pages at the snapshot. Those facts do not cancel Bybit's delisting; they simply prevent the article from turning a venue decision into a universal project-death claim.

The action checklist

The first check is balances. A user should check whether any L3 or VIC remains in the Bybit account, subaccount, funding account, Unified Trading Account, bot wallet or accounting export. This article cannot verify an individual account, and no public page can do that. The account interface is the only source for the user's actual balances.

The second check is open Spot orders. Because Bybit says open orders will be automatically removed when trading ends, users who need a controlled record should export order history and decide whether to cancel manually before the deadline. Manual cancellation can make records easier to reconcile because the user knows when the action happened and why.

The third check is bots. DCA and Spot Grid Bots are easy to forget because they are meant to run in the background. Bybit explicitly names both. If the bot is active on L3USDT or VICUSDT, the user should review holdings, bot profit/loss display, remaining inventory, order history and termination behavior before September 17 at 08:00 UTC. Do not assume the bot exit equals an economically ideal exit.

The fourth check is deposits. If a user was planning to deposit L3 or VIC into Bybit, the safer interpretation is to stop that plan unless the live deposit page proves the route is still open before the September 16 deadline. If the user has already sent a deposit close to the cutoff, they should preserve transaction hashes, network names, memo or tag details and support-ticket evidence.

The fifth check is withdrawals. For VIC, the long runway ends on December 16 at 08:00 UTC. That is the last date stated in the notice for normal withdrawal availability. Users who choose to withdraw should verify the destination exchange or wallet supports the exact token and network, run a small test where appropriate, check withdrawal fees, and preserve the transaction record. For L3, the notice says withdrawals can continue after L3 trading pairs are closed, but the crawled notice does not state a separate final L3 withdrawal cutoff. That unknown should stay visible.

The sixth check is accounting. Delistings often create messy records: canceled orders, bot termination, withdrawals, conversion attempts, small dust balances and later account credits. If the user needs tax or internal accounting, the export work should happen before the interface changes. A future stablecoin credit, if any, may not carry the same context as the original token position.

What not to infer

Do not infer that L3 and VIC are delisted everywhere. The Bybit notice is about Bybit. CoinGecko's L3 page said at the snapshot that L3 was calculated from data across 19 exchanges and 19 markets, and CoinGecko's VIC page still listed Bybit among VIC markets when crawled. Those market pages can change, but they show why a single-venue action should not be rewritten as a universal market fact.

Do not infer that deposits, withdrawals or conversion behavior will be identical for both tokens. The notice gives the same deposit, Spot, Convert and bot deadlines for L3 and VIC, but it gives a VIC-specific asset-retirement and withdrawal end date. The L3 withdrawal text is looser: Bybit says users can continue withdrawing after the L3 trading pairs are closed and recommends doing so early. That is useful, but it is not the same as a final withdrawal calendar for L3.

Do not infer that a post-withdrawal conversion is a guaranteed safety net. Bybit's own wording says VIC tokens may be converted into stablecoins but that this is not guaranteed. The general Spot Delisting Mechanism explains that conversion depends on market conditions and liquidity. That makes "leave it and wait" a materially different choice from "withdraw while the normal withdrawal path is still open."

Do not infer a price forecast. Delisting can reduce venue availability, fragment liquidity and change user behavior, but price impact depends on order books, alternative venues, project news, broader market stress and holders' choices. This article does not model any of that. It only maps the Bybit operational update and the checks a user can perform.

Do not infer that Bybit's stated review reason reveals every private factor behind the decision. The notice says Bybit conducts regular reviews to maintain performance and compliance standards. It does not disclose a detailed scoring sheet for L3 or VIC. A responsible summary should not invent one.

Source-backed context on L3

Layer3's official documentation describes the Layer3 Foundation as supporting community-led governance over Layer3 protocols and the development and adoption of the Layer3 ecosystem. It describes Layer3 protocols and products as omnichain infrastructure for distribution, identity and incentives, and says Layer3 infrastructure has facilitated 120 million transactions across more than 500 ecosystems.

That context is useful because it frames L3 as a project token tied to a broader Web3 distribution and identity infrastructure narrative, not as a token that exists only because Bybit listed a pair. At the same time, the project description does not weaken the operational force of Bybit's notice. If a user holds L3 on Bybit, the relevant Bybit fact is still that L3USDT trading ends, Convert support is removed, deposits close and active bots on that pair are affected.

CoinGecko's L3 page adds a market-data lens. At the snapshot, CoinGecko said L3's price was calculated in real time by aggregating data across 19 exchanges and 19 markets. It also listed market cap, volume, circulating supply and several non-Bybit market links. That supports a narrow analytical point: Bybit is one venue in the market-data picture, not the entire market. It does not prove liquidity quality at any other venue, and it does not tell a user where to move assets.

Source-backed context on VIC

Viction's documentation describes Viction as a public blockchain documentation set and says 150 masternodes work to secure the ecosystem. It states that masternodes receive rewards in VIC and that a masternode candidate requires 50,000 VIC. This frames VIC as a network token associated with staking and masternode participation.

For Bybit users, the key point is narrower. Bybit's notice gives VIC the clearest retirement path: deposits close on September 16, Spot and Convert end on September 17, bots need closure before that, and withdrawals stop after December 16 at 08:00 UTC. CoinGecko's VIC page showed market data, market cap, trading volume, and a markets table that still included Bybit at the snapshot. That snapshot is useful only as market context. It is not a reason to ignore the exchange's stated withdrawal cutoff.

The VIC conversion caveat deserves extra attention because it can sound comforting at first glance. "May be converted into stablecoins" is not the same as "will be converted at a guaranteed price." Bybit's general mechanism states that conversion can depend on OTC liquidity, market price, transaction fees, timing and minimum value thresholds. For a small, illiquid or post-deadline balance, the user's practical control may be far weaker than the phrase "may be converted" suggests.

Known unknowns

The article does not know whether a particular user has a balance, order, bot, deposit, withdrawal address or subaccount exposure. That must be checked inside the account.

The article does not know whether Bybit will change, amend or cancel the delisting timeline later. Bybit's help article says it reserves the right to amend, change or cancel delistings.

The article does not know the final L3 withdrawal cutoff beyond the notice's statement that withdrawals can continue after L3 trading pairs are closed. If a later notice adds a date, this package should be updated.

The article does not know whether alternative venues will maintain L3 or VIC markets, how deep those markets will be, or whether withdrawals to those venues will be supported on the exact network a user needs.

The article does not know whether any later VIC conversion will occur, what price would be used, how fees would apply, how long it would take, or whether a user's balance would fall below the minimum distribution threshold.

FAQ

When does Bybit end L3USDT and VICUSDT Spot trading?

Bybit's notice says Spot trading of L3USDT and VICUSDT will end after September 17, 2026 at 08:00 UTC. It also says all open orders will be automatically removed.

When do deposits close?

Deposits for L3 and VIC close after September 16, 2026 at 08:00 UTC. A user should verify the live deposit page before sending anything close to the cutoff.

What happens to DCA Bots and Spot Grid Bots?

Bybit says users with active DCA Bots or Spot Grid Bots on L3USDT or VICUSDT should close them before September 17, 2026 at 08:00 UTC. Otherwise, the system will terminate them automatically.

Is Convert still available after Spot trading ends?

Bybit says L3 and VIC will be removed from Bybit Convert after September 17, 2026 at 08:00 UTC. Convert should not be treated as a fallback after that point.

What is the VIC withdrawal deadline?

Bybit says withdrawals for VIC will no longer be available after December 16, 2026 at 08:00 UTC. The notice says VIC may be converted into stablecoins after withdrawal closure, but that conversion is not guaranteed.

Does this mean L3 and VIC are finished projects?

No. The Bybit notice supports a claim about Bybit delisting and support deadlines. It does not prove that the projects have ended or that every other venue will remove the assets.

Is this investment advice?

No. This is an operational notice analysis for deadline management and source verification. It is not a recommendation to buy, sell, hold, short, deposit or withdraw any asset.

Claim-source map

Editorial attribution and disclosure

Written and reviewed by NexuAlpha Research Desk from first-party Bybit pages and independent project/market-data context. Last updated at the September 11, 2026 01:35 Asia/Shanghai snapshot. This article is educational research and operational deadline analysis only. It is not financial, legal, tax, accounting or investment advice.