Skip to content
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.

Consider using epochs #116

Open
adlerjohn opened this issue Jan 27, 2021 · 4 comments
Open

Consider using epochs #116

adlerjohn opened this issue Jan 27, 2021 · 4 comments
Labels
investigation Investigation required.

Comments

@adlerjohn
Copy link
Member

adlerjohn commented Jan 27, 2021 •
edited by liamsi
Loading

#114 (comment)
@adlerjohn adlerjohn added the investigation Investigation required. label Jan 27, 2021
@liamsi
Copy link
Member

liamsi commented Feb 4, 2021 •
edited
Loading

I'm very much in favour of this.
Also, see:

@liamsi liamsi added this to To do in Mainnet and beyond via automation Mar 16, 2021
@liamsi
Copy link
Member

liamsi commented Jun 27, 2021

See also: https://github.com/osmosis-labs/osmosis/blob/0509525b6cafb0c1c5b41c06c6e1dd13c8e7a98b/x/epochs/spec/README.md#L11-L10 (already deployed in production / used in https://app.osmosis.zone/pools

@Wondertan
Copy link
Member

Would it be correct to say that this change is just about recalculating stake not per each block, but per some amount of blocks(epoch)?

@adlerjohn
Copy link
Member Author

Not just "voting power" (to use Tendermint lingo), but potentially also things like rewards and managing slashing/jailing. But in large part, yes it's mostly about changing the validator set each epoch rather than each block.

@liamsi liamsi removed this from To do in Mainnet and beyond Dec 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
investigation Investigation required.
Projects
No open projects
Celestia Node
Status: TODO
Milestone
No milestone
Development

No branches or pull requests
3 participants
@adlerjohn @liamsi @Wondertan