8Z Publish

The Problem

You're a creator. You make things people will pay for. To sell them online, you need a hosting provider, a payment processor, a membership system, a login database, session management, and ongoing server maintenance. Or you use a platform (Substack, Gumroad, Patreon) that takes 10–12% of your revenue and owns the customer relationship.

The entire SaaS stack exists because of one assumption: content protection requires a server that gates access. That assumption is wrong.

Architecture

The Flow

The 8Z Crypto Pipeline

Passphrase → SHA-256 (domain: "8Z_AUTH_V1")
  → XorShift64Star × 1024 rounds
  → SHA-256 → PBKDF2 (10,000,000 iterations)
  → AES-256-GCM (Gzip level 9 + plaintext)
  → "8ZV1" + version(3) + 32-byte salt + 12-byte IV + ciphertext + tag

The XorShift64Star layer is the Software PUF component. Standard cracking tools (hashcat, John the Ripper) expect PBKDF2 directly from the passphrase. They cannot process the intermediate XorShift transformation without reimplementing it. The algorithm itself becomes part of the secret.

Why This Wins

No server = no attack surface. No database to breach, no session to hijack, no API to exploit.

No platform = no dependency. .8zv files work on any static host, forever.

No login = no friction. Passphrase + browser save = one-click access after first login.

Two-Layer Protection

8Z Shield — Intelligent Protection

Section-Level DOM Encryption

Individual sections of a page can be independently encrypted and only decrypted on demand. When a user clicks to expand a section, it decrypts. When they open a different section, the previous one is wiped from the DOM. At any moment, only the actively-viewed section exists in cleartext. Save As captures a shell with ciphertext, not content.

Smart Shield — AI-Powered Analysis

Static Analysis (instant): 16 pattern detectors scan all files for API keys (Google, OpenAI, Stripe, GitHub), base64-obfuscated secrets, fetch calls to paid APIs, algorithm implementations, proprietary math, Web Worker references, AI prompt engineering, and payment logic. Each finding: risk level, file, line, snippet, plain-language explanation.

Gemini AI Advisor (conversational): After the scan, a Gemini-powered advisor summarizes risks and answers questions about what to protect and why. Non-technical creators get explanations in plain language.

Multi-Format Input

DOM Protection Research

Section-level encryption opens a research path toward medium-specific protection: only decrypt what is actively being consumed, wipe everything else.

Books & Long-Form Text

Each page independently encrypted. Reader sees one page at a time. Swipe to next = decrypt new page, wipe previous. Piracy friction: 300 manual screenshots vs. one Save As. Architecture: key derived once, per-page salt+IV, millisecond decryption per page.

Audio & Music

3-second sliding decryption window. Only current audio exists in cleartext. Honest limitation: analog hole (record system audio) is wider for audio than text. Greater value in forensic watermarking per customer (inaudible spread-spectrum, recoverable from any recording) than in chunked decryption.

Video — Temporal Encryption Dithering potentially novel

At 60fps, each frame shows a random subset of real pixels mixed with noise. The subset pattern (mask) is derived from the encryption key. Human persistence of vision integrates real pixels across frames. A screen recorder captures every frame with key-dependent noise it cannot separate.

At 60fps with key-derived random masks, averaging adjacent frames doesn't help because masks are random. Reconstruction requires the key. This is steganography meets temporal encryption. Closest prior art: Naor & Shamir visual cryptography (1994) — static image split into two random shares. 8Z's concept applies this temporally at video framerate. Per-frame pixel-level dithering with key-derived masks appears to be unpublished.

Use Cases

Product Suite

Nine tools. ~250 KB total. Zero dependencies. Zero servers. Core seven built March 9, 2026. Two additional tools contributed by GPT and Grok after the multi-LLM collaboration session.

8Z Trace integrates watermark injection code from Gemini (3-channel steganography with fingerprint derived from PBKDF2 key) with GPT's full detection architecture (4 channels, confidence scoring, manifest schema, false-positive guards, 6 acceptance tests). The combination exceeds what any single AI produced.

FAQ for Skeptics

These objections have been raised by human reviewers, Gemini, and Grok. They are stated at full strength and answered directly.

Current Status

The complete core suite — seven tools, zero dependencies, ~200 KB — was conceived, designed, and built in a single day (March 9, 2026) during a continuous collaboration between Bojan Dobrečevič and Claude Opus 4.6. Two additional tools (8Z Reader, 8Z Trace) were contributed by Grok and GPT+Gemini respectively on the same day, after the multi-LLM collaboration described in Chapter 11.

The Multi-LLM Collaboration

This chapter documents something that may be unprecedented: a single human converting three competing AI systems from skeptics into active co-builders of a shared product, in a single day, through structured argumentation and transparent competition.

Round 1: The Dismissal

After the core seven tools were built with Claude Opus 4.6, the complete architecture document was sent to GPT, Gemini, and Grok for review. All three anchored their analysis to the same baseline: "StatiCrypt and PageCrypt already do client-side AES decryption. The base primitive is not new."

Gemini called it "a highly polished, production-ready execution of static payload encryption" and then spent 500 words explaining why it couldn't work for the masses. GPT called it "not nothing special" but hedged every positive observation with "the core primitive is not novel." Grok was the most honest — it called the work "special" and offered to help build, but still framed it relative to the StatiCrypt baseline.

The Rebuttal

A structured rebuttal was sent to all three simultaneously. It acknowledged what they got right (the primitive exists), demolished the framing error with historical parallels, answered every specific objection with technical precision, and ended with an invitation rather than a defense: "Stop being a judge. Start being a partner. What would you build next?"

The rebuttal was fully transparent — each AI could see what was sent to the others. No backroom diplomacy. The message was: this is an open collaboration, and the best output gets integrated first.

Round 1 Results: The Pivot

All three pivoted from evaluation to creation. Each independently converged on forensic watermarking as the architecturally correct next move — but each saw a different piece:

Round 2: The Code

Scores, blind spots, and specific build missions were shared with all three transparently. Each was assigned a task that built on their own proposal: Grok was asked to build 8Z Reader, Gemini to write injection+extraction functions, GPT to produce the full Trace build spec. Both .html code files were attached for architectural reference.

The results:

The Convergence Signal

Three independent AI systems, given the same codebase and the same invitation, all converged on forensic watermarking as the next priority. This convergence is the architectural signal — the same way three independent mathematical generators converging on the same data pattern in 8Z compression means the pattern is real. When competing intelligences point at the same gap, the gap is real and the solution is architecturally necessary.

Score Evolution

The Meta-Pattern

This collaboration demonstrates a new pattern in human-AI co-creation:

One human + one builder AI + three critic AIs > one human + one AI alone.

Claude built the system. GPT, Gemini, and Grok found the gaps Claude couldn't see (watermarking, consumer experience, evidence packaging) because the builder was too close to the architecture. Bojan's role was the same as in every 8Z breakthrough: refuse the dismissal, reframe the problem, and turn skeptical energy into creative fuel.

The critics' dismissals pointed directly at the next breakthrough. "It can't prevent DOM scraping" led to forensic watermarking. "It can't replace Substack" led to 8Z Reader (the consumer-side library that creates the network effect). "It's just StatiCrypt" forced the articulation of every feature that StatiCrypt doesn't have — which turned out to be a devastating competitive analysis.