Manifest Integrity Verifier

A common pattern for any tool that ships or downloads a bundle of data files (symbol lists, calibration tables, exported history) is to trust that the files are still exactly what they were when the bundle was built. This library replaces that assumption with an actual check: every file gets a genuine FNV-1a 32-bit checksum computed over its full byte content, plus a line/row count, and both are compared against a manifest recorded earlier. FNV-1a is not a cryptographic hash and makes no collision-resistance claim - it is the right tool here because the threat model is accidental corruption or an incomplete transfer, not a deliberate adversary. A same-size file with even one byte changed produces a different checksum, which a size-only or filename-only check would miss entirely. The manifest itself is a plain CSV (filename, hash, rows) that this library both writes (SnapshotEntry + SaveManifestCsv, from a known- good state) and reads back (LoadManifestCsv), so the same library covers building the baseline and checking against it later - the demo runs both halves in one pass, then deliberately tampers with a file and deletes another to show the mismatch and missing-file reports. MQL4 file I/O is sandboxed to MQL4\Files\ (or MQL5\Files\ on the native MQL5 build) - every file name used by this library is relative to that folder, the same restriction any MQL4 program lives under. Notes and limitations - FNV-1a is a checksum, not a cryptographic hash. It detects accidental corruption and incomplete transfers reliably; it is not a defence against a deliberate, hash-aware tamperer. - All file names are relative to MQL4\Files\ (or MQL5\Files\ on the native MQL5 build) (or MQL4\Files\ (or MQL5\Files\ on the native MQL5 build)Common\ if you extend this to use FILE_COMMON) - MQL4 cannot read or hash files outside its sandbox, including the terminal's own history folder. - Row count is a text-line count (FileReadString until end-of-file), which assumes the file is genuinely line-oriented text. A binary file's "row count" from this library is meaningless and should be ignored - the hash check alone is what matters for binary payloads. - HashFile() reopens the file for the row-count pass rather than trying to derive line breaks from the binary read - two short sequential passes, simple and correct, at the cost of reading the file twice.

Script · MT4 · v1.0 · Free

Tags: MT4 Script · MQL4 Source Code

MQL4 & MQL5 scripts · PolyMaria