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

Check for storage collisions in metadata #575

Open
HCastano opened this issue May 23, 2022 · 0 comments
Open

Check for storage collisions in metadata #575

HCastano opened this issue May 23, 2022 · 0 comments

Comments

@HCastano
Copy link
Contributor

As a follow up to use-ink/ink#1217 we'll want cargo-contract
to go through the contract's metadata and determine whether or not any storage collisions
arise. While the probably of this is quite low, the impact of a storage collision would
be problematic for anyone interacting with the smart contract.

See this comment for more context: use-ink/ink#1134 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@HCastano