Skip to content
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

Update PoS parameter values #478

Closed
Tracked by #340
brentstone opened this issue Sep 20, 2022 · 2 comments · Fixed by #708
Closed
Tracked by #340

Update PoS parameter values #478

brentstone opened this issue Sep 20, 2022 · 2 comments · Fixed by #708
Assignees
Labels

Comments

@brentstone
Copy link
Collaborator

During the August retreat in Italy, we decided upon some parameter values for the PoS system. These are:

  • pipeline_offset = 2
  • unbonding_offset = 21
  • slash rate = 0.001 / namnam (fundamental token unit)
  • votes per token = 1 / namnam (fundamental token unit)
  • max active validators = 100
  • block proposer reward = 1% minimum
  • PoS inflation = 10% maximum

Furthermore, subsequent conversations established:

  • unit denomination = 10^6 (fundamental tokens per whole NAM)
@brentstone brentstone added the PoS label Sep 20, 2022
@brentstone brentstone self-assigned this Sep 20, 2022
@brentstone
Copy link
Collaborator Author

@cwgoes @adrianbrink @tzemanovic - do we want the same slash rate for duplicate vote attacks and light client attacks?

@cwgoes
Copy link
Contributor

cwgoes commented Oct 2, 2022

@cwgoes @adrianbrink @tzemanovic - do we want the same slash rate for duplicate vote attacks and light client attacks?

Yes - both varying from 0 to 1 (100%) according to the cubic slashing function.

This was referenced Oct 25, 2022
phy-chain pushed a commit to phy-chain/namada that referenced this issue Mar 1, 2024
)

Changes injected and content scripts to read the version from
package.json instead of src/manifest/_base.json.
phy-chain pushed a commit to phy-chain/namada that referenced this issue Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants