# Ecosystem Overview
Learn about the Qubic ecosystem and its core project areas.
Source: https://www.qools.org/en/docs/ecosystem
---
# Glossary
The following terms are widely used in the Qubic documentation and development ecosystem.
Source: https://www.qools.org/en/docs/learn/glossary
### Aigarth [#aigarth]
Aigarth is a project focused on AI technology, aiming to solve artificial intelligence challenges by leveraging idle computing resources through the Qubic network. It runs a unique algorithm based on spiral logic gates, capable of evolving solutions in response to demand, and the process is publicly transparent. All participants can track progress and collectively drive the pursuit of efficient solutions.
### Arbitrator [#arbitrator]
In Qubic’s dispute‑resolution mechanism, the arbitrator plays a critical role. It is dedicated to handling conflicts and safeguarding users’ rights within this self‑sufficient ecosystem. Its core responsibilities include setting miner algorithms, ranking compute nodes each epoch, replacing under‑performing nodes, and aggregating the $QUBIC that under‑performing nodes failed to receive.
### Candidate [#candidate]
A candidate may become a compute node within each epoch, provided it ranks in the top 676 in scoring. Up to 256 candidates have the chance to achieve this promotion. Typically, only those who have run for a full week and performed exceptionally will receive $QUBIC as a reward. Candidates do not receive any $QUBIC, but working as a candidate is the first step toward pushing solutions onto the blockchain, a necessary condition for becoming a compute node.
### Computor [#computor]
A computor is a machine or node that participates in the network consensus protocol and executes computational tasks. It is a key component of the Qubic network, responsible for executing transactions and running smart contracts on Spectrum.
### Computor Controlled Fund / CCF [#computor-controlled-fund--ccf]
The Computor Controlled Fund is a community‑centric funding system whose primary goal is to promote the growth and development of the Qubic ecosystem. It provides financial support for projects that enhance, expand, or improve the functionality, influence, and efficiency of the Qubic network. Projects are selected through community proposals and voting. CCF can rapidly integrate project plans and ensure efficient, orderly budget allocation. Its purpose is to co‑plan the community’s development path and ultimately give decision power to computors.
Key aspects of CCF include:
* **Project Proposals:** Any community member can submit proposals aimed at improving or expanding the Qubic ecosystem.
* **Community Voting:** Projects are selected and funded based on community engagement and consensus, ensuring that funds go to widely recognized and supported projects that align with community needs.
* **Rapid Implementation:** Once approved, funding is quickly deployed to realize proposals, fostering innovation and accelerating the ecosystem’s adaptive development.
### Energy [#energy]
The amount of QUs a given ID holds on Spectrum (analogous to a “balance”).
### Epoch [#epoch]
During a one‑week period (starting at 12:00 UTC on Wednesday and ending at the same time a week later), 1 trillion $QUBIC are created. After a halving event, only 450 billion $QUBIC are in effective circulation each epoch.
### Identity (ID) [#identity-id]
Qubic’s wallet address, also the identity ID of a computor. In Qubic, miners are crucial to supporting computors: miners fetch problems or tasks from computors. When a solution for a given address ID is found, miners send the result back to the computor. This continuous exchange between tasks and solutions is key to determining each computor’s score within an epoch. A high score is essential for maintaining a top‑676 position.
### Oracles [#oracles]
One of the features being developed on Qubic involves “oracles” from blockchain technology. These are third‑party services that allow smart contracts to receive external data and information. Thus, smart contracts can link the virtual world to real‑world conditions and execute actions that must adjust to reality.
### $QUBIC [#qubic]
In the Qubic ecosystem, $QUBIC or QUs serve as the “energy” unit, used to run smart contracts and obtain other services. These units can be exchanged as a form of currency, but they also represent a resource investment—just as electricity powers a power grid, $QUBIC powers functionality in Qubic. Transfer operations are free and do not involve “fees” to the smart contract, because $QUBIC is consumed rather than compensated to the computor.
When interacting with oracles, a requester consumes a specific amount of $QUBIC as a form of investment or sacrifice, rather than directly paying the oracle. Therefore, we cannot guarantee that every query will receive a response; oracle replies are not deterministically guaranteed.
### Quorum [#quorum]
A quorum is the minimum number of participants required to make decisions for various matters. In Qubic, the quorum required for consensus is two‑thirds of all computors (or 451 computors).
### Quottery [#quottery]
Quottery is one of Qubic’s first smart contracts, enabling decentralized wagering with transparent payouts that make the process fair and predictable.
* 10 % goes to the Computor Controlled Fund
* 20 % is distributed to Quottery shareholders
* 70 % goes to the winning bettor
This marks the beginning of Qubic’s first oracle application, signifying an important milestone in technical practice.
### Qx [#qx]
Qx is the first decentralized exchange (DEX) in the Qubic ecosystem. In epoch 65, it completed an IPO (initial public offering) by selling a total of 676 shares to the community. Qx holders enjoy passive income from trading fees, thanks to the network’s ability to process up to 40 M transactions per second, providing a unique profit opportunity to shareholders.
### Smart Contracts [#smart-contracts]
Contracts whose terms are directly encoded in code and executed automatically. Qubic’s first smart contract is a decentralized exchange named Qx, which completed a 676‑share IPO.
### Spectrum [#spectrum]
Spectrum is a definitive and immutable ledger within the Qubic network that records every transaction that occurs inside the network each epoch. Using decentralized nodes to process its consensus validation, Spectrum emphasizes transparency, security, and decentralization, making it one of the key components of the Qubic network and providing trust and openness to users worldwide.
### Ticks [#ticks]
In the Qubic ecosystem, ticks refer to the time interval during which transaction and smart contract calculations reach consensus. A tick may last only a very short time (less than one second).
### Useful Proof of Work / UPoW [#useful-proof-of-work--upow]
An innovative consensus mechanism is being explored that redirects computational power from energy‑intensive mining to tasks with tangible value, such as training AI models. Unlike traditional proof‑of‑work systems that waste energy solving complex puzzles, UPoW focuses on providing substantial help and meaning to society rather than merely squandering resources.
***
Qubic is still in development, and certain aspects of the system may change during development and real‑world testing.
---
# Overview
Start learning about Qubic
Source: https://www.qools.org/en/docs/learn
## What is Qubic? [#what-is-qubic]
Qubic is an innovative cryptocurrency platform founded by Come-from-Beyond (Sergey Ivancheglo, founder of IOTA and NXT) and launched in the second quarter of 2022. Qubic enables high‑speed, fee‑less transactions and scalable AI‑driven solutions through a quorum‑based protocol. It supports dApps (decentralized applications) and smart contracts, catering to various industry challenges such as enhancing network resilience, reducing single points of failure, and promoting trust and collaboration. The platform emphasizes decentralization, security, and efficiency, using distributed ledger technology to maintain the integrity and immutability of transaction records.
## What Makes Qubic Unique? [#what-makes-qubic-unique]
Computational resources are used for AI training in the Aigarth project, aiding the development of AGI and avoiding the resource waste of traditional PoW.
Aigarth is committed to opening real AI source code to everyone, aiming to promote the sharing and popularization of AI technology.
All projects have their source code publicly available on GitHub, for people to view and use, and community contributions and audits are encouraged.
Provide real‑time external data (such as stock prices, sports scores) to enhance smart contract functionality.
Qubic’s true guarantee mechanism, providing the fastest smart contract service and a high level of decentralization.
The most efficient Turing‑complete smart contracts built on C++, running on bare metal, capable of fully leveraging computational potential.
Qubic offers fast, zero‑fee transactions with instant finality, making it the fastest CertiK‑verified blockchain to date, with a peak TPS of 15.52M.
The Qubic protocol runs on bare metal, independent of any operating system, reducing software layers and enhancing efficiency and security.
## How does Qubic work? [#how-does-qubic-work]
The Qubic network is driven by 676 computors/validators, high‑performance hardware machines that run the Qubic protocol directly on bare metal to achieve optimal performance. These computing devices communicate with oracles, execute smart contracts rapidly, secure the blockchain, handle fee‑less transactions, and receive $QUBIC‑based rewards based on network performance.
Each computor requires substantial mining support (each computor may have thousands of miners participating, and each computor can operate as a mining pool) to maintain a top‑676 ranking. Miners maximize the use of mining energy through AI training tasks. Miners themselves do not receive direct payment for AI training work; instead, computors/mining pool operators reward miners based on the performance of their AI training tasks.
## What problems does Qubic solve? [#what-problems-does-qubic-solve]
In addressing numerous challenges, Qubic adopts a series of innovative measures. First, all transactions on the Qubic protocol are fee‑less, which not only improves user experience but also provides vast prospects for applications such as NFTs, tokens, and dApps.
Second, Qubic is praised as one of the few protocols capable of seamlessly integrating smart contracts with oracles, enhancing smart contract functionality by providing real‑world information in real time. Its innovative quorum protocol ensures that every decision is based on majority consensus, enabling every transaction and smart contract execution to reach finality.
Moreover, in the field of mining technology, Qubic has found an effective way to reduce energy waste by using computational power to improve the training efficiency of ANN (Artificial Neural Networks). This strategy effectively harnesses the network’s vast resources, advancing the field of machine learning while alleviating the energy waste associated with traditional mining activities.
## What is Qubic’s consensus protocol? [#what-is-qubics-consensus-protocol]
Qubic adopts a unique consensus protocol called the quorum protocol. Notably, Qubic does not operate like traditional blockchains; when creating a new tick (similar to a block in conventional blockchains), mining is not required. Even if all mining operations cease entirely, new ticks will continue to be generated without interruption. However, without mining, it becomes impossible to determine the most performant computor for the next epoch.
To create a new tick, an entity called a “tick validator” must broadcast a proposal for a new tick. The 676 computors send encrypted signed votes that include hashes of the internal Qubic network state. Once the new tick achieves a 2/3 majority quorum consensus, it can be accepted. If the tick validator does not announce a new vote, an empty tick is produced. In this case, the tick data is all zeros, and its hash is also all zeros, yet a quorum vote on the empty tick is still required.
If the quorum vote count cannot be reached, Qubic halts new tick generation. Continuous tick generation indicates that most computors are fully synchronized with the Qubic network state. Computors require substantial mining to maintain their positions. Therefore, mining activity in Qubic is not to produce the next block but to help computors secure one of the coveted computor seats, as only 676 computors receive rewards. Within each epoch, candidates can receive miner support and compete with other computors for one of the seats, and up to 225 computors may lose their positions each cycle. After a halving, a total of 450 billion $QUBIC is distributed to the 676 computors, calculated based on their work performance.
***
### Disclaimer [#disclaimer]
All content in this document, including all information resources provided on the website, is for informational and technical support purposes only and does not offer any form of guarantee, warranty, or statement. The information is provided for educational and reference purposes only and is not investment advice; please consult your financial advisor or professional. We strongly recommend independent research before connecting to any dApp, third‑party service, or making investment and financial decisions.
---
# Tokenomics
The utility (or coin) that drives the Qubic ecosystem is more than a currency—it’s an “energy” unit. These units are called $QUBIC and are used as fuel for executing smart contracts and accessing other services on the Qubic platform. Unlike conventional monetary units, $QUBIC is burned upon use, a fundamental concept for understanding Qubic’s unique token economics.
Source: https://www.qools.org/en/docs/learn/tokenomics
### $QUBIC [#qubic]
In Qubic, $QUBIC serves as the standard for measuring the consumption of computational “energy.” Whether running a smart contract or retrieving data from an oracle, the action is performed by burning $QUBIC, and this consumption forms the basis of all transactions within the system. It’s important to note that, although $QUBIC has value, it is not paid out to the system’s individual computors; instead, it is destroyed or permanently removed from circulation to maintain a balance between inflation and deflation.
* $QUBIC is burned when used, supporting the dynamic of inflation and deflation.
* Every creation and execution of smart contracts affects Qubic.
* Deflation can exceed inflation.
Qubic’s network uses “$QUBIC” (not “$QU”) as its official token code.
### Epochs and $QUBIC Generation [#epochs-and-qubic-generation]
#### Weekly Issuance Allocation [#weekly-issuance-allocation]
| **Type** | **Amount** |
| ------------------------- | ---------- |
| Weekly issuance | 1,000 B |
| Weekly max burn | 550 B |
| Weekly effective issuance | 450 B |
| CCF (8 %) | 36 B |
| QEarn (12.25 %) | 50.7 B |
| Minimum mappable supply | 363.3 B |
In Qubic, each epoch (a 7‑day period from UTC Wednesday 12:00 to the next Wednesday 12:00) can generate one trillion units of $QUBIC. Due to a halving mechanism, the actual production gradually decreases; the first halving has already occurred, leaving an effective weekly issuance of 450 billion $QUBIC. These $QUBIC are primarily allocated to computors, which are the core nodes of the network. In the most efficient scenario, a single computor can earn roughly 5.37 billion $QUBIC (363.3 billion ÷ 676). This allocation model is designed to incentivise efficiency—computors that run below optimal performance may see reduced earnings, with the remaining $QUBIC distributed to arbitrators. Arbitrators do not participate in smart‑contract governance, voting, or other $QUBIC distributions, preserving balance within Qubic’s economic framework.
Qubic’s total supply is finite; the upper limit on circulating $QUBIC is 200 T (excluding newly issued portions). At some point in the future—at least until 2041—the burn rate will equal or exceed the issuance rate, causing the velocity of circulating coins to stall. Nonetheless, miners can still earn rewards permanently. This safeguard comes from embedded economic drivers: theoretically, when Qubic’s circulating quantity approaches 999 T $QUBIC, the quorum will trigger a weekly burn of one trillion $QUBIC as execution fees, ensuring continuous revenue generation.
### Transfers and Fees [#transfers-and-fees]
Transfers on the Qubic network are **free**—this is where the platform’s efficiency and user experience shine. Moreover, the “fee generated by smart‑contract execution” is not a traditional cost but rather a consumption process of $QUBIC that is not allocated to computors, reinforcing the notion of $QUBIC as an “energy” rather than a fiat‑like currency.
### How Does the $QUBIC Burn Mechanism Work? [#how-does-the-qubic-burn-mechanism-work]
Currently, Qubic employs two burn mechanisms:
* Launching an IPO to initiate a smart contract, where the purchase cost of shares is burned.
* New smart‑contract deployments burn $QUBIC.
Future additions will include two more mechanisms:
* Oracles burn $QUBIC when supplying data to Qubic.
* Aigarth burns $QUBIC during its usage.
$QUBIC is the lifeblood of the Qubic network, powering operations, incentivising efficiency, and maintaining equilibrium through reward and burn systems. In the design of the Qubic platform, the role of $QUBIC highlights its flexibility, efficiency, and democratic nature.
---
# Get to Know Qubic
Start here to understand Qubic and choose what to explore next
Source: https://www.qools.org/en/docs/learn2
Qubic is a distributed computing platform operated by a network of Computors. It supports value transfers, assets, smart contracts, and computation tasks. Begin with the overall structure, or go directly to wallets, mining, or the ecosystem.
## Understand Qubic [#understand-qubic]
Learn what Qubic is, how the network is organized, and what it can support.
See how Epochs, ticks, Computors, Quorum, and mining relate to one another.
Learn about Identity, QUBIC, issued assets, shares, and smart contracts.
## What do you want to do? [#what-do-you-want-to-do]
Start with Identity, wallets, and signing, then learn about backups, transfers, and assets.
Learn about pools, mining software, modes, earnings, and common issues.
Discover Qubic projects, wallets, explorers, DEXs, and useful tools.
## Go deeper [#go-deeper]
Explore network roles, consensus, state, transactions, and the asset model.
Understand issuance, burns, incentives, fund flows, and community governance.
Find terminology, the current mainnet baseline, data sources, and official resources.
---
# Mining Overview
Learn the basic concepts and resources for Qubic mining.
Source: https://www.qools.org/en/docs/mining
---
# Advanced Concepts
Explore Qubic network roles, governance, and deeper protocol topics.
Source: https://www.qools.org/en/docs/learn/advanced
This section collects advanced Qubic learning materials, including network roles, governance, and protocol concepts.
---
# Network Roles
In the Qubic ecosystem, two primary node types—computors and miners—work together to support its decentralised infrastructure. These entities carry distinct responsibilities and ensure the network runs efficiently, while arbitrators play a crucial role in maintaining the network's fairness and reliability.
Source: https://www.qools.org/en/docs/learn/advanced/network-role
## Computors [#computors]
In the Qubic system, each computor is a node specifically configured to handle tasks that may involve running smart contracts or facilitating transactions on the blockchain. Unlike traditional blockchain systems that rely on miners for transaction verification and block addition, computors in the Qubic ecosystem perform a broader range of functions. They not only execute specific tasks but also actively participate in consensus‑based, distributed decision‑making and keep the internal economic model balanced and stable.
**Key Features**
* The role they play in safeguarding the network's decentralisation.
* In each epoch iteration, computors receive a share of the newly minted $QUBIC allocation to support the overall operation and participation of the network. This allocation scheme is designed to encourage active engagement in network services and contributions, improving overall efficiency and security.
* Participation in critical network voting and decision‑making processes.
**Limitations**
At any given time, the Qubic network runs a fixed pool of 676 computors to ensure optimal performance and smooth decision workflows. Weekly rankings, based on solutions supplied by their miners, determine that the top 451 high‑performing computors retain their positions, while the remaining 225 slots are replenished each epoch from the candidate pool or lower‑ranked computors.
**Challenges of Running a Computor on Qubic**
* Running directly on bare metal, which requires proper UEFI configuration.
* Regular compilation of `qubic.cpp` each epoch.
* Continuous system updates.
* A backup system is essential to guarantee that the tick continues to run.
* Ongoing competition: computors must defeat candidates with sufficient mining capability to keep their spots.
* Constant vigilance: computors must continuously monitor network status to ensure ticks run smoothly and respond promptly to emergencies.
Operating a computor demands specialised knowledge and technical awareness, and it must always be handled with a high degree of alertness. If you’re considering becoming a computor, be sure to prepare mentally and practically for the challenges ahead.
## Miners [#miners]
Miners in the Qubic ecosystem differ from their counterparts in traditional blockchain networks. They do not compete to validate and add transactions to the chain; instead, computors assign them specific computational problems or tasks. Once a solution is found, it is fed back to the relevant computor. This interaction not only helps verify the integrity of the task but also contributes to the overall handling and validation of operations across the network.
**Key Features**
* Receive computational problems or tasks from computors (identified by IDs).
* After successfully solving a problem, return the solution to the computor, contributing to its score.
* The core focus is on the overall task execution within Qubic's innovative system, not just transaction validation.
**Potential Capacity**
The Qubic network theoretically allows an unlimited number of miners, encouraging broad participation and ensuring robust computational power behind the system.
Only computors receive weekly payouts from the Qubic protocol. To maintain a spot among the 676 computors, a computor must accumulate enough solutions each epoch through its associated miners. Consequently, each computor eventually needs to develop a strong mining pool and use pool payouts to provide incentives.
Running a single miner is considerably easier, and many public [mining pools](../../mining/index.mdx) are already available.
Understanding the fundamental distinction between miners and computors is essential in Qubic’s new era. As we progress into this fresh developmental phase, the role and responsibilities of computors will undoubtedly become increasingly prominent.
## Arbitrators [#arbitrators]
Within the Qubic ecosystem, a key role exists specifically to resolve disputes and protect user rights. An arbitrator is an entity in Qubic responsible for settling conflicts and safeguarding user interests.
Arbitrators set parameters for mining algorithms, publish computor rankings each epoch, and can replace underperforming computors. They also accumulate the $QUBIC that underperforming, frequently failing computors are unable to capture—approximately 1 % of the effective production each epoch. Node operators select trusted arbitrators by setting the corresponding ID in the source file `Qubic.cpp` according to their individual needs and preferences. Computors can collectively cover or replace arbitrators through consensus processes, a feature essential to preventing any single entity from gaining excessive control over the network.
---
# Spectrum
Spectrum serves as a clear, tamper‑proof ledger within the Qubic network, maintaining a complete record of every transaction executed in each cycle. Managed by a decentralized node consensus, it showcases transparency, security, and decentralization, solidifying Spectrum’s role as a core component of Qubic and building trust and openness for users worldwide.
Source: https://www.qools.org/en/docs/learn/advanced/spectrum
## Understanding Spectrum [#understanding-spectrum]
In the Qubic universe, **Spectrum** represents a key, decentralized ledger system that holds an immutable, transparent transaction history for every epoch. As an open record, it presents the sequential order of every transaction that occurs within each epoch of the Qubic network.
Spectrum can be viewed as a digital, transparent ledger that anyone can access. It meticulously logs the transaction history of each epoch in the Qubic network.
## How It Operates [#how-it-operates]
* **Recording transactions**: After a transaction is executed, it is recorded as a new entry in Spectrum. The transaction’s details—such as the sender’s and receiver’s addresses and the transferred amount—are all captured.
* **Immutable records**: Once a transaction is recorded within an epoch, it cannot be altered. This immutable nature of Spectrum guarantees the accuracy and security of the network’s transaction history.
## Security and Decentralization [#security-and-decentralization]
Spectrum’s decentralized structure ensures that control is not concentrated in any single entity. Instead, Spectrum is distributed across all computors. This decentralization enhances Spectrum’s resilience against censorship and fraud. Altering Spectrum would require the consensus of the majority of computors, which is effectively impossible.
---
# 创建钱包
钱包是您使用 Qubic 的主要工具，它存储您的数字资产，创建钱包是您进入 Qubic 的第一步，通过钱包，你可以登录DApps、查看余额、发送交易和验证身份。
Source: https://www.qools.org/en/docs/learn/usage/wallet-create
## 官方钱包 [#官方钱包]
Metamask Snap 钱包（开发中）
注意事项：当前，在 MetaMask 的钱包内的全部 $QUBIC 代币均为骗局。
## 如何创建钱包？ [#如何创建钱包]
所有以下教程均为 [Qubic 网页钱包](https://wallet.qubic.org/)。
1. 打开 [Qubic 网页钱包](https://wallet.qubic.org/)，输入金库名称。
2. 为你的地址添加一个名字，并选择**随机种子**来生成你的地址。
这55位字符是你的 Qubic 地址私钥（种子）！
请将此种子保存在安全的位置。
若未备份种子，你可能会丢失资金！
强烈建议不要使用自定义的种子，因为这样做会增加被黑客盗取的风险！！！
3. 在确保安全的前提下，设定一个强有力的密码，并将 Vault 文件进行下载和妥善保存。
Vault 文件存储你的钱包地址相关的所有信息，并对其进行加密。使用密码来验证并解锁文件。如果你的钱包包含多个地址，它们都将保存在 Vault 文件中。
4. 输入你在上一步设置的密码，并导入 Vault 文件进行验证。
每次更新你的钱包（例如：添加或编辑地址），你将被提示下载最新的 Vault 文件，请记得更新并保存该文件。
5. 创建完成，成功进入钱包页面。
#### 忘记保存种子？ [#忘记保存种子]
1. 首先点击右上角的锁形图标，输入密码并导入 Vault 文件以解锁。
2. 点击地址信息内的“眼睛”图标，点击打开后就可以可以看到公共ID的地址和 55 位字符的种子。
**再次强调，这 55 位字符的种子非常重要，等同于地址的私钥，请不要随意告诉他人，并妥善保存。**
## 钱包安全性 [#钱包安全性]
#### K12 哈希算法 [#k12-哈希算法]
Qubic 采用 Keccak 团队设计的 K12 算法来进行其加密操作，相比传统的 SHA-256 等算法，K12 在速度和安全性上更加优越。通过将字母数字种子转换为具有高随机性的私钥，从而达到强化加密安全的目的。这一策略确保了每个生成的私钥不仅独特而且具备强大的抗暴力破解能力。
#### 密钥和地址生成 [#密钥和地址生成]
Qubic 系统采用一个由 55 个小写字母组合而成的种子作为基础来生成 256 比特位的私钥，通过 K12 哈希算法完成。根据私钥，我们使用 FourQ 曲线与标准的椭圆曲线乘法运算（ecc\_mul\_fixed）结合进行签名处理，从而得到公钥。FourQ 曲线在确保系统加密安全方面发挥了巨大作用，因为它提供了当前最高效且最安全的椭圆曲线之一。这使得我们的数字签名过程不仅更加快速，而且也更为稳固可靠。
---
# 钱包自救手册
如果发现无法访问钱包，请保持冷静。检查仍然可用的信息，例如你的密码、文件和种子。不要清除浏览器缓存。
Source: https://www.qools.org/en/docs/learn/usage/wallet-self-help
## 确保你拥有以下信息和文件 [#确保你拥有以下信息和文件]
* **地址 55 位种子**
* **钱包密码**
* **文件**
Vault file
或者
qubic.li-wallet.config and qubic.li-wallet.unlock
或者版本更老的
qubic.li-wallet.config and qubic.li-wallet.privatekey
早期的钱包文件由两部分组成：一个配置文件和一个解锁文件。如果你仍在使用这类文件，请尽快更新到 Vault 文件。
#### 1. 有 55 位字符种子备份 [#1-有-55-位字符种子备份]
这种情况最容易解决，只需创建新钱包将种子导入即可找回。
为避免意外，请先使用浏览器的隐私标签页或者是其他浏览器创建新的钱包进行尝试。
这就是为什么要备份 55 位种子的重要性。
#### 2. 有钱包密码和 Vault 文件 [#2-有钱包密码和-vault-文件]
Vault 文件存储了你的钱包地址信息，只需要使用新的网页钱包域名输入密码和导入文件即可。
网页钱包新域名: [https://wallet.qubic.org/](https://wallet.qubic.org/)
*其他情况：由于钱包每次编辑或更新时都需要下载新的 Vault 文件，如果您有多个 Vault 文件且发现导入地址不正确，请尝试导入不同的 Vault 文件。*
#### 3. 有钱包密码还有 qubic.li-wallet.config 和 qubic.li-wallet.unlock/qubic.li-wallet.privatekey [#3-有钱包密码还有-qubicli-walletconfig-和-qubicli-walletunlockqubicli-walletprivatekey]
与前一种情况类似，主要区别在于需要导入两个文件。
为了防止未知风险，请尽快将钱包文件更新至 Vault 格式。
#### 4. 高难度模式 - 仅拥有钱包密码和qubic.li-wallet.unlock/qubic.li-wallet.privatekey [#4-高难度模式---仅拥有钱包密码和qubicli-walletunlockqubicli-walletprivatekey]
如果意外删除了 qubic.li-wallet.config 并且浏览器缓存仍然可访问，可以尝试输入密码和导入 qubic.li-wallet.unlock/qubic.li-wallet.privatekey 来解锁你的钱包。如果仍然有效，请尽快导出你地址的 55 位字符的种子，并尽快更新到 Vault 文件。
> **记得，始终要保护好你的关键信息，并确保自己的数字资产安全。**
---
# 使用钱包
创建 Qubic 钱包的指南
Source: https://www.qools.org/en/docs/learn/usage/wallet-use
# 钱包使用 [#钱包使用]
## 转账 [#转账]
在使用网页钱包进行转账之前，需要先将钱包解锁。
执行刻度指执行转账时的刻度，默认设置为当前刻度 +10，通常不需要额外的设置。
## 交易记录 [#交易记录]
地址交易记录可以通过浏览器查询。
官方浏览器: [QUBIC Explorer](https://explorer.qubic.org/network)
## 资产 [#资产]
在 Qubic 生态系统中，“资产”指的是股票或代币，例如 Qx 股份和 CFB 代币。只有当你持有时，你的地址才会显示资产。
当前，可以通过 Qx Dex 或场外交易（OTC）平台进行交易。CFB 代币可以在 Safatrade 交易平台进行购买。
如何使用 Qx Dex 进行交易: [How to Buy/Sell $CFB on QX ($Qubic ’s Dex) using Qwallet](https://x.com/c_f_b_token/status/1797543889139859917)
## 投票 [#投票]
Qubic 计算者投票用于在关于整个网络的决策主题上达成共识。这可以包括接受智能合约或其他协议决定。只有计算者能够参与。
如果你想提出任何东西，你需要至少拥有一个计算者的种子。
---
# Incentives, Fees, and Fund Flows
Explain value flows among computors, miners, contracts, and protocol mechanisms.
Source: https://www.qools.org/en/docs/learn2/economics-governance/incentives-fees-fund-flows
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page maps computor rewards, pool settlement, contract execution reserves, and protocol fees without confusing logical accounting with transfers.
## Questions this page will answer [#questions-this-page-will-answer]
* How do computor rewards reach pool settlement?
* Where do smart-contract execution fees come from?
* Which flows change effective supply?
---
# Issuance, Burns, Supply, and Halving
Trace QUBIC from scheduled issuance to effective supply changes.
Source: https://www.qools.org/en/docs/learn2/economics-governance/issuance-burn-supply-halving
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page separates scheduled issuance, protocol burns, contract burns, and halvings, using consistent units to show their supply effects.
## Questions this page will answer [#questions-this-page-will-answer]
* Why can scheduled and effective issuance differ?
* How should burn mechanisms be classified?
* Which parameters change at a halving?
---
# Proposals, Community Voting, and CCF
Distinguish proposal types, voter eligibility, quorum, and outcome effects.
Source: https://www.qools.org/en/docs/learn2/economics-governance/proposals-voting-ccf
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page separates computor proposals, shareholder votes, community voting, and CCF funding instead of applying one threshold to every process.
## Questions this page will answer [#questions-this-page-will-answer]
* Who can submit and vote on each proposal type?
* How do participation and approval rules differ?
* Are results protocol-binding?
---
# Tokenomics Overview
Understand QUBIC economics through supply, issuance, burns, and incentives.
Source: https://www.qools.org/en/docs/learn2/economics-governance/tokenomics-overview
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page gives an overview of the economic model and separates fixed rules, versioned parameters, and facts that require code or network verification.
## Questions this page will answer [#questions-this-page-will-answer]
* How do maximum and circulating supply differ?
* How do epoch issuance and burns affect supply?
* Which figures require a version and date?
---
# Assets and Applications
An introduction to Identity, QUBIC, issued assets, shares, and smart contracts
Source: https://www.qools.org/en/docs/learn2/getting-started/assets-and-applications
Qubic's network state contains more than QUBIC balances. It also includes issued assets and smart-contract data. Users interact with these forms of state through identities, while wallets and applications turn protocol data into interfaces that can be used directly.
## Identity: an entity identifier in the network [#identity-an-entity-identifier-in-the-network]
An Identity is a public identifier used to represent an entity in Qubic. People, services, Computors, and smart contracts can all appear in network interactions through identities.
A wallet derives private keys and a public Identity from a Seed. The Identity can be shared to receive QUBIC or assets. Private key material creates signatures and is kept by its holder. The network verifies transaction signatures without requiring a user's name or account profile.
## QUBIC: the network's native unit [#qubic-the-networks-native-unit]
QUBIC is Qubic's native unit. It can transfer value between identities and is also used in smart contracts and some protocol functions.
Ordinary QUBIC transfers do not carry the base network fee commonly found in traditional blockchains. Smart contracts, DEXs, pools, exchanges, and other services can still define burns, fees, or settlement differences according to their own rules. These belong to the economic design of the specific feature or service.
## Spectrum: QUBIC state [#spectrum-qubic-state]
Spectrum describes network state related to identities and QUBIC. After executing a Tick, Computors derive a new Spectrum state so that all nodes participating in consensus can agree on current balances.
Wallets normally read Spectrum through a node or data service and present the result as a familiar balance. Historical transaction lists can be assembled separately from Tick data, Bob, archival nodes, and explorers.
## Universe: issued-asset state [#universe-issued-asset-state]
Qubic supports creating and transferring issued assets. Universe records issuance and holding relationships for these assets. Two common concepts are:
* **Ownership:** an Identity's ownership of an asset;
* **Possession:** an Identity's current control or possession of an asset.
An asset is identified by both its name and issuer. Two assets can use the same name while being issued by different identities, so wallets and markets commonly display both fields.
## Shares: interests defined by smart contracts [#shares-interests-defined-by-smart-contracts]
Shares commonly represent an interest or right defined by a particular smart contract. They can participate in distribution, rewards, or governance logic, with their exact meaning determined by that contract.
QUBIC, issued assets, and shares can all express economic relationships, but they come from different data structures:
| Type | Origin | Main state |
| ------------ | ------------------------- | ---------------------------------------------- |
| QUBIC | Qubic protocol | Spectrum |
| Issued asset | Asset issuer | Universe |
| Share | Particular smart contract | Contract state and related asset relationships |
## Smart contracts: application logic in the protocol [#smart-contracts-application-logic-in-the-protocol]
Qubic smart contracts are written in restricted C++ and integrated into Core. A contract can keep its own state, execute Procedures in response to transaction input, and update results according to deterministic rules.
Ecosystem functions that can be implemented through smart contracts include:
* asset issuance and exchange;
* staking and reward distribution;
* auctions and markets;
* governance or treasury management;
* shared capabilities used by other contracts.
A contract's behavior in the network is determined by its code and current state. Front-end applications organize the interaction flow, while Computors perform the execution and establish consensus.
## Oracle Machines and external information [#oracle-machines-and-external-information]
Smart-contract execution is deterministic, while real-world data originates outside the network. Oracle Machines allow Computors to answer external questions and make a Quorum result available to protocol logic.
This lets applications refer to prices, time, event outcomes, or other external information. The data source, question design, and answer process are part of the particular Oracle implementation.
## Outsourced Computation and external operations [#outsourced-computation-and-external-operations]
Outsourced Computation lets the protocol send a Quorum-authorized instruction to an external system. It has a different direction from smart contracts and Oracle Machines:
| Capability | Data direction | Role |
| ---------------------- | --------------------------- | --------------------------------------------------------------- |
| Smart Contract | Inside the protocol | Executes deterministic logic and updates state |
| Oracle Machine | External to protocol | Brings answers to external questions into the network |
| Outsourced Computation | Protocol to external system | Authorizes an external system to perform a particular operation |
Together, these capabilities provide a foundation for Qubic applications. The functions available at a given time still depend on the current Core version and deployed contracts.
## Wallets, explorers, DEXs, and pools [#wallets-explorers-dexs-and-pools]
Ecosystem products provide different entry points to the protocol:
| Service | Main protocol capabilities it connects to |
| -------- | ----------------------------------------------------------------------------- |
| Wallet | Manages an Identity, creates signatures, and reads balances and assets |
| Explorer | Indexes ticks, transactions, identities, assets, and contract data |
| DEX | Calls exchange or market contracts and presents asset prices and order state |
| Pool | Receives Miner submissions, records Shares or Solutions, and settles earnings |
These products can use different data sources, refresh intervals, and interaction designs, while ultimately connecting to Qubic's identity, transaction, state, or computation mechanisms.
## Related topics [#related-topics]
* [Spectrum, Universe, and Identity](../protocol-basics/spectrum-universe-identity)
* [Transactions, Assets, and Shares](../protocol-basics/transactions-assets-shares)
* [Tokenomics Overview](../economics-governance/tokenomics-overview)
* [Identity, Seed, Vault, and Signing Security](../wallet-usage/identity-seed-vault-signing)
## Primary sources [#primary-sources]
* [Qubic ID](https://docs.qubic.org/developers/qubic-id/)
* [Spectrum](https://docs.qubic.org/learn/spectrum/)
* [Qubic Tokenomics](https://docs.qubic.org/learn/tokenomics/)
* [Smart Contracts Overview](https://docs.qubic.org/developers/smart-contracts/overview/)
* [Smart Contract Lifecycle](https://docs.qubic.org/developers/smart-contracts/lifecycle/)
* [Oracle Machines](https://docs.qubic.org/developers/oracles/)
---
# How the Network Works
Learn how Epochs, ticks, Computors, Quorum, and mining relate to one another
Source: https://www.qools.org/en/docs/learn2/getting-started/concept-map
Qubic operates in Epochs and processes transactions and computation in a continuous sequence of ticks. Computors in the current Epoch execute the same inputs and use Quorum to agree on results. Miners provide computation results and participate in competition for Computor seats in later Epochs.
These processes run at the same time. Ticks advance current network state, while Epochs organize the node set and mining Score over a longer operating period.
## Epoch: the network operating period [#epoch-the-network-operating-period]
An Epoch usually lasts about one week and contains many consecutive ticks. It provides a common time boundary for:
* the current set of Computors participating in consensus;
* the Score of Candidates and Computors;
* the accounting of Solutions submitted by Miners;
* some data and parameters that the protocol updates periodically.
When a new Epoch begins, the Computor set and period-based counters enter a new stage. Persistent state such as QUBIC balances, assets, and smart contracts continues with the network.
## Tick: the point of execution and consensus [#tick-the-point-of-execution-and-consensus]
A Tick is Qubic's basic unit for processing transactions and establishing results. Ticks have increasing numbers, and Computors process the inputs for each point according to shared rules.
A typical transaction follows this sequence:
1. A wallet constructs a transaction containing the sender, destination, amount, input data, and a future target Tick.
2. The wallet signs it with private key material and broadcasts it to the network.
3. The transaction propagates to Computors.
4. When the target Tick arrives, Computors validate and execute the transaction.
5. Enough Computors derive the same result to form Quorum.
6. Nodes, wallets, and indexing services can then read the resulting state.
Whether a transaction is executed in its target Tick depends on conditions such as its signature, balance, input format, target Tick, and network propagation. Wallets normally combine the Tick result and subsequent state to present a transaction status to the user.
## Computor: executing network state [#computor-executing-network-state]
A Computor is a node in Qubic's current consensus set. It receives transactions and network data, runs Core and smart contracts, and calculates the state that follows a Tick.
The current architecture has 676 Computor seats. When at least 451 Computors agree on a result, the network reaches Quorum. The result therefore comes from independent nodes executing the same rules rather than from a single node's decision.
## Candidates and Miners: competing for future seats [#candidates-and-miners-competing-for-future-seats]
A node identity outside the current Computor set can participate as a Candidate. Miners perform the computation task currently specified by the protocol and submit valid Solutions to an associated Computor or Candidate identity.
These results contribute to Score. At an Epoch boundary, Score participates in determining future Computor seats, connecting contributed computing resources with changes to the consensus node set.
Public pools provide connectivity, statistics, and settlement services along this path. Shares, Solutions, hashrate, and earnings are pool-specific representations of the submission process. At the protocol layer, the focus is the valid computation result and its contribution to Score.
## Quorum: establishing a common result [#quorum-establishing-a-common-result]
Computors execute the same rules on the same input and are expected to derive the same output. Quorum confirms that a sufficient number of nodes produced the same result.
The mechanism applies to Tick state and is also reused by other Qubic capabilities. Oracle Machines, for example, collect Computor answers to external questions, while Outsourced Computation uses Quorum to authorize a specific operation by an external system.
## How state is read [#how-state-is-read]
Network operation produces current state, Tick data, and logs. Different components use these sources to provide different views:
| Data layer | Main content |
| ------------------------------- | ------------------------------------------------------------------------------------------- |
| Core state | Current QUBIC, asset, and smart-contract state |
| Tick data | Transactions and consensus results for an execution point |
| Bob and archival nodes | Longer-range retention and access to Tick data |
| Explorers and indexing services | Searchable transaction records, statistics, and other views assembled from lower-level data |
The same transaction can therefore appear in wallets, node interfaces, and explorers, while the time each interface updates and the range of history it covers may differ.
## The complete relationship at a glance [#the-complete-relationship-at-a-glance]
```text
User or application
│ signed transaction
▼
Target Tick ──► Computor execution ──► Quorum ──► network state update
Miner
│ Solution
▼
Identity Score ──► Epoch settlement ──► future Computor set
```
The next page, [Assets and Applications](./assets-and-applications), describes how Identity, QUBIC, issued assets, shares, and smart contracts build on this network.
## Primary sources [#primary-sources]
* [Qubic Consensus](https://docs.qubic.org/overview/consensus/)
* [Official node roles](https://docs.qubic.org/learn/nodes/)
* [Ticks and Concurrency](https://docs.qubic.org/developers/ticks-and-concurrency/)
* [Qubic ID](https://docs.qubic.org/developers/qubic-id/)
* [Oracle Machines](https://docs.qubic.org/developers/oracles/)
---
# What Is Qubic?
An introduction to Qubic through its network, computation, state, and applications
Source: https://www.qools.org/en/docs/learn2/getting-started/what-is-qubic
Qubic is a computing network operated by distributed nodes. It can process QUBIC transfers, issued assets, and smart contracts, while also directing computing resources toward tasks defined by the protocol.
At its center is not a ledger extended by miners adding one block after another, but a group of Computors that operate continuously. They receive the same transactions and inputs, perform computation in successive ticks, and use Quorum to agree on results.
## A continuously operating distributed computer [#a-continuously-operating-distributed-computer]
Qubic can be viewed as a computer made up of many independent nodes:
* **Inputs** come from user transactions, smart-contract calls, and protocol data.
* **Execution** is performed by the Computors of the current Epoch.
* **Results** are established when enough Computors reach the same conclusion.
* **State** records QUBIC, issued assets, and smart-contract data associated with identities.
* **Applications** read state and submit new transactions through nodes, wallets, or indexing services.
No single node can decide the network result on its own. Each Computor processes inputs according to the same rules, while Quorum turns a matching result from a sufficient number of nodes into state accepted by the network.
## Time in the network [#time-in-the-network]
Qubic organizes operation with **Epochs** and **ticks**.
### Epoch [#epoch]
An Epoch is a network operating period. It contains many ticks and provides a shared boundary for Computor seats, mining Score, and some protocol parameters. On mainnet, a new Epoch usually begins each week.
### Tick [#tick]
A Tick is the time unit in which transactions and computation are executed and agreed upon. A transaction specifies a future target Tick. When that Tick arrives, Computors execute the transaction and form agreement on the result. The network therefore advances through a continuous sequence of execution points rather than waiting for a miner to produce the next block.
## Participants in the network [#participants-in-the-network]
| Role | Role in the network |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Computor | Executes transactions and smart contracts, exchanges Tick data, and participates in consensus |
| Candidate | Has a node identity but no current Computor seat and competes for a later seat |
| Miner | Performs the computation task specified by the protocol and contributes valid Solutions to an associated identity's Score |
| Users and applications | Create signed transactions, hold QUBIC or assets, and call smart contracts |
The current architecture has 676 Computor seats, and a matching result from at least 451 Computors normally forms Quorum. Computors execute transactions and participate in consensus. Miners contribute computation results used in Score and future seat competition. The roles are connected, but their responsibilities differ.
## What Qubic stores [#what-qubic-stores]
Qubic must enable every Computor to derive the same current state. Its main state includes:
* **Spectrum:** state related to identities and QUBIC;
* **Universe:** issued assets and relationships such as ownership and possession;
* **Smart-contract state:** internal data maintained by each contract;
* **Tick data and logs:** data produced during network operation and processed by nodes and indexing services.
Wallets and explorers turn these underlying data sources into familiar views such as balances, asset lists, transaction records, and charts. They are interfaces to the network rather than the consensus process itself.
## What Qubic can support [#what-qubic-can-support]
### QUBIC and assets [#qubic-and-assets]
QUBIC is the network's native unit. It is used for value transfers and interactions with the protocol and smart contracts. Qubic also supports assets created by particular issuers. Assets can share the same name, so an asset is identified by both its name and issuer.
### Smart contracts [#smart-contracts]
Qubic smart contracts are written in restricted C++, reviewed, and integrated into Core through the network's deployment process. Every Computor executes the same contract logic on the same input, making contract state part of network consensus.
### External data and execution [#external-data-and-execution]
Oracle Machines bring answers to external questions into the network. Outsourced Computation allows Quorum to authorize an external system to perform a specific operation. These capabilities connect deterministic protocol state with systems outside Qubic.
## Main differences from familiar blockchains [#main-differences-from-familiar-blockchains]
| Familiar blockchain model | How Qubic operates |
| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Block producers select transactions for a new block | Transactions target a future Tick and are executed by Computors |
| Later blocks accumulate confirmations | Tick results are established through Quorum |
| Miners or validators combine packaging and consensus roles | Computors execute and form consensus, while Miners contribute computation and participate in seat competition |
| Contracts deploy bytecode to a general-purpose virtual machine | Contracts are written in restricted C++ and integrated into Core |
| Nodes commonly retain a traversable blockchain history | Current state, Tick data, and indexed historical views occupy different data layers |
These differences shape how wallets, explorers, mining, and smart contracts work in Qubic. The next page, [How the Network Works](./concept-map), follows a transaction and an Epoch transition in more detail.
## Primary sources [#primary-sources]
* [Qubic overview](https://docs.qubic.org/overview/introduction/)
* [Qubic Consensus](https://docs.qubic.org/overview/consensus/)
* [Official node roles](https://docs.qubic.org/learn/nodes/)
* [Ticks and Concurrency](https://docs.qubic.org/developers/ticks-and-concurrency/)
* [Smart Contracts Overview](https://docs.qubic.org/developers/smart-contracts/overview/)
* [Qubic Glossary](https://docs.qubic.org/learn/glossary/)
---
# Epochs, Ticks, and Finality
Explain Qubic time organization and when a transaction can be considered final.
Source: https://www.qools.org/en/docs/learn2/protocol-basics/epoch-tick-finality
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page explains the relationship between epochs and ticks, what an epoch transition means, and how finality relates to protocol state.
## Questions this page will answer [#questions-this-page-will-answer]
* What purposes do epochs and ticks serve?
* What changes at an epoch transition?
* How is transaction finality determined?
---
# Computors, Candidates, Miners, and Elections
Distinguish network roles and explain miner support and computor selection.
Source: https://www.qools.org/en/docs/learn2/protocol-basics/network-roles-election
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page defines computors, candidates, and miners, then outlines how they cooperate and how epoch elections work.
## Questions this page will answer [#questions-this-page-will-answer]
* Which roles participate directly in consensus?
* How does mining affect computor selection?
* Why are these role names not interchangeable?
---
# Quorum and Consensus
Explain quorum, voting, and tick confirmation.
Source: https://www.qools.org/en/docs/learn2/protocol-basics/quorum-consensus
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page explains quorum through tick production and separates consensus thresholds from governance and other voting processes.
## Questions this page will answer [#questions-this-page-will-answer]
* What role does quorum play in tick confirmation?
* How is consensus voting different from governance voting?
* What happens when quorum cannot be reached?
---
# Spectrum, Universe, and Identity
Separate QUBIC state, asset state, and entity identity.
Source: https://www.qools.org/en/docs/learn2/protocol-basics/spectrum-universe-identity
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page separates identity, Spectrum state, and the Universe model for asset issuance, ownership, and possession.
## Questions this page will answer [#questions-this-page-will-answer]
* How does an identity relate to a wallet address?
* Is Spectrum a complete transaction history?
* How do ownership and possession differ in Universe?
---
# Transactions, Assets, and Shares
Build a basic model of transfers, asset issuance, and contract shares.
Source: https://www.qools.org/en/docs/learn2/protocol-basics/transactions-assets-shares
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page distinguishes QUBIC transfers, issued assets, and smart-contract shares, with an overview of common wallet and explorer fields.
## Questions this page will answer [#questions-this-page-will-answer]
* How do QUBIC, issued assets, and shares differ?
* How do ownership and possession affect asset use?
* Which fields matter when viewing transactions and assets?
---
# Fact Status, Sources, and Conflicts
Document sources, fact status, and conflicts that cannot be safely simplified.
Source: https://www.qools.org/en/docs/learn2/reference/fact-status-sources-conflicts
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page explains stable facts, dynamic facts, design goals, and unverified claims while recording important source conflicts.
## Questions this page will answer [#questions-this-page-will-answer]
* How are source conflicts handled?
* How are dynamic facts dated?
* Which conclusions should remain explicitly uncertain?
---
# Glossary
Concise definitions of Qubic terms with links to related pages.
Source: https://www.qools.org/en/docs/learn2/reference/glossary
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page serves as the shared terminology entry point with concise definitions and links to deeper explanations.
## Questions this page will answer [#questions-this-page-will-answer]
* What are the preferred Chinese translations?
* Which English terms should remain untranslated?
* Which concepts are commonly treated as synonyms incorrectly?
---
# Current Network, Epoch, and Version Baseline
Record the network and software versions used by dynamic documentation.
Source: https://www.qools.org/en/docs/learn2/reference/network-epoch-version-baseline
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page records the current network, Core version, key tool versions, and a shared verification date for changing facts.
## Questions this page will answer [#questions-this-page-will-answer]
* Which Core version does the documentation use?
* When were dynamic parameters last verified?
* Which pages require review after a release?
---
# Whitepaper and Official Resources
Collect official documentation, source code, releases, and long-term references.
Source: https://www.qools.org/en/docs/learn2/reference/whitepaper-official-resources
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page organizes the whitepaper, official Learn and Developer docs, Core source, releases, and community channels by verification purpose.
## Questions this page will answer [#questions-this-page-will-answer]
* Which facts can each source verify?
* Why prefer version-pinned source links?
* Where are recent protocol changes published?
---
# Create, Back Up, and Recover a Wallet
Provide a product-neutral workflow for safe wallet creation, backup, and recovery.
Source: https://www.qools.org/en/docs/learn2/wallet-usage/create-backup-recover
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page covers environment checks, backup principles, recovery drills, and common mistakes while leaving product-specific buttons to ecosystem pages.
## Questions this page will answer [#questions-this-page-will-answer]
* What should be checked before creating a wallet?
* What makes a backup recoverable?
* When should a small recovery test be performed?
---
# Identity, Seed, Vault, and Signing Security
Understand identities, secret material, custody tools, and signing authorization.
Source: https://www.qools.org/en/docs/learn2/wallet-usage/identity-seed-vault-signing
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page builds a security model for public identity, secret material, offline custody, and the meaning of a wallet signature.
## Questions this page will answer [#questions-this-page-will-answer]
* What are an identity and a seed?
* What custody problem does a vault solve?
* Why should no page ever request a seed?
---
# Legacy Wallet and Recovery Guide
Separate legacy migration and recovery from current wallet workflows.
Source: https://www.qools.org/en/docs/learn2/wallet-usage/legacy-wallet-recovery
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page contains only still-relevant legacy wallet, vault, and migration scenarios, with explicit versions, risks, and stop conditions.
## Questions this page will answer [#questions-this-page-will-answer]
* When is a legacy guide actually needed?
* How can compatibility with the current network be checked?
* When should recovery attempts stop?
---
# Transfer QUBIC and Use Assets
Explain common steps for sending, receiving, verifying, and using assets.
Source: https://www.qools.org/en/docs/learn2/wallet-usage/transfer-and-assets
This page is part of the Learn 2 information-architecture preview. Full research and fact review have not started.
## Overview [#overview]
This page provides a wallet-neutral transfer checklist covering identity, amount, asset identifier, tick, and result verification.
## Questions this page will answer [#questions-this-page-will-answer]
* What should be verified before and after a transfer?
* How do QUBIC and other assets differ?
* How can an explorer verify the result?
---
# Quorum
The design of the Qubic system is rooted in the core principle of decentralization. Its unique governance model ensures that power never concentrates in a single entity. This is achieved through a quorum protocol and a separation of authority between arbitrators.
Source: https://www.qools.org/en/docs/learn/advanced/governance
## What is Quorum? [#what-is-quorum]
In meetings or assemblies, a minimum number of participants must be present to conduct official business. This minimum count is called a *quorum*. Typically, the quorum required for a meeting is defined by the organization’s bylaws or charter. In many cases, a certain level of participation—such as a simple majority or a quorum—must be reached before a decision or vote can be taken. If the threshold is not met, the meeting may not proceed, or any actions taken might be deemed invalid.
For example, if a club’s rule is that a quorum must be a majority of all members, then only when at least half of the members attend can the club handle any formal matters.
## Qubic Quorum [#qubic-quorum]
In Qubic, the quorum goes beyond a simple majority rule—it is a dynamic body composed of 451 voting computors. Any decision that requires quorum must secure at least 451 computor votes. This body is indispensable to the decision‑making process of the Qubic system.
Computors form a democratic ecosystem where each has an equal vote. The goal is to disperse power and foster healthy competition that best serves the system’s interests. This distinctive governance structure separates the roles of computors and arbitrators, ensuring that no single entity can control both simultaneously.
## Group Decision Mechanism [#group-decision-mechanism]
The quorum plays a core role in the Qubic ecosystem:
* Formation and creation of ticks
* Initiation, voting, and acceptance of votes
This mechanism allows the construction of a dynamic, community‑driven, consensus‑based ecosystem—critical to the operation of the Qubic network.
## Voting on Proposals with Quorum [#voting-on-proposals-with-quorum]
During the voting process, once a proposal gains at least 451 computor votes, it is deemed valid and the outcome is decided by a simple majority. This mechanism guarantees that decisions are guided by the majority’s opinion.
To make impactful decisions, we need broad support and to stimulate active participation from computors. When two options are on the table, the winning choice must receive more than half of the votes (or one‑third of all participating computors if only two‑thirds are voting). For proposals with multiple alternatives, the one that garners the most votes wins—provided that at least 451 computors have cast their ballots.
---
# Proposal
In the Qubic community, decisions are not made by a single individual or a centralized group; instead, the entire community shapes them through a democratic, transparent process. The proposal system is the key link in this process. Community participation is essential for preserving Qubic’s decentralised nature and ensuring its evolution aligns with user needs and wishes. Critical decisions are collectively made by the quorum.
Source: https://www.qools.org/en/docs/learn/advanced/governance/proposals
## What Is a Proposal? [#what-is-a-proposal]
A proposal is a suggestion for changes, improvements, or new features in the Qubic ecosystem. Any member of the Qubic community can submit a proposal. Proposals span a wide range of topics, from minor tweaks and bug fixes to major changes that could redefine how Qubic operates.
### Types of Proposals [#types-of-proposals]
Qubic proposals are grouped into the following categories:
#### 1. Computor Proposals [#1-computor-proposals]
When the protocol needs to be altered or new smart contracts are to be added to Qubic, a computor proposal is required.
**Example use cases:**
* Add a new smart contract
* Extend protocol functionality
#### 2. Computor Donation Proposals [#2-computor-donation-proposals]
These proposals ask computors to donate a percentage of their earnings per epoch.
**Example use cases:**
* Request to burn $QUBIC
* Request funding for the Computor Control Fund (CCF)
* Request donation for a long‑term project
#### 3. CCF Funding Proposals [#3-ccf-funding-proposals]
If you have a project idea and want the Computor Control Fund (CCF) to help build it, this is the right place.
**Example use cases:**
* Core development needs funds to pay salaries
* Company X wants to integrate Qubic into their wallet
* Funding support for an ecosystem project
#### 4. Shareholder Proposals [#4-shareholder-proposals]
*(This type is not yet enabled)*\
Shareholder proposals are used to solicit votes from smart‑contract shareholders.
**Example use cases:**
* Adjust smart‑contract fees
* Change the smart‑contract revenue address
***
## How to Submit a Proposal [#how-to-submit-a-proposal]
Anyone in the Qubic community can submit a proposal. The steps are:
1. **Identify the Topic** – You likely already know the issue, improvement opportunity, or new feature that could benefit the entire community.
2. **Draft the Proposal** – Clearly describe the change you want. Articulate the problem or opportunity, your proposed solution, and the benefits it brings to Qubic.
3. **Submit the Proposal** – Publish it on the platform where community members can review it (usually GitHub). Be sure to follow all formatting guidelines or submission rules.
4. **Community Review** – Members can review, comment, and ask questions about your proposal. Welcome feedback and be ready to iterate if necessary.
***
## How Proposals Are Reviewed [#how-proposals-are-reviewed]
Once submitted, the community will review the proposal. The review covers:
* Evaluating the problem or opportunity identified
* Assessing the feasibility of the proposed solution
* Considering potential benefits and drawbacks
* Asking questions of the proposer and seeking answers
We encourage community members to actively participate in the review process, as the decision will ultimately be made collectively.
***
## How Decisions Are Made on Proposals [#how-decisions-are-made-on-proposals]
1. **After in‑depth discussion, the idea can evolve into a formal proposal.**\
This proposal incorporates all feedback and revisions from the community discussion. It provides a detailed action plan, clearly outlining the specifics of the change or new feature and how it will be implemented.
2. **Once finalized, the proposal is published on‑chain and waits for computors to vote.**\
The proposal must achieve quorum voting to become effective.
3. **If the proposal receives a majority of computor votes, it is accepted and moves into the implementation phase.**\
If it does not receive majority support, it will be revised for further consideration or discarded.
***
---
# Community Voting
Community voting in Qubic is used for incubation projects, Discord polls, and other temporary solutions, ensuring that only genuine $QUBIC holders participate. It marks a significant step toward transparent, fair, and community‑driven governance.
Source: https://www.qools.org/en/docs/learn/advanced/governance/voting
## What Is Community Voting? [#what-is-community-voting]
Community voting replaces Discord polls and other ad‑hoc mechanisms, guaranteeing that only legitimate $QUBIC holders take part and eliminating the risk of vote manipulation by Discord throw‑away accounts. The weighted‑vote system lets each participant’s influence reflect the amount of $QUBIC they hold, including asset‑based voting.
Voting resets each epoch. Active polls become inactive when an epoch ends. A maximum of 16 new polls can be created per epoch.
### Key Features [#key-features]
* **Weighted voting**: Weight scales with the $QUBIC held in a wallet, supporting asset‑based voting.
* **Community access**: Open to all $QUBIC holders.
* **Incubation impact**: For incubation projects, the community now controls 60 % of voting power (Core Tech 15 %, Ecosystem 15 %, Ops 10 %).
### How It Works [#how-it-works]
* Votes do not transfer funds or assets.
* Each vote consumes **100 $QUBIC**.
* Creating a poll consumes **10 ,000,000 $QUBIC**.
* Voting power = current wallet balance (or the maximum balance allowed for an asset).
### Types of Votes [#types-of-votes]
* **$QUBIC vote** → $QUBIC balance = voting power.
* **Asset vote** → Asset balance = voting power.
### Voting Balance Requirements [#voting-balance-requirements]
* Throughout the poll, you must keep your balance above a minimum threshold. If your balance falls below this minimum, your voting rights are automatically revoked.
* If your balance increases during the poll, your voting power remains unchanged.
---
# 生态概览
了解 Qubic 生态系统和核心项目方向。
Source: https://www.qools.org/zh/docs/ecosystem
---
# 词汇表
在 Qubic 文档和开发生态系统中，以下术语被广泛使用。
Source: https://www.qools.org/zh/docs/learn/glossary
### Aigarth [#aigarth]
Aigarth 是一个专注于 AI 技术、旨在通过 Qubic 网络利用闲置计算资源解决人工智能挑战的项目。它运行一种独特的算法，该算法基于螺旋逻辑门，能够根据需求进化解决方案，并且这个过程是公开透明的。所有参与者都能追踪进展，共同推动寻找高效解决方案的方法。
### Arbitrator（仲裁者） [#arbitrator仲裁者]
在 Qubic 的争议解决机制中，仲裁员担当着至关重要的角色。它致力于处理纠纷并保障用户权益不受损害，在这个自给自足的生态系统里运行。其核心职责涵盖矿工算法设定、每个纪元提供计算者排名、替换表现不佳的计算者，并汇总那些性能不佳的计算者未能接收到的 $QUBIC。
### Candidate（候选者） [#candidate候选者]
候选者在每一纪元内都有可能晋升为计算者，条件是在评分上位列前 676 名的计算者中。最多有 256 个候选者有机会实现这一晋升目标。通常情况下，只有那些运行了完整一周、且表现突出的计算者才能获得 $QUBIC 作为奖励。虽然候选者不会获得任何 $QUBIC，但以候选者身份进行工作是推动解决方案进入区块链的第一步，这是成为计算者的必要条件。
### Computor（计算者） [#computor计算者]
计算者指参与网络共识协议并执行计算任务的机器或节点。它们是 Qubic 网络的关键组成部分，负责在 Spectrum 上执行交易并运行智能合约。
### Computor Controlled Fund/CCF(计算者控制基金) [#computor-controlled-fundccf计算者控制基金]
计算者控制基金是一个以社区为中心的资金支持体系，其主要目标在于促进 Qubic 生态系统的壮大与发展。它为那些有助于增强、扩大或提高 Qubic 网络功能、影响力与效率的项目提供资金援助。这一机制通过社区成员提案和投票决策来选择项目。CCF 能够迅速整合项目计划，并确保预算分配高效有序。其宗旨旨在社区共同规划并优先考虑网络的发展路径，最终决策权归计算者所有。
CCF 的关键方面包括：
* **项目提案：** 社区中的任何成员都可以提交旨在改进或扩展 Qubic 生态系统的项目提案。
* **社区投票：** 在社区参与度和共识基础上挑选并资助项目，保证资金投入于具有广泛认可和支持、且能贴合社区需求的项目上。
* **快速实施：** 经过审批后，资助能够迅速落实提议，推动创新并加速生态系统的适应性发展。
### Energy（能量） [#energy能量]
每个 ID 在 Spectrum 上的 QUs 数量（类似于“余额”）。
### Epoch（纪元） [#epoch纪元]
在一个为期一周的时间段里（始于UTC时间星期三12点，并在一周后的同一时刻结束），一共产生了 1 万亿个 $QUBIC，在经历一次减半后，每纪元只有 4500 亿 $QUBIC 有效流通。
### Identity（ID） [#identityid]
Qubic 的钱包地址，也是计算者的身份 ID。
在 Qubic 中的矿工对于计算者的支持至关重要。矿工从计算者获取问题或任务。当为给定的地址 ID 找到这些任务的解决方案时，矿工会将结果传回给计算者。这种任务和解决方案之间的连续交换是在一个纪元内确定每个计算者评分的关键。高分对计算者保持在排名前 676 的位置至关重要。
### Oracles（预言机） [#oracles预言机]
正在 Qubic 上开发的功能之一涉及区块链技术中的“预言机”。这些是由第三方提供的服务，通过他们，智能合约能接收到外界的数据和信息。这样一来，智能合约便能在虚拟世界中与真实环境产生联系，执行需要根据现实情况调整的操作。
### $QUBIC [#qubic]
在 Qubic 这个生态系统中，$QUBIC 或 QUs 单位充当了“能量”的角色，用于运行智能合约和获取其他服务。这些单位不仅可以用作货币形式的交换方式，它们还代表了一种资源投入——就像我们在电力系统中使用电一样，在 Qubic 中使用 $QUBIC 来驱动功能。转账操作是免费进行的，并不涉及向智能合同提供“费用”，因为在这个过程中，$QUBIC 是被消耗而非作为补偿给予计算者。
在与预言机的互动中，提问者通过消耗特定数量的 $QUBIC 作为一种形式的投入或牺牲，而不是直接支付报酬给预言机。因此，我们并不能保证每次提问都能得到回应，预言机回应与否并非全然确定的。
### Quorum（法定人数） [#quorum法定人数]
"法定人数"是指为处理各类事务所需的基本决策人数。在 Qubic 中，需要达成共识的“法定人数”是所有计算者的 2/3（或 451 个）。
### Quottery [#quottery]
Quottery 是 Qubic 首批智能合约之一，它允许人们进行去中心化的赌注，其特点在于赔付结果的公开透明，让整个过程变得更加公平和可预测。
* 10% 进入计算者控制基金
* 20% 分发给 Quottery 持股人
* 70% 归赌注赢家所有
这是 Qubic 网络中首个预言机应用的开始，预示着技术实践的一个重要里程碑。
### Qx [#qx]
Qx 是 Qubic 生态系统的第一个去中心化交易所，于第 65 个纪元通过向社区公开出售共计 676 股股票完成了 IPO（首次公开募股活动）。Qx 持有者得以享受来自交易手续费的被动收益，得益于网络每秒能够处理高达 40M 转账的能力，从而为持股人提供独特的盈利机会。
### Smart Contracts（智能合约） [#smart-contracts智能合约]
协议条款直接写入代码的自动执行合约。Qubic 的第一份智能合约是名为 Qx 的去中心化交易所 (DEX) 并完成了 676 股 IPO（首次公开募股活动）。
### Spectrum [#spectrum]
Spectrum 是 Qubic 网络中的明确且无法修改的帐本，在每一纪元内都记录了网络内部发生的全部交易。借助分散化节点来处理其共识验证过程，Spectrum 强调了其透明、安全以及去中心化的属性，使其成为 Qubic 网络的关键元素之一，为全球用户带来了信任和公开性。
### Ticks（刻度） [#ticks刻度]
在 Qubic 生态系统中，刻度是指交易和智能合约计算结果达成共识的时间间隔。一次刻度可能只持续极短的时间（少于1秒）。
### Useful Proof of Work/UPoW（有用的工作证明） [#useful-proof-of-workupow有用的工作证明]
一种创新的共识机制正被探索，旨在通过将计算能力从耗能的挖掘过程重定向至具有实际价值的任务上，如训练人工智能模型。与那些仅通过解复杂谜题来消耗大量能源的传统工作证明系统不同，该机制（UPoW）专注于为社会提供实质性帮助和意义，而非仅仅浪费资源。
***
Qubic 仍在开发中，系统的某些方面在开发和实际测试阶段可能会有所变化。
---
# 概述
开始了解 Qubic
Source: https://www.qools.org/zh/docs/learn
## Qubic 是什么？ [#qubic-是什么]
Qubic 是一个创新的加密货币平台，由 Come-from-Beyond（Sergey Ivancheglo，IOTA 和 NXT 的创始人）创立，于2022年第二季度推出。Qubic 通过基于法定人数协议实现高速、无手续费的交易和可扩展的 AI 驱动解决方案。
Qubic 支持 dApps（去中心化应用）和智能合约，适用于各种行业挑战，如增强网络弹性、减少单点故障，并促进信任与协作。平台强调去中心化、安全性和效率，利用分布式账本技术来维护交易记录的完整性和不可篡改性。
## Qubic 的独特之处 [#qubic-的独特之处]
计算资源用于 Aigarth 项目的 AI 训练，助力通用人工智能（AGI）发展，避免传统 PoW 的资源浪费。
Aigarth 致力于向每一个人开放真实的 AI 源代码，旨在促进人工智能技术的共享与普及。
所有项目在 Github 平台上公开源代码，供人们查阅和使用，并且鼓励社区贡献和审计。
提供实时外部数据（如股价、体育比分），增强智能合约功能。
Qubic 的真正确保机制，提供最快速度的智能合约服务与高度的去中心化特性。
基于 C++ 构建的最高效图灵完备型智能合约，在裸机上运行，能够全面发挥计算潜能。
Qubic 提供快速、无费用的交易，并具有即时确定性，是迄今为止最快的 CertiK 验证区块链，峰值 TPS 为 15.52M。
Qubic 协议在裸机上运行，不依赖于任何操作系统，减少软件层，提高效率和安全性。
## Qubic 的工作原理是什么？ [#qubic-的工作原理是什么]
Qubic 网络由 676 个 计算者/验证者驱动，这些高性能硬件机器直接在裸机上运行 Qubic 协议，以获得最佳性能。这些计算设备与预言机通信、迅速执行智能合约、保障区块链安全、处理无费用交易，并根据网络性能获得基于 $QUBIC 的奖励。
每台计算者需要大量矿工（每台计算者可能有数千名矿工参与，且每台计算者可以作为一个矿池操作）的支持，以保持在前 676 名的排名。矿工通过 AI 训练任务最大化利用挖矿能源。矿工本身不会直接因 AI 训练工作而获得支付，会由计算者/矿池运营商对矿工的 AI 训练任务表现给予奖励。
## Qubic 解决什么问题？ [#qubic-解决什么问题]
在应对诸多挑战方面，Qubic 采取了一系列创新措施。首先，在 Qubic 协议上进行的所有交易都是无费用的，这不仅提升了用户体验，而且为 NFTs、代币和 dApps 等的应用提供了广阔前景。
其次，Qubic 被誉为能够无缝集成智能合约与预言机的少数几个协议之一，通过实时接入现实世界的资讯来增强智能合约的功能。其独创的法定人数协议确保了每一个决定都建立在多数决策之上，使得每一笔交易和智能合约执行都能最终确定。
再者，在挖矿技术服务，Qubic 找到了降低能源浪费的有效途径，将计算能力用于提升 ANN（人工神经网络）的训练效率。这一策略有效地利用了网络的庞大资源，不仅推动了机器学习服务的进步，还减轻了传统挖矿活动对能源的浪费。
## Qubic 的共识协议是什么？ [#qubic-的共识协议是什么]
Qubic 采用了一种独有的共识协议，叫做法定人数协议。特别的是，Qubic 并非像传统区块链一样运作，形成新刻度（类似一般区块链的区块）时不需要进行挖矿活动。即使所有的挖矿操作完全停止，这些新刻度仍会继续生成而不会中断。然而，如果没有了挖矿，就无法确定下一个纪元中性能最佳的计算者。
为了创建一个新刻度，需要有一个称为"刻度验证者"的实体广播一个提议中的新刻度。676 台计算者会发送包括 Qubic 网络内部状态哈希值的加密签名投票。在获得 2/3 多数法定人数的一致同意后，这个新刻度才能被接受。如果刻度验证者没有公布新投票，将会产生一个空刻度。在这种情况下，刻度数据全为零，并且其哈希也全部为零，但是仍然需要就空刻度进行法定人数投票。
若无法达成法定人数数量的投票，Qubic 会停止生成新刻度。持续生成刻度表明了大部分计算者已完全同步至 Qubic 网络状态。计算者需要大量矿工挖矿以保持自己的位置。因此，Qubic 中的挖矿活动并不是为了产生下一个区块，而是帮助计算者争取到那些备受瞩目的计算者席位之一，因为只有 676 台计算者能够获得奖励。每个纪元内，候选者可以得到矿工的帮助与其他计算者竞争来赢得其中的一个席位，并且在每个周期内可能有最多 225 台计算者会失去其地位。在经历一次减半后，总共有 4500 亿 $QUBIC 被分发给 676 个计算者，基于它们的工作性能进行计算。
***
### 免责声明 [#免责声明]
本文档中的所有内容，包括网站上提供的所有信息资源，仅用作信息和技术支持的目的，并不提供任何形式的担保、保证或陈述。
提供的信息仅为教育和参考，不作为投资建议，请咨询您的财务顾问或专业人士。强烈推荐您在连接至任何去中心化应用（dApps）、第三方服务或是做出投资与财务决策前进行独立研究。
---
# 代币经济学
驱动 Qubic 生态系统的效用（或硬币）不仅仅是一种货币，而是一种“能源”单位。这些单元称为 $QUBIC，用作执行智能合约和访问 Qubic 平台上其他服务的燃料。与传统的货币单位不同，$QUBIC 在使用时会被烧毁，这是理解 Qubic 独特代币经济学的基本概念。
Source: https://www.qools.org/zh/docs/learn/tokenomics
### $QUBIC [#qubic]
在 Qubic 中，$QUBIC 作为衡量计算“能量”消耗的标准。无论是运行智能合约还是从预言机获取信息，都是通过消耗 $QUBIC 来完成的，并且这种消耗构成了系统内的交易基础。必须注意到，尽管 $QUBIC 有其价值，但它们并不会支付给系统的实体计算者，而是以被“烧毁”或永久退出流通的形式存在，以此在通货膨胀与通缩之间保持平衡。
* $QUBIC 在使用时进行“烧毁”，为通货通胀和通货紧缩的动态提供支持。
* 所有的智能合约创建和执行都会对 Qubic 产生影响。
* 存在通货紧缩超过通货膨胀的可能性。
Qubic 网络使用 "$QUBIC"（并非 "$QU"）作为其官方代币代码。
### 纪元和 $QUBIC 生成 [#纪元和-qubic-生成]
#### 每周发行量分配 [#每周发行量分配]
| **类型** | **数量** |
| -------------- | ------ |
| 每周发行量 | 1000B |
| 每周最大烧毁量 | 550B |
| 每周有效发行量 | 450B |
| CCF (8%) | 36B |
| QEarn (12.25%) | 50.7B |
| 最小可挖供应量 | 363.3B |
在 Qubic 中，每个纪元（一纪元时间为 7 天，从 UTC 周三 12:00 至下一周周三 12:00）能产出一万亿单位的 $QUBIC，但由于有减半机制，实际产出会逐渐减少，当前已经进行第一次减半，每周有效发行量为 4500 亿 $QUBIC。这些 $QUBIC 主要分配给计算者，它们是网络的核心节点。在效率最高的情况下，一个 计算者最大可以获得相当于 3633 亿 $QUBIC 除以 676（即大约 5.37 亿个 $QUBIC）的收入。该分配模式旨在鼓励效率，那些运行效率不足的计算者其收入可能会下降，剩余的 $QUBIC 被分配给仲裁者。仲裁者不参与智能合约治理、投票或其他 $QUBIC 分配，确保了 Qubic 经济框架内的平衡。
Qubic 的总供应量不是无限的，流通的 $QUBIC 上限为 200T，排除新增发行的部分。在未来某个时间点——至少在2041年之前——烧毁率将与发行率相等或超过发行数量，导致流通硬币增长速度的停滞不前。尽管如此，矿工还是可以永久地获得回报。这个保障来自于内嵌的经济驱动因素，理论上，如果 Qubic 的流通数量接近 999T $QUBIC 时，法定人数将会启动每周 1 万亿个 $QUBIC 的烧毁作为执行费用，确保持续的收入产生。
### 转帐和费用 [#转帐和费用]
Qubic 在转账方式和费用处理上独树一帜。Qubic 网络中进行的转账是**免费**的，这是平台高效率与用户体验之所在。进一步地，“智能合约执行产生的费用”并非通常意义上的成本，而是 $QUBIC 的消耗过程，并未分配给计算者，这更加强调了 $QUBIC 作为“能量”的本质而非货币属性。
### 什么是 $QUBIC 的烧毁机制？ [#什么是-qubic-的烧毁机制]
当前，Qubic 有以下两种烧毁机制：
* 通过启动 IPO 来发起智能合约，其中股份的购买费用被烧毁掉。
* 新的智能合约发布将会烧毁 $QUBIC。
在之后，将添加两个其他机制：
* 预言机在提供数据给 Qubic 时，将会烧毁 $QUBIC。
* Aigarth 将会在使用的过程中烧毁 $QUBIC。
***
$QUBIC 构成了 Qubic 网络的命脉，它不仅驱动着网络运行，还通过提供激励来提高效率，并且通过建立奖励和烧毁机制来保持代币经济学体系的平衡。在 Qubic 平台的设计中，$QUBIC 的角色凸显了其灵活性、高效性和民主性特点。
---
# 快速开始
从这里认识 Qubic，并找到适合自己的下一步
Source: https://www.qools.org/zh/docs/learn2
Qubic 是一个由 Computor 网络共同运行的分布式计算平台，支持价值转移、资产、智能合约和计算任务。你可以先了解它的整体结构，也可以直接从钱包、挖矿或生态开始。
## 认识 Qubic [#认识-qubic]
了解 Qubic 的定位、网络组成，以及它能够提供哪些能力。
了解 Epoch、Tick、Computor、Quorum 和挖矿之间的关系。
了解 Identity、QUBIC、发行资产、Shares 和智能合约。
## 你想做什么 [#你想做什么]
从 Identity、钱包和签名开始，学习备份、转账与资产使用。
了解矿池、矿工软件、挖矿模式、收益和常见问题。
查看 Qubic 生态中的项目、钱包、Explorer、DEX 和常用工具。
## 继续深入 [#继续深入]
深入了解网络角色、共识、状态、交易与资产模型。
了解发行与燃烧、激励与资金流，以及社区治理机制。
查找术语、当前主网基线、数据来源和官方资料。
---
# 挖矿概览
了解 Qubic 挖矿的基础概念和相关资源。
Source: https://www.qools.org/zh/docs/mining
---
# 进阶概念
深入了解 Qubic 网络角色、治理和协议相关主题。
Source: https://www.qools.org/zh/docs/learn/advanced
本章节整理 Qubic 的进阶学习资料，包括网络角色、治理机制和协议相关概念。
---
# 网络角色
在 Qubic 生态系统中，两种主要节点类型——计算者和矿工——协同工作，以支持其去中心化基础设施。这些实体承担着独特的责任，并确保网络高效运行，而仲裁者则扮演着至关重要的角色，维护网络的公正性和可靠性。
Source: https://www.qools.org/zh/docs/learn/advanced/network-role
## 计算者 [#计算者]
在 Qubic 系统中，每个计算者是一个专门配置来处理任务的节点，这些任务可能涉及运行智能合约或促进区块链上的交易。不同于传统区块链系统依赖矿工进行交易验证和添加，Qubic 生态系统中的计算者执行更广泛的功能。它们不仅用于执行具体任务，还积极参与基于共识的分散决策过程，并确保网络内部经济模型保持平衡稳定。
**主要特征**：
* 在保护和保障网络的去中心化特性方面所扮演的角色。
* 在每个纪元迭代中，计算者都会从新产生的 $QUBIC 分配中获得一部分奖励，以支持整个网络的运行和参与活动。这样的分配方式旨在鼓励积极参与网络服务和贡献，提升整体网络的效率与安全性。
* 参与关键网络投票和决策过程。
**限制**: 在 Qubic 网络中，任何时刻都有一个固定的 676 台计算者进行运作，以保证最佳性能和决策流程的顺畅。每周根据他们的矿工提供的解决方案进行评分排名，确定前 451 表现优秀的计算者保持其地位，而剩下的 225 个位置则从候选者池或低排名的计算者中每纪元补充。
**在 Qubic 上运行计算者的挑战：**
* 直接在裸机上运行，并且需要如何操作 UEFI。
* 每纪元对 qubic.cpp 进行定期编译。
* 持续的系统更新。
* 备份系统是必要的，以确保刻度持续运行。
* 持续竞争，计算者要保持位置，必须击败候选者中的那些具有足够挖矿能力的竞争者。
* 时刻保持警惕，计算者要时刻关注网络状态，以确保刻度持续运行和及时响应突发情况。
操作一台计算者需要具备相应的专业知识和技术意识，并且始终要保持高度警觉。如果你正在考虑成为计算者，请务必提前做好面对挑战的心理与实际准备。
## 矿工 [#矿工]
在 Qubic 生态系统中的矿工与传统区块链网络中的同行不同。他们不是为了验证并添加交易到区块链而竞争，而是由计算者分配特定的计算问题或任务进行工作。一旦找到解决方案，就将其反馈给相应的计算者。这种互动不仅有助于验证任务的完整性，还有助于整个网络中操作和验证的总体处理与验证。
**主要特征**：
* 从计算者接收计算问题或任务（用 IDs 表示）。
* 在成功解决问题后，将解决方案回传给计算者，为它们的分数做出贡献。
* 其核心在于 Qubic 创新系统的整体任务执行，而不仅仅是交易验证。
**潜在能力**: Qubic 网络允许理论上无限的矿工数量，推动广泛参与并确保系统背后的强大计算能力。
只有计算者可以从 Qubic 协议中获得每周的支付。为了在 676 个计算者中保持其位置，计算者必须通过相关的矿工每纪元积累足够的解决方案。因此，每个计算者最终都不得不培养一个强大的矿池，并通过矿池支付来提供激励。
运行一个矿工则要容易得多，并且已经有很多公开的[矿池](../../mining/index.mdx)可用。
在 Qubic 的新时代背景下，理解矿工和计算者之间的基本区别至关重要。随着我们迈进这一全新的发展阶段，计算者的角色及其责任的重要性无疑会日益凸显。
## 仲裁者 [#仲裁者]
在 Qubic 生态中，有一类关键角色专门负责处理纠纷并保障用户的权益。仲裁者是 Qubic 生态系统中的一个实体，负责解决争端和保护用户利益。
仲裁者对采矿算法的参数进行设定，在每个纪元发布计算者排名，并有能力替换表现不佳的计算者。同时，仲裁者还会累积那些性能不佳、故障频发的计算者无法获取的 $QUBIC，约为每个纪元有效产出的 1%。每个节点操作者依据个人需求和偏好，在程序文件 Qubic.cpp 中设置对应的 ID，来单独选择信任的仲裁者进行权益保障工作，计算者能够通过共识流程集体覆盖或替换仲裁者，此功能对于防止任何单一实体获得对网络的过度控制至关重要。
---
# Spectrum
Spectrum 作为 Qubic 网络中清晰且不可篡改的账本，维护着每个周期在网络上执行的交易的完整日志。Spectrum 由去中心化节点管理其共识，凸显了其透明性、安全性和去中心化的特性。这些特性巩固了 Spectrum 作为 Qubic 网络核心组件的地位，为全球用户构建信任和透明度。
Source: https://www.qools.org/zh/docs/learn/advanced/spectrum
## 了解 Spectrum [#了解-spectrum]
在 Qubic 宇宙中，“Spectrum”代表着一个关键的、去中心化的账本系统，它保存着每个纪元透明且不可篡改的交易历史记录。Spectrum 作为一个开放的记录，呈现了 Qubic 网络每个纪元内进行的每笔交易的顺序记录。
Spectrum 可以看作是一个任何人都可以访问的数字化、透明的账本。它细致地记录了 Qubic 网络中每个纪元的交易历史记录。
## 运行机制 [#运行机制]
记录交易：交易执行后，会将其记录为 Spectrum 中的新条目。交易的详细信息，例如发送方和接收方的地址以及转账金额，都会被记录下来。
不可篡改的记录：一笔交易一旦在一个纪元内被记录下来，就无法被更改。Spectrum 的这种不可篡改的特性确保了网络交易历史的准确性和安全性。
## 安全性和去中心化 [#安全性和去中心化]
Spectrum 的去中心化结构确保控制权不集中在单一实体。相反，Spectrum 分布在所有计算者上。这种去中心化增强了 Spectrum 对审查和欺诈行为的抵御能力。修改 Spectrum 需要大多数计算者的共识，这实际上是不可能的。
---
# 创建钱包
钱包是您使用 Qubic 的主要工具，它存储您的数字资产，创建钱包是您进入 Qubic 的第一步，通过钱包，你可以登录DApps、查看余额、发送交易和验证身份。
Source: https://www.qools.org/zh/docs/learn/usage/wallet-create
## 官方钱包 [#官方钱包]
Metamask Snap 钱包（开发中）
注意事项：当前，在 MetaMask 的钱包内的全部 $QUBIC 代币均为骗局。
## 如何创建钱包？ [#如何创建钱包]
所有以下教程均为 [Qubic 网页钱包](https://wallet.qubic.org/)。
1. 打开 [Qubic 网页钱包](https://wallet.qubic.org/)，输入金库名称。
2. 为你的地址添加一个名字，并选择**随机种子**来生成你的地址。
这55位字符是你的 Qubic 地址私钥（种子）！
请将此种子保存在安全的位置。
若未备份种子，你可能会丢失资金！
强烈建议不要使用自定义的种子，因为这样做会增加被黑客盗取的风险！！！
3. 在确保安全的前提下，设定一个强有力的密码，并将 Vault 文件进行下载和妥善保存。
Vault 文件存储你的钱包地址相关的所有信息，并对其进行加密。使用密码来验证并解锁文件。如果你的钱包包含多个地址，它们都将保存在 Vault 文件中。
4. 输入你在上一步设置的密码，并导入 Vault 文件进行验证。
每次更新你的钱包（例如：添加或编辑地址），你将被提示下载最新的 Vault 文件，请记得更新并保存该文件。
5. 创建完成，成功进入钱包页面。
#### 忘记保存种子？ [#忘记保存种子]
1. 首先点击右上角的锁形图标，输入密码并导入 Vault 文件以解锁。
2. 点击地址信息内的“眼睛”图标，点击打开后就可以可以看到公共ID的地址和 55 位字符的种子。
**再次强调，这 55 位字符的种子非常重要，等同于地址的私钥，请不要随意告诉他人，并妥善保存。**
## 钱包安全性 [#钱包安全性]
#### K12 哈希算法 [#k12-哈希算法]
Qubic 采用 Keccak 团队设计的 K12 算法来进行其加密操作，相比传统的 SHA-256 等算法，K12 在速度和安全性上更加优越。通过将字母数字种子转换为具有高随机性的私钥，从而达到强化加密安全的目的。这一策略确保了每个生成的私钥不仅独特而且具备强大的抗暴力破解能力。
#### 密钥和地址生成 [#密钥和地址生成]
Qubic 系统采用一个由 55 个小写字母组合而成的种子作为基础来生成 256 比特位的私钥，通过 K12 哈希算法完成。根据私钥，我们使用 FourQ 曲线与标准的椭圆曲线乘法运算（ecc\_mul\_fixed）结合进行签名处理，从而得到公钥。FourQ 曲线在确保系统加密安全方面发挥了巨大作用，因为它提供了当前最高效且最安全的椭圆曲线之一。这使得我们的数字签名过程不仅更加快速，而且也更为稳固可靠。
---
# 钱包自救手册
如果发现无法访问钱包，请保持冷静。检查仍然可用的信息，例如你的密码、文件和种子。不要清除浏览器缓存。
Source: https://www.qools.org/zh/docs/learn/usage/wallet-self-help
## 确保你拥有以下信息和文件 [#确保你拥有以下信息和文件]
* **地址 55 位种子**
* **钱包密码**
* **文件**
Vault file
或者
qubic.li-wallet.config and qubic.li-wallet.unlock
或者版本更老的
qubic.li-wallet.config and qubic.li-wallet.privatekey
早期的钱包文件由两部分组成：一个配置文件和一个解锁文件。如果你仍在使用这类文件，请尽快更新到 Vault 文件。
#### 1. 有 55 位字符种子备份 [#1-有-55-位字符种子备份]
这种情况最容易解决，只需创建新钱包将种子导入即可找回。
为避免意外，请先使用浏览器的隐私标签页或者是其他浏览器创建新的钱包进行尝试。
这就是为什么要备份 55 位种子的重要性。
#### 2. 有钱包密码和 Vault 文件 [#2-有钱包密码和-vault-文件]
Vault 文件存储了你的钱包地址信息，只需要使用新的网页钱包域名输入密码和导入文件即可。
网页钱包新域名: [https://wallet.qubic.org/](https://wallet.qubic.org/)
*其他情况：由于钱包每次编辑或更新时都需要下载新的 Vault 文件，如果您有多个 Vault 文件且发现导入地址不正确，请尝试导入不同的 Vault 文件。*
#### 3. 有钱包密码还有 qubic.li-wallet.config 和 qubic.li-wallet.unlock/qubic.li-wallet.privatekey [#3-有钱包密码还有-qubicli-walletconfig-和-qubicli-walletunlockqubicli-walletprivatekey]
与前一种情况类似，主要区别在于需要导入两个文件。
为了防止未知风险，请尽快将钱包文件更新至 Vault 格式。
#### 4. 高难度模式 - 仅拥有钱包密码和qubic.li-wallet.unlock/qubic.li-wallet.privatekey [#4-高难度模式---仅拥有钱包密码和qubicli-walletunlockqubicli-walletprivatekey]
如果意外删除了 qubic.li-wallet.config 并且浏览器缓存仍然可访问，可以尝试输入密码和导入 qubic.li-wallet.unlock/qubic.li-wallet.privatekey 来解锁你的钱包。如果仍然有效，请尽快导出你地址的 55 位字符的种子，并尽快更新到 Vault 文件。
> **记得，始终要保护好你的关键信息，并确保自己的数字资产安全。**
---
# 使用钱包
创建 Qubic 钱包的指南
Source: https://www.qools.org/zh/docs/learn/usage/wallet-use
# 钱包使用 [#钱包使用]
## 转账 [#转账]
在使用网页钱包进行转账之前，需要先将钱包解锁。
执行刻度指执行转账时的刻度，默认设置为当前刻度 +10，通常不需要额外的设置。
## 交易记录 [#交易记录]
地址交易记录可以通过浏览器查询。
官方浏览器: [QUBIC Explorer](https://explorer.qubic.org/network)
## 资产 [#资产]
在 Qubic 生态系统中，“资产”指的是股票或代币，例如 Qx 股份和 CFB 代币。只有当你持有时，你的地址才会显示资产。
当前，可以通过 Qx Dex 或场外交易（OTC）平台进行交易。CFB 代币可以在 Safatrade 交易平台进行购买。
如何使用 Qx Dex 进行交易: [How to Buy/Sell $CFB on QX ($Qubic ’s Dex) using Qwallet](https://x.com/c_f_b_token/status/1797543889139859917)
## 投票 [#投票]
Qubic 计算者投票用于在关于整个网络的决策主题上达成共识。这可以包括接受智能合约或其他协议决定。只有计算者能够参与。
如果你想提出任何东西，你需要至少拥有一个计算者的种子。
---
# 激励、费用与资金流
说明计算者、矿工、合约和协议资金之间的价值流向。
Source: https://www.qools.org/zh/docs/learn2/economics-governance/incentives-fees-fund-flows
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将用资金流视角解释计算者奖励、矿池结算、合约执行储备和其他协议费用，避免把逻辑记账和链上转账混为一谈。
## 本页计划回答 [#本页计划回答]
* 计算者奖励如何进入矿池结算？
* 智能合约执行费用来自哪里？
* 哪些价值流会改变实际供应？
---
# 发行、燃烧、供应与减半
追踪 QUBIC 从计划发行到实际供应变化的过程。
Source: https://www.qools.org/zh/docs/learn2/economics-governance/issuance-burn-supply-halving
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将分开计划发行、协议燃烧、合约燃烧和减半，并用一致的单位说明它们如何共同影响有效供应。
## 本页计划回答 [#本页计划回答]
* 计划发行与有效发行为什么不同？
* 不同燃烧机制应如何分类？
* 减半改变了哪些参数？
---
# Proposal、Community Voting 与 CCF
区分提案类型、投票资格、法定参与和结果效力。
Source: https://www.qools.org/zh/docs/learn2/economics-governance/proposals-voting-ccf
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将把 Computor 提案、Shareholder 投票、社区投票与 CCF 资金流程分开说明，避免用同一套阈值解释所有治理活动。
## 本页计划回答 [#本页计划回答]
* 不同提案由谁发起和投票？
* 参与门槛与胜选规则如何区分？
* 投票结果是否具有协议约束力？
---
# Tokenomics 总览
从供应、发行、燃烧和激励四个维度理解 QUBIC 经济模型。
Source: https://www.qools.org/zh/docs/learn2/economics-governance/tokenomics-overview
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将提供经济模型的总览，标出固定规则、会随版本变化的参数，以及需要从链上或代码核验的数据。
## 本页计划回答 [#本页计划回答]
* 最大供应量与流通供应量有什么区别？
* 每个 Epoch 的发行与燃烧如何影响供应？
* 哪些数字不能脱离版本和时间引用？
---
# 资产与应用
介绍 Identity、QUBIC、发行资产、Shares 和智能合约
Source: https://www.qools.org/zh/docs/learn2/getting-started/assets-and-applications
Qubic 的网络状态不仅包含 QUBIC 余额，也包含发行资产和智能合约数据。用户通过 Identity 与这些状态发生联系，钱包和应用则把协议中的数据转换成可操作的界面。
## Identity：网络中的实体标识 [#identity网络中的实体标识]
Identity 是 Qubic 中用于识别实体的公开标识。个人、服务、Computor 和智能合约都可以通过 Identity 出现在网络交互中。
钱包根据 Seed 派生私钥和公开 Identity。Identity 用于接收 QUBIC 或资产，可以公开分享；私钥材料负责生成签名，由持有者自行保管。网络验证的是交易签名，而不需要知道使用者的姓名或账户资料。
## QUBIC：网络原生单位 [#qubic网络原生单位]
QUBIC 是 Qubic 的原生单位，用于在 Identity 之间转移价值，也用于参与智能合约和部分协议功能。
普通 QUBIC 转账没有传统区块链常见的基础网络手续费。智能合约、DEX、矿池、交易平台或其他服务仍可以根据自身规则产生燃烧、费用或结算差异，这些属于具体功能的经济设计。
## Spectrum：QUBIC 状态 [#spectrumqubic-状态]
Spectrum 描述 Identity 与 QUBIC 相关的网络状态。Computor 在执行 Tick 后得到新的 Spectrum 状态，使所有参与共识的节点能够对当前余额形成相同结果。
钱包通常从节点或数据服务读取 Spectrum，并把其中的数据呈现为用户熟悉的余额。历史交易列表则可以由 Tick 数据、Bob、归档节点和 Explorer 进一步整理得到。
## Universe：发行资产状态 [#universe发行资产状态]
Qubic 支持创建和转移发行资产。Universe 记录这些资产的发行与持有关系，其中包含两个常见概念：
* **Ownership：** 某个 Identity 对资产的所有权；
* **Possession：** 某个 Identity 当前对资产的控制或持有关系。
资产由名称与发行者共同识别。两个资产可以使用相同名称，但由不同 Identity 发行，因此钱包和市场通常会同时展示资产名称与发行者。
## Shares：智能合约中的份额 [#shares智能合约中的份额]
Shares 通常表示某个智能合约内部定义的份额或权利。它们可以参与合约的分配、收益或治理逻辑，具体含义由对应合约决定。
QUBIC、发行资产和 Shares 都可以体现价值关系，但属于不同的数据结构：
| 类型 | 来源 | 主要状态 |
| ------ | -------- | ----------- |
| QUBIC | Qubic 协议 | Spectrum |
| 发行资产 | 资产发行者 | Universe |
| Shares | 具体智能合约 | 合约状态及相关资产关系 |
## 智能合约：协议中的应用逻辑 [#智能合约协议中的应用逻辑]
Qubic 智能合约使用受限 C++ 编写，并集成到 Core 中。合约可以保存自己的状态，对交易输入执行 Procedure，并按照确定的规则更新结果。
一些生态功能直接由智能合约提供，例如：
* 资产发行与交换；
* 质押与奖励分配；
* 拍卖和市场；
* 治理或资金管理；
* 面向其他合约的公共能力。
合约在网络中的行为由其代码和当前状态共同决定。前端应用负责组织交互流程，Computor 则负责实际执行并形成共识。
## Oracle Machines 与外部信息 [#oracle-machines-与外部信息]
智能合约的执行是确定性的，但现实世界的数据来自网络之外。Oracle Machines 允许 Computor 回答外部问题，并把达到 Quorum 的答案提供给协议内逻辑。
这使应用能够参考价格、时间、事件结果或其他外部信息。数据来源、问题设计和回答方式属于具体 Oracle 的组成部分。
## Outsourced Computation 与外部操作 [#outsourced-computation-与外部操作]
Outsourced Computation 为协议提供向外部系统发送经 Quorum 授权指令的能力。它与智能合约和 Oracle Machines 分别对应不同方向：
| 能力 | 数据流向 | 作用 |
| ---------------------- | ----- | ------------ |
| Smart Contract | 协议内部 | 执行确定性逻辑并更新状态 |
| Oracle Machine | 外部到协议 | 把外部问题的答案带入网络 |
| Outsourced Computation | 协议到外部 | 授权外部系统执行特定操作 |
这些能力共同构成 Qubic 的应用基础，但具体可用功能仍取决于当前 Core 版本和已上线合约。
## 钱包、Explorer、DEX 与矿池 [#钱包explorerdex-与矿池]
生态产品围绕协议提供不同入口：
| 服务 | 主要连接的协议能力 |
| -------- | ---------------------------------- |
| 钱包 | 管理 Identity、生成签名、读取余额和资产 |
| Explorer | 索引 Tick、交易、Identity、资产与合约数据 |
| DEX | 调用交易或市场合约，展示资产行情和订单状态 |
| 矿池 | 接收矿工提交、统计 Share 或 Solution，并执行收益结算 |
这些产品可以采用不同的数据源、刷新频率和交互方式，但最终都围绕 Qubic 的身份、交易、状态或计算机制工作。
## 相关内容 [#相关内容]
* [Spectrum、Universe 与 Identity](../protocol-basics/spectrum-universe-identity)
* [交易、资产与 Shares](../protocol-basics/transactions-assets-shares)
* [Tokenomics 总览](../economics-governance/tokenomics-overview)
* [Identity、Seed、Vault 与签名安全](../wallet-usage/identity-seed-vault-signing)
## 主要依据 [#主要依据]
* [Qubic ID](https://docs.qubic.org/developers/qubic-id/)
* [Spectrum](https://docs.qubic.org/learn/spectrum/)
* [Qubic Tokenomics](https://docs.qubic.org/learn/tokenomics/)
* [Smart Contracts Overview](https://docs.qubic.org/developers/smart-contracts/overview/)
* [Smart Contract Lifecycle](https://docs.qubic.org/developers/smart-contracts/lifecycle/)
* [Oracle Machines](https://docs.qubic.org/developers/oracles/)
---
# 网络如何运行
了解 Epoch、Tick、Computor、Quorum 和挖矿之间的关系
Source: https://www.qools.org/zh/docs/learn2/getting-started/concept-map
Qubic 网络以 Epoch 为周期运行，并在连续的 Tick 中处理交易与计算。当前 Epoch 的 Computor 共同执行相同输入，通过 Quorum 确定结果；Miner 提供计算结果，参与后续 Epoch 的 Computor 席位竞争。
这两部分同时运行：Tick 推进当前网络状态，Epoch 则组织较长周期内的节点集合和挖矿计分。
## Epoch：网络运行周期 [#epoch网络运行周期]
一个 Epoch 通常持续约一周，其中包含大量连续 Tick。Epoch 为以下内容提供共同的时间边界：
* 当前参与共识的 Computor 集合；
* Candidate 与 Computor 的 Score；
* Miner 提交的 Solution 统计；
* 部分由协议按周期更新的数据与参数。
进入新 Epoch 后，Computor 集合和周期性计数进入新的阶段。QUBIC 余额、资产和智能合约等持续状态则会随网络状态继续存在。
## Tick：执行与共识时点 [#tick执行与共识时点]
Tick 是 Qubic 处理交易和形成结果的基本时间单位。每个 Tick 都有递增编号，Computor 按共同规则处理该时点的输入。
一笔普通交易大致经历以下过程：
1. 钱包构造交易，写入发送方、接收方、金额、输入和未来的目标 Tick；
2. 钱包使用私钥材料签名，并把交易广播到网络；
3. 交易随网络传播到 Computor；
4. 目标 Tick 到来后，Computor 验证并执行交易；
5. 足够多 Computor 得到一致结果，形成 Quorum；
6. 新状态随后可被节点、钱包和索引服务读取。
交易是否进入目标 Tick，取决于签名、余额、输入格式、目标 Tick 和网络传播等条件。钱包通常会结合 Tick 结果与后续状态，向用户展示交易状态。
## Computor：执行网络状态 [#computor执行网络状态]
Computor 是 Qubic 当前共识集合中的节点。每个 Computor 接收交易和网络数据，运行 Core 与智能合约，并计算 Tick 完成后的状态。
当前架构设有 676 个 Computor 席位。当至少 451 个 Computor 对同一结果形成一致意见时，网络达到 Quorum。这样，结果来自多个独立节点对同一规则的执行，而不是某一个节点的单独判断。
## Candidate 与 Miner：参与后续席位 [#candidate-与-miner参与后续席位]
没有进入当前 Computor 集合的节点身份可以作为 Candidate 参与竞争。Miner 执行协议当前指定的计算任务，并把有效 Solution 提交给关联的 Computor 或 Candidate 身份。
这些结果形成 Score。Epoch 结束时，Score 会参与后续 Computor 席位的确定，使计算资源与网络节点集合的更新联系起来。
公共矿池在这条路径上提供连接、统计和结算服务。矿工看到的 Share、Solution、算力和收益属于矿池对提交过程的具体表示；协议层最终关注的是有效计算结果及其对 Score 的贡献。
## Quorum：形成共同结果 [#quorum形成共同结果]
Computor 对相同输入执行相同规则，理论上应得到相同输出。Quorum 用来确认足够多节点确实形成了同一个结果。
这一机制应用于 Tick 状态，也被 Qubic 的其他能力复用。例如 Oracle Machines 汇集 Computor 对外部问题的回答，Outsourced Computation 则使用 Quorum 授权外部系统执行特定操作。
## 状态如何被读取 [#状态如何被读取]
协议运行后会产生当前状态、Tick 数据和日志。不同组件使用这些数据提供不同视图：
| 数据层 | 主要内容 |
| -------------- | -------------------- |
| Core 状态 | 当前 QUBIC、资产和智能合约状态 |
| Tick 数据 | 某个执行时点的交易和共识结果 |
| Bob 与归档节点 | 保存和提供更长范围的 Tick 数据 |
| Explorer 与索引服务 | 将底层数据整理成交易记录、统计和搜索结果 |
因此，同一笔交易可以同时出现在钱包、节点接口和 Explorer 中，但这些界面读取数据的时间与历史覆盖范围可能不同。
## 一张流程图看完整关系 [#一张流程图看完整关系]
```text
用户或应用
│ 签名交易
▼
目标 Tick ──► Computor 执行 ──► Quorum ──► 网络状态更新
Miner
│ Solution
▼
身份 Score ──► Epoch 结算 ──► 后续 Computor 集合
```
下一篇 [资产与应用](./assets-and-applications) 会继续介绍 Identity、QUBIC、发行资产、Shares 和智能合约如何建立在这套网络之上。
## 主要依据 [#主要依据]
* [Qubic Consensus](https://docs.qubic.org/overview/consensus/)
* [官方节点角色说明](https://docs.qubic.org/learn/nodes/)
* [Ticks and Concurrency](https://docs.qubic.org/developers/ticks-and-concurrency/)
* [Qubic ID](https://docs.qubic.org/developers/qubic-id/)
* [Oracle Machines](https://docs.qubic.org/developers/oracles/)
---
# Qubic 是什么
从网络、计算、状态和应用四个层面认识 Qubic
Source: https://www.qools.org/zh/docs/learn2/getting-started/what-is-qubic
Qubic 是一个由分布式节点共同运行的计算网络。它可以处理 QUBIC 转账、发行资产和智能合约，也可以把计算资源用于协议指定的任务。
Qubic 的核心并不是一条由矿工不断追加区块的账本，而是一组持续协同工作的 Computor。它们接收相同的交易和输入，在一个个 Tick 中执行计算，并通过 Quorum 对结果形成一致意见。
## 一个持续运行的分布式计算机 [#一个持续运行的分布式计算机]
可以把 Qubic 看成一台由许多独立节点共同组成的计算机：
* **输入**来自用户交易、智能合约调用和协议数据；
* **执行**由当前 Epoch 的 Computor 完成；
* **结果**在足够多 Computor 得到相同结论后确定；
* **状态**记录 Identity 的 QUBIC、发行资产和智能合约数据；
* **应用**通过节点、钱包或索引服务读取状态并提交新的交易。
单个节点不能独自决定网络结果。每个 Computor 按相同规则处理输入，Quorum 则把多数节点得到的一致结果变成网络共同接受的状态。
## 网络中的时间 [#网络中的时间]
Qubic 使用 **Epoch** 和 **Tick** 组织运行时间。
### Epoch [#epoch]
Epoch 是一个网络运行周期。一个 Epoch 包含大量 Tick，并为 Computor 席位、挖矿 Score 和部分协议参数提供共同边界。主网通常每周进入一个新的 Epoch。
### Tick [#tick]
Tick 是交易与计算被执行和确定的时间单位。交易会指定一个未来 Tick；当该 Tick 到来时，Computor 执行交易并对结果形成一致意见。网络因此表现为连续推进的一系列执行时点，而不是等待矿工生成下一个区块。
## 网络中的参与者 [#网络中的参与者]
| 角色 | 在网络中的作用 |
| --------- | ---------------------------------------- |
| Computor | 执行交易和智能合约、交换 Tick 数据并参与共识 |
| Candidate | 具备节点身份但尚未取得当前 Computor 席位，参与后续席位竞争 |
| Miner | 完成协议指定的计算任务，并把有效 Solution 贡献给关联身份的 Score |
| 用户与应用 | 创建签名交易、持有 QUBIC 或资产，并调用智能合约 |
当前架构由 676 个 Computor 席位组成，通常至少需要 451 个一致结果形成 Quorum。Computor 负责交易执行和共识；Miner 的计算结果主要参与 Score 与后续席位竞争。这两类角色相互关联，但承担的工作不同。
## Qubic 保存什么 [#qubic-保存什么]
Qubic 需要让所有 Computor 对当前状态得到相同结果。主要状态包括：
* **Spectrum：** Identity 与 QUBIC 相关的状态；
* **Universe：** 发行资产、ownership 和 possession 等资产关系；
* **智能合约状态：** 每个合约维护的内部数据；
* **Tick 数据与日志：** 网络运行过程中产生、可供节点和索引服务处理的数据。
钱包和 Explorer 会把这些底层状态整理成余额、资产列表、交易记录和图表。它们是访问网络的界面，而不是共识本身。
## Qubic 能承载什么 [#qubic-能承载什么]
### QUBIC 与资产 [#qubic-与资产]
QUBIC 是网络原生单位，用于价值转移以及与协议和合约交互。Qubic 还支持由特定发行者创建的资产，同名资产可以来自不同发行者，因此资产身份由名称与发行者共同确定。
### 智能合约 [#智能合约]
Qubic 智能合约使用受限的 C++ 编写，经过审核和网络流程后集成进 Core。所有 Computor 对相同输入执行同一份合约逻辑，使合约状态成为共识的一部分。
### 外部数据与执行 [#外部数据与执行]
Oracle Machines 用于把外部问题的答案带入网络；Outsourced Computation 用于由 Quorum 授权外部系统执行特定操作。这些能力把协议内的确定性状态与外部世界连接起来。
## 与常见区块链的主要差别 [#与常见区块链的主要差别]
| 常见区块链模型 | Qubic 的运行方式 |
| --------------- | -------------------------------- |
| 交易由区块生产者选入新区块 | 交易面向未来 Tick，由 Computor 执行 |
| 通过后续区块累计确认 | Tick 结果由 Quorum 确定 |
| 矿工或验证者同时承担打包与共识 | Computor 负责执行和共识，Miner 参与计算与席位竞争 |
| 合约在通用虚拟机中部署字节码 | 合约以受限 C++ 编写并集成进 Core |
| 节点通常保存可遍历的区块链历史 | 当前状态、Tick 数据和索引后的历史视图分属不同数据层 |
这些差别决定了 Qubic 钱包、Explorer、挖矿和智能合约的使用方式。下一篇 [网络如何运行](./concept-map) 会沿着一笔交易和一次 Epoch 切换继续展开。
## 主要依据 [#主要依据]
* [Qubic 官方概览](https://docs.qubic.org/overview/introduction/)
* [Qubic Consensus](https://docs.qubic.org/overview/consensus/)
* [官方节点角色说明](https://docs.qubic.org/learn/nodes/)
* [Ticks and Concurrency](https://docs.qubic.org/developers/ticks-and-concurrency/)
* [Smart Contracts Overview](https://docs.qubic.org/developers/smart-contracts/overview/)
* [Qubic Glossary](https://docs.qubic.org/learn/glossary/)
---
# Epoch、Tick 与最终性
解释 Qubic 的时间组织方式以及交易何时可以视为确定。
Source: https://www.qools.org/zh/docs/learn2/protocol-basics/epoch-tick-finality
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将说明 Epoch 与 Tick 的关系、纪元切换的含义，以及最终性应如何结合协议状态来理解。
## 本页计划回答 [#本页计划回答]
* Epoch 和 Tick 分别解决什么问题？
* 纪元切换时哪些状态会变化？
* 如何判断一笔交易已经确定？
---
# Computor、Candidate、Miner 与选举
区分网络参与角色，并解释矿工支持与计算者席位之间的关系。
Source: https://www.qools.org/zh/docs/learn2/protocol-basics/network-roles-election
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将分别定义 Computor、Candidate 和 Miner，说明角色之间的协作关系，并概述每个 Epoch 的选举过程。
## 本页计划回答 [#本页计划回答]
* 哪些角色直接参与共识？
* 矿工的工作如何影响计算者选举？
* 角色名称为什么不能互换使用？
---
# Quorum 与共识
说明法定人数、投票和 Tick 确认之间的关系。
Source: https://www.qools.org/zh/docs/learn2/protocol-basics/quorum-consensus
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将从 Tick 的产生过程解释 Quorum，并区分共识阈值、治理投票和其他类型的多数决策。
## 本页计划回答 [#本页计划回答]
* Quorum 在 Tick 确认中扮演什么角色？
* 共识投票与治理投票有什么区别？
* 网络无法形成 Quorum 时会怎样？
---
# Spectrum、Universe 与 Identity
分别解释 QUBIC 状态、资产状态与实体标识。
Source: https://www.qools.org/zh/docs/learn2/protocol-basics/spectrum-universe-identity
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将拆开三个经常被混写的概念：Identity 如何标识实体，Spectrum 保存什么状态，Universe 如何描述资产的发行、所有权与占有。
## 本页计划回答 [#本页计划回答]
* Identity 与钱包地址是什么关系？
* Spectrum 是否等于完整交易历史？
* Universe 中的 ownership 与 possession 有何区别？
---
# 交易、资产与 Shares
建立转账、资产发行和合约份额之间的基本模型。
Source: https://www.qools.org/zh/docs/learn2/protocol-basics/transactions-assets-shares
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将介绍 QUBIC 转账、普通资产与智能合约 Shares 的差别，并说明浏览器或钱包中常见字段的基本含义。
## 本页计划回答 [#本页计划回答]
* QUBIC、发行资产和 Shares 有什么差异？
* ownership 与 possession 如何影响资产使用？
* 查看交易或资产时应关注哪些字段？
---
# 事实状态、来源与冲突说明
公开记录资料来源、事实状态和无法简单消除的冲突。
Source: https://www.qools.org/zh/docs/learn2/reference/fact-status-sources-conflicts
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将说明如何区分稳定事实、动态事实、设计目标和待验证信息，并记录官方文档与代码之间的重要冲突。
## 本页计划回答 [#本页计划回答]
* 来源冲突时采用什么处理顺序？
* 动态事实如何标注核验日期？
* 哪些结论应保留不确定性？
---
# 术语表
给出 Qubic 核心术语的简洁定义和相关页面链接。
Source: https://www.qools.org/zh/docs/learn2/reference/glossary
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将作为全站统一术语入口，优先给出简短定义，并把容易混淆的词引向对应专题页。
## 本页计划回答 [#本页计划回答]
* 核心术语的推荐中文译法是什么？
* 哪些英文术语应保留原文？
* 哪些概念容易被错误地当作同义词？
---
# 当前主网、Epoch 与版本基线
记录阅读动态文档时所依据的主网和软件版本。
Source: https://www.qools.org/zh/docs/learn2/reference/network-epoch-version-baseline
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将集中记录当前主网、Core 版本和关键工具版本，并为会变化的结论提供统一的核验日期。
## 本页计划回答 [#本页计划回答]
* 当前文档基于哪个 Core 版本？
* 动态参数最后一次何时核验？
* 版本变化后哪些页面需要复核？
---
# 白皮书与官方资料入口
汇总官方文档、源码、发布说明和长期参考资料。
Source: https://www.qools.org/zh/docs/learn2/reference/whitepaper-official-resources
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将按用途整理白皮书、官方 Learn、Developer 文档、Core 源码、Release 和社区入口，并说明每类来源适合验证什么。
## 本页计划回答 [#本页计划回答]
* 不同资料适合验证哪些事实？
* 为什么应优先引用固定版本源码？
* 在哪里查看最新协议变更？
---
# 创建钱包、备份与恢复
提供不依赖具体钱包产品的安全操作流程。
Source: https://www.qools.org/zh/docs/learn2/wallet-usage/create-backup-recover
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将说明创建新身份前的环境检查、备份原则、恢复演练和常见错误；具体钱包按钮位置交给生态产品页介绍。
## 本页计划回答 [#本页计划回答]
* 创建钱包前应检查什么？
* 备份怎样才算可恢复？
* 何时应该先做小额恢复测试？
---
# Identity、Seed、Vault 与签名安全
理解身份、密钥材料、保管工具和签名授权之间的边界。
Source: https://www.qools.org/zh/docs/learn2/wallet-usage/identity-seed-vault-signing
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将建立安全模型：哪些信息可以公开，哪些信息必须离线保管，以及钱包签名究竟授权了什么。
## 本页计划回答 [#本页计划回答]
* Identity 与 Seed 分别是什么？
* Vault 解决的是哪类保管问题？
* 为什么任何页面都不应索要 Seed？
---
# Legacy 钱包与自救指南
把旧钱包迁移和故障恢复与当前标准流程分开。
Source: https://www.qools.org/zh/docs/learn2/wallet-usage/legacy-wallet-recovery
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将仅收录仍有实际需求的旧版钱包、Vault 或迁移场景，并清楚标注适用版本、风险和停止条件。
## 本页计划回答 [#本页计划回答]
* 哪些情况才需要使用 Legacy 指南？
* 如何确认旧工具仍与当前网络兼容？
* 遇到异常时何时应停止操作？
---
# 转账 QUBIC 与使用资产
解释发送、接收、核对和使用资产时的通用步骤。
Source: https://www.qools.org/zh/docs/learn2/wallet-usage/transfer-and-assets
本页是 Learn 2 信息架构预览，正文尚未进入事实核验和正式编写阶段。
## 概述 [#概述]
本页将提供跨钱包产品通用的转账检查清单，并说明 Identity、金额、资产标识、Tick 和确认结果应如何核对。
## 本页计划回答 [#本页计划回答]
* 转账前后分别要核对哪些信息？
* QUBIC 与其他资产的操作有何不同？
* 如何从 Explorer 验证结果？
---
# 法定人数
Qubic 系统的设计秉承了去中心化的核心原则。其独特的治理方式确保系统内的权力不会集中在单一实体身上。这是通过法定人数协议和仲裁员之间的权力分离来实现的。
Source: https://www.qools.org/zh/docs/learn/advanced/governance
## 什么是法定人数？ [#什么是法定人数]
在会议或集会上，至少需要多少成员在场才能进行正式事务的处理，这个最小数量被称为法定人数（Quorum）。通常情况下，组织召开会议所需的法定人数由该组织制定的规定或者章程定义。
在许多情况下，需要达到一定的参与度（即“过半数”或“法定人数”）才能做出决定或进行投票。如果没有达到这个标准，会议可能无法继续进行，或者所采取的任何行动都可能被认为是无效的。
例如，假设一个社团的规定是法定人数必须为全体成员中的多数，则只有当会议中有至少半数的成员参与，这个团体才能处理任何正式事务。
## Qubic 法定人数 [#qubic-法定人数]
在 Qubic 中，法定人数超越了简单的多数规则——它是一个动态的、包含了 451 个计算者表决的集合体。任何需要通过法定人数来决定的事情，都需要得到至少 451 张计算者投票的支持。这个集合体是 Qubic 系统决策过程中不可或缺的一部分。
计算者形成了一种民主的生态系统，每个都有平等的一票。目标是分散权力并促进系统利益的最佳健康竞争。这种独特的治理形式将计算者和仲裁者的角色分开，确保没有单一实体能够同时控制两者。
## 群体决策机制 [#群体决策机制]
Qubic 生态系统中的法定人数扮演着核心角色：
* 形成和创建刻度
* 发起、投票和接受投票
这个功能允许构建一个动态、社区导向和基于共识的生态系统，这是 Qubic 网络运行的关键。
## 对提案进行法定人数投票 [#对提案进行法定人数投票]
在表决过程中，一旦某个提案获得了不少于 451 个计算者的支持认可，它便被认为是有效的，并且将通过最多数者胜利的原则决定胜负。这样的机制确保了以大多数人的意见为导向的决策过程。
为了作出具有影响力的决策，我们需要得到广泛的认同，并激发计算者的积极参与。当有两个决策方案时，胜利的选择需要赢得超过半数的选票（或者是所有参与的计算者中的三分之一，如果只有三分之二的计算者在投票）。对于有多个选项的情况，则通过获得最多票数来决定胜利的提议——前提条件是至少已经有 451 个计算者投下了他们的选票。
---
# 提案
在 Qubic 社区中，决策并非由个人或某个中心化的群体制定，而是由整个社区通过民主透明的流程共同制定。其中，提案系统是这一流程的关键环节。社区的参与对于维护 Qubic 的去中心化特性至关重要，并确保其发展符合用户的需求和愿望，关键决策由法定人数集体做出。
Source: https://www.qools.org/zh/docs/learn/advanced/governance/proposals
## 什么是提案？ [#什么是提案]
提案是针对 Qubic 生态系统的变更、改进或新功能的建议。任何 Qubic 社区成员都可以提出提案。提案涵盖的主题范围广泛，从细微的调整和错误修复，到可能重新定义 Qubic 运作方式的重大变更。
### 提案类型有哪些？ [#提案类型有哪些]
Qubic 提案主要分为以下几类：
#### 计算者提案 [#计算者提案]
如果协议需要更改或者想要向 Qubic 添加新的智能合约，则需要计算者提案。
示例用例：
* 添加新的智能合约
* 扩展协议功能
#### 计算者捐赠提案 [#计算者捐赠提案]
该提案用于要求计算者提供每个纪元的收入相对应百分比的捐赠。
示例用例：
* 请求烧毁 $QUBIC
* 请求资助计算者控制基金 (CCF)
* 请求捐赠一个长期项目
#### CCF 资助提案 [#ccf-资助提案]
如果您有一个项目想法，并希望计算者控制基金 (CCF) 帮助您构建它，那么这里就是正确的地方。
示例用例：
* 核心开发需要资金来支付工资
* X 公司希望将 Qubic 集成到他们的钱包中
* 开发 Qubic 生态项目需要资金支持
#### 股东提案（此类提案尚未启用） [#股东提案此类提案尚未启用]
股东提案用于向智能合约的股东征求投票。
示例用例：
* 调整智能合约费用
* 更改智能合约收入地址
## 如何提出提案？ [#如何提出提案]
Qubic 社区中的任何人都可以提出提案。具体方法如下：
1. 确定主题： 您可能已经确定了需要解决的问题、改进的机会或可以使整个社区受益的新功能。
2. 起草提案： 详细描述您想要改变的地方。清晰地阐述问题或机会、您提出的解决方案以及它将给 Qubic 带来的好处。
3. 提交提案： 将您的提案发布到 Qubic 社区成员可以审阅的指定平台（一般是 GitHub）上。请务必查看所有格式指南或提交规则。
4. 社区审核： 社区成员可以审核、评论并提出关于您的提案的问题。请虚心接受反馈，并准备好在必要时进行修改。
## 如何审核提案？ [#如何审核提案]
提案提交后，社区将对其进行审核。审核内容包括：
* 评估提案中发现的问题或机会。
* 评估所提解决方案的可行性。
* 考虑潜在的好处和坏处。
* 向提议者提出问题并寻求答案。
我们鼓励社区成员积极参与审核过程，因为该决定将由集体做出。
## 如何对提案做出决定？ [#如何对提案做出决定]
1. 经过深入讨论后，该想法可以演变为正式提案。该提案整合了社区讨论中的所有反馈和修订意见。提案提供了详细的行动计划，明确说明了变更或新功能的具体内容以及如何实施。
2. 提案最终确定后，需要在链上发布提案，等待计算者进行投票，提案必须达到法定人数投票才能生效。
3. 如果提案在计算者投票中获得多数支持，则该提案将被接受并进入实施阶段。如果没有获得多数支持，则该提案将被修改以进一步考虑或被丢弃。
---
# 社区投票
Qubic 社区投票将用于孵化计划及 Discord 投票和其他临时解决方案，确保只有真正的 $QUBIC 持有者参与，在透明、公平和社区驱动的治理方面迈出了重要一步。
Source: https://www.qools.org/zh/docs/learn/advanced/governance/voting
## 什么是社区投票？ [#什么是社区投票]
Qubic 社区投票取代了 Discord 投票和其他临时解决方案，确保只有真正的 $QUBIC 持有者参与，并消除了 Discord 小号账户投票的可能。加权投票机制使每位参与者的影响力能够反映其持有的 $QUBIC 数量，包括基于资产的投票。
每个纪元都会重置投票。当前纪元结束时，活跃的投票将变为非活跃状态。每个纪元最多可创建 16 个新投票。
### 主要特点 [#主要特点]
* 投票加权：权重会随着钱包中的 $QUBIC 而扩大，支持基于资产的投票。
* 社区访问：向所有 $QUBIC 持有者开放。
* 孵化影响：对于孵化计划，社区现在拥有 60% 的投票权重（核心技术 15%，生态系统 15%，运营 10%）。
### 工作原理 [#工作原理]
* 投票不会转移资金或资产
* 每次投票需要烧毁 100 $QUBIC
* 创建投票需要烧毁 10,000,000 $QUBIC
* 投票权重=钱包当前余额（或允许资产的最大余额）
### 投票类型 [#投票类型]
* $QUBIC 投票 → $QUBIC 余额 = 投票权重
* 资产投票 → 资产余额 = 投票权重
### 投票余额要求 [#投票余额要求]
* 在整个投票期间，您必须保持您的余额高于最低金额。如果您的余额低于最低金额，您的投票权将被自动取消。
* 在整个投票期间，如果您的余额增加，您的投票权保持不变。