Copyright Verification System

I. Core Principle: The Self-Verifying Hash Chain

After each chapter is written, the system automatically computes its cryptographic hash fingerprint。 This fingerprint is not arbitrarily generated — it strictly follows a chain structure: each chapter's hash is derived from Chapter Content + the previous chapter's hash + a precise timestamp + an author identity marker — these four elements, processed through SHA-256 -256 algorithm. This means the hash value cryptographically binds "who — when — wrote what" into an inseparable unity.

Author Identity Binding

Each chapter's hash embeds the author's registered email（ (verified), cryptographically binding the creator's identity to the content. Email is a globally unique external identity marker—— — Chinese email providers (QQ/163 , 163, etc.) all require real-name registration. Account real-name information can be retrieved from email providers, forming a complete evidentiary chain from "Real-Name Identity → Email → Hash Chain → Creative Content".

Even if two authors wrote identical content (extremely unlikely), the hashes would be completely different due to different email addresses. AuthorChanging the bound email does not affect verification of historical chapters — each chapter independently records the email address at the time of hash creation, permanently preserving the historical evidence.

Mathematical Guarantee Against Tampering

SHA-256 is an internationally recognized cryptographic hash algorithm with preimage resistance and collision resistance—— — meaning it's impossible to reverse-engineer the original text from its hash, or find two different inputs that produce the same hash. This guarantees:

• One-way irreversibility: The chapter content cannot be reverse-engineered from its hash value.
• Uniqueness: Any change to content or author — even a single character — produces a completely different hash value.
• Chain locking: Modifying any single chapter breaks the hashes of that chapter and all subsequent chapters. Since every chapter's timestamp and author identity are fixed, the entire chain cannot be rebuilt without detection.

II. Merkle Tree: Work-Level Fingerprint Aggregation

All chapter hashes of a work are organized into a Merkle tree，. Through pairwise hashing layer by layer, they produce a unique 64-character hex value — the Work Merkle Root。 This Root is the single cryptographic fingerprint ，of the entire work. Anchoring this single value provides temporal proof for all chapters of the work.

Similarly, every day, the Merkle Roots of all updated works on the platform are built into a new Merkle tree, producing the daily Platform MetaRoot。 . A single anchor covers the copyright status of all works across the entire platform for that day, enabling efficient large-scale copyright protection.

III. The Four-Layer Evidence System

IV. Defense in Depth: Why This System Cannot Be Breached

Server-Side Tampering?

Even if the platform server is fully compromised, an attacker cannot tamper with historical data without being detected:

• Daily emails already sent to the author's inbox and the email provider's servers contain the Merkle Root at that time — this is external evidence independent of this platform
• Records on timestamp services and blockchains are one-way and irreversible — they cannot be revoked or modified
• Any tampering will cause the hash chain to break, and the break point can be precisely located.

Preemptive Forgery?

To preemptively generate chapters in bulk and forge a timeline, an attacker would need to:

• Predict all future content — impossible in a real creative scenario.
• Forge the email provider's send time — email providers are independent third parties outside the attack surface.
• Forge blockchain or timestamp records — would require breaking cryptographic guarantees, computationally infeasible.

Collusion?

Even if the platform colludes with a participant, multiple layers of the four-layer evidence system remain independent of the platform: Email providers, timestamp authorities, and blockchain networks are all independent third parties， that do not rely on platform trust. Evidence preserved in any single layer is sufficient to prove rights ownership.

V. Independent Verification

Online Verification

On the novel reading page, click the "Verify Chain" button. The system will recalculate hashes chapter by chapter, compare them to stored values, and report chain integrity in real time.

Evidence Package Download & Offline Verification: On the novel page, click "Download Evidence" to download a JSON evidence package, then visit the /verify verification page. Import the evidence package and paste the chapter text to independently recompute the hash chain in your browser using the Web Crypto API — all computations run locally, independent of our servers. Third parties (including forensic institutions) can verify independently.。 All computations are performed locally, independent of our platform servers. Third parties (including forensic institutions) can verify independently.

Offline Independent Verification

All hash calculations are based on the open international standard SHA-256 algorithm. ，No proprietary technology is involved. Any third party (including forensic institutions and copyright arbitration bodies) can:

1. Obtain the evidence package (JSON format, including the hash list, timestamps, and all data) via the "Download Evidence" button on the novel page.
2. Use any programming language or standard tool to compute hashes chapter by chapter following the public formula.
3. Compare the computed results to determine whether the chain is intact.

Forensic Pathway

In a copyright dispute, the following evidence can be sequentially obtained to form a closed loop:

1. Server Data: Complete hash chain and Merkle Tree records.
2. Email Records: Proof of sending time and content issued by the email provider.
3. Timestamp Certificate: Trusted timestamp certification issued by an authorized timestamp authority.
4. Blockchain Records: Publicly queryable blockchain transactions and block heights.

These four types of evidence independently prove the same fact from different dimensions — that specific content definitely existed at a specific point in time， — forming a complete evidentiary chain loop.

VI. Frequently Asked Questions

VII. Disclaimer

This copyright verification system is designed to provide creators with technical-level auxiliary proof of temporal existence，, assisting creators in presenting digital evidence in copyright disputes. However, this service does not constitute legal advice or legal guarantee，. Creators should be aware of the following:

1. No Guarantee of Judicial Admissibility: While hash chains, email timestamps, and other technical means possess cryptographic probative value and comply with the principles of the Electronic Signature Law and Supreme People's Court Provisions on Internet Court Cases, the evidentiary effect in any specific case is ultimately determined independently by the judicial authority in accordance with the law，. This platform makes no guarantee regarding the outcome of any specific case.
2. Does Not Replace Copyright Registration: This verification system is a supplementary technical measure，. It does not replace voluntary registration with the National Copyright Administration. For significant commercial interests, official copyright registration is recommended for the most comprehensive legal protection.
3. Scope of Free Services: Currently, only Layer 1 (Chain-Based Evidence) and Layer 2 (Email Timestamp) services are provided. Layer 3 (Judicial Time Anchoring) and Layer 4 (Blockchain Notarization) are paid feature，paid features, not yet live. Notification will be provided when they go live.
4. Service Continuity: The platform will make every effort to ensure the stable operation of the verification system, but assumes no responsibility for evidence loss due to force majeure or third-party service interruptions (such as email provider outages or timestamp authority service anomalies).
5. Email Verification Responsibility: Author identity binding depends on the verification status of the registered email. Please ensure you use a genuine and valid email address for registration and complete email verification promptly. The platform assumes no responsibility for identity disputes arising from unverified emails or the use of another person's email.
6. Technical Limitations: SHA-256 The SHA-256 hash algorithm is currently considered secure, but cryptographic technology continues to evolve. The platform will monitor technological developments and upgrade the hash algorithm when necessary, but assumes no responsibility for future cryptographic breakthroughs.