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

Support for stacking #7

Open
uhbif19 opened this issue Mar 9, 2024 · 3 comments
Open

Support for stacking #7

uhbif19 opened this issue Mar 9, 2024 · 3 comments

Comments

@uhbif19
Copy link
Contributor

uhbif19 commented Mar 9, 2024

This is similar to slotting. Real consensus has slots moving, and our emulator should have slot changing API instead.

Same goes for stacking rewards. We should probably have simple API for selection of slotting leader, not really conforming PoS algorithm.

We could use PoS docs to check it working correctly.

@uhbif19
Copy link
Contributor Author

uhbif19 commented Mar 28, 2024

@euonymos

Seems like there is some Stacking logic and params in ledger. So may be it already does stacking somehow?

https://github.com/IntersectMBO/cardano-ledger/blob/c2fd86ea034a8021766a794cd06f888b9cfbf62c/eras/shelley/impl/src/Cardano/Ledger/Shelley/LedgerState/IncrementalStake.hs

@euonymos
Copy link
Member

You are quite right, the ledger is capable of handling the state of certificates (from what I saw) and probably something else. We have to use this. In terms of emulating, I would say we need to emulate a set of SPOs that can used to delegate funds (and related things) @uhbif19 .

@euonymos euonymos changed the title Add stacking emulation API Stacking emulation Mar 28, 2024
@euonymos
Copy link
Member

I have some doubts about how we should do that, but the bottom line is to try to reuse the ledger as far as possible.

@euonymos euonymos changed the title Stacking emulation Support for stacking Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants