PAGE ROLE · INSTALL + VERIFY

INSTALL 13.0. VERIFY BEFORE TRUST.

Download the exact ZIP, hash it, extract it, ask the binaries what they are, then run one file. Do not debug your program before you know which compiler bytes you are running.

00 download

DOWNLOAD WINDOWS X64. The tracked route counts one hashed network actor at most once per rolling 24 hours and redirects to the static package.

PACKAGE  dbyte-v13.0.0-windows-x64.zip
BYTES    4016724
SHA256   40468ef823543b23638d633fbfc5e7e82b6da23ce4659238a3c427f2916337d9

10 verify the ZIP

PS> Get-FileHash .\dbyte-v13.0.0-windows-x64.zip -Algorithm SHA256

SHA256  40468EF823543B23638D633FBFC5E7E82B6DA23CE4659238A3C427F2916337D9

If the hash differs, stop. A release package is identified by bytes, not by a familiar filename.

20 extract and smoke

PS> Expand-Archive .\dbyte-v13.0.0-windows-x64.zip .\dbyte-13
PS> .\dbyte-13\dbyte.exe --version
DByte 13.0.0

PS> .\dbyte-13\dbytec.exe --help

The package contains 536 entries, including 25 runtime entries. dbyte.exe SHA-256 is 645b1277116f7681c1abbf40777992a12b259f150826bccdb51b16a63e4a7d98; dbytec.exe is 645184f0aa838851ac5d37fc0322377a780eb55926f0aac41ce0c9f7e24b84f6.

30 run one file

fn main() -> i32:
    return 42 as i32

Put that in hello.dby. For native Windows output, the toolchain retains the x86_64 Windows target and bounded O0/O1 selection established before v13.

PS> dbytec build hello.dby --target x86_64-dbyte-windows --emit exe --opt-level 1

40 if something fails

ZIP hash wrong	Wrong artifact. Redownload. Do not continue.
`--version` is not 13.0.0	Your PATH points at another installation. Run the extracted binary by explicit path.
Build fails before parsing source	Capture exact command and output. Check target spelling and package completeness.
Behavior differs across backends	Reduce to a small repro. For upcoming portability work, read 13.1 strict portability.

RULE. Prove the tool bytes. Prove the command. Then debug the program.