-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add centauri-chain.md #3742
Add centauri-chain.md #3742
Conversation
Once the Picasso connection is established, the remaining 9 billion PICA tokens can also be transferred to Centauri, allowing users to delegate to those validators as well. The rewards mentioned earlier are distributed among the staked users, including both delegators and validators. Any new validator can join the active set and remove an existing genesis validator should they hold a higher stake. | ||
|
||
## Governance | ||
Similar to the way Cosmos chains operate, validators can vote using tokens they are delegated with. However, if the delegator votes themselves, it will override the validator’s vote. The parameters for the governance on the Centauri chain are as follows: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you say that governance controlled by PICA
| Parameter | Period/Number | | ||
|----------------------------------------------------|----------------| | ||
| Total Deposit | 2 days | | ||
| Quorum | 30% | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
plz also add chain parameters like unbonding period etc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
plz review
- [x] PR title is my best effort to provide summary of changes and has clear text to be part of release notes - [x] I marked PR by `misc` label if it should not be in release notes - [ ] I have linked Zenhub/Github or any other reference item if one exists - [ ] I was clear on what type of deployment required to release my changes (node, runtime, contract, indexer, on chain operation, frontend, infrastructure) if any in PR title or description - [ ] I waited and did best effort for `pr-workflow-check / draft-release-check` to finish with success(green check mark) with my changes - [ ] I have added at least one reviewer in reviewers list - [ ] I tagged(@) or used other form of notification of one person who I think can handle best review of this PR - [ ] I have proved that PR has no general regressions of relevant features and processes required to release into production
misc
label if it should not be in release notespr-workflow-check / draft-release-check
to finish with success(green check mark) with my changes