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

[RPC] report PoX anchor block once discovered when in Nakamoto #5444

Open
jcnelson opened this issue Nov 10, 2024 · 0 comments
Open

[RPC] report PoX anchor block once discovered when in Nakamoto #5444

jcnelson opened this issue Nov 10, 2024 · 0 comments

Comments

@jcnelson
Copy link
Member

Right now, the /v2/info handler reports the cached anchor block information in the PeerNetwork instance. This in turn is loaded via a SortitionHandleConn, which reads the selected anchor block from the MARF.

The trouble is, this record of the anchor block information is only stored at the start of the relevant reward cycle. While this was okay in epoch 2.x, in Nakamoto we know the anchor block after the second sortition in the prepare phase.

The PeerNetwork code should load the anchor block from the Nakamoto chainstate when caching anchor block data for a Nakamoto reward cycle.

@github-project-automation github-project-automation bot moved this to Status: 🆕 New in Stacks Core Eng Nov 10, 2024
@saralab saralab added this to the Nakamoto-3.0.x milestone Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Status: 🆕 New
Development

No branches or pull requests

2 participants