VANRY migrated to Base: Why did the redemption window close five weeks before the Binance withdrawal

Anyone with a VANRY has a full thirty days from August 11, 2026 to complete an action that no one will take on their behalf. Vanar's tokens are being migrated to the Base network and redeemed through a portal operated by the project party, which will close at 13:00 (UTC) on September 10, 2026. After that, access through the portal will be closed.

This case was not eye-catching unless the three dates were interrelated and located in three different positions, and each had different meanings. Binan removed VANRY from spot trading at 03:00 (UTC) on August 17, 2026, but still allowed withdrawals until October 17. Anyone who follows this date will consider the day five weeks after the actual critical date as the decisive date. Anyone who has pledged VANRY must act earlier because there is a 21-day cooling-off period in between.

There are three cut-off dates in VANRY conversions: What are applicable on August 19, September 10 and October 17?

These three dates are not interchangeable or replaceable for each other. The following order is the order in which they reach the holder.

August 19, 2026

VANRY pledge will be closed, which is also the last day for the accumulation of pledge rewards. This detail comes from the official Vanar redemption portal itself.

September 10, 2026 at 13:00 (UTC)

The redemption window closes. This is a common deadline for two different actions: redemption must be completed through the portal at that time, and the holder must at least initiate a de-pledge if the token has been pledged.

October 17, 2026 03:00 (UTC)

Binance ends the withdrawal of old VANRY tokens. This date only relates to the time when the token can leave the exchange. It made no sense to the exchange itself, as it had been closed for five weeks by then.

Therefore, between September 10 and October 17, there is a 37-day period where holders can still withdraw tokens from Binance, but they can no longer be redeemed through the portal. In fact, this is the most dangerous stage in the whole process, because everything seems normal, but nothing can be done.

Exchange window: From August 11 to September 10 at 13:00 (UTC), a total of 30 days.

The portal will be open on August 11, 2026 at 13:00 (UTC) for thirty days. The project party clearly wrote in its FAQ: "There is only one redemption window. "For the subsequent period, it is equally clear: " After the 30-day window closes, post-migration through the portal cannot be carried out. "

The project party has set the official relocation announcement date as August 5, 2026. According to the same portal, trading liquidity on the Ethereum decentralized exchange was removed on August 10, the day before the portal opened. That's why holders can no longer easily dispose of old tokens there, and redemption has become the regular path.

The redemption itself is made on a 1:1 basis. Exchange 1.00 old VANRY for 1.00 new VANRY (on Base). The project party stated that there will be no fees for migration; the transaction network fees on the source chain will be paid by the holder.

Binan removes VANRY and clearly states that it will not process contract changes

Binance announced on August 3, 2026 that it would remove all spot trading pairs of six tokens, including VANRY. The measure came into effect today at 03:00 UTC. Regarding VANRY, there was a statement in the announcement that was not covered by the other five assets: The exchange does not support upcoming contract changes and recommends that holders wishing to redeem use the project side's migration portal. The exchange does not process exchanges.

We wrote about the removal itself and its impact on five other assets in a separate article on August 14, which also covered the options between selling and withdrawing cash: Binance removes six tokens. At the time, the issue of subsequent conversions had not been determined because there was no specific date at that time. Now the date has been confirmed, which is September 10.

For holders who hold VANRY in Binance, this creates an uncleverable process: withdraw cash first and then exchange. Both must be completed by September 10, and the withdrawal itself will take time, as withdrawals from the exchange cannot be completed in minutes, considering verification and network load.

The trap in the calendar: The withdrawal deadline is October 17 and the redemption deadline is September 10.

The two dates are in different positions, which is the core of the problem. Log in to your Binance account and you will see the withdrawal deadline. Holders who don't know about the migration will think it can be until mid-October. This calculation is correct for withdrawal, but wrong for redemption.

To make matters worse, Binance continues to support the withdrawal of old tokens on Ethereum and Polygon. Therefore, withdrawals will still proceed smoothly after September 10, and holders will not receive any feedback that the key dates have passed. As a result, the tokens they hold are on a chain where transaction liquidity has been withdrawn and cannot be processed through the portal.

We have seen similar patterns on other trading platforms, where multiple deadlines appear one after another, and the most conspicuous one is not the most important one. An overview of current deadlines can be found in our Exchange Deadline Summary; the VANRY exchange does not appear there because it is not the exchange date, but the project party's date.

Some processes cannot be rushed: You won't be able to complete them until the last day.

Pledge and 21-day cooling-off period: Why releasing pledge actually expires

Pledged positions have their own mechanism, which is why this article cannot wait until September. Vanar's pledge contract has a 21-day lock-up period. If you initiate the release of pledge today, it will take more than three weeks before your tokens can be freely circulated again.

The portal states this condition as follows: "Any wallet that has not been released before September 10, 2026 will not be included in the Base airdrop. "So the key is when the process starts, not when it ends. Holders who began to release pledges before September 10 will still qualify even if they are still in progress for 21 days. They will then receive the migrated tokens on Base via airdrop on September 11, 2026.

What does "initiating release of pledge" mean in practice

The difference between initiation and completion determines the fate of the entire hold, so precision is worth it. The process starts with a transaction that initiates a cooling-off period. When the tokens can move freely again after 21 days, the process ends. For eligibility, the portal says the former is critical; for manual redemption through the portal, the latter is required, and you will only have enough time starting on August 20 at the latest.

The project parties also stated that they could not unpledge or withdraw tokens on behalf of users. Therefore, this action is entirely the responsibility of the holder. A wallet that no one opens and cannot be operated externally.

Redeem through the portal: Lock on Ethereum, VanarChain or Polygon, receive on Base

The portal describes the process as four steps, eliminating the need for bridging or manual collection. The holder connects to the wallet, selects the chain in which his VANRY is located, enters the amount, and confirms the authorization and locks the transaction itself. The new VANRY will then be sent on Base to the same wallet address, which typically takes approximately four hours, according to portal instructions.

Supports Ethereum, VanarChain and Polygon as source chains, and the target chain is only Base and nothing else. Anyone holding a VANRY on these multiple chains can migrate in turn; the portal clearly states that each chain is processed separately.

One feature of this process is worth noting because it is irreversible: once the locked transaction is confirmed, old tokens cannot be retrieved from the portal. The project party wrote that the locked VANRY could not be extracted. If the address or chain is wrong, there will be no second chance in the same operation. Therefore, authorization and lock-in transactions should take place during cool-down moments rather than at the last moment of the window.

Exchanges that have committed to migrate: Six names on the official list

For holders with balances on a centralized exchange, everything depends on whether the platform handles the migration itself. The portal maintains a list with links to relevant announcements. When we searched on August 17, 2026, there were six platforms on the list: Paribu, Bitvavo, LBank, Indodax, BingX and WEEX.

Among them, Bitvavo is the most important to German readers because the provider directly serves German customers. People holding VANRY there should look for authoritative information in the platform's own announcements and read it before moving any tokens.

What is missing from the list is worth noting. An English report on August 10 stated that KuCoin would automatically handle the migration. However, KuCoin was not on the official list of project parties on August 17. We were unable to resolve this difference, so we presented it truthfully: this was a media statement, but there was no corresponding one in the project party's own list. Please rely only on announcements from your platform.

The portal itself is cautious about general rules: each exchange conveys its own methods, some directly handle migration, and some require users to withdraw and redeem their own cash. Therefore, there is no unified statement covering all platforms.

Don't transfer directly from the exchange to the portal: Why you have to go through your own wallet

There is a particularly clear warning in the portal for those who want to save time: Tokens must never be sent directly from the exchange to the redemption portal. The route must first go through your own wallet.

The reason lies in the receiving process. The new VANRY will be sent to the same Base address as the old token lock address. However, the exchange's recharge address belongs to the exchange rather than the user, and may not necessarily be the same or exist on Base. Locked internally from the exchange account, you will specify a receiving address that you cannot access.

In practice, this means that you need your own wallet that can represent Base and make sure you can also access that wallet on Base. Which hosting method is appropriate and what the differences are, we explain in the comparison of software wallets. Project owners added that they never ask for private keys and should not use links from comments, private messages or forwarded screenshots. In fixed-deadline migration, this is not a cliché, because time pressure is what makes the fake portal work.

Old and new contract addresses: How to identify the real Base token

The project party announced the contract address in the portal. On Ethereum and Polygon, the old VANRY has the same address, which is 0x8de5b80a0c1b02fe4976851d030b36122dbb8624. On VanarChain, VANRY is a web-native currency, so there are no token contracts. The new VANRY address on Base is 0x07848a7 b542a9 cd856122c6c4 ab9 ec87 c44f8 b63.

These details are not decoration. After a fixed deadline for migration, counterfeit tokens with the same name and abbreviation often appear in large numbers. The contract address is a feature that cannot be forged and should be checked in your own wallet before making the first transaction.

The old contract still exists technically, but no longer points to anything meaningful.

Total supply changed from 2.4 billion to 10 billion: How 1:1 conversion changes your share

Conversion is 1:1, but this is not the case for the supply structure of the two tokens. We self-retrieved the public data records of these two contracts at approximately 03:53 (UTC) on August 17, 2026, and both returned an HTTP code of 200. This analysis was conducted by cryptoticker.io on August 17, 2026.

Records for old tokens show a total supply of 2,377,565,576 VANRY, with a maximum supply of 2.4 billion. The records of the new tokens on Base show that the total supply and maximum supply are both 10,000,000,000 VANRY, of which 3.8 billion is in circulation. It can be inferred from these two figures that 6.2 billion coins, or 62% of the new maximum supply, have not yet been circulated.

For holders whose balance remains unchanged during conversion, this means a change in share. Relative to their respective total supply, their share dropped to approximately 23.8% of the original value, or roughly one-quarter. This is a mathematical division, not a statement about price: how the market will react to this, these numbers do not include, and we do not draw any expectations or suggestions from them.

Another observation in the same search related to the status of the data. Entries for old tokens are now labeled "OLD" by data providers, showing zero circulation supply and no market value. Six days after the window opened, the data provider has regarded the old contract as replaced, even though it is still running and transferable on the chain. When the holder checks the balance on the price page, he may have seen the new token while the old token is still in his wallet.

Information we cannot get from this search: how many holders have completed the migration, how the 3.8 billion in circulating tokens will be divided between the redemption balance and other allocations, and the release schedule of the remaining 6.2 billion. The portal does not provide any verifiable relevant data.

The fate of the old VANRY contract after the redemption window closes

The project party is more cautious about describing the status after September 10, and some contents are still open. According to records, old contracts on Ethereum, Polygon and VanarChain no longer represent the active VANRY economy and will be deactivated after the window closes. Complete contract details and any final measures will be announced in advance through the official channels of the project party.

There are two technical points in the same FAQ that are worth explaining here because they are often confused. The old contract included a function that could suspend transfers at the contract level. According to the project party, there is no function that can lock, freeze, withdraw or change individual balances. As a result, the team cannot take away the balance of a particular holder, but can suspend the contract as a whole.

In practice, this means that old tokens will not disappear from your wallet on September 10. It will lose connection. Whether and when it can still be moved later depends on decisions that have not yet been made by the project party.

Tax treatment: Why conversions need to be documented

German tax authorities converting one cryptocurrency for another is regarded as a disposal of one asset and acquisition of another asset. During the one-year holding period stipulated in Article 23 of the German Income Tax Law, income generated will be subject to tax if it exceeds the annual tax exemption limit of € 1000.

Whether this principle applies to the transfer of the same token to a new contract in a 1:1 ratio is still unclear. We are not aware that the tax authorities have a clear statement on this specific process, and we do not assert anything that does not exist here. Both interpretations are possible: the process is regarded as a tax-neutral continuation of the same asset, or as a conversion with normal holding period and acquisition date consequences. The difference is whether your holding period continues or starts over.

In practice, this yields one recommendation that is correct in either case: document the entire process completely. Including the date and time of the locked transaction, the amount, the source chain, the transaction hash of the two parties, and the original acquisition date of the old token. If these details need to be pieced together later, once the old contract is suspended, it may not be found. The tax assessment itself should be left to the tax adviser.

Limitations of this analysis: What we can't verify

Three things remain unknown and are noted rather than hidden in footnotes.

First, we did not trigger the redemption personally. All process details come from the project party's own descriptions, not our attempts. Therefore, we cannot confirm whether delivery can actually be completed within four hours.

Second, the Binance announcement blocks automatic requests; the page responds to us with a rejection message rather than content. Readers can access it normally through a browser. We confirmed their content through search results from multiple independent industry publications and linked them in a regular manner.

Third, we have not obtained self-confirmation for platforms other than the official list. Which exchange handles the migration may also change in a short period of time; the list in the portal is a snapshot from August 17, 2026.

Check VANRY conversions: What you need to remember

Check immediately where your VANRY is stored.

If deposited on an exchange, announcements from your platform will determine whether you need to do it yourself. If your platform does not process migration, you must withdraw the balance into your wallet and redeem it there before September 10. If you need another platform, our comparison of the best regulated cryptocurrency exchanges will help.

If you have a pledge, please initiate the release of the pledge immediately.

The lock-up period is 21 days, and the key is the start time of the process, not the end time. At the same time, make sure you can actually access the receiving address on Base; please refer to our hardware wallet comparison for which hosting solution is suitable.

Record relevant data while redemption is in progress.

Dates, amounts, source chains, and transaction hashes between both parties should be recorded while still available. For tools that can continuously record these details, see our comparison of cryptocurrency tax tools and portfolio trackers.

(As of August 17, 2026. This article is not investment advice. Price and fee structures may change; please check terms with your provider before purchasing.)