ADR 0004: Runtime Governance

[kostko]

See #2515

[pro-wh]

what is the workflow for creating a runtime with runtime governance? do you create it that way, and it's immediately suspended and then you do something? or maybe you create it under entity governance, and you transfer some tokens and then you update it to runtime governance?

[kostko]

You can escrow tokens to the runtime account before registering the runtime itself. And then you can register it with runtime governance directly.

[pro-wh]

what does this safeguard against?

[kostko]

In theory it would give users time to e.g., move tokens out of the runtime in case they don't agree with the upgrade (security parameter change/MRENCLAVE change/etc.). Of course there are ways to prevent this, so it may not be worth adding the complexity.

[hydai]

Hi, I would like to request a feature of the runtime governance.

Is it possible to limit the number of compute nodes per entity?

As a ParaTime developer, we will encounter the following issues if the number of compute nodes per entity is not limited:

1. Someone can create as many as possible compute nodes with malicious modification. When the number of compute nodes per entity is not limited, all of the active compute nodes can be taken by this maliciously modified version in one epoch time.
2. If we want to provide rewards for the active compute nodes, an entity which creates more compute nodes may increase its possibility to join the active group.