search

skalenetwork / skale-admin

SKALE admin docker container orchestrates all other SKALE Docker containers
https://skale.network
GNU Affero General Public License v3.0
18 stars 4 forks source link

Investigate end to end flow: moving from schain to another schain #385

Open sync-by-unito[bot] opened 3 years ago

sync-by-unito[bot] commented 3 years ago

Need to investigate the flow and functional changes to transition data from one schain to another May imply starting schain from snapshot from another schain

┆Issue is synchronized with this Jira Task

sync-by-unito[bot] commented 3 years ago

➤ Ganna Kulikova commented:

https://skalelabs.atlassian.net/wiki/spaces/SKALE/pages/1449689096/Schain+restore ( https://skalelabs.atlassian.net/wiki/spaces/SKALE/pages/1449689096/Schain+restore|smart-link )

sync-by-unito[bot] commented 3 years ago

➤ Ganna Kulikova commented:

Oleh Nikolaiev to update snapshots documentation https://skalelabs.atlassian.net/wiki/spaces/SKALE/pages/734396515/Snapshots+Functionality ( https://skalelabs.atlassian.net/wiki/spaces/SKALE/pages/734396515/Snapshots+Functionality|smart-link )

sync-by-unito[bot] commented 3 years ago

➤ Chadwick Strange commented:

one user flow goal:

  1. schain owner decides to move to a new schain.
  2. owner creates new schain.
  3. owner pauses their dApp on the old schain.
  4. owner initiates transition flow (python script).
  5. owner unpauses contract on new schain.
  6. owner then sunsets old chain when its lease expires.

another user flow:

same as above but schain is swapped/transitioned to a new schain and old schain is removed.

what is the engineering suggestions assuming schain only transition? vs schain + IMA transition? how can this support schains with custom bridges?