Skip to main content
The current macOS app is ad-hoc signed and not notarized, while the Windows installer is unsigned. The operating system may therefore display a security warning when you open Edge0. This page explains how to handle these prompts and verify downloaded files.
Do not turn off system security protectionsDo not turn off your system’s security protections in order to run Edge0.

​
Get files from official sources

​
macOS: Gatekeeper prompt

Because macOS cannot verify an identified developer for the current app, Gatekeeper may display a warning when you open it. If you have confirmed the app was built from the official source and has not been replaced, you can open it as follows:
  1. Try to open the app first and read the system prompt.
  2. Open System Settings → Privacy & Security.
  3. Click Open Anyway next to the prompt for the app.
  4. Confirm again and click Open.
This adds an exception for that app only; it does not turn off Gatekeeper. If the system says the app will harm your computer, detects malware, or says the app is damaged, do not open it. Verify the source and obtain or build the app again. Reference: Apple: Safely open apps on your Mac.

​
Windows: SmartScreen prompt

Because the current Windows installer is unsigned, SmartScreen may show Windows protected your PC. If you have confirmed the source is trustworthy, you can click More info to view the file details, then decide whether to click Run anyway. Note:
  • If security software reports malware, a tampered file, or a checksum mismatch, do not run it.
  • If the computer is managed by a company or school and there is no run option, contact your administrator.
  • Installing and using Edge0 does not require turning off Defender or SmartScreen.
Reference: Microsoft Defender SmartScreen documentation.

​
Verify files with SHA-256

A SHA-256 check confirms that a file’s contents match the value provided by the publisher. You need:
  1. The file to check.
  2. The SHA-256 value the publisher provides for that file and version.
Replace the path with the actual file location:

​
Automatic verification in the app

  • macOS / Windows: the app verifies files automatically when downloading models and reports an error on failure.
  • iOS 35B: the verify step during conversion checks the conversion result.
  • Android: model conversion produces a verification manifest, and the import script checks that the files transferred completely.
It is normal for a model file you converted yourself to have a different SHA-256 than the original download.

​
When verification fails

  1. Stop using the file.
  2. Confirm that the file name, model version, and expected checksum all correspond.
  3. Re-download the problematic file, or re-prepare the model following the platform guide.
  4. If the problem persists, keep the error message and report it through the support channels.