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

feat: burn op definition and storage for vote-for-agg-key #4376

Merged
merged 36 commits into from Mar 13, 2024

Conversation

hstove
Copy link
Contributor

@hstove hstove commented Feb 14, 2024

Based on my notes in this discussion, this PR implements a burn op for vote-for-aggregate-key.

This PR is currently a work in progress. The code exists for parsing and storing this new burn op, but I've yet to actually process the burn op by making a Clarity tx.

This is built on top of #4360, because that PR has the updated function signature for vote-for-aggregate-public-key.

jcnelson and others added 15 commits February 6, 2024 14:19
…aleView if the rc_consensus_hash doesn't match
…asn't completed a full state-machine pass yet
…move that outer error before acting on a blanket `Ok(_)` / `Err(_)` match
Copy link

codecov bot commented Feb 14, 2024

Codecov Report

Attention: Patch coverage is 92.28371% with 99 lines in your changes are missing coverage. Please review.

Project coverage is 83.28%. Comparing base (067633d) to head (e3a76f7).
Report is 34 commits behind head on next.

Additional details and impacted files
@@            Coverage Diff             @@
##             next    #4376      +/-   ##
==========================================
+ Coverage   83.22%   83.28%   +0.05%     
==========================================
  Files         452      453       +1     
  Lines      326058   327328    +1270     
  Branches      323      323              
==========================================
+ Hits       271359   272610    +1251     
- Misses      54691    54710      +19     
  Partials        8        8              
Files Coverage Δ
stackslib/src/burnchains/bitcoin/bits.rs 94.03% <100.00%> (ø)
stackslib/src/chainstate/burn/db/sortdb.rs 91.94% <100.00%> (+0.09%) ⬆️
...c/chainstate/burn/operations/test/serialization.rs 100.00% <100.00%> (ø)
stackslib/src/chainstate/nakamoto/mod.rs 83.47% <100.00%> (+0.06%) ⬆️
stackslib/src/chainstate/stacks/db/accounts.rs 91.50% <100.00%> (+<0.01%) ⬆️
stackslib/src/chainstate/stacks/db/mod.rs 84.19% <100.00%> (+0.05%) ⬆️
stackslib/src/net/mod.rs 72.91% <ø> (-0.05%) ⬇️
stackslib/src/chainstate/burn/mod.rs 94.19% <0.00%> (-0.25%) ⬇️
stackslib/src/chainstate/burn/db/processing.rs 86.47% <33.33%> (-0.92%) ⬇️
...t/stacks-node/src/burnchains/mocknet_controller.rs 71.24% <0.00%> (-1.89%) ⬇️
... and 7 more

... and 18 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 067633d...e3a76f7. Read the comment docs.

[CI] fix error in release step that generates checksums
Base automatically changed from feat/4354-aggregate-key to next February 21, 2024 20:50
@hstove hstove marked this pull request as ready for review February 21, 2024 23:58
@hstove hstove linked an issue Feb 21, 2024 that may be closed by this pull request
obycode
obycode previously approved these changes Mar 4, 2024
Copy link
Contributor

@obycode obycode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm! 🚀

@saralab saralab requested a review from setzeus March 5, 2024 14:52
@hstove hstove requested a review from obycode March 12, 2024 14:27
@hstove
Copy link
Contributor Author

hstove commented Mar 12, 2024

Ok, finally figured out why my Nakamoto integration test was failing. Ready for reviews now @obycode @8marz8 @setzeus

Copy link
Contributor

@obycode obycode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@hstove hstove added this pull request to the merge queue Mar 13, 2024
Merged via the queue into next with commit 9058e22 Mar 13, 2024
2 checks passed
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

Successfully merging this pull request may close these issues.

[Nakamoto] Vote for aggregate public key on Bitcoin
5 participants