this is very vague and incomplete in my opinion which is probably why it has not been merged yet.
i suggest turning it into clear steps and then also include alternative ways and also possible different replies that you get from each command.
for example:
1. Download files from electrum.org
-this should include what files (the .exe or tarball or .dmg file,... + signature file)
2. get the developer's public key
- then it should mention the alternative way here also you must mention what to do when you fail to connect to mit server since it is a common thing for it to go down!
3. do the verification
this should include the example of BOTH good and bad signatures highlighting the part of the response message saying whether it was good or bad and also explaining the other part (the error) that always confuses everyone.
i suggest turning it into clear steps and then also include alternative ways and also possible different replies that you get from each command.
for example:
1. Download files from electrum.org
-this should include what files (the .exe or tarball or .dmg file,... + signature file)
2. get the developer's public key
- then it should mention the alternative way here also you must mention what to do when you fail to connect to mit server since it is a common thing for it to go down!
3. do the verification
this should include the example of BOTH good and bad signatures highlighting the part of the response message saying whether it was good or bad and also explaining the other part (the error) that always confuses everyone.
Wanna help?
