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.

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

Use new bridge config #33

Merged
merged 2 commits into from
Jun 15, 2023
Merged

Conversation

alistair-singh
Copy link

Resolves: SNO-512
Snowfork companion: Snowfork/snowbridge#860

AssetFilter::ByMultiLocation(
MultiLocationFilter::default()
.add_starts_with(EthereumLocation::get())
) // TODO: Change to registry contract address. For now accept any ethereum address.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it safe for us to trust any multilocation that is from Ethereum as a reserve location? I think so because only contracts that have SUBMIT_ROLE permission will be able to enqueue messages. However, another contract with SUBMIT_ROLE privilege could send through a Mint message and this predicate would not guard against that.

@alistair-singh alistair-singh marked this pull request as ready for review June 14, 2023 22:34
@alistair-singh alistair-singh merged commit f1fcc16 into snowbridge Jun 15, 2023
@alistair-singh alistair-singh deleted the alistair/fix-bridge-config branch June 15, 2023 19:50
alistair-singh added a commit that referenced this pull request Jun 15, 2023
alistair-singh added a commit that referenced this pull request Jun 15, 2023
@alistair-singh alistair-singh mentioned this pull request Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant