Creating New Verification

Fields marked with (*) are required.

App ID:

Example: app.zeusln.zeus. Start typing wallet name or ID to search for known apps, or write a new app ID. If you can't find the app here, you can open an MR to add it to the inventory, or drop us a message on our Discord.

Version (*): Example: 0.9.2

Platform (*):

Asset Description (*): Example: Firmware / Bootloader / Universal APK from Github / Debian package amd64 / ARM v8 / MacOS App Store

Status (*):

Reproducible: You've been able to build the asset and differences with the tested binary are minimal.

Not Reproducible: You've been able to build the asset, but differences with the tested binary are significant.

Failed to Build from Source: You failed to build the asset from source.

Spam: The asset is a spam or is not what it says it is.

No git revision: The git revision to compile is not clear.

No source: The source for this version was not found or the repository was taken down.

Obfuscated: The source code is obfuscated.

Warning: If another status could apply but some red flag has come up. Reproducible but known backdoor found, or irreproducible with a discrepancy clearly not benign.

Content (*):

Characters: 0/60000

Describe your verification process and findings with as much detail as possible, including scripts you used and output logs (minimum 20, maximum 60000 characters). Markdown is supported.

Script Usage: Select how you are providing build verification scripts, if any.

If you've used scripts or docker files to build the asset, drag & drop them here to attach them (max 60KB each). Each file will be linked to this verification and could be used by other users to reproduce the asset.

For larger files, drag & drop them here to upload to our server. These files will be uploaded when you save or publish your verification.

- Asciicast files are supported (*.cast). The first one will autoplay in the verification.

- Diffoscope files are supported (diffo*.html).

- You can also upload other log files, like build logs showing successful or failed builds.

If you've used a script created by another user in a different verification, mark it here with the icon:

Delete Draft

Note: Draft verifications are not displayed directly, but they can still be seen by you and other users if they opt to view them. You'll be able to view them and publish them later.

Notifications

Creating New Verification