forked from axelarnetwork/axelar-amplifier
-
Notifications
You must be signed in to change notification settings - Fork 0
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: contract_call event capture #20
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ctoyan
changed the title
draft: feat: call contract capture
feat: call contract capture
Apr 30, 2024
ctoyan
changed the title
feat: ContractCall event capture
feat: contract_call event capture
May 3, 2024
ctoyan
commented
May 5, 2024
tomekpiotrowski
approved these changes
May 7, 2024
ctoyan
changed the title
feat: contract_call event capture
feat: contract_call event capture
May 10, 2024
ctoyan
added a commit
that referenced
this pull request
Jun 10, 2024
ctoyan
added a commit
that referenced
this pull request
Jun 10, 2024
ctoyan
added a commit
that referenced
this pull request
Aug 7, 2024
ctoyan
added a commit
that referenced
this pull request
Sep 9, 2024
ctoyan
added a commit
that referenced
this pull request
Sep 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
After https://github.com/eigerco/giza-axelar-starknet/issues/77 and https://github.com/eigerco/giza-axelar-starknet/issues/78, we need to capture the ContractCall event from Starknet, in order to prepare it for verification against the Axelar message passed from the relayer.
Requirements
Todos
Steps to test manually
call_contract
on the gateway, so it can emit a ContractCall event.For example -
starkli invoke 0x055fddb9d939ab8c6cfd5a9871663457cd5b2fcb9dad9cdf464a12f1e045c4d4 call_contract str:destination_chain 4 0x4c6f6e67206c6f6e6720737472696e672c2061206c6f74206d6f72652074 0x68616e2033312063686172616374657273207468617420776f756c646e27 0x74206576656e2066697420696e2074776f2066656c74732c20736f207765 0x276c6c2068617665206174206c656173742074776f2066656c747320616e 0x6420612070656e64696e6720776f72642e 17 5 104 101 108 108 111
, which equals the following eventContractCallEvent { destination_address: "Long long string, a lot more than 31 characters that wouldn't even fit in two felts, so we'll have at least two felts and a pending word.", destination_chain: "destination_chain", source_address: "0x00b3ff441a68610b30fd5e2abbf3a1548eb6ba6f3559f2862bf2dc757e5828ca", payload_hash: 0x1c8aff950685c2ed4bc3174f3472287b56d9517b9c948127319a09a7a36deac8 }