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

Feat/core v20 hardfork activation height #56

Merged
merged 2 commits into from
Dec 8, 2023
Merged

Feat/core v20 hardfork activation height #56

merged 2 commits into from
Dec 8, 2023

Conversation

pankcuf
Copy link
Collaborator

@pankcuf pankcuf commented Dec 8, 2023

Issue being fixed or feature implemented

  • Set core v0.20 hard fork activation height to 1987776
  • Bump up protocol version to 70230
  • Bump up podspec and crate version to 0.4.16

What was done?

How Has This Been Tested?

Breaking Changes

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

@pankcuf pankcuf requested a review from a team December 8, 2023 09:07
Syn-McJ
Syn-McJ approved these changes Dec 8, 2023
View reviewed changes
Copy link
Member

@Syn-McJ Syn-McJ left a comment

Choose a reason for hiding this comment

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

Looks good

@pankcuf pankcuf merged commit 8a8c03c into main Dec 8, 2023
1 of 2 checks passed
@Syn-McJ Syn-McJ deleted the feat/core-v20-hardfork-activation-height branch June 21, 2024 06:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Syn-McJ Syn-McJ Syn-McJ approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@pankcuf @Syn-McJ