There are no compiled binaries in the official repository, only the source code.
Which "official repository" was it downloaded from?

[/quote]

I'm not sure which repository it was, just that is was not from the AUR.

[/quote]
If you are going that way, I think that is not the best way to use Electrum. Instead, I suggest you should use and verify the wallet directly from the official website of Electrum. That way, you are able to use/verify the app directly from Electrum developers. You can refer to @BitMaxz post about that.
[/quote]

This is super helpful info; i'll be redoing the whole thing straight from the website then verify, and yes you're correct: Manjaro >Electrum from Pamac.

It seems the source where he downloaded the Electrum is not from the official website I found 4.1.5-2 in Github user Archlinux
[/quote]

Thats correct, i got it from my package manager but not sure where the sig file went... so maybe its best to wipe it and start all over. I'll get it from the official site this time since the sig file is right there as well; i'll give that a shot and see if verifying w/gpg works out, thanks

The binary i downloaded from the repo...do you know where or how to get the appropriate sig file, or where its path would be if it installed together with the download? If you could spellout the process on how to verify the linux binary electrum it would be very helpful, thanks

Installed electrum 4.1.5-2 thru my package manager (official repositories) on linux which placed the file to:
/usr/bin/electrum

Manually downloaded the linux sig file from electrum.org and placed in the same directory as electrum and ran the following command:
"gpg --verify /usr/bin/electrum-4.1.5-x86_64.AppImage.asc"

And the following *errors come up:
gpg: no signed data
gpg: can't hash datafile: No data

Does someone in the community know what the issue is here?

no luck with that last command; that just downloaded the sig file somewhere, but not in the bin directory. I already have the sig file after you mentioned its a seperate download, i'll just have to force it into bin somehow or try that dual command; i'll post again tomorrow, thanks

---

it doesn't seem to work;
after managing to force the sig file into the same bin directory as electrum, and running the following command:
"gpg --verify /usr/bin/electrum-4.1.5-x86_64.AppImage.asc"

the following errors come up:
gpg: no signed data
gpg: can't hash datafile: No data

any clues?
-just to check, 'certifying' is completely optional & not necessary to verify, right?

[moderator's note: consecutive posts merged]

there seems to be a permissions issue for bin directory denying the sig file to be added there.
i'll have to try to get around this, or try your command for dual paths; i'll post the results tomorrow, thanks for helping!

path:  /usr/bin directory  --doesn't exist.

how would you locate the correct path for the sig file?
the sig file gets automatically downloaded/installed together with electrum, right?

also the command was tried with/without (~)... neither work.

Thanks for making this guide, but i'm still having trouble verifying. The verify terminal command i'm entering is not turning up anything - its not able to find the file. If someone could shed some light on what the exact command needs to be, using the commands given on the guide isn't working; i'm sure i'm entering it wrong, but i can't find where the error is:

sys: linux-manjaro-kde x86_64
file-path: /usr/bin/electrum
file-vers: 4.1.5-2

command: "gpg --verify ~/usr/bin/electrum-4.1.5-2-x86_64.AppImage.asc"

errors using above command:
gpg: can't open '/home/<username>/usr/bin/electrum-4.1.5-2-x86_64.AppImage.asc': No such file or directory
gpg: verify signatures failed: No such file or directory