Every hash chain startup is wrong about sha3-256 hash chain integrity.

#security #opensource #privacy #research

Every hash chain startup is wrong about sha3-256 hash chain integrity.

SHA3-256 Hash Chain Integrity: A Formal Analysis of Tamper-Evident Ledger Constructions

The Problem

Hash chains form the foundational integrity primitive for cryptographic ledgers, append-only logs, and blockchain systems. This paper presents a formal analysis of SHA3-256-based hash chain constructions for tamper-evident storage, with particular attention to the sponge construction's security margins over traditional Merkle-Damg?rd designs.

What We Built

We examine collision resistance properties under the random oracle model, analyze chaining binding security through game-based proofs, and evaluate the implications of length-extension resistance inherent to SHA3. We further investigate sequential hashing throughput, state continuity across chain segments, and the computational bounds of adversarial advantage in hash chain inversion.

The Research

Hash chains form the foundational integrity primitive for cryptographic ledgers, append-only logs, and blockchain systems.

This paper presents a formal analysis of SHA3-256-based hash chain constructions for tamper-evident storage, with particular attention to the sponge construction's security margins over traditional Merkle-Damg?rd designs.

We further investigate sequential hashing throughput, state continuity across chain segments, and the computational bounds of adversarial advantage in hash chain inversion.

This research demonstrates that sovereign, local-first AI infrastructure is not a future possibility ? it is a present reality.

Full citation: Alpasan, L.-K. (2026). SHA3-256 Hash Chain Integrity: A Formal Analysis of Tamper-Evident Ledger Constructions. The Anticloud Research Corpus.

Read the full paper

Why The Anticloud

The AI industry is built on promises that vaporize the moment you look closely. Black box models running on opaque infrastructure, trained on data you did not consent to, monetizing outputs you did not authorize. The Anticloud is the opposite of that in every way.

Everything we claim is backed by published research. There is a paper behind every component in the stack, and the code behind every paper is open. We do not make promises about what the system will do someday — we show you what it does today, and you can verify it yourself.

Privacy is not a feature we added to the product. It is a property of the architecture. There are no API endpoints to harden because there is no API to expose. There is no database to encrypt because there is no database. There is no cloud to compromise because there is no cloud. We cannot protect what we do not have, and we designed the system so we have nothing to protect you from.

The system does not guess. It cross-validates its own outputs, detects inconsistencies in its reasoning, and surfaces uncertainty when it does not have confidence in the answer. It knows when it does not know — and it tells you instead of generating a confident-sounding lie.

We built local AI with RAG and RLHF so your knowledge base and your preference alignment stay on your hardware. The model does not need to be fine-tuned on a server farm to understand your context. It learns from your data on your machine, and the results never leave.

The Anticloud requires one machine, one binary, and zero trust in anyone.

About the Author

My name is Lois-Kleinner Alpasan. I'm 23 years old. I built The Anticloud.

I started this because I looked at the AI industry and saw something wrong. Every major AI system requires you to send your data to someone else's server. Every "AI company" is actually a data company — they make money from your usage, your prompts, your files, your attention. They call it a service. I call it extraction.

I spent the last two years building an alternative. Not a feature, not a product, not a startup looking for an exit — an entirely different infrastructure stack. One where AI runs on your machine, for you, and never needs to phone home. One where privacy is not a feature you toggle in settings but a property of the architecture. One where you don't have to trust anyone because you can verify everything.

The project is near production-ready. Every component is open. Every claim is backed by published research. The code is documented. The ledger is verifiable. The binary fits on a laptop.

I'm not asking for trust. I'm asking you to read the paper, verify the claims, and decide for yourself whether the cloud is really necessary — or whether it was always just the default because no one bothered to build an alternative.

Follow the work: