Where are my binaries being fetched from when my node updates?

I’ve seen several people use different terminology when they are referring to their node using a “CDN through Github” or different variations. I want to clarify what is going on when using

GitHub

If you use the ‘release_autorun.sh’ script that comes with the Github repo you are actually NOT fetching your updated binaries from Github.

GitLab

If you run the ‘release_autorun.sh’ script from Gitlab, you are fetching updated binaries from the Gitlab server https://source.quilibrium.com.

  • This is NOT fetching through a CDN (currently).
  • This script is checking the Gitlab repo for updates and fetching them if there is an update.

Directly from the CDN (no git repo or autorun script)

  • This requires interacting with a command line or a custom script.
  • This doesn’t use any git or download any source code.

Just FYI, binaries are pre-compiled source code for your architecture. Building from source will not net you any benefits, generally, than just downloading the pre-compiled versions and the signatures.

I’ve seen some people still asking how to compile them… if a person is asking this question I’m concerned why a person who doesn’t know how to lookup how to compile it is needing to compile it. I.e. if it’s beyond their skill level, they may need to take a step back-- in this case there is a better way to approach getting an updated binary.

Please, if you don’t know what you are doing, figure out how to use the pre-compiled versions rather than keep trying to do what you were taught initially-- you no longer need to compile the node OR the qclient binaries.

5 Likes