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

Add 32 byte chainwork support #368

Merged
merged 3 commits into from
Dec 12, 2024

Conversation

nathanieliov
Copy link
Contributor

@nathanieliov nathanieliov commented Dec 9, 2024

Description

  • Bump version to 0.14.4-rsk-17-SNAPSHOT
  • Add support to 32-byte chainwork to ThinConverter class

How Has This Been Tested?

Unit tests

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • Tests for the changes have been added (for bug fixes / features)
  • Requires Activation Code (Hard Fork)

rskj:32-byte-chainwork-support-integration

@nathanieliov nathanieliov requested a review from a team as a code owner December 9, 2024 22:11
Copy link

github-actions bot commented Dec 9, 2024

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Manifest Files

@marcos-iov marcos-iov force-pushed the 32-byte-chainwork-support-integration branch from 1d082b2 to 202f8ef Compare December 12, 2024 13:12
@marcos-iov marcos-iov merged commit 338f3a5 into master Dec 12, 2024
12 checks passed
@marcos-iov marcos-iov deleted the 32-byte-chainwork-support-integration branch December 12, 2024 15:25
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.

3 participants