Reproducible build
A build process that turns the same source into byte-for-byte identical output every time, so anyone can confirm a binary came from the published code.
Most builds aren't reproducible: timestamps, file ordering and tool versions creep in, so two builds of the same code differ. That makes it impossible to tell from the outside whether a binary really came from the source it claims.
A reproducible build pins everything that affects the output: compiler and dependency versions, timestamps, file order and environment. Then anyone who builds the same commit gets an identical result, down to the hash.
Paired with remote attestation, this closes the loop: the attestation proves which measurement is running, and the reproducible build proves which source that measurement came from.
On Valtu
The enclave image is built reproducibly: everything that affects its measurement is pinned. The current release was built twice from scratch with identical results. A second, independent rebuild by someone outside the team is still owed, and the security page will say when it's done.
Related terms
Keep reading.
More in key security: HSM · Shamir secret sharing · MPC wallet · Multisig · Approval policy · Passkey. The whole glossary.
Put it into practice.
Every workspace starts on testnets with free test coins: same dashboard, same API. Go live when your team is ready.