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.

Sign up for GitHub

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

Jump to bottom

Implement data put and get endpoints #360

Closed
muneeb-ali opened this issue Mar 23, 2017 · 3 comments
Closed

Implement data put and get endpoints #360

muneeb-ali opened this issue Mar 23, 2017 · 3 comments
Assignees
@jcnelson
Labels
feature Brand new functionality. New pages, workflows, endpoints, etc. locked

Comments

@muneeb-ali
Copy link
Member

We need to finalize the Core API PUT and GET functionality for persistent storage.
@muneeb-ali muneeb-ali added feature Brand new functionality. New pages, workflows, endpoints, etc. storage labels Mar 23, 2017
@muneeb-ali muneeb-ali added this to the Blockstack v0.14.2 milestone Mar 23, 2017
@jcnelson
Copy link
Member

This has stabilized. Where's the best place to document it? The API table we have in the api/README.md file isn't expressive enough, since we need to also document how to construct the inputs and how to parse the outputs.

@muneeb-ali
Copy link
Member Author

@jcnelson Closing this and starting a new issue for documentation.

@muneeb-ali muneeb-ali mentioned this issue Apr 4, 2017
Closed
jcnelson added a commit that referenced this issue Jan 13, 2023
@jcnelson
fix: the heaviest affirmation map calculation is different in epoch 2…
c71ee0c 
….05 -- it's the same as the sortition affirmation map.

Normally, there's no difference because the heaviest block-commit by BTC spend (the 2.1 rule) is the same as the Stacks block-commit with the most confirmations (the 2.05 rule). However, in the current testnet, this is not the case for reward cycle #360. This means that once the 2.1 rules take effect, the node will get stuck -- it will think that the stacks and sortition affirmation maps are not in sync with the heaviest affirmation map, and the node will never sync as a result.

This fix makes it so the heaviest affirmation map -- and by extension, the canonical affirmation map -- is calculated from the sortition affirmation map for reward cycle in epoch 2.05 and earlier.
@blockstack-devops
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Nov 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jcnelson jcnelson

Labels
feature Brand new functionality. New pages, workflows, endpoints, etc. locked
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jcnelson @muneeb-ali @blockstack-devops