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

chore: sync paseo chainspec changes #853

Merged
merged 2 commits into from
Jan 22, 2025
Merged

chore: sync paseo chainspec changes #853

merged 2 commits into from
Jan 22, 2025

Conversation

ggera
Copy link
Member

@ggera ggera commented Jan 20, 2025

fixes NO TICKET

ss58format of the chain spec in source repo is changed

Metadata Diff to Develop Branch

Peregrine Diff
Spiritnet Diff

Checklist:

  • I have verified that the code works
    • No panics! (checked arithmetic ops, no indexing array[3] use get(3), ...)
  • I have verified that the code is easy to understand
    • If not, I have left a well-balanced amount of inline comments
  • I have left the code in a better state
  • I have documented the changes (where applicable)
    • Either PR or Ticket to update the Docs
    • Link the PR/Ticket here

Sorry, something went wrong.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@ggera ggera requested a review from ntn-x2 January 20, 2025 16:06
@ggera ggera self-assigned this Jan 20, 2025
@ggera ggera marked this pull request as draft January 20, 2025 17:02
@ntn-x2 ntn-x2 changed the title chore:sync paseo chainspec changes chore: sync paseo chainspec changes Jan 21, 2025
@ggera ggera marked this pull request as ready for review January 21, 2025 10:04
@ggera ggera requested a review from Ad96el January 21, 2025 10:24
@ggera ggera merged commit f9b7328 into develop Jan 22, 2025
16 of 17 checks passed
@ggera ggera deleted the paseo-chainspec branch January 22, 2025 10:35
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.

None yet

3 participants