# Who wrote this byte?

DevFeed: [Who wrote this byte?](<https://devfeed.tech/articles/who-wrote-this-byte-98446.md>)

Original publisher: [Read original article](<https://fzakaria.com/2026/10/23/who-wrote-this-byte>)

Published: 2026-10-23T17:00:00Z

Content type: article

Language: en

Sources: [Farid Zakaria's Blog](<https://devfeed.tech/sources/farid-zakaria-s-blog.md>)

Topics: [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [reproducibility](<https://devfeed.tech/topics/reproducibility.md>), [Nix](<https://devfeed.tech/topics/nix.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Data integrity in software engineering](<https://devfeed.tech/topics/data-integrity-in-software-engineering.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [GPU instancing](<https://devfeed.tech/topics/gpu-instancing.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [git](<https://devfeed.tech/tags/git.md>), [hash](<https://devfeed.tech/tags/hash.md>), [input](<https://devfeed.tech/tags/input.md>), [nix](<https://devfeed.tech/tags/nix.md>), [package](<https://devfeed.tech/tags/package.md>), [reproducibility](<https://devfeed.tech/tags/reproducibility.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [software](<https://devfeed.tech/tags/software.md>)

## AI overview

Rewind VM's `rewind blame` traces the first program that wrote a differing byte between two build runs. In the `tiles` example, varying Python's random hash seed changes the order of dependencies written to a pkg-config file; blame traces the difference through `install` to `python3`, and sorting the dependencies fixes it. Rewind records file writes and opens in the guest kernel, then reads those traces to identify byte provenance without replaying both runs. Its checks can vary random seeds, thread schedules, and directory-entry order, each of which can expose different sources of non-reproducibility. The excerpt also describes a visual comparison in the Rewind app and says recording overhead was measured as small enough to keep enabled in every run.

## Source excerpt

git blame for your build's bytes. 🔍 A build is bit reproducible when the same inputs give the same bytes. Why does reproducibility matter? They provide certainty that software is genuine and has not been tampered with. See reproducible-builds.org. Nix is infamously not bit reproducible, but rather input-addressed: the hash of a package is calculated from the inputs rather than the output.