Qubetics announced on October 16, 2026, that it is making 29 GitHub repositories public after stopping development of its original blockchain and applications. The project, which reported raising over $18 million through its presale, said the release would preserve the work completed and allow developers, holders, and the wider community to independently examine what was built.
Qubetics described the publication as a step toward transparency, giving the public direct access to code previously held in private repositories. Independent developers can review, fork, or build upon the software, although the project is not announcing a new roadmap or committing to restart development.
The release covers 15 core repositories and 14 wallet repositories, including blockchain, decentralized VPN, explorer, and wallet software. Qubetics cautioned that the repositories are not necessarily ready for production use and may require further testing, configuration, and development. Chain abstraction repositories remain under technical review, with publication expected by the end of the following week.
Alongside the code release, Qubetics reported burning 333.64 million TICS, half its previous treasury balance. The burn reduces the maximum supply to 960.13 million TICS, leaving the treasury with 34.75% of the supply.
The project did not decide on the remaining treasury tokens, saying the balance would remain unchanged pending further review.
Qubetics Reversed Development Plans After Ethereum Migration
Qubetics announced its move from its own blockchain to Ethereum in August 2026, presenting the migration as a foundation for continued development of its Bitcoin chain abstraction protocol and decentralized VPN. TICS migrated to Ethereum in September, replacing the project’s native coin with an ERC-20 token.
Weeks later, Qubetics announced on October 6 that it had stopped commissioning development of those products and its Layer-1 blockchain. It also began ending its engagement with development contractor Antier, acknowledging that the original technology had not been delivered within the timeframe or scope expected.
Qubetics promised to publish the existing code so independent developers could inspect and build upon it. It left open the possibility of supporting future contributions but announced no developer program, funding commitment, or replacement roadmap.
