Skip to content

Official Support vs. a Community Project

Qubic-Hub's wallet is a genuine, community-built option — but it's built by volunteers, not the Qubic core team, and its own documentation is upfront about that.

Decide fast

Official Support vs. a Community Project

Qubic-Hub's wallet is a genuine, community-built option — but it's built by volunteers, not the Qubic core team, and its own documentation is upfront about that.

Community wallets play a real role in any ecosystem. Here's what's actually different between the official desktop wallet and Qubic-Hub's community project.

A Fair Starting Point

Community wallets play a real role in any ecosystem — they fill gaps, reach platforms the core team hasn't prioritized, and are often built by people who genuinely care about the project succeeding. Qubic-Hub's wallet is exactly that kind of effort: a multi-platform application built and maintained by community volunteers, backed by qubic.li's infrastructure rather than official Qubic servers. The comparison here isn't about tearing that down; it's about being clear on what you're actually getting with each option, since 'official' and 'community' carry real, practical differences in support and guarantees, whatever the intentions behind either project.

Feature Comparison

Feature Qubic Desktop Wallet (official) Qubic-Hub Wallet (community)
Built by Qubic core team Community volunteers
Support Official support channels Project states it cannot guarantee support
Crypto library audit status Not independently audited Project's own documentation flags it as not yet audited
Platforms Windows, macOS, Linux Android, Windows, Linux (others in progress)
Release cadence Nine releases in the latest cycle, actively patched Not confirmed
Backing infrastructure Qubic core team's own repos Backed by qubic.li, a third-party infrastructure provider
Qearn staking Yes, built in Not confirmed
MSVault multi-signature Yes Not confirmed

What 'No Support Guarantee' Actually Means

It's worth being specific about what this difference means in practice, rather than leaving it as an abstract phrase. If something goes wrong with an official wallet — a sync bug, a transaction question, an unclear error — there's an accountable team behind it with a track record of responding to issues and shipping patches. Qubic-Hub's own project documentation directly states it cannot guarantee support for its users. That's an honest, responsible disclosure on their part, not a hidden flaw — but it's a meaningfully different experience if you run into a problem and need help resolving it, particularly with something as consequential as a wallet handling real funds.

On the Unaudited Crypto Library

Qubic-Hub's own documentation flags its cryptographic library as not yet audited, alongside a direct statement that the team cannot support users in any case. An unaudited crypto library isn't automatically broken or unsafe — plenty of unaudited code works correctly — but an audit is specifically the process of having independent security researchers verify that cryptographic code does what it claims and doesn't contain exploitable flaws. Without one, that verification simply hasn't happened yet for a component handling private key security. This is exactly the kind of gap official, actively-maintained software is built to close: the desktop wallet's crypto handling is public, reviewable, and backed by a team with ongoing responsibility for it.

Backing Infrastructure Matters More Than It Sounds

Qubic-Hub's wallet runs on infrastructure provided by qubic.li, a separate third-party service rather than Qubic's own official servers and repositories. This isn't necessarily a problem in itself — plenty of legitimate software relies on third-party infrastructure — but it does mean an additional layer of dependency sits between you and the network: if qubic.li's infrastructure has an outage, changes its terms, or discontinues support, Qubic-Hub's wallet is affected in ways the official desktop wallet, built directly against Qubic's own infrastructure, is not. It's a subtle difference until it matters, and worth understanding upfront rather than discovering during an outage.

Neither Choice Is About Loyalty

It's worth saying plainly: choosing between these two wallets isn't a statement about which community you support, and switching from one to the other isn't a betrayal of anything. Your seed works across official Qubic wallets, so if you've been using Qubic-Hub's wallet and want the additional assurances of core-team support and an actively audited codebase, moving over is straightforward and doesn't require abandoning any funds or history — everything you hold is tied to your seed and visible on the network itself, not locked into whichever wallet application you happen to be using at a given moment.

A Fair Note

Qubic-Hub's wallet is a real, legitimate community effort — it's just not the same thing as official, core-team-backed software. Both can coexist; this page is about helping you choose knowingly, not about disparaging a volunteer project. If you're already using it and it works for you, there's no urgency to switch — but if you're deciding between the two for the first time, the support and audit differences above are worth weighing seriously, especially for anything beyond a small test amount.

How to Decide

If you're weighing this decision for the first time, a few honest questions can help: How much QUBIC are you actually planning to hold in this wallet — a small amount for testing, or a meaningful portion of your holdings? Would you know who to contact and what to expect if something went wrong? Are you comfortable relying on software whose core cryptographic components haven't yet gone through independent security review? None of these questions have a universally right answer, but they're the right ones to ask before committing funds to either option, and the honest answers usually make the decision fairly clear for your specific situation.

Respecting the Community Effort

None of the above is meant to diminish what Qubic-Hub's volunteers have built. Community-maintained software fills real gaps and reflects genuine care from people who didn't have to build anything at all. The comparison exists so you can make an informed choice, not to steer you away from a legitimate project out of brand loyalty.