Tidemark
Software Supply Chain Tracking on Cardano
OpenFP × StrataflowOpenFP×
What Tidemark does
Tidemark records exactly which sources each Haskell package set and release was built from. It hashes Horizon's lock data (horizon.lock and flake.lock, one leaf per pinned package or input) into a Merkle root, and anchors that root on Cardano.
Anyone can check that a package was part of a release by verifying a short inclusion proof against the anchored root.
Why it matters
Four incidents show why it matters to know exactly what each release was built from. The sentences that begin With Tidemark describe what the design is meant to give, because Tidemark is still an exploration.
Log4Shell, December 2021. A bug in Log4j, a Java logging library used almost everywhere, let attackers run code on servers just by getting a crafted string logged. For weeks afterwards, many organisations struggled simply to find which of their software contained the vulnerable versions. With Tidemark, "which of our releases include log4j-core 2.14?" is one query, answered with a proof against roots anchored at release time.
event-stream, 2018. A popular npm package was handed to a new maintainer, who added a dependency carrying hidden code that targeted the Copay Bitcoin wallet. Thousands of projects pulled it in indirectly, without ever choosing it. With Tidemark, indirect dependencies are in the tree too, so you can prove exactly which releases did and did not include the poisoned version.
xz-utils, 2024. After two years of earning a maintainer's trust, an attacker hid a backdoor targeting SSH logins on Linux in the xz compression library. It was caught by chance, shortly before it reached major distributions. With Tidemark, every release records exactly which source archive of each dependency it was built from, and the record can't be rewritten afterwards.
chalk and debug, September 2025. A maintainer of some of npm's most downloaded packages was phished, and versions that hijacked cryptocurrency transactions in browsers were published before being pulled hours later. With Tidemark, anchored roots show whether a release was built inside that window, with no need to trust edited lockfiles.
How it works
Coming later
- Build attestations from independent builders, with k-of-n agreement on output hashes.
- Review attestations that reference the root.
- Revocations.