Over the past several months, Qubetics has been through a significant period of transition. The project was originally built around an ambitious Layer 1 blockchain and wider technical ecosystem. $TICS has since migrated to Ethereum as an ERC-20 token, and Qubetics has continued reviewing what the project's technical structure should look like following that transition.
When we announced the move to Ethereum in August 2026, our intention was to use Ethereum as the foundation for the next stage of Qubetics. At that time, we expected that elements of the wider technology, including chain abstraction and the dVPN, could continue to be developed within an Ethereum-based structure.
The migration went ahead, but our assessment of the wider technical roadmap continued. We reviewed the technology already developed, the work still required, the resources necessary to continue and whether adapting the original roadmap remained the right direction for Qubetics.
That review has now concluded, and some of the decisions reached differ from the direction described in August.
This update explains where Qubetics stands today, what happens to the technology already developed, the status of our relationship with Antier, changes to the $TICS token structure and what happens from here.
From the Original Qubetics Roadmap to Where We Are Today
Qubetics began with a technical roadmap centred around the development of its own Layer 1 blockchain. The wider vision included chain abstraction technology, a decentralised VPN and additional infrastructure intended to form a broader Qubetics ecosystem.
Antier was contracted by Qubetics to undertake development work across significant parts of this technology.
As the project progressed, Qubetics began reassessing whether the original blockchain architecture remained the appropriate foundation for the project. This ultimately led to the decision to transition $TICS from the original Cosmos-based environment to Ethereum as an ERC-20 token.
At the point that transition was announced, Qubetics still expected to explore continuing significant elements of the wider technology within an Ethereum-based structure. The August migration update reflected that position.
Following the migration, our assessment continued. After reviewing the development completed to date, the additional work required and the resources necessary to continue, Qubetics determined that pursuing the original technical roadmap under the existing development structure was no longer the appropriate path forward.
As a result, Qubetics is not currently commissioning continued development of the previously proposed Layer 1, chain abstraction protocol or dVPN.
We recognise that this differs from the direction described in August. That announcement reflected Qubetics' intended direction at that stage. This announcement reflects the decisions reached through the review that followed and represents the current position of Qubetics.
Where Things Stand With Antier
Antier was engaged by Qubetics as a technical development vendor, undertaking development work across significant parts of the Qubetics technology, including the Layer 1, chain abstraction protocol, dVPN, Qubetics Wallet and other related technology. Antier's role was limited to technical development and did not extend to the wider operations, management, tokenomics or strategic decision-making of Qubetics.
The code developed by Antier for Qubetics has been committed to Qubetics' official GitHub repositories from the beginning of the project. Qubetics is currently working with Antier to conclude the engagement and ensure the appropriate repository access and associated development materials are in place.
We appreciate Antier's cooperation as this process is completed.
The work completed during that engagement will not simply disappear. Once the engagement has concluded and the appropriate repositories have been reviewed, we intend to make that work publicly available. Independent developers and the community will be able to inspect what was built, study the repositories and, where appropriate, fork or build upon the existing codebases.
Making the code public also leaves the door open for development around Qubetics to emerge organically without requiring us to announce another roadmap today.
If developers ultimately create useful applications, integrations, tools or other products around Qubetics, we would be open to considering how meaningful contributions could be supported. There is no developer programme or commitment being announced. The immediate purpose of publishing the code is to preserve the work, make it accessible and allow its future potential to be explored openly.
We also do not intend to announce another development team, Layer 1 launch date or replacement delivery schedule simply to fill the space left by the previous roadmap. Any future technical development announced by Qubetics should be supported by a concrete and deliverable plan.
A Clarification Regarding Previous Community Updates
We want to address previous communications within the Qubetics community because individual moderators should not be unfairly held responsible for information they communicated in good faith.
Members of the community may previously have been told that development of the original Qubetics technology was continuing. At that time, continued development remained one of the options Qubetics was considering and was consistent with the direction described when the Ethereum migration was announced.
There was therefore no final decision to discontinue that direction for moderators to communicate.
The moderators were not withholding a decision that had already been made, nor were they knowingly providing information Qubetics had already determined to be incorrect. They communicated based on the information available to them at the time.
The $TICS Migration and Claim Portal
The migration of $TICS to Ethereum has taken place, but it is important to distinguish between the original migration process and claiming ERC-20 tokens already allocated to eligible holders.
The original migration process determined which tokens and holders were eligible to transition to ERC-20. The claim portal allows those with an existing eligible allocation to claim ERC-20 $TICS already set aside for them.
Those tokens are held within the migration claim smart contract, and there is currently no planned deadline for eligible holders to claim them.
Keeping the portal available does not reopen the original migration or create new migration eligibility. It simply allows existing eligible claimants to receive the ERC-20 tokens already allocated to them.
These tokens are also separate from the Qubetics-controlled allocations discussed below. Tokens held within the migration claim smart contract for eligible holders will not be included in the planned token burns.
The Entire Qubetics Team Allocation Has Been Burned
Alongside this announcement, we wanted to take an action that could be independently verified rather than simply making another future commitment.
Qubetics has permanently burned the entire $TICS allocation previously designated to the team.
That allocation was established under the original roadmap, which contemplated a considerably broader technical ecosystem than the structure that exists today. We also have to acknowledge that the original technology and roadmap did not materialise within the timeframe or to the extent expected by our community or by ourselves.
Given the project's revised structure, we did not believe it was appropriate for the team to retain an allocation established on the basis of that original roadmap.
For that reason, the entire team allocation has been permanently removed from the $TICS supply.
Team allocation burned: 68,093,398.2 $TICS
Transaction hash: 0x886........6f0ece
Total supply before burn: 1,361,867,964 $TICS
Total supply after burn: 1,293,774,565.8 $TICS
The burn has already taken place and can be independently verified on Ethereum using the transaction information above.
The $TICS smart contract contains a burn function and has no minting capability. The reduction in total supply is permanent, and the burned tokens cannot be recovered by Qubetics or recreated through subsequent minting.
Why This Does Not Conflict With the 1:1 Migration
Our August migration update stated that the transition to Ethereum would take place on a 1:1 basis and would not itself change the total $TICS supply.
That remains separate from the decision described above.
The migration itself was conducted on a 1:1 basis. The team-token burn was a subsequent decision made as part of the wider review of Qubetics' technical direction and token structure.
The migration therefore did not itself reduce the $TICS supply. The later burn did.
The Qubetics Treasury and $TICS Supply Review
Following the team allocation burn, the Qubetics Treasury currently holds 667,281,541.37 $TICS, representing approximately 51.6% of the current total supply of 1,293,774,565 $TICS.
These holdings include allocations originally designated for Network Operations, Reserves and other functions associated with the original Qubetics token structure, which was designed around a dedicated blockchain and a considerably broader technical ecosystem.
This figure does not include $TICS held separately within the migration claim contract for eligible holders. Those tokens have already been allocated to eligible claimants and do not form part of the Qubetics Treasury.
Following the move to ERC-20 and the subsequent technical review, we do not believe the original Treasury allocations should automatically remain simply because they formed part of the original tokenomics.
Once the existing development engagement has been concluded and the appropriate Qubetics codebases have been made public on GitHub, each remaining Treasury allocation will be reviewed to determine whether it continues to have a clear and justified purpose under the project's current structure.
This may include retaining an allocation intended to support independent developers and builders who make meaningful contributions to the Qubetics ecosystem, should a genuine need for such an allocation emerge in the future.
No developer programme or allocation for this purpose is being announced today. We simply do not want to permanently remove the possibility of supporting meaningful development around Qubetics before we know what opportunities may emerge from making the existing code public.
Equally, tokens will not be retained simply because they might become useful at some unspecified point in the future. Any allocation retained following the review will need to have a clearly defined and justified purpose. Allocations for which no such requirement remains will be permanently burned.
We are deliberately not announcing an estimated additional burn figure. The appropriate amount should be determined through the review rather than announced in advance and subsequently changed.
Once that process has been completed, we will publish the allocations retained, the number of additional $TICS burned, the allocations from which those tokens originated, the relevant transaction hashes, the resulting on-chain total supply and the number and percentage of $TICS remaining in the Qubetics Treasury.
Remaining Qubetics Holdings Will Be Locked for 12 Months
Following the allocation review and additional burns, Qubetics intends to lock its remaining token holdings for 12 months.
The exact structure will depend on the outcome of the review, including which allocations, if any, continue to have a justified purpose.
When the lock takes place, we will publish the number of tokens locked, the relevant wallet and locking contract information, the transaction details and the date on which the lock expires.
The community will therefore be able to verify the lock and its terms directly on-chain rather than relying solely on a statement from Qubetics.
Setting Clear Expectations Going Forward
As Qubetics moves through this transition, we also believe it is important to establish clear expectations around communication, decision-making and the $TICS token.
We understand that members of the community want regular updates, particularly during periods of uncertainty or when the market price of $TICS is under pressure. Questions, criticism and constructive feedback are all part of having an active community, and we will continue to listen to them.
At the same time, holding $TICS does not represent ownership of Qubetics, an equity interest in the project or a right to participate in the management of Qubetics. $TICS holders should not be regarded as shareholders, and token ownership does not create an entitlement to direct operational decisions, determine development priorities or require announcements according to a particular timetable.
The same distinction is important when discussing the market price of $TICS. Once a token is traded on an open market, its price is determined by buyers and sellers and can move in either direction. Qubetics cannot control, guarantee or promise a particular market price, nor would it be appropriate for us to make decisions simply in response to short-term price movements.
We also recognise the desire for frequent updates. However, we do not believe that publishing announcements simply because there is pressure to provide an update serves the community well. Where there is material information to communicate, we will communicate it. Where an action can be independently verified, we will provide the relevant information wherever possible. If a process is still underway and there is nothing substantive to add, we would rather wait until there is meaningful information than repeat previous statements or create expectations that may later change.
None of this means community feedback is unimportant. We value the people who continue to follow Qubetics, raise questions and contribute constructively. But listening to the community and allowing operational decisions to be dictated by community pressure are two different things.
Going forward, our approach will be simple. We will communicate material developments when there is something meaningful to report, avoid making commitments before they are ready to be made and provide verifiable information wherever possible.
We believe this is ultimately more useful to the community than providing updates for the sake of providing updates.
What Happens From Here
Our immediate priority is to conclude our existing engagement with Antier and ensure the appropriate repository access and associated development materials are in place.
The relevant Qubetics-owned repositories will then be reviewed and made publicly available through GitHub.
After publication, Qubetics will complete its review of the remaining controlled token allocations. Allocations without a justified purpose under the project's current structure will be burned. The remaining holdings will then be structured according to the outcome of that review and locked for 12 months.
The migration claim contract remains separate from this process. ERC-20 tokens already allocated to eligible claimants will remain available to them and will not form part of the Qubetics-controlled token review.
As these steps are completed, we will publish the relevant information and provide on-chain transaction details wherever applicable.
What This Means for the Future of Qubetics
The change in technical direction does not require us to decide today what Qubetics must become tomorrow.
Our focus now is narrower and more immediate. We need to conclude our existing engagement with Antier, ensure the appropriate repository access and associated development materials are in place, preserve and publish the work that already exists, establish an appropriate structure for the remaining Qubetics-controlled tokens and provide verifiable information as those actions are completed.
Publishing the existing code is an important part of that process. It means the technology already developed remains accessible and gives independent developers the opportunity to examine and, where appropriate, build upon it.
It also leaves the door open without creating another set of expectations.
There is no new Layer 1, developer programme, replacement ecosystem or technical roadmap being announced today. If useful development emerges around the published technology, Qubetics can consider it on its merits. If Qubetics later decides to undertake further development itself, that decision can be communicated when there is a concrete plan behind it.
For now, we believe that is a more responsible position than replacing one ambitious roadmap immediately with another.
Why This Update Is Being Made Now
Some members of the community may reasonably ask why these decisions are being communicated now rather than earlier.
The answer is that the final position had not yet been determined. Continued development remained under consideration while Qubetics assessed the work completed, the resources required and the appropriate structure following the Ethereum migration.
That assessment has now concluded. Our existing engagement with Antier is being brought to a close, the process of ensuring the appropriate repository access and associated development materials are in place is underway, and the team allocation has been permanently burned.
We recognise that some members of the community may have preferred definitive answers sooner. However, we did not want to communicate a final position before those decisions had actually been made.
Now that they have, we want the position to be clear.
Moving Forward With Transparency
The original Qubetics vision was ambitious, and we have to acknowledge that it did not materialise in the way originally intended. The technology and roadmap were not delivered within the timeframe or to the extent expected by the community or by Qubetics itself.
Changing direction does not rewrite that history.
Our responsibility now is to deal clearly with the position in front of us. Our existing engagement with Antier needs to be concluded, the appropriate repository access and associated development materials need to be in place, the Qubetics-owned development work will be preserved and published, and the token structure created around the original technical model will be reviewed against the project as it exists today.
The team allocation has already been permanently burned. Other allocations without a justified purpose will follow. Any tokens retained will need to have a clear reason for remaining, after which the relevant Qubetics-controlled holdings will be locked for 12 months.
We cannot change what was originally expected of Qubetics, but we can make the actions taken from this point transparent and, wherever possible, independently verifiable.
The next major milestone is the conclusion of our existing engagement with Antier, followed by the review and publication of the appropriate Qubetics codebases. We will provide further information as that process and the subsequent token review are completed.
Thank you to everyone who has continued to engage with Qubetics, ask difficult questions and follow the project through this transition.
Qubetics
Frequently Asked Questions
Why does today's position differ from the August migration announcement?
The August announcement reflected Qubetics' intended direction at that point. Qubetics expected to explore continuing elements of the original technology within an Ethereum-based structure, while its wider technical assessment remained ongoing.
That assessment subsequently resulted in a different decision. The August article therefore remains a record of the direction being considered at that stage, while this announcement represents Qubetics' current position.
Is Qubetics still developing its Layer 1 blockchain?
At present, Qubetics is not commissioning continued development of the previously proposed Layer 1 blockchain, chain abstraction protocol or dVPN.
The immediate focus is concluding the existing development engagement, ensuring the appropriate repository access and associated development materials are in place, and publishing the appropriate Qubetics-owned codebases through GitHub.
Does this mean the original Qubetics technology will never be developed further?
No decision has been made that permanently prevents elements of the technology from being revisited in the future.
Publishing the appropriate codebases will also allow independent developers to examine and, where appropriate, build upon the existing work.
This should not be interpreted as an announcement that further development will take place. It simply means that the work will remain accessible and its potential future use is not being closed off.
Is Qubetics ending its relationship with Antier?
Yes. As Qubetics moves away from the original technical roadmap, our existing development engagement with Antier is being brought to a close.
Antier has confirmed that the code developed during the engagement has been committed to Qubetics' official GitHub repositories from the beginning of the project and that Qubetics owns the code developed for the project. We are now working with Antier to ensure the appropriate repository access and associated development materials are in place.
Once that process has been completed and the relevant materials have been reviewed, the existing engagement will conclude.
What will happen to the technology that has already been developed?
The appropriate Qubetics-owned codebases will be reviewed and published through GitHub once the necessary repository access and associated development materials are in place.
This will allow the community and independent developers to inspect what was built, study the repositories and, where appropriate, fork or build upon the existing work.
Could Qubetics support developers who build on the published code?
Potentially, but no developer programme or reward structure is being announced.
The upcoming token review may consider whether retaining an allocation to support meaningful independent development has a justified purpose. This would only be relevant if a genuine need emerges in the future.
The intention is to preserve flexibility, not to suggest that a developer programme is coming.
Why was the community previously told that development was continuing?
Because continued development remained under consideration at the time. A final decision to change direction had not yet been made.
The moderators communicated based on the information available to them and were not withholding a decision or knowingly communicating information Qubetics had already determined to be incorrect.
Why did Qubetics move $TICS to Ethereum?
The transition moved $TICS into Ethereum's established token infrastructure and was intended to provide broader compatibility and integration possibilities.
At that time, Qubetics also expected to explore continuing elements of the wider technology within an Ethereum-based structure. The decision not to continue the original technical roadmap under the existing development structure was reached subsequently.
The previous article said the $TICS supply would remain unchanged. Why has Qubetics now burned tokens?
The previous statement referred to the 1:1 migration itself.
The team-token burn was a separate decision made later as part of the wider review of Qubetics' technical direction and token structure. The migration did not itself reduce the supply. The subsequent burn did.
Why did Qubetics burn the entire team allocation?
The allocation was established around the original Qubetics roadmap and its broader technical ecosystem.
Following the change in structure, Qubetics did not believe it was appropriate for the team to retain an allocation established on the basis of that original roadmap. It was therefore permanently burned.
Can the burned team tokens ever be recovered or replaced?
No. The $TICS smart contract has no minting capability. Tokens removed through its burn function cannot be recovered by Qubetics or recreated through subsequent minting.
Will there be further $TICS burns?
Qubetics will review its remaining controlled allocations after the Antier handover and GitHub publication.
Allocations that no longer have a clear and justified purpose under the project's current structure will be permanently burned.
How many additional $TICS will be burned?
That has not yet been determined.
Rather than announce an estimate, Qubetics will complete the allocation review first. The exact amounts, affected allocations, transaction hashes and resulting on-chain total supply will then be published.
What will happen to tokens that are not burned?
Any retained Qubetics-controlled allocation will need to have a clearly justified purpose.
Following the review and additional burns, Qubetics intends to lock its remaining holdings for 12 months under the structure established through that process. The amount, relevant addresses, transaction information and expiry date will be published.
Is the migration portal going to close?
There is currently no planned deadline for eligible holders to claim ERC-20 $TICS already allocated to them within the migration claim smart contract.
Keeping the claim portal available does not reopen the original migration or create new eligibility.
Will tokens in the migration claim contract be included in the burns?
No. ERC-20 tokens already allocated within the migration claim smart contract for eligible holders are separate from Qubetics-controlled allocations and will not be included in the planned burns.
Is Qubetics shutting down?
No. Qubetics is transitioning its technical direction, not shutting down.
The immediate work is focused on concluding the existing development engagement, ensuring the appropriate repository access and associated development materials are in place, publishing the appropriate Qubetics-owned codebases and restructuring the remaining Qubetics-controlled token allocations.
Publishing the code also ensures that the technology already developed remains accessible without requiring Qubetics to make new promises today about what will be built next.
What happens next?
The next major step is to conclude the existing development engagement and ensure the appropriate repository access and associated development materials are in place, followed by the review and publication of the appropriate Qubetics-owned codebases through GitHub.
Qubetics will then complete its review of the remaining controlled token allocations, burn allocations without a justified purpose and establish the structure for the remaining holdings and 12-month lock.
Relevant information and on-chain transaction details will be published as those actions are completed.