Skip to content
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: Valued express example #176

Draft
wants to merge 9 commits into
base: main
Choose a base branch
from
Draft

feat: Valued express example #176

wants to merge 9 commits into from

Conversation

benjamin852
Copy link
Contributor

added valued express executable tx. Also made a few (very minor) alterations to express token tx

@benjamin852 benjamin852 requested a review from npty April 2, 2024 18:04
Copy link
Member

@npty npty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you pls also add the folder name to the tests? I think just add call-contract-with-valued-express would work.

@@ -1,8 +1,9 @@
//SPDX-License-Identifier: MIT
// //SPDX-License-Identifier: MIT
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo? Double comment?

@@ -0,0 +1,52 @@
# Call Contract with Valued Express

This is an example of sending an express transaction where the value is not a cross chain asset transfer using `callContractWithToken()`. Rather the value is in the `payload` of the transaction. Once the payload has been decoded and derived to a specific contract address that value can be transfered to the end receiver.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reverse this to make the first sentence of the readme what it IS rather than what it ISN'T.

# Call Contract with Valued Express

This is an example of sending an express transaction where the value is not a cross chain asset transfer using `callContractWithToken()`. Rather the value is in the `payload` of the transaction. Once the payload has been decoded and derived to a specific contract address that value can be transfered to the end receiver.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add details about how it works at a high level? An overview? I hope we will also have corresponding updates in the docs?


```bash
npm run deploy evm/call-contract-with-valued-express local
npm run execute evm/call-contract-with-token local "Avalanche" "Fantom" 100 0xBa86A5719722B02a5D5e388999C25f3333c7A9fb
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this right? Deploying a different contract that we execute?

@benjamin852 benjamin852 marked this pull request as draft April 16, 2024 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants