Repository navigation
fix(contract): require configured bridge addresses - #557
Closed
h1065153539-create wants to merge 1 commit into
Closed
h1065153539-create wants to merge 1 commit into
h1065153539-create wants to merge 1 commit into
Conversation
Contributor
|
@h1065153539-create — issue #510 isn't currently assigned to anyone, so I can't merge this one per repo policy. Could you ask a maintainer to assign it to you (or to whoever picks it up), then I'll merge. 👍 |
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.
Closes #510 by distinguishing chains that merely exist in storage from chains that have an explicitly configured bridge.
Changes:
bridge_configuredtoChainConfigupdate_bridge_addressis calledLocal Rust verification was attempted, but the Windows toolchain on this machine is missing
link.exe, so full build/test execution is blocked by environment.