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

Bank epoch schedule is not coupled to the epoch schedule sysvar #34137

Closed
jstarry opened this issue Nov 17, 2023 · 1 comment
Closed

Bank epoch schedule is not coupled to the epoch schedule sysvar #34137

jstarry opened this issue Nov 17, 2023 · 1 comment
Labels
stale [bot only] Added to stale content; results in auto-close after a week.

Comments

@jstarry
Copy link
Member

jstarry commented Nov 17, 2023

Problem

Unlike other sysvars, the epoch schedule sysvar account is only ever updated during genesis. This is probably fine most of the time since the epoch schedule currently can't be changed. However, it seems that devnet was started with epochs that were only 8,192 slots long (reflected here: https://explorer.solana.com/address/SysvarEpochSchedu1e111111111111111111111111?cluster=devnet) which doesn't match the bank epoch schedule which states that epochs are the typical 432k slots long.

This means that devnet programs cannot get accurate epoch schedule data through the epoch schedule sysvar. Also, if the epoch schedule ever changes in the future (like perhaps the leader_schedule_slot_offset), those changes wouldn't be reflected in the sysvar.

Proposed Solution

Update the epoch schedule sysvar at the beginning of each epoch

@github-actions github-actions bot added the stale [bot only] Added to stale content; results in auto-close after a week. label Nov 18, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 26, 2024
@jstarry jstarry reopened this Nov 26, 2024
Copy link
Contributor

This repository is no longer in use. Please re-open this issue in the agave repo: https://github.com/anza-xyz/agave

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale [bot only] Added to stale content; results in auto-close after a week.
Projects
None yet
Development

No branches or pull requests

1 participant