As promised in our previous update, Qubetics is beginning the public release of technology developed for the Qubetics ecosystem.
Today, 15 core Qubetics repositories and 14 Qubetics Wallet repositories are being made publicly accessible. This is an important step in making the technology available for developers, validators, holders, other interested parties and the wider community to independently inspect, review and, where appropriate, build upon.
The repositories are being released in their current state. Publication provides transparency and some degree of predictability in accessing the work completed.
Qubetics Public Repository Directory
The first release of core Qubetics technology comprises 15 repositories covering the Layer 1 blockchain, core applications, dVPN infrastructure and explorer services.
The full repository directory, including the relevant mainnet and testnet branches and accompanying technical documentation, is available here:
Qubetics Public Repository Directory
Developers can use the directory to navigate the available repositories, identify the appropriate branches and access supporting documentation.
Using the Published Code
Developers are free to inspect, fork and build upon the code in its current form. However, publication should not be interpreted as confirmation that every repository represents a final production-ready release.
Anyone choosing to clone, deploy or build upon the code should carry out their own technical review, testing, configuration and any development work required for their intended use.
The repositories are being made available to preserve the work completed and allow it to be independently examined. They are not being presented as turnkey products that can necessarily be used without further technical work.
Qubetics Wallet Repositories
Alongside the core Qubetics technology release, 14 Qubetics Wallet repositories are also being made public today.
These repositories cover the wallet backend, scheduler, blockchain indexers, administration panel, browser extension, mobile application and supporting dVPN macOS helper:
- wallet-backend
- wallet-scheduler
- wallet-indexer-bsc
- wallet-indexer-btc
- wallet-indexer-eth
- wallet-indexer-polygon
- wallet-indexer-solana
- wallet-indexer-tron
- wallet-indexer-tics
- wallet-indexer-cosmos
- wallet-admin-panel
- wallet-browser-extension
- wallet-mobile-app
- dvpn-macos-helper
The wallet application incorporates certain third-party open-source dependencies. Since the original wallet development, some of these upstream projects have released newer versions.
Limited commits may be made to the wallet repositories over the coming days to update relevant third-party dependencies, configuration or documentation, helping developers access and work with the existing code more easily.
These commits do not represent new feature development, a new product roadmap or a commitment to make every repository fully operational without further work. Developers should carry out their own technical review, testing, configuration and development work for their intended use.
Chain Abstraction Remains Under Review
The repositories relating to the chain abstraction development are not included in today’s initial public release.
This includes components relating to the Chain Abstraction Backend, Solver Onboarding Backend, Crypto API Service, BTC Sync Service and the Chain Abstraction MPC Node.
These repositories are undergoing a separate technical review before publication. Given the technical nature of this work and the different components involved, we believe it is appropriate to complete that review before making the repositories publicly accessible and providing further information about their functionality.
We currently expect the relevant chain abstraction repositories to be made public by the end of next week.
Once published, developers and other technically experienced members of the community will be able to inspect the code directly and independently assess the work that was developed and how the different components operate.
Why We Are Publishing the Code
Our previous update committed to making the technology developed for Qubetics publicly available.
Publishing these repositories puts that commitment into practice. It preserves the technology that has been developed, makes it accessible beyond private repositories and enables independent review by developers and the wider community.
The release is intended to provide transparency. Rather than asking the community to rely solely on descriptions of the technology, Qubetics is making the available code accessible for direct examination.
Treasury Token Burn
The size of the Qubetics treasury allocation has been a consistent question within the community. In particular, many holders have asked for clarity around the treasury wallet’s previous holding of 667,281,541.3722 TICS tokens.
To address this, Qubetics has permanently burned 333,640,770.6861 TICS tokens, equal to 50% of the treasury wallet’s prior balance.
Before the burn, the maximum TICS supply was 1,293,774,565.8 TICS. Following the burn, the maximum supply is now 960,133,795.1139 TICS.
The treasury wallet now holds 333,640,770.6861 TICS tokens, representing approximately 34.7494% of the new maximum supply.
No decision is being announced today regarding the use of the remaining treasury tokens. They will remain unchanged while further review is completed.
The purpose of this burn is to materially reduce the treasury allocation and provide greater clarity around the token supply, while allowing appropriate time for the remaining balance to be reviewed carefully.
Verify the Treasury Burn
Treasury allocation burned: 333,640,770.6861 TICS
Transaction hash: View the treasury burn transaction
Maximum supply before burn: 1,293,774,565.8 TICS
Maximum supply after burn: 960,133,795.1139 TICS
Treasury balance after burn: 333,640,770.6861 TICS
Remaining treasury allocation: approximately 34.75% of the maximum supply
What Happens Next
Today’s release is the beginning of an ongoing process of making the available Qubetics technology accessible to the community.
Where appropriate, limited commits may be made to improve usability of the existing repositories, including updates to relevant dependencies, configuration or documentation. These commits are intended to reduce friction for developers working with the existing code. They do not represent new feature development or a commitment that the repositories will operate without additional technical work.
We will provide a further update as the chain abstraction review progresses and the remaining repositories become available.
This publication does not represent the announcement of a new Qubetics development roadmap or a commitment to restart the original development programme. It is about preserving what was built, making it accessible and allowing it to be independently examined and, where appropriate, developed further.
Qubetics
Frequently Asked Questions
What is being published today?
Qubetics is making 15 core technology repositories and 14 Qubetics Wallet repositories publicly accessible. These cover the Layer 1 blockchain, core applications, dVPN infrastructure, explorer services and wallet-related components.
Where can I find the repository directory?
The Qubetics Public Repository Directory contains the available core repositories, relevant mainnet and testnet branches, and accompanying technical documentation.
Can anyone review or build upon the code?
Yes. Developers and other technically experienced community members can inspect the public repositories, review the code and, where appropriate, fork or build upon it.
Does publication mean that every repository is production-ready?
No. The repositories are being released in their current state to make the technology accessible and open to independent review. Anyone choosing to use or build upon the code should conduct their own appropriate technical review, testing, configuration and development work.
Will the repositories continue to receive updates?
The repositories may receive limited commits to improve usability, such as updating relevant third-party dependencies, configuration or documentation that helps developers access and work with the existing code more easily.
These commits do not represent new feature development, a new product roadmap or a commitment to make every repository fully operational without further work. Anyone cloning, deploying or building upon the code should expect to carry out their own technical review, testing, configuration and any development work required for their intended use.
Why are the wallet repositories also being updated?
The wallet application uses certain third-party open-source dependencies. Some of those upstream projects have released newer versions since the original wallet development. Limited updates may be made to reflect the latest appropriate versions of those dependencies.
What is happening with the chain abstraction repositories?
The repositories relating to the chain abstraction development are undergoing a separate technical review before publication. We currently expect them to be made public by the end of next week.
Does this announcement introduce a new Qubetics development roadmap?
No. This release is intended to preserve and make accessible technology developed for Qubetics. It does not represent an announcement of a new development roadmap or a commitment to restart the original development programme.
Why is public access important?
Public access allows developers, holders and the wider community to independently examine the available technology rather than relying only on descriptions of what was developed.