Whitepaper v1.2 · Foundational Concept
All Streams Converge, Consensus Builds Together
The Guixu Consensus Network is not merely a DApp or a tool, but a resource value network — its core mission is to aggregate the physical resources and traffic resources scattered across users' idle devices and idle attention, connect them to real commercial demand, and form a sustainable commercial loop.
Physical Resources: Users' idle devices (PCs, phones, routers, edge nodes, etc.) are inherently capable of computing, storing and transmitting. Within the Guixu network these capabilities are scheduled as compute nodes, storage nodes, bandwidth nodes and edge-computing nodes. The value of physical resources has no ceiling — the more devices, and the more idle they are, the larger the physical foundation the platform can mobilize.
Traffic Resources: Users' attention, visit behavior, social relations and content-consumption paths are all traffic. Through the terminal entry (node.guixu.club), desktop and mobile, Guixu builds multi-touch reach and turns users' active behavior into a measurable traffic pool. The value of traffic resources likewise has no ceiling — the larger the user base, the stronger the stickiness and the richer the content ecosystem, the greater the commercial pricing room of the traffic pool.
The token is not the goal, but the carrier of value consensus. Guixu operates in three phases:
The key to this loop is sustainability — physical resources do not shrink through consumption (on the contrary, the more they are used, the more mature the devices and the larger the network); traffic resources do not dry up through monetization (users' commercial behavior can feed back to users, generating more contribution). The token acts as lubricant, ensuring value flows fairly among contributors, platform and demand side.
Idle resources aggregated by the Guixu Consensus Network are not merely bookkept internally. Through standardized interfaces they connect directly to real-world demand-side platforms, forming a complete commercial loop: contribute → aggregate → match → monetize → reinvest. This is Guixu's core survival capability and what distinguishes it from purely conceptual networks — its resources always have real buyers.
| Resource Type | Demand-Side Platforms | Monetization Path |
|---|---|---|
| Disk storage | Professional storage providers, distributed cloud storage & backup/archive services | Enterprise backup, cold-data archiving, object storage capacity leasing |
| Bandwidth | CDN providers, edge computing networks, mining resource operators | Traffic distribution, node acceleration, bandwidth leasing (including mining-related use) |
| Terminal compute | AI training & inference providers, rendering and scientific computing platforms | GPU / CPU compute leasing, model inference hosting |
| Traffic & network effects | Token holders, ecosystem applications, secondary markets | Accumulated traffic itself generates token economic value |
Beyond direct monetization of the three physical resource classes, the growth of the network itself constitutes independent commercial value. As connected terminals and active addresses keep increasing, the traffic, user attention and transaction activity accumulated by the platform can themselves form token economic value: the transaction tax continuously feeds the Operations Reserve Fund, rising network activity drives token demand, and ultimately a positive three-way loop emerges among resource contributors, demand-side buyers and token holders.
The value of the Guixu Consensus Network is not single-dimensional. It is a complete system that starts from idle user resources, takes the token as the cornerstone of consensus, resource aggregation as the means, and the commercial loop as the goal.
The endgame of business is not extraction, but a continuing cycle of mutual benefit. What Guixu wants to do is to let every contribution, every visit and every transaction find its place in this cycle.
In 2026, compute power remains concentrated in mining farms, and nodes still operate silently within server clusters. The idle computers, mobile phones, bandwidth caps, and storage of ordinary people have never been integrated into blockchain's consensus networks. The centralization of compute and network makes the rhetoric of decentralization seem hollow in reality.
The Guixu Consensus Network is born from a simple belief: true decentralization should not require anyone to sacrifice their own devices. Idle resources in everyone's hands are, in themselves, the consensus power that blockchain most desperately needs.
Guixu is a concept from ancient Chinese mythology, first appearing in "Liezi · Tang Wen" (The Questions of Tang). It refers to the bottomless abyss where all ocean currents converge, where every river eventually flows into, yet its volume never increases.
English Definition: Guixu (The Great Abyss) / Oceanic Abyss / The Great Sinkhole
Symbolism: The oceanic abyss's theme of "all things converging to one" and "never depleting" symbolizes terminal devices from across the world pooling together to form a unified consensus network. Resources are continuously utilized and perpetuate. Just as rivers and streams all eventually reach the sea, every person with idle devices is a participant in building a decentralized world.
To build a blockchain consensus system truly based on distributed terminal resources, allowing every person with idle devices to participate equally in the construction of a blockchain network and earn returns. Zero threshold, no private sale, no public sale, fully decentralized.
The system records contribution scores separately based on the type of resources contributed by the terminal device. Each resource type has a different contribution coefficient:
| Resource Type | Contribution Description | Collection Method |
|---|---|---|
| Network Bandwidth | Utilize idle bandwidth for node-to-node communication, data synchronization, and network forwarding | Bandwidth metering + connectivity detection |
| Storage Space | Provide distributed storage nodes for the network, storing blockchain data and application data | Disk usage + availability detection |
| Compute Power | Idle CPU/GPU power participates in consensus computation, data verification, and smart contract execution | CPU cycle detection + GPU usage monitoring |
| Stability | Device uptime, continuous running duration, network fluctuation tolerance | Heartbeat detection + uptime logging |
| Geographic Location | Multiple terminals distributed in different geographic regions enhance network resistance to single-point failures | IP geolocation tagging |
| Terminal Type | PC Client | Mobile | Primary Contribution |
|---|---|---|---|
| Home Computer | ✅ Primary | — | Storage + Bandwidth + Compute |
| Mobile Phone | — | ✅ Lightweight | Bandwidth + Light Storage + Mobile Node |
| Server / NAS | ✅ Heavy | — | High Bandwidth + Large Storage + High Compute |
| Mobile Devices (In-car / Wearables) | — | ✅ Lightweight | Mobile Bandwidth + Location Contribution |
The Guixu Consensus Network token (hereinafter referred to as the "Guixu Token") is the sole credential for community members to participate in consensus network construction and earn contribution rewards. This token continuously provides funding for the operations reserve fund through the contract's built-in "transaction tax" mechanism.
| Item | Rule |
|---|---|
| Total Supply | Minted on demand, no fixed upper limit, issuance speed determined dynamically by contribution scores |
| Issuance Method | No private sale, no public sale, all minted automatically through terminal resource contribution |
| Distribution Mechanism | Allocated proportionally by terminal resource contribution score: more contribution equals more rewards |
| Minting Trigger Condition | Automatic minting and allocation when terminal contribution reaches a certain threshold |
| Minting Cooldown | Each mint separated by 1-hour interval to prevent frequent small minting |
Contribution Score = Σ(Resource Type × Contribution Coefficient × Contribution Duration × Stability Weight × Anti-Exploit Coefficient)
Not all connected terminals can produce effective resource contribution. To ensure overall network quality and meet commercial demand standards, the system sets the following minimum thresholds for an "Effective Resource Contributor":
| Dimension | Minimum Requirement | Note |
|---|---|---|
| Hardware | PC ≥ 4-core CPU + 8GB RAM + 50GB free storage; Phone ≥ 4GB RAM + 20GB free storage | Terminals below this threshold have their contribution capped |
| Bandwidth | Downlink ≥ 50Mbps, Uplink ≥ 20Mbps (continuous 7 days) | Coefficient = Uplink / 100Mbps, capped at 1.5 |
| Stability | Uptime ≥ 90% within 7 days | Non-compliance zeroes that day's contribution |
| Value Score | 7-day cumulative contribution ≥ 100 | Tiered: PC ≥ 200, Phone ≥ 100, Server/NAS ≥ 500 |
To prevent automated scripts, AI agents, and malicious users from mass-producing fake terminals for exploiting the system, the network integrates a multi-layer defense mechanism:
| Defense Strategy | Implementation | Purpose |
|---|---|---|
| Device Fingerprint | Terminal unique identifier (device ID + network environment fingerprint). Repeated contribution from the same device does not stack. | Prevent single-device multi-account |
| Contribution Decay Curve | New devices start at contribution coefficient 1.0, gradually increasing to 1.5 after 30 days of continuous online presence. Prevents short-term farming. | Prevent short-term mass farming |
| Behavioral Analysis | Abnormal activity detection: non-human-regular operation frequency, anomalous contribution curves, automated script pattern recognition. | Detect automated scripts |
| Resource Authenticity Verification | Bandwidth usage matched against device capability. Abnormally high contribution scores trigger manual review. | Prevent capability mismatch |
| Geolocation Validation | Multiple terminal registrations under the same IP range trigger rate limiting. Frequent IP changes trigger warnings. | Prevent distributed fake nodes |
| Community Reporting Mechanism | Users can report anomalous contributors; confirmed via community vote, with contribution scores deducted. | Community Co-Governance |
The system adopts a three-tier architecture of "decentralized nodes + on-chain ledger + off-chain verification" to ensure system security and scalability.
| Layer | Function | Technology |
|---|---|---|
| Terminal Layer | Terminal resource contribution, data collection, local verification | PC Client / Mobile App / Browser Extension |
| Consensus Layer | Contribution score calculation, node weight assessment, token minting | Distributed consensus algorithm (resource-contribution-weighted PoR) |
| On-Chain Ledger | Contribution record storage, token distribution, tax collection, on-chain governance | Smart Contract + On-Chain Ledger |
| Application Layer | Contribution dashboard, token wallet, community voting, operations reserve query | Web Frontend + Mobile App |
Traditional PoW consumes massive electricity; PoS depends on locked capital. The Guixu Consensus Network adopts the PoR (Proof of Resource) consensus mechanism: it replaces capital staking and hashrate competition with resource contribution, establishing an independent path distinct from PoW and PoS; the technical implementation draws on PoS's stake-weighting approach, but the weight derives from resource contribution rather than token staking.
The system operates on fully decentralized governance. All major decisions are determined by Guixu token holder voting:
| Access Method | Platform | Function |
|---|---|---|
| PC Client | Windows / macOS / Linux | Full resource contribution, high bandwidth utilization, large storage node |
| Mobile App | iOS / Android | Lightweight resource contribution, mobile bandwidth, location contribution |
| Browser Extension | Chrome / Firefox / Edge | Browser-internal resource contribution, web acceleration node |
| API Interface | Developer Platform | Third-party device access, enterprise-level node support |
| Risk Type | Risk Description | Mitigation Strategy |
|---|---|---|
| Device Fragmentation | Significant performance differences between terminal devices make unified contribution scoring difficult | Contribution coefficient weighting model with dynamic weights based on device capability |
| Cybersecurity | Terminal device security cannot be fully guaranteed | Periodic security audits, endpoint protection, abnormal activity monitoring |
| Legal Compliance | Divergent legal regulations on blockchain tokens across countries | Regional compliance operations, localized legal advisor teams |
| Technology Maturity | PoR consensus algorithm requires real-world validation | Phased testing, academic collaboration, public whitepaper |
| Community Growth | Requires a sufficiently large number of terminal users to form an effective network | Early incentives, community promotion, partner programs |
The Guixu Consensus Network is not a concept about the future, but a reflection on reality: in the digital age, everyone's idle resources represent a form of wasted wealth. When these resources pool together, they are sufficient to support a decentralized blockchain network.
We believe that true decentralization is not a slogan, but practice. No expensive mining rigs, no massive capital thresholds, just your idle devices, your idle bandwidth, and your idle storage. These resources are your chips, your contribution, your vote for a decentralized world.
Guixu Consensus Network — All Streams Converge, Consensus Builds Together.
The Guixu Consensus Network relies not only on the aggregation of physical resources, but also on precise definitions of "people" and "behavior." The following three role definitions are the core prerequisites for the sustainable operation of the network's commercial loop.
Guixu reaches users through multiple touchpoints — the terminal entrance (node.guixu.club), desktop, and mobile — transforming user activity into a measurable traffic pool. However, traffic resources must exclude bots and automated farming; otherwise the commercial monetization end (advertising / promotion / distribution) loses its pricing power.
An access event counts as effective traffic only if it simultaneously meets all of the following conditions:
| Dimension | Standard | Implementation |
|---|---|---|
| Identity Uniqueness | One wallet address per natural person, bound to a device fingerprint | Wallet signature + device fingerprint hash (IP + User-Agent + screen resolution + Canvas fingerprint); new wallets on different devices require behavioral verification |
| Non-Automated | Behavior has randomness, dwell time and interaction; no fixed script pattern | Behavior analysis engine: records mouse trajectory, scroll speed, key intervals; deviations from human distributions (e.g. constant-speed scrolling, fixed-interval clicks) trigger automatic downweighting |
| Effective Dwell | Single-session dwell ≥ 15 seconds with at least 1 meaningful interaction (click, form input, route jump) | Frontend tracking + backend aggregation; the 15s threshold is adjustable via community governance |
| Source Quality | Excludes search engine crawlers, CDN preload requests and known proxy-pool IPs | Bot detection + proxy IP blacklist + reverse DNS verification |
The system records contribution scores separately according to the resource types a terminal actually contributes. However, not every connected terminal produces effective resource contribution. To ensure overall network quality and meet commercial demand-side purchasing standards, a terminal must simultaneously satisfy the following four criteria within a 7-day evaluation cycle to be defined as an "Effective Resource Contributor":
| Dimension | Minimum Requirement | Note |
|---|---|---|
| Hardware | PC ≥ 4-core CPU + 8GB RAM + 50GB free storage; Phone ≥ 4GB RAM + 20GB free storage; Router/Gateway ≥ 256MB RAM | Terminals below this threshold have their contribution capped and are not counted as effective contributors |
| Bandwidth | Downlink ≥ 50Mbps, Uplink ≥ 20Mbps (at least 7 consecutive days) | Coefficient = Uplink / 100Mbps, capped at 1.5 |
| Stability | Uptime ≥ 90% within 7 days (≥ 18 hours online per day) | Non-compliance zeroes that day's contribution |
| Value Score | 7-day cumulative contribution ≥ 100 | Tiered: PC ≥ 200, Phone ≥ 100, Server/NAS ≥ 500 |
The Guixu Consensus Network has no private placement and no public offering, yet it requires market promotion. A team lead must not operate as a "recruit-heads-and-take-commission" pyramid scheme, nor "sit back and earn" in a way that undermines PoR consensus decentralization. Promotion incentives are realized through "contribution-value bonuses + team activity rewards," not "direct token dividends."
A role that simultaneously satisfies the following criteria is defined as an effective team lead:
| Dimension | Criterion | Note |
|---|---|---|
| Recruitment Scale | Directly invited ≥ 10 effective resource contributors (Lv1 or above) to join the Guixu Network | Only effective contributors count; invalid traffic / zero-contribution registrations excluded |
| Team Quality | ≥ 30% of team members are Lv2 Premium Contributors | Prevents padding with low-spec devices |
| Personal Participation | The team lead must also be an effective resource contributor (Lv1 or above) | Avoids pure recruitment models |
| Continuous Activity | Team average daily active terminals ≥ 15 over the past 30 days | Prevents dissolution after one-off recruitment |
Incentive Structure (three tiers, progressively unlocked):
Key Anti-Fraud Mechanisms:
| Risk | Prevention |
|---|---|
| Team lead mass-creates fake contributors via scripts | Team members must meet the "Effective Traffic User" definition (behavior analysis engine); script accounts' contribution values are zeroed |
| Team lead pads with low-spec devices | Lv2/Lv3 bonuses apply only to genuine effective contributors; low-spec device contribution values are capped |
| Team dissolves but rewards continue | Continuous-activity check: 30 days of inactivity suspends reward eligibility; reactivation requires a 7-day re-evaluation |
| Team lead self-recruits for self-reward | Team members must complete KYC / device binding; the same natural person cannot be both team lead and team member |
Core Logic Behind the Three Roles:
| Term | Definition |
|---|---|
| Guixu | Ancient Chinese mythological concept referring to the bottomless abyss where all ocean currents converge, symbolizing all things converging to one |
| The Great Abyss | English definition of Guixu, referring to the deepest trench in the ocean |
| PoR | Proof of Resource, resource-proof consensus mechanism |
| Contribution Score | Quantified indicator of terminal resource contribution, determines token distribution ratio |
| Operations Reserve Fund | System operations fund pool formed by the transaction tax |
| Token | Guixu Consensus Network token, on-chain value exchange credential |
| Node | Terminal device participating in the Guixu Consensus Network |