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

Crypto import no longer recognized #748

Closed
sisyphusSmiling opened this issue Feb 14, 2025 · 1 comment
Closed

Crypto import no longer recognized #748

sisyphusSmiling opened this issue Feb 14, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@sisyphusSmiling
Copy link

Problem

Contracts were previously able to import Crypto by declaring import Crypto, but these imports now fail with "checking of imported program Crypto failed". This is probably a result of onflow/cadence#3619.

Steps to Reproduce

In a local flow project, import the Crypto contract to a Cadence script, transaction or contract. The error should arise

Acceptance Criteria

Legacy crypto imports don't break parsing.

Context

Crypto is imported into the EVM contract with the original format of import Crypto which breaks contract parsing and affects downstream dependencies. This was noticed while working on onflow/flow-evm-bridge#143

@sisyphusSmiling sisyphusSmiling added the bug Something isn't working label Feb 14, 2025
@sisyphusSmiling
Copy link
Author

Closing as seems to have resolved itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

1 participant