This is a retry of motion 58. The previous motion failed because it turns out removing workers from a cluster must be performed by the cluster owner (the Council multisig account), instead of as a council motion. In this motion, the last action was removed, and they will be moved to a separate multisig call.

Original proposal

This motion will setup two new GKs for Phala Network, and the Gemini tokenomic balancer.

Two new GKs are added (both are at confidence level 2):

• 0x52dd554813e99c4efe9b086fc385b9ea91c22cbc8967669f66c341da0041f261
• 0x4ce6d07252f7735b88a9c83f048d959b52780fb49405147b3747677f28d07863

The two GKs are converted from workers in the contract cluster. Therefore it will remove the shutdown workers:

• 0xbc58464ce13637151c51235a31a56472b7fc1fbc76aa4adb10d14c20a79df14a
• 0xda9c7aa880cfadddabf9b1667a2daaabfa7c1c421b34e3387dfe67c9284ae179

Finally, this motion will set the tokenomic balancer controlled by a Phat Contract. The contract controlled account is generated within the Phat Contract, living at 0xaaa789d2b1232cb53e2f3e964d7bf924069becc4979451f9c67935521a7f500e.

The contract code is available at: https://github.com/Phala-Network/tokenomic-contract