-
Notifications
You must be signed in to change notification settings - Fork 61
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
Migrate to use templating: Value #95
Comments
@fadeev, can you assign this to me? |
@1337-ishaan I recommend the following process:
Thanks on working on this! |
@fadeev, can you just have a look at https://github.com/1337-ishaan/template, for unknown reason the transaction keeps failing. Goerli Transaction hash: |
@1337-ishaan can you, please, verify the contract? If this is cross-chain messaging (Value) you need to set the interactors. |
I have already set the interactors, due to some reason it doesn't seem to work, I'll just verify the contract once! |
@1337-ishaan are you working on this, or should I unassign this issue? |
@fadeev, was stuck into something else, I'll surely get this done in a week. Apologies for the inconvenience caused. |
@1337-ishaan no worries, just wanted to make sure the status of the issue is updated. The value tutorial in its current state uses ZETA for fees, which is one of the ways to pay for cross-chain gas fees. I propose we switch to using native gas token for fees, similar to all other tutorials. So, instead of something like this: You would have something like this: This is the default behavior of the |
The reason I mentioned this is that in the next version of the toolkit you would be able to customize the messaging command and choose which method you want to use for code generation (ZETA or native gas token): I want the existing tutorial to keep using native tokens (the default behavior), and I'll write a separate tutorial that shows how to use this new functionality. |
Works totally! Will get this done. |
@1337-ishaan I needed to update tutorials pretty asap, so I had to do it myself in the following PRs: #173 Sorry it couldn't wait longer. If you have any suggestions, feel free to leave them in the PRs above. Thank you! |
@fadeev, apologies for the inconvinience cause, was just busy understanding the zetachain technical stacks & code respectively. Will surely go through this. |
No description provided.
The text was updated successfully, but these errors were encountered: