Repository navigation
Record the v3 mainnet package address - #149
Merged
Merged
Conversation
The upgrade landed at 0x91959c5ec15155dab3005c66e53e92b4dd946563a06a27a2a972a174d1e0683f (on-chain version 3). Published.toml is what the next upgrade and verify-source use, and the example scripts call the latest package id.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem / goal
The mainnet upgrade of deeptrade-core landed at
0x91959c5ec15155dab3005c66e53e92b4dd946563a06a27a2a972a174d1e0683f(on-chain version 3).Published.tomland the example scripts still pointed at the v2 package, so the next upgrade andverify-sourcewould target the wrong address.Approach
Set
published-atto the new package id and bumpversionto 3. PointDEEPTRADE_CORE_PACKAGE_IDat the same address, and append it to the README package-id list.original-idstays the v1 package.Risk & blast radius
Example scripts that build Move calls now target v3.
original-idand the UpgradeCap are unchanged. This does not retarget the SDK or the indexer.How to verify
Published.tomlpublished-atmatches the on-chain package at version 3examples/constants.tslatest id matchespublished-atoriginal-idis still0xc10d536b6580d809711b9bb8eee3945d5e96f92a346c84d74ff7a0697e664695Docs
README package-id list updated. No other doc change; the post-upgrade steps in
docs/upgrade-provenance.mdare what this follows.Created-with: local-agent