De Brakke Network
Security — File Integrity

Verify Your Connector EA

Connector version: v2.37 Algorithm: SHA-256 File: DT_SAAS_CONNECTOR.ex5

Every release of the Connector EA has an official SHA-256 checksum published here. Before attaching the EA to your live chart, spend 30 seconds comparing the hash of your downloaded file against the value below. If they match, the file is exactly what DeBrakke built — untampered and safe to run.

Only download from daytrading.debrakke.com

Never run a copy of the connector received via email, Telegram, Discord, or any third party. The official download link is inside your account dashboard only.

Current Official Checksum

SHA-256 — DT_SAAS_CONNECTOR.ex5 v2.37
6a5ccd7de63afc592ed7e4b805a9e61645f9c716886132fe09a15617c3b43da2
Click the hash to select all, then copy.

How to Verify (Windows)

Two methods — both built into Windows, no extra software needed.

Method 1 — PowerShell (recommended)

1

Open PowerShell — press Win + R, type powershell, press Enter.

2

Run the following command — replace the path with wherever you saved the file:

Get-FileHash "C:\Users\YourName\Downloads\DT_SAAS_CONNECTOR.ex5" -Algorithm SHA256 | Select-Object -ExpandProperty Hash

Or, if you have already placed it in your MT5 Experts folder:

(Get-FileHash "$env:APPDATA\MetaQuotes\Terminal\*\MQL5\Experts\DT_EURUSD\DT_SAAS_CONNECTOR.ex5" -Algorithm SHA256).Hash
3

Compare the output hash to the official value above. They must match character for character.

Method 2 — Command Prompt (CertUtil)

1

Open Command Prompt — press Win + R, type cmd, press Enter.

2

Run:

certutil -hashfile "C:\Users\YourName\Downloads\DT_SAAS_CONNECTOR.ex5" SHA256
3

The second line of output is the hash. Compare it to the official value above.

What the Result Means

✓ Hashes match

Your file is authentic and identical to the build published by DeBrakke. You are safe to attach it to your chart.

✗ Hashes do not match

Do not run the file. Delete it and download a fresh copy from your account dashboard. Contact support if the mismatch persists.

🛡
Re-verify after every update

When a new connector version is released, the checksum table below is updated. Re-run the verification any time you download a new build.

Checksum History

All past checksums are kept here so you can verify any build you have on disk.

Version Released SHA-256
v2.37  Current Jun 2026 6a5ccd7de63afc592ed7e4b805a9e61645f9c716886132fe09a15617c3b43da2
v2.36 Jun 2026 c8bdd87ce2c55557dda4f2dc86d598b0d8bab569ec238340742d996518433560
v2.35 Jun 2026 4a0eed1708a801643bf9f13f1712eaa4d15e375b703a59ea73d22d803e974803
v2.34 Jun 2026 ae28af05101ea567035c129a3a94a5eeb52c0715b2273f4802b3a2b67a4d6208
v2.32 May 2026 23dcc82bba52362d961591e0c288d13cd6652e0eb6e2322343b9509475a6b2c2
v2.31 May 2026 8546f30f96f13acf48a8deccbef79c6b56965bd57f36a91d50acaa10b2804229
v2.30 May 2026 a12056169dd1114ab60be7ec17eae3634ac02a112a99e7bb8a875b5a104b4203
v2.29 May 2026 62f6304c5d271f5f6b03b0c19ddb0dceb265b0f1366cadcbf93a06e588dc34c2
v2.28 May 2026 057133b5bd815ebeaf5dbff276957d51e0278ab3db6a1ebfa17e91d67e1456cb
v2.27 May 2026 a1dc99ece4f4e22b8ca7a94f528d97edac1b80da2833386706d959e8f2ff8227
v2.26 May 2026 83b87d8772c97ce601d5cc1f384864ef55d1cb684cc8436ba7d44850853195b6
v2.25 May 2026 3dbefc3d43e7818020337655d6f6a3c7297a104a0f34db2160a112241761980c
v2.24 May 2026 ab044b3017f718087b8d700b6afb794768adb8335e1b270a71ab3aa78d03335d
v2.23 Apr 2026 697317428f2cf8b43c077f6902435c72839a3843a51d8cfd6a39d78b13ee93ff
v2.22 Apr 2026 7c2030f08cd4c54cf2442ba65d8c676a70da2155f7fe332ca1267ab03d071236
v2.21 Apr 2026 99a7fb8bc13e8ae2b0e2edffe4aa2a9da5a7f282935b07c737ec124084cb70ce
v2.20 Apr 2026 a43e6aa56f0461c7b04f6e33a48a13121fc4cc441914d11e4471b1cf05671090
v2.19 Apr 2026 3bae419175fb667103bf1024060fba3d4af06d3297c5dfa7398bfeab975c992a
v2.18 Apr 2026 a8c9915de3cf512c589882d80be86acab3726d83b6ad90a6499ad5ec4c90a326
v2.17 Apr 2026 8954c5798ecd126920e57db2fb24625757dff04535c8a6da20b2d7cc222ac0c9
v2.16 Apr 2026 0c9079a337e2f135eaca9b60de618d52198c124b0d91c9c63d6e99cb0ef45bae
v2.15 Apr 2026 efcf588f04e956b48ecff6175846a0c1cb0f4263bec75cb3c91a79130d1d370a
v2.14 Apr 2026 110353db79e6e2280fec5c48fd22aa7d49dbc6304c7f65192d05aa106cf199b0
v2.13 Apr 2026 110353db79e6e2280fec5c48fd22aa7d49dbc6304c7f65192d05aa106cf199b0
v2.12 Mar 2026 93a8fbd28e82949a151406b67c6184db2a8e39a0d3abcfac437448b4d6cdf54a
v2.11 Mar 2026 ab2e9ea9289fefacf2a6096e113cad27c33b695b84205ec4f0b9f1fff57d51c9

Frequently Asked Questions

What is SHA-256?

SHA-256 is a cryptographic hash function. It takes any file and produces a unique 64-character fingerprint. Even a single changed byte produces a completely different fingerprint, making it an effective tamper-detection tool.

Can I verify the .mq5 source file instead?

The source file is not distributed — only the compiled .ex5 binary. Source code is kept server-side as part of the DeBrakke proprietary strategy. Verifying the binary is what protects you.

The hash changed after MT5 ran the file — is that normal?

No. MT5 does not modify .ex5 files after compilation. If the hash differs from the published value, the file was modified before or during transfer. Discard it and re-download.

My antivirus flagged the file — should I be worried?

Some antivirus tools flag MT5 Expert Advisors because they communicate with remote servers over HTTP. This is a false positive — it is exactly how the connector is designed to work (sending market data to dt.debrakke.com). Verifying the hash confirms the file has not been tampered with. You can whitelist the file in your AV settings after verification.