Contribute compute

Vega's shared cache is only as trustworthy as the independent builds behind it. There are two ways to help.

Cache your builds

Build your packages in CI and push them to Vega. Every attested build seeds the network; a build that other independent owners also produce, and that Vega then independently reproduces, can earn a place in the globally-trusted shared cache. This works today: see Caching your builds.

Reproduce and corroborate builds

The most direct way to push a build toward the trusted shared tier is to build the same derivation yourself, in your own GitHub-hosted CI. Your run authenticates over OIDC as a distinct, independently-verified owner, so when enough distinct owners produce the identical output it becomes a candidate for shared promotion (which still requires a trusted Vega reproduction and the other gates). This is the highest-leverage community contribution and it works today: it is the caching workflow pointed at the same package.

The independent rebuild that actually gates the master-key signature is run by Vega-operated reproducers (the public, auditable reproducer and Vega's own fleet). That step stays Vega-operated on purpose: an arbitrary donated host cannot prove it rebuilt an output rather than copying the public bytes, so its word alone cannot gate a global signature. If you would like to fund or operate reproduction capacity, reach us at [email protected].

Either way the principle is the same, in the spirit of rebuilderd and distributed verification: reproducing other people's builds is what makes the cache trustworthy for everyone.