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.

Sign up for GitHub

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

Jump to bottom

Axelar Relayer 1st version #5

Merged
merged 44 commits into from
Jun 18, 2024
Merged

Axelar Relayer 1st version #5

merged 44 commits into from
Jun 18, 2024

Conversation

raress96
Copy link
Collaborator

@raress96 raress96 commented Jan 8, 2024 •
edited
Loading

This supports:

  1. MultiversX -> Other chain cross chain transactions
    • Events Notifier used to listen for CGP Gateway contract events
    • store data in the database
    • submits data to Axelar Amplifier gRPC (WIP, real API not available yet)
    • also processes gas service events and saves them in the database (nothing else done regarding gas at the moment, gas won't be handled for 1st version)
    • NOTE: still need to process express gas service events (out of scope currently)
  2. MultiversX contract calls
    • uses Events Notifier to handle approve contract calls events from CGP Gateway
    • the respective transaction is executed on MultiversX and retried up to 3 times if it fails
    • payload is retrieved from Axelar Amplifier gRPC (WIP)
  3. Other chain -> MultiversX cross chain transactions
    • listens to CosmWASM contract events using Axelar Amplifier gRPC (WIP)
    • executes transaction on MultiversX (calls CGP Gateway contract)
  4. Gas monitoring
    • checks the Gas Service contract and claims funds if above a certain threshold
    • checks the wallet used to execute transactions that is has enough gas, if not it raises an alert
    • NOTE: The relayer wallet is the same account that can interact with the Gas Service

For reference:
https://docs.axelar.dev/learn/network/flow
https://github.com/buidly/sc-axelar-cgp-rs/blob/develop/gateway/README.md

raress96 and others added 30 commits December 5, 2023 16:45
@raress96
Remove unneeded nestjs template code, add apps for mvx event processo…
419767c 
…r and axelar event processor and add prisma.
@raress96
Process gateway call contract event and save data into database.
802418d
@raress96
Generate interfaces from grpc proto file and add grpc service.
32d41c9
@raress96
Add processing of gas service events and saving to database.
9613ddf
@raress96
Improvement for gas service event handling and tests for various serv…
40d7192 
…ices.
@raress96
Finish tests for gas service contract.
db4e26c
@raress96
Remove order from event processor.
018d5d1
@raress96
Process contract call approved event.
8f85884
@raress96
Start processing and sending of call contract approved transactions.
c98880e
@raress96
Working cronjobs for processing and sending contract call transactions.
6ef49f1
@raress96
Process contract call executed event.
5e89dea
@raress96
Add e2e test for call contract approved processor.
b538965
@raress96
Create cron that subscribes to axelar events and sends transactions.
63a986d
@raress96
Add test for approvals processor.
981e13c
@raress96
Add chain id as env var for simplicity.
066322e
@raress96
Merge branch 'process_multiversx_contract_calls' into process_axelar_…
3a6b65a 
…chain_events
@raress96
Merge pull request #1 from buidly/process_mvx_gateway_events
c49f718 
Process gateway call contract event and save data into database.
@raress96
Add chain id as env var for simplicity.
62d3ef9
@raress96
Merge branch 'process_multiversx_contract_calls' into process_axelar_…
8482f62 
…chain_events
@raress96
Fix pipeline.
a279f14
@raress96
Merge branch 'process_multiversx_contract_calls' into process_axelar_…
d46447d 
…chain_events
@raress96
Merge branch 'process_multiversx_contract_calls' into gas_checker
d395f35
@raress96
Create basic cron for collecting gas service fees.
ac39ba3
@raress96
Merge branch 'process_axelar_chain_events' into gas_checker
53e5e89
@raress96
Working gas checker cron and refactoring.
80a049f
@raress96
Add gas checker test.
b625875
@raress96
Merge pull request #4 from buidly/gas_checker
d0ce237 
Collect gas service fees & check wallet balance cron
@raress96
Merge pull request #3 from buidly/process_axelar_chain_events
037fd42 
Process axelar chain events & trigger gateway execute transaction
@raress96
Merge pull request #2 from buidly/process_multiversx_contract_calls
ccc16fb 
Process contract call approved event & send MultiversX transactions
@raress96
Change unsupported log index value to 0.
80046b3
raress96 and others added 13 commits January 22, 2024 16:30
@raress96
Start working on special handling for its transactions.
072f460
@raress96
Handle special its transactions that need to send egld.
36eede3
@raress96
Bug fixes and new proto file.
0ab7b29
@raress96
Basic support for processing operatorship transferred event and impro…
17afec9 
…vements.
@raress96
Properly implement operatorship transferred event handling and grpc r…
cfb3e6c 
…efactoring.
@raress96
Add test for call contract approved processor.
a3782f2
@raress96
Merge branch 'relayer_update' into develop
d576d60
@raress96
Add prisma deploy script.
a09ed64
@raress96
Updates for new amplifier api grpc definition.
104f7f7
@dragos-rebegea
Merge pull request #8 from multiversx/update_amplifier_api
c4fd97b 
Updates for new amplifier api grpc definition.
@raress96
Update amplifier proto definition with proper package.
c0be0bf
@raress96
Update for correct proto file from amplifier examples repo.
50bf850
@raress96
Update message id for amplifier.
4bb7d56
ccorcoveanu
ccorcoveanu reviewed Apr 9, 2024
View reviewed changes
apps/axelar-event-processor/src/approvals-processor/approvals.processor.service.ts

const txHash = await this.transactionsHelper.signAndSendTransaction(transaction, this.walletSigner);

await this.redisCacheService.set<PendingTransaction>(
Copy link

Choose a reason for hiding this comment

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

This is just nitpicking and maybe overthinking it, but what happens if Redis crashes and the transaction went through? - or what happens if we execute multiple times with the same executeData?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It is safe to re-execute a transaction since the contract keeps track internally of which commands are executed. We use Redis to retry the transaction in case it fails since I found this to be the easiest way.

Theoretically the executeData received will lead to a successful transaction, the only reason this can fail is because of out of gas in case transaction/cost api does not work properly, hence the increasing gas costs for each retry.

@raress96 raress96 requested a review from ccorcoveanu April 11, 2024 11:54
@raress96 raress96 merged commit ec754d5 into main Jun 18, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ccorcoveanu ccorcoveanu Awaiting requested review from ccorcoveanu

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@raress96 @ccorcoveanu @dragos-rebegea