Qubetics | Layer 1 Web3 Multi-chain Aggregator | Presale Is Live
Qubetics Publishes Additional Source Code and Archives GitHub Repositories for Review

Following our previous announcement, Qubetics Begins Public Release of Its Technology on GitHub, we would like to provide a further update on the publication of the technology developed during the original Qubetics development programme.

As previously communicated, our intention has been to make the existing source code publicly accessible, allowing developers, holders and the wider community to independently examine the work undertaken.

We can now confirm that the remaining chain abstraction repositories have been made public, alongside the updated Qubetics Wallet source code and its supporting components.

With these additional repositories now available, we have also taken the decision to archive the Qubetics GitHub repositories while we carry out a broader evaluation of the published technology.

Chain Abstraction Source Code Now Public

The source code relating to the chain abstraction development, which remained under technical review at the time of our previous announcement, has now been made publicly accessible.

Qubetics/qubetics-chain-abstraction

This allows developers and other technically experienced members of the community to examine the implementation directly, including the architecture, underlying components and functionality developed as part of the original programme.

It is important to distinguish between making source code available and confirming that a technology achieved every objective originally envisioned for it.

Publication does not constitute certification that the chain abstraction implementation is complete, production-ready or capable of delivering all the functionality described in the original roadmap.

Instead, it provides the opportunity for independent technical assessment, allowing the code itself to serve as the primary source of information about what was developed.

Qubetics Wallet Source Code Now Public

The updated Qubetics Wallet source code has also been made publicly accessible.

This release includes the mobile application, browser extension, backend infrastructure, blockchain-specific indexers, scheduling services and administration components.

The following repositories form part of the Wallet publication:

1. qubetics-mobile-app

2. qubetics-extension

3. qubetics-wallet-backend

4. qubetics-wallet-indexer-bsc

5. qubetics-wallet-indexer-btc

6. qubetics-wallet-indexer-eth

7. qubetics-wallet-indexer-pol

8. qubetics-wallet-indexer-sol

9. qubetics-wallet-indexer-tron

10. qubetics-wallet-indexer-tics

11. qubetics-wallet-indexer-cosmos

12. qubetics-wallet-scheduler

13. Wallet Admin Panel

Together, these repositories provide visibility into the different components developed to support the Qubetics Wallet and its integration with multiple blockchain networks.

As with the other repositories, publication allows the community to independently inspect the code, assess its functionality and understand the technical work undertaken.

The availability of source code should not be interpreted as a guarantee of security, completeness or production readiness. Developers wishing to use any part of the technology should carry out their own appropriate testing and security assessments.

Qubetics GitHub Repositories Archived

Following the publication of these additional repositories, Qubetics has archived its GitHub repositories while we evaluate the codebases and supporting documentation.

Archiving places the repositories into a read-only state, preventing further commits and modifications to the archived repositories during this review.

This decision is intended to preserve the published code in a consistent and accessible state, providing a clear reference point for the technology as it currently stands.

The repositories remain publicly accessible, and developers can continue to inspect, download and, where permitted by the applicable licences, fork the code for their own independent work.

Archiving does not represent a conclusion regarding the quality, completeness or future potential of the technology. It is a measure to preserve the existing code while its technical implementation is assessed.

Any decision to resume development, modify the repositories or undertake additional technical work would be communicated separately.

Independent Review and Transparency

One of the primary reasons for making the Qubetics technology public has been to provide greater transparency around the original development programme.

Throughout that programme, substantial technical work was undertaken across the Layer 1 blockchain, Wallet, dVPN, chain abstraction and supporting infrastructure.

However, the existence of developed code and the successful delivery of every intended feature are not necessarily the same thing.

Rather than attempting to characterise every technical outcome through announcements alone, we believe it is more constructive to make the underlying work accessible for independent examination.

Developers can now review the relevant implementations, identify the functionality present, examine how different components interact and form their own conclusions about the technology.

We recognise that this process may lead to further technical questions. Where clarification is necessary, we will aim to distinguish between documented functionality, intended functionality and matters that require additional verification.

Our objective is to provide an accurate and transparent record of the development work, without speculation or premature conclusions.

What Happens Next

With the additional repositories now public, our immediate focus is on reviewing and preserving the existing code and accompanying technical documentation.

As previously communicated, Qubetics is not announcing a restart of the original Layer 1 development programme or a new roadmap for the technologies being published.

The source code is being made available so that the work undertaken can be independently examined and, where appropriate, used as a foundation for further development by interested parties.

We appreciate Antier's cooperation throughout the publication process and the technical work undertaken during the original engagement.

We will continue to provide relevant updates where there is verified information to share.

Our position remains straightforward: the technology should be accessible, the development work should be independently verifiable, and the code should be available for others to examine and evaluate for themselves.

Qubetics

Frequently Asked Questions

1. Does publishing the chain abstraction source code mean the technology was completed?

No. Publishing the source code confirms that the development work is now publicly accessible for independent examination. It does not, by itself, establish that every feature or capability originally intended for chain abstraction was successfully implemented or achieved its intended functionality.

The repositories allow developers to assess the actual implementation, its capabilities and any limitations directly.

2. Does the publication of the Wallet repositories mean the Qubetics Wallet is fully functional?

The Wallet repositories contain the source code for the mobile application, browser extension, backend services and supporting blockchain infrastructure developed during the original programme.

Their publication does not constitute a guarantee that every feature is complete, fully operational or production-ready. The code is being made available for independent technical examination, and anyone considering using it should conduct appropriate testing and security assessments.

3. Why have the Qubetics GitHub repositories been archived?

The repositories have been archived to preserve the published code in its current state while Qubetics evaluates the technology and accompanying documentation.

Archiving prevents further commits to those repositories during this process, providing a consistent reference point for independent review. It does not prevent the public from accessing, downloading or examining the code.

4. Can developers still use or build upon the code?

Yes. The public repositories remain accessible despite being archived. Developers can inspect and download the code and, where permitted by the applicable licences, fork it or use it as a foundation for their own development.

Anyone choosing to build upon the technology is responsible for conducting their own technical and security assessments.

5. Does this announcement mean Qubetics is restarting development of the original technology?

No. As communicated previously, Qubetics is not announcing a restart of its original Layer 1 development programme or introducing a replacement development roadmap.

The purpose of publication is to preserve the work undertaken, make it independently accessible and allow interested developers to examine or potentially build upon it.

6. Will Qubetics provide further clarification if developers identify technical issues or limitations?

We recognise that making the source code public may lead to additional technical questions and independent findings.

Where relevant information can be reliably verified, Qubetics will consider providing further clarification. However, we will avoid speculation or drawing conclusions before the underlying technical details have been properly assessed.

Our intention is to ensure that any information communicated about the technology is accurate, factual and supported by verifiable evidence.