CDAO Airdrop Implementation #410
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rupansh-sekar-yral
changed the title
ravi-sawlani-yral
requested changes
Oct 22, 2024
src/canister/platform_orchestrator/src/api/canister_management/upgrade_canisters_in_network.rs
Show resolved
Hide resolved
...pgrade_individual_user_template/update_user_index_upgrade_user_canisters_with_latest_wasm.rs
Outdated
Show resolved
Hide resolved
src/canister/individual_user_template/src/data_model/airdrop.rs
Outdated
Show resolved
Hide resolved
rupansh-sekar-yral
force-pushed
the
rupansh/airdrop
branch
from
663b43a to
5ed899e
Compare
rupansh-sekar-yral
force-pushed
the
rupansh/airdrop
branch
from
846f9ef to
8c453c3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds two features:
Couple of notes:
I've added upgrade code for proof of participation, all existing canisters will need this.
The cycle cost will be expensive
Platform orchestrator: (25_000_000_000 * number of subnet orchestrators)
for each subnet orchestrator: (25_000_000_000 * number of individual canisters in the subnet)
Please ensure all canisters have enough cycles.
upgrade sequence:
I am not sure if this is how we perform upgrades so im defining the sequence here. Ensure its followed so all canisters get a proof of participation:
For each subnet orchestrator:
Upgrade subnet orchestrator
Once the given subnet orchestrator has upgraded, upgrade all individual canisters
We should also remove the upgrade logic from subnet orchestrator and platform orchestrator once the upgrades are complete to not waste cycles.
Following updates in off-chain components will be required to switch the network to airdrop flow(to be done AFTER upgrades):