A content-addressed VCS.
Content-addressed means the name of a thing is the BLAKE3 hash of its bytes — every file, folder, and commit. Change one byte, get a new name. Every commit is signed with an Ed25519 key, and any claim about a commit — reviewed, tested, deployed — travels as a signed statement anyone can verify. Written in Rust; here it runs in your browser.
mkit is git-like where it can be — add, commit, branch, push — and different where it counts: one hash algorithm, signatures on every commit, attestations as first-class objects. Alpha, open source: officialunofficial/mkit on GitHub, cargo install mkit-cli to try it.
- hash
Edit a file and watch the BLAKE3 hashes of every container that holds it — folder, parent folder, commit — rewrite live.
- sign
Generate a key, sign a message, flip a character, watch the verifier reject it.
- tree
A Merkle tree of BLAKE3 hashes — edit any file and the hashes ripple up to the commit at the root.
- streaming
Edit a 2 GB video and git stores it again, whole. mkit cuts it into chunks, ships only the changed ones, and verifies each chunk as it streams in.
- performance
Hashing, committing, packing — mkit measured against git on real operations.
- attest
Attach a signed statement to a commit so anyone with your public key can verify it later.