-
Notifications
You must be signed in to change notification settings - Fork 18
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
[feat] sepolia deployment #27
Comments
I would also vote for option |
If we align with what is done on zaun side we should go with option 3. As you mentionned option 2 is still experimental and option 3 gives us more flexibility. To be fair it's not that much code. |
@EvolveArt this is just what was merged on blobstream-starknet what are your thoughts on this vs what is done in zaun? |
Hey, I can work on this after it's been discussed |
@thomas192 still around and interested to do so? Let's try with |
Hey if this is open to be taken up, I would like to work on this @glihm |
@byteZorvin yup! Which direction would you want to take for the deployment Strat? Adding this to cainome could make the deployment process very easy from rust. :) |
Yes makes sense, even I lean towards starknet.rs scripts. If this sounds good can proceed @glihm |
Sounds great @byteZorvin! You can go with |
The idea of this PR is to implement the tooling around piltover to easily deploy the contract on Sepolia.
This includes:
To achieve this task, several options:
We could give a try to the option
2
even if it still experimental and the API may change in the future. @b-j-roberts @drspacemn @EvolveArt what do you think it's better?If we go with
3
, it could be a dedicated command line tool for piltover. But more stuff to maintain.The text was updated successfully, but these errors were encountered: