cess-primary-sources-2026-05-15

CESS primary sources

Reviewed: 2026-05-15 UTC

Core product framing

• https://cess.network/
  • Best concise official marketing page for the current positioning: a data infrastructure stack spanning storage, CD²N delivery, AI-oriented data flows, data sovereignty, and compliance language.
• https://doc.cess.network/
  • Best official docs entrypoint. Useful for navigating node roles, technical highlights, user storage flows, SDK surfaces, and whitepaper links.
• https://raw.githubusercontent.com/CESSProject/cess/main/README.md
  • Best short repo-level source for the Substrate implementation, node software, and the project’s own framing as a decentralized cloud-data storage network.

Role split and protocol layers

• https://doc.cess.network/cess-miners
  • Most important operational source in this pass. Explains the four node roles: consensus nodes, storage nodes, CDN nodes, and TEE nodes, plus retriever/cacher subdivision and TEE mode differences.
• https://doc.cess.network/readme/technical-highlight
  • Best concise source for the protocol-layer story: disaster recovery via PoDR², idle-capacity verification via PoIS, unified pricing, CD²N retrieval, and several roadmap-marked privacy/AI features.

Storage rights and user allocation model

• https://doc.cess.network/user/user-space
  • Best source for territory as the user-facing storage-right object. Shows that storage space is reframed as named, unique, transferable, expiring territory with expand/renew/order flows.

Storage mining and audit mechanics

• https://raw.githubusercontent.com/CESSProject/cess/main/docs/designs-of-storage-mining.md
  • Best source for the deeper proof/control-plane split. Shows separate submission and verification pools for idle versus service segments, scheduler-driven checks, and how proof timing affects miner power.

Canonical long-form reference

• https://doc.cess.network/readme/whitepaper
  • Docs entry that points to the latest official whitepaper PDF.
• https://raw.githubusercontent.com/CESSProject/Whitepaper/main/cess-whitepaper.pdf
  • Official whitepaper PDF saved locally for the corpus.

Main takeaways from this pass

• CESS is worth keeping separate from generic decentralized-storage buckets because it combines audited capacity, trusted-hardware-assisted verification, CDN-style retrieval roles, and onchain/user-visible storage rights in one bundled system.
• The key control-plane split is between R²S consensus nodes, PoIS/PoDR²-audited storage nodes, SGX-backed TEE workers/verifiers, and retriever/cacher delivery roles in CD²N.
• Territory is one of the strongest reasons to keep CESS explicit in the corpus: storage is presented as a named, expiring, transferable right rather than only as invisible account quota or one-off provider contracts.
• The storage-mining design docs matter because they show that proof submission/verification scheduling and idle-versus-service segment handling are central to miner economics and not just implementation details.
• The TEE requirement matters analytically because CESS’s trust story is not purely blockchain-plus-cryptography; it explicitly depends on enclave-backed data tagging and challenge verification.
• The site’s broader AI/privacy claims should be handled carefully. Several features, including IPFS compatibility, proxy re-encryption access control, and MDRC ownership traceability, are marked in the docs as planned launches rather than current baseline behavior.
• Good comparison targets after this pass: Filecoin, Swarm, Storj, Akave, CD²N-style bandwidth layers, trusted-hardware storage systems, and any protocol where user storage rights become transferable onchain objects.