Closed joepetrowski closed 1 year ago
Would be great if the RFC file is renamed according to the template.
Would be great if the RFC file is renamed according to the template.
:+1: done
I think this RFC sums the situation up really nicely. I am just missing a description of a mechanism by which the Invulnerable collators will be selected in the future - there were various ideas in the collator group but we ended up using a quite simple solution based on fairness and gentleman's agreement. Is this mechanism going to stay the same in the future or should we get general governance involved when new system chains come out (like Coretime)?
There is no way to enforce on-chain what someone proposes to governance. Any individual or group can use any mechanism to propose to add or remove someone as an Invulnerable, and the referendum process will accept or reject the proposal. "Fairness" is quite subjective. Therefore, it is not part of the RFC.
/rfc process
Please provider a block hash where the referendum confirmation event is to be found. For example:
/rfc process 0x39fbc57d047c71f553aa42824599a7686aea5c9aab4111f6b836d35d3d058162
/rfc process 0x37ae0558f4b008f9e7e421488b3466bfb2ea3510a1a58a2d40beff681e84cc42
Unable to find the referendum confirm event in the given block.
/rfc process 0x9ad960de812071c892cc545743b4ffb85fcdaf969f1b77429ce9c1d4219f2f4b
@joepetrowski Handling the RFC command failed :( You can open an issue here.
Error: Merge commits are not allowed on this repository.
The bot doesn't specify the merge option - apparently it defaults to a merge commit which is disabled in this repo.
I have a change to use squash-merging in the bot.
/rfc process 0x9ad960de812071c892cc545743b4ffb85fcdaf969f1b77429ce9c1d4219f2f4b
The on-chain referendum has approved the RFC.
As discussed in the roadmap with corresponding implementation issues, converting this to an RFC. This proposes a means of selecting collator sets on system chains.