Semantic versioning is used in upgradable contracts #28
Conversation
This file contains 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
Phanco
reviewed
Jan 16, 2024
|
Other parts look good 👍 |
Phanco
approved these changes
Jan 16, 2024
matjazv
force-pushed
the
23-semver-upgradable-contracts
branch
from
83a5f09
to
6b7c954
Compare
sergeyshemyakov
approved these changes
Jan 17, 2024
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.
What was the problem?
This PR resolves #23.
How was it solved?
ISemverinterface was used in currently upgradable contract -Claim contract.version()function which may be called by 3rd party web3 applications to check to which version of smart contract are they communicate with.How was it tested?