Supply chain security
Every binary Meridian ships is cryptographically attested from build to delivery. No unsigned byte reaches your machine.
Ed25519 code signing
The loader and payload are signed with Ed25519. The public key is pinned inside the installer. If the signature fails verification, execution halts before any untrusted code runs.
Deterministic builds
Our CI pipeline produces bit-for-bit identical artifacts given the same source tree and toolchain. Reproducibility means any tampering in the build environment is detectable by comparing hashes across independent rebuilds.
Authenticode dual-verify
Every shipped PE file carries an Authenticode signature. At runtime, Meridian re-verifies its own signature against the Windows certificate store before unpacking the payload. A revoked or stripped certificate triggers immediate shutdown.
CDN integrity
Auto-update payloads are fetched over HTTPS with pinned certificate hashes. Each update blob includes an HMAC-SHA512 covering the full payload, keyed with a secret derived from the installed license. Replay attacks and downgrade attempts are rejected at the network edge.
Runtime self-attestation
The loader hashes its own .text section in memory and compares it against the link-time baseline. Any discrepancy — whether from a debugger breakpoint, IAT hook, or patch — triggers a silent integrity violation that disables sensitive operations without alerting the tamperer.