Skip to content

Conversation

@shelvenzhou
Copy link
Contributor

@shelvenzhou shelvenzhou commented Jan 5, 2022

  • Support add/remove workers for contract cluster
    • will be done after the contract state is written back to the chain
  • Allow user to specify cluster to deploy contract
    • Anyone can freely deploy contracts to any cluster with no access control
  • Support deploy the contract to worker group
    • If a contract is deployed to an existing cluster, it must specify the same worker group
  • Provision contract key to contract cluster
  • Use ContractId to specify contract instead of ContractPubkey and generate it on-chain when instantiating
  • Add e2e test for code upload and contract instantiation

@shelvenzhou
Copy link
Contributor Author

This PR follows the #546

@shelvenzhou shelvenzhou marked this pull request as ready for review January 6, 2022 02:10
Copy link
Contributor

@h4x3rotab h4x3rotab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move the contract related features from pallet-registry to pallet-fat in a future PR?

@shelvenzhou
Copy link
Contributor Author

Move the contract related features from pallet-registry to pallet-fat in a future PR?

Will do

Copy link
Contributor

@h4x3rotab h4x3rotab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Please remember to move to cluster based key dispatch later

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants