QNet Wallet

One app with the same screens and the same features on every phone and tablet: the wallet, and a Node tab that runs this wallet's light node on the device. Keys stay in the device's secure storage. The app opens with the device's own authentication — Face ID, Touch ID, a fingerprint or the device passcode — and, on a device without any of them, with an app password; a wallet set up with an app password can switch to the device's authentication.

On Android it is one app, io.aiqnet.wallet: the file shared outside Google Play is the same signed build. It runs the whole wallet; its light node runs once Google Play licenses the install, which needs the Google Play listing to be live for your account, and until then its Node tab says to install QNet Wallet from Google Play. The app does not update itself: a newer version comes from the store, or as a newer file from the same place. On Android it is on Google Play; on iPhone and iPad, until the App Store listing is live, it installs from TestFlight.

Create or import a wallet, send and receive QNC, SOL and 1DEV, follow your history. Keys are generated in the browser and stored encrypted; they never leave it. The Activate tab burns 1DEV on Solana for a light or a super node, one activation per wallet, issues the activation code and, for a light node, records it on QNet Blockchain in the same approval; a light node then runs on a phone or tablet, a super node on a server. A site such as aiqnet.io can read the wallet's addresses only after you approve it in the extension.

A recovery phrase, generated locally, is the only backup. The publisher has no servers that hold keys, no accounts and no way to recover a lost phrase.

A light node runs on one phone or tablet at a time; computers and emulators cannot run one. Linking it to a device includes a device check by the device's operating system. A few times per four-hour epoch QNet Blockchain asks the device for a status answer; the device signs it and answers while QNet Wallet runs on it, open, in the background or behind the lock screen.

No hashing and no proof-of-work: each answer is one signature, so the device does no sustained work. For each epoch the chain records which nodes answered, and the protocol adds a share of that epoch's emission to their node balance — three quarters among light nodes, one quarter among super nodes. The wallet moves the node balance into itself with an ordinary transaction.

Nodes are activated at aiqnet.io/node. In Phase 1 a light node's 1DEV burn is made by the page from a one-time payment address in the browser, after QNet Wallet confirms the wallet, or by the QNet Wallet extension from its own address; a super node's burn only by the extension, and the super node runs on the user's own server with the QNet Blockchain node software. The tokens are destroyed, and the burn transaction is the proof. QNet Wallet then confirms the light node of its own wallet on its own screen and runs it on that device. One node per wallet, light or super. The app burns nothing, sells nothing and shows no price. Phase 2 moves activation to QNC. The documentation has the details.

Nodes keep about a day of transactions; the explorer keeps all of them. The wallet reads its QNet Blockchain history from the explorer archive and the freshest blocks from the nodes, and each confirmed transaction in it opens in the explorer. The app also lists the SOL and 1DEV sends made on that device, and says so above its History.

The app reads right to left where the language needs it.

• English
• 中文
• Русский
• Español
• 한국어
• 日本語
• Português
• Français
• Deutsch
• العربية
• Italiano