-
Notifications
You must be signed in to change notification settings - Fork 3
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: track deploy_token
calls to bind token
#206
base: main
Are you sure you want to change the base?
Conversation
…-transfer-changes
omni-relayer/src/workers/near.rs
Outdated
) | ||
.await; | ||
|
||
if vaa.is_none() { |
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.
This part looks similar to a section of the claim_fee function. Maybe the common code can be extracted?
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.
I've splitted core methods into handle_{chain}_fin_transfer
and handle_{chain}_deploy_token_event
in b66fac6. Technically I could extract this, but IMO after doing such refactor it would be harder to follow the logic. Let me know if you think that it's worth to extract it even more
}, | ||
} | ||
|
||
pub async fn bind_token( |
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.
Can we split this function on a few parts? For example handle_evm_bind_tokens and handle_solana_bind_tokens. This function turned out to be very long.
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.
Fixed in b66fac6
closes #207