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

Add support for fetching verified ABI from registry for forc call #6893

Open
zees-dev opened this issue Feb 5, 2025 · 0 comments
Open

Add support for fetching verified ABI from registry for forc call #6893

zees-dev opened this issue Feb 5, 2025 · 0 comments
Labels
forc forc-call Everything related to the `forc-call` plugin in `forc-client` package forc-registry Everything to do with forc-registry; IPFS sourcing, package registery team:tooling Tooling Team

Comments

@zees-dev
Copy link
Contributor

zees-dev commented Feb 5, 2025

forc call can currently utilize an ABI provided as local path or from URL.
We want to update this behaviour such that the ABI can also be provided from verified ABI registry (when it's ready).

  • Also, the default behaviour should be this; i.e. if no ABI is provided explicitly in forc call, we should try fetch the ABI from registry.
@zees-dev zees-dev added forc forc-call Everything related to the `forc-call` plugin in `forc-client` package forc-registry Everything to do with forc-registry; IPFS sourcing, package registery team:tooling Tooling Team labels Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
forc forc-call Everything related to the `forc-call` plugin in `forc-client` package forc-registry Everything to do with forc-registry; IPFS sourcing, package registery team:tooling Tooling Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant