How Qblockx works

Two layers, one gap

A wallet is not "cold" because it is slow or inconvenient. It is cold because the private key has no network path to a remote attacker. Qblockx splits the system into two layers with different jobs and different trust:

• The cold layer holds private keys and signs transactions. It exposes no listening network service, so nothing can reach in from outside to ask it for a key, because there is nothing there to answer.
• The connected layer is the interface you use: balances, history, requests. It holds no private keys, so compromising it exposes data, not funds.

The two exchange exactly one thing: an unsigned transaction going in, and an already-signed transaction coming out. The key moves in neither direction.

The bridge transfer

"Bridging" is where cold-storage claims usually go vague. This is the sequence a transfer actually follows:

1. The connected layer builds an unsigned transaction: from your address, to a destination, for an amount, with a fee. Incomplete and harmless.
2. It crosses to the cold layer as data, by one-way presentation. The cold layer opens no return channel.
3. The cold layer re-validates against its own view of the ledger: balance covers it, destination is well-formed for the chosen network, fee is inside your configured ceiling. A tampered request is rejected here, and rejection is the safe default.
4. The required signatures are applied inside the cold layer. This is the only step that touches a key.
5. The signed transaction crosses back and is broadcast. Signatures do not generalise to a different transaction, so what leaves the cold layer cannot be edited in transit and remain valid.

The security property is that no party needs to be trusted absolutely. The online tier can request but cannot compel. Only a signature made in the cold layer moves coins, and only the destination chain can confirm the result.

What backs a balance

A Qblockx balance is not a claim on a shared pool and not a token backed by something else in a vault. It is a real coin or token on its own blockchain, held at an address whose spend condition includes your key. When the platform shows 1.5 BTC, that is 1.5 BTC on the Bitcoin chain, checkable by anyone with the address, on a public ledger, without asking us.

That distinction is the whole reason this page exists. On a pooled platform your balance is an IOU against a pot that might be lent out, and "backed" means the operator promises it is there. Here, "backed" would be redundant: the asset is the asset, and the only question of substance is who can authorise moving it, which the custody document answers.

How it settles

Deposits settle when the source blockchain confirms the transaction into a block. Qblockx credits after the confirmations that chain requires, not on first sight, because a transaction visible in the mempool is not yet final. Cold storage is not a barrier on the way in; no signature of yours is needed to receive.

Withdrawals settle outward through the bridge sequence above and are final when the destination chain confirms them. Between those moments the platform's ledger is a record of what the chains report, not a parallel system of credit that has to be redeemed later.

The exception, stated for completeness: value you deliberately deploys, mining rewards awaiting claim and investment positions, is not a direct on-chain holding. It is a claim on Qblockx, with our credit risk attached.

Which chains, and how a transfer is verified

Withdrawals move on these networks, matching the product's withdraw flow:

• USDT on Tron (TRC-20) — default, normally fastest and cheapest.
• USDT on Ethereum (ERC-20)
• Bitcoin (BTC)
• Ethereum (ETH)
• BNB on BNB Smart Chain (BEP-20 / BSC)

A transfer is verified twice, by parties that do not rely on each other. Before anything is signed, the cold layer re-checks the request against its own view of the chain, and a request that fails is rejected rather than passed through. After release, the network verifies it: every node checks the signature, and a replayed or edited transaction fails validation and is dropped.

What "cold storage" means here, and where the keys live

In this product, cold storage means key material held in a signing environment with no inbound network exposure. Not a metaphor for "slow". Not a label for a database with a password on it. Concretely: no listening service an off-box attacker can query, and no path from the web tier into key storage. The only thing that ever leaves is a signed transaction, which is public anyway once broadcast.

Where the cold keys live: in that air-gapped signing layer, created there at wallet setup from a cryptographically secure entropy source, and never transmitted to the connected layer afterwards. The connected layer keeps the public derivation information it needs to compute your receiving addresses and display balances. Knowing an address and a balance confers no ability to spend. Access to the signing environment is restricted and logged, and is separate from the credentials that administer the web application, so an administrative password reveals the dashboard rather than the keys. The full control model, including the multisig threshold and the option to keep your phrase entirely offline, is in Custody & Security.

Mining cycle length

As implemented today there is no fixed mining cycle. A rig accrues at a fixed rate per day from the moment it starts, and you claim into your wallet whenever you choose. There is no N-day term, no maturity date, and nothing that has to complete before earnings are yours. Rates are on the mining page.

If a fixed cycle is introduced it will be published here as a number of days before it is sold, with the rate table and claim mechanics updated in the same change. Until then the accurate answer to "how long is a cycle" is that the product has none, and we would rather say that than print a figure the system does not enforce.

Storage versus deployed value

Your dashboard shows things the landing page does not mention: a premium virtual card, mining rewards, investments, gated behind paid tiers. Those are not storage tiers. Reading the two sets of claims as one is the commonest way to misunderstand this platform.

If anything here is out of date, tell us at support@qblockx.com and we will fix it.