This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
how_auto_updates_work [11/01/2022 02:18] – gfactor | how_auto_updates_work [04/27/2023 18:30] (current) – gfactor | ||
---|---|---|---|
Line 2: | Line 2: | ||
{{: | {{: | ||
- | Qortal' | + | Qortal' |
- | As the developer group grows, the number of admins will also grow, making it more signatures required for the network to update. The nodes see the approved special transaction type, and execute the update. In the near future, every Qortal registered name, will have a git repo tied to it as well, therefore our git repo will be on QDN. That should be completed sometime around the end of the year. As it sits, the update verifies the signature of the qortal.jar on GitHub, and pulls it from there. (Yes, obviously that isn't yet ideal.) | + | As the developer group grows, the number of admins will also grow, making it more signatures required for the network to update. The nodes see the approved special transaction type, and execute the update. In the near future, every Qortal registered name will have a git repo tied to it as well, therefore our git repo will be on QDN. That should be completed sometime around the end of the year. As it sits, the update verifies the signature of the qortal.jar on GitHub, and pulls it from there. (Yes, obviously that isn't yet ideal.) |
Eventually, the updates will be calling from its own network, meaning NOT from GitHub - but on Qortal itself. Until then, we have to work with what is available, and literally every repo for every project is on GitHub. We will be able to help all other open source projects once Qortal Git goes live. | Eventually, the updates will be calling from its own network, meaning NOT from GitHub - but on Qortal itself. Until then, we have to work with what is available, and literally every repo for every project is on GitHub. We will be able to help all other open source projects once Qortal Git goes live. |