Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define the contracts Bootstrapping Release Process & Batch Migration #83

Open
ct-ctrl opened this issue Dec 7, 2022 · 1 comment
Open
Labels

Comments

@ct-ctrl
Copy link

ct-ctrl commented Dec 7, 2022

Define the plan, process and order for initialisation of the contracts and oracle setting price upon release etc.

note: batch migration should be done before the price is set to the minimum on the Oracle. During the migration make sure to not set roles or deploy other contracts or set the price.

question: Do we now force set initial price to the minimum so there is no zero case? If so will this negatively affect the previous note on the batch migration process?

question: the copyBatch does not fire expire(expireLimited?) or update validchunkcount - does that mean that it is only to be intended to be used during the initialisation of the contract?
validChunkCount += 1 << _depth; should it be added to copybatch?

@bee-runner bee-runner bot added the issue label Dec 7, 2022
@significance
Copy link
Member

i agree, it would be good to document the bootstrapping process for completeness

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants