charon
charon copied to clipboard
Make the validator order deterministic, so the current activated validator is the first on the list
🎯 Problem to be solved
- The current validator selection process after recombination is not the first one in the list, causing confusion and potential issues in managing clusters with many validators.
- Uncertainty about the possibility of depositing for a different validator and the need for a deterministic order to prevent double deposits and facilitate programmatic key generation.
🛠️ Proposed solution
- [ ] Check the criteria for validator ordering post-recombination to understand why the currently activated validator isn't the first on the list.
- [ ] Make the validator order deterministic by sorting based on the pubkey, filename, or other attributes.
I think a charon info
command would go a long way in making things like this viewable. It could check a chain for status too, and pretty-print or json-print the info to console for people to eyeball.