Qortal Project

The future of blockchain platforms

User Tools

Site Tools

Trace:
how_auto_updates_work

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
how_auto_updates_work [11/01/2022 02:16] – created gfactorhow_auto_updates_work [04/27/2023 18:30] (current) – gfactor
Line 2: Line 2:
 {{:qortal_official_logo_transparent_.png?400|}} {{:qortal_official_logo_transparent_.png?400|}}
  
-Qortal's auto-updates are controlled by a special type of multi-signature transaction: the developer group on-chain (DevTeam Admins). The developer group has 'admins' like any other group on Qortal, but the admins of this group are required to sign the update transaction prior to it going live. How it works, is one of the core developers puts up an auto-update transaction, that sits unconfirmed until 60% or more of the developer group signs it. Once that happens, the update goes live, staggered so that the entire network doesn't update at the same time. It takes about 2 hours at this point for the entire network to update. As the network grows, it will take longer.+Qortal's auto-updates are controlled by a special type of multi-signature transaction: the developer group on-chain (DevTeam Admins). The developer group has 'admins' like any other group on Qortal, but the admins of this group are required to sign the update transaction prior to it going live. How it works is that one of the core developers puts up an auto-update transaction that sits unconfirmed until 60% or more of the developer group signs it. Once that happens, the update goes live, staggered so that the entire network doesn't update at the same time. It takes about 2 hours at this point for the entire network to update. As the network grows, it will take longer.
  
-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.
Line 15: Line 15:
  
 We'll update this page when we have more info to share on this aspect of development! We'll update this page when we have more info to share on this aspect of development!
 +
 +You can read more about the [[GitHub Replacement]] concept on the wiki!
how_auto_updates_work.1667283370.txt.gz · Last modified: 11/01/2022 02:16 by gfactor

Page Tools