What it writes
Everything tare build, weigh and prove leave under target/.
Programs
| File | What it is |
|---|---|
target/deploy/<program>.so | The stock build. The reference in every comparison. |
target/idl/<program>.json | The IDL, from Anchor's own IDL build. |
target/tare/<program>.so | The Tare build, after the bytecode stage. The one you deploy. |
target/tare/<program>.linked.so | The Tare build as linked, before the bytecode stage. |
Documents
| File | Written by | What it holds |
|---|---|---|
build.json | build | Both artifacts, their hashes, the Anchor version, the source, the platform tools. |
dependency-graph.json | build | The resolved graph the Tare build compiled against. |
optimization.json | build | The bytecode stage's counters and the hashes before and after. |
corpus.json | weigh, prove | The inputs both builds ran. |
execution.json | weigh, prove | Every transaction outcome on both builds. |
weigh.json | weigh | The weighing. |
proof.json | prove | The proof report. |
Several programs in one workspace
Each program also gets its own copies, prefixed with its name: <program>.build.json, <program>.weigh.json, <program>.proof.json and so on. The unprefixed files hold the program selected last.
Lockfiles
The lockfile each compilation resolved is kept as <program>.stock.Cargo.lock and <program>.tare.Cargo.lock, with their hashes in <program>.dependency-locks.json. Your own Cargo.lock is left as it was.