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

wrong format used for contract ID when scheduling Soroban network upgrades #4246

Closed
MonsieurNicolas opened this issue Mar 14, 2024 · 0 comments · Fixed by #4247
Closed

wrong format used for contract ID when scheduling Soroban network upgrades #4246

MonsieurNicolas opened this issue Mar 14, 2024 · 0 comments · Fixed by #4247
Assignees
@sisuresh
Labels
bug

Comments

@MonsieurNicolas
Copy link
Contributor

After arming a phase 2 upgrade, core info returns

      "status" : [
         "Armed with network upgrades: upgradetime=2024-03-19T16:00:00Z, configupgradesetkey = {\n  contractID = bcc748055098ece70fb97dc327141083a772b33c07220cc16c134642ec4fc4e9,\n  content
Hash = 2b3ea4cc865ace6e6c2ceaf9e19b1301cd09191d58fc21f889bc9b62a1d5c6f5\n}\n"
      ]

the contractID should be the strkey CC6MOSAFKCMOZZYPXF64GJYUCCB2O4VTHQDSEDGBNQJUMQXMJ7COSZSN instead

missed when addressing #4184
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sisuresh sisuresh

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Define custom cereal override for ConfigUpgradeSetKey and use it sisuresh/stellar-core
2 participants
@MonsieurNicolas @sisuresh