-
Notifications
You must be signed in to change notification settings - Fork 501
DeployWrappedNative
: adding wrapping & unwrapping
#2963
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
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
0d1ac89
to
52151cf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's discuss in our 1:1
By wrapping your native token (e.g., AVAX), you ensure compatibility with these systems. | ||
<CheckWalletRequirements configKey={[ | ||
WalletRequirementsConfigKey.EVMChainBalance | ||
]}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use container that is including the wallet requirements check (see other tools)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
owen said to now use container for or new metadata component
const allowance = async (owner: string, spender: string): Promise<string> => { | ||
if (!publicClient || !contractAddress) throw new Error('Contract not ready'); | ||
|
||
const allowanceAmount = await publicClient.readContract({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we shouldn't use publicClient anymore.
use avalancheWalletClient
from useWallet
hook. We have viem client in it.
No description provided.