-
Notifications
You must be signed in to change notification settings - Fork 2
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 eth-weth example to readme #53
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
export function generateStakeAction( | ||
userAddress: Address, | ||
value: bigint, | ||
): CrossChainAction { | ||
return { | ||
target: STAKE_CONTRACT.address, | ||
callData: generateStakeCallData(userAddress), | ||
value, | ||
}; | ||
} | ||
|
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.
deleting unused function
packages/sdk/README.md
Outdated
|
||
> This follows the logic in the example app. | ||
|
||
To implement this feature, we need to bridge either ETH or WETH from our origin chain to our destination chain. Across will always send WETH to the recipient on the destination chain, **unless the recipient is an EOA**. For our use-case, we want to stake native ETH, moreover we want to do this in one step. For this we recommend using Across's MulticallHandler contract (or deploying your own). |
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.
Please check this information is accurate
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.
It does feel a bit verbose now 🤔 I think it might be better to either change the example app to support USDC or rewrite the guide section in the README to mirror only the example app. wdyt?
Yeah I agree this is too verbose. The example app uses eth/weth precisely because it can be a confusing implementation since you have to update calldata AND value when building your cross-chain actions. So maybe it does make sense to just use that example int he README? |
Yeah, agree let's do that. In future iterations, we can add other examples as well. |
closes ACX-3033