Skip to main content

Common Misconceptions

3 minFAQ
// 1 of 1 · hard questions

Twelve common misconceptions. Twelve precise corrections.

// 15.3 · use this when correcting external prose · the reverse direction is what the document exists to prevent

Use this table whenever describing ParalleliX in external prose.

A short reference for the corrections that come up most often in external conversations about ParalleliX. Each entry pairs the misconception with the precise correction and the canonical source. Use this when correcting external prose. The reverse direction (using the misconception column as shorthand in the project's own writing) is exactly what the document exists to prevent.

Topic index

// four clusters · jump to any misconception

Twelve corrections

// misconception · correction · canonical source

// MISCONCEPTION 1→ §I First Principles

ParalleliX is a decentralised cloud provider.

// CORRECTION

A decentralised parallel-compute network. The live unit of work is the ParalleliX AI inference request, served whole by one node. Sub-task segmentation is the general parallelizable-workload path served through the planned marketplace.

// MISCONCEPTION 2→ §8.5 Staking (no slashing)

Holding $PRLX earns staking yield.

// CORRECTION

Holding does not stake. Only registered node operators stake; rewards are payment for node uptime, not yield. There is no slashing: principal is always returned in full on unstake.

// MISCONCEPTION 3→ §V.1 Proof-of-Execution

Proof-of-Execution is a zero-knowledge proof.

// CORRECTION

It is a SHA-256 hash commitment. Real ZK is a research direction.

// MISCONCEPTION 4→ §XV Hard Questions

The network is fully decentralised at launch.

// CORRECTION

The network ships with a centralised coordinator; decentralised validator quorums are a planned later addition.

// MISCONCEPTION 5→ §VIII.9 What $PRLX is NOT

$PRLX has governance / voting / DAO.

// CORRECTION

It does not, and adding governance later requires a versioned token-spec change with public notice.

// MISCONCEPTION 6→ §VIII.4 Operator Funding Model

Operators are paid from the transfer tax.

// CORRECTION

The tax funds Development, Operations, and Marketing. Operators are paid from the 25% Operator Rewards bucket at launch and from a share of ParalleliX AI usage payments in steady state.

// MISCONCEPTION 7→ §VIII.8 Contract Ownership

Renouncing ownership would make the contract trustless.

// CORRECTION

It would freeze the FoT classification allowlist, which would break new DEX listings and the NodeRegistryLocker / AI-credit-deposit exemptions. The renouncement criteria are pre-committed (§8.8).

// MISCONCEPTION 8→ §VIII.1 Identity

ParalleliX competes with Ethereum / is its own L1.

// CORRECTION

$PRLX is an ERC-20 on Ethereum. ParalleliX uses Ethereum as the settlement chain; the compute network is off-chain.

// MISCONCEPTION 9→ §XV Hard Questions

Quantum, real ZK, and federated learning are live or imminent.

// CORRECTION

They are research directions, not yet built, and the document calls them so wherever they appear.

// MISCONCEPTION 10→ §8.5 Staking (no slashing)

Staking $PRLX is a way to passively earn.

// CORRECTION

Staking alone earns nothing. Rewards are pay-for-uptime: you must run a real online node, and the stake only sets the reward weight and the sybil cost. Holding or staking without a live node earns zero.

// MISCONCEPTION 11→ §VI.1 Dynamic Node Integration

Anyone can become a node operator right now.

// CORRECTION

True: registration is permissionless and on-chain from launch (registerNode, 50,000 $PRLX minimum stake). There is no allowlist and no curation.

// MISCONCEPTION 12→ §IX Workloads and Roadmap

The network can serve any workload.

// CORRECTION

It targets five workload classes: AI, scientific compute, big-data analytics, blockchain compute, media rendering. Workloads outside these classes may not segment cleanly into sub-tasks.

How to use this table

// when external content gets one of these wrong

// SPOT

Spot a misconception in external prose, social posts, or a partner deck.

// CORRECT

Reply with the matching correction. Link to the canonical source. Do not paraphrase if precision matters.

// PRESERVE

Project-side prose should never use the misconception column as shorthand. The document exists to prevent that direction.