feat: proof of participation #471
Open
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
force-pushed
the
rupansh/pop
branch
from
de54223 to
ef9d96e
Compare
…me after provisioning subnet orchestrator
…iting time after provisioning subnet orchestrator" This reverts commit 24cf650.
…ad of [u8; 32] for Hashes
TODO: check compatibility between the two
rupansh-sekar-yral
force-pushed
the
rupansh/pop
branch
from
7f460f1 to
4a1cd56
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.
Proof of participation: trustless method to verify that a call was done by a YRAL canister
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)
Please ensure all canisters have enough cycles.
upgrade sequence:
Upgrade platform orchestrator
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 can be done to benefit from this: