You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a robust way of allowing a user to deploy any AVS Smart Contract(s) - we must allow for generic user input. Smart Contracts have completely unique inputs.
We could utilize an arbitrary input system that parses input based on a passed Smart Contract, returning an error if incorrect data is passed.
Another approach would be expecting a file with the required input, which would also be parsed based on the passed Smart Contract.
Expected Flags
Deployer/Signer
Target Network (Endpoint)
The text was updated successfully, but these errors were encountered:
I do not prefer dashes in the name of commands, instead add the protocol in the deploy command too (similar to the run command) and by default the protocol is Tangle, so the command now reads: cargo tangle blueprint deploy --protocol eigenlayer
Overview
Similar to how we are able to deploy blueprints on tangle with:
we want to be able to deploy an AVS to EigenLayer with a
cargo tangle
command.Requirements and Specs
deploy
subcommand:Expected Flags
The text was updated successfully, but these errors were encountered: