-
Notifications
You must be signed in to change notification settings - Fork 5
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
A0-3392 Finality checks for eth #27
Conversation
relayer/src/listeners/azero.rs
Outdated
info!(" Decoded event data:"); | ||
info!( | ||
" dest_token_address: 0x{}", | ||
hex::encode(dest_token_address) | ||
); | ||
info!(" amount: {amount}"); | ||
info!( | ||
" dest_receiver_address: 0x{}", | ||
hex::encode(dest_receiver_address) | ||
); | ||
info!(" request_nonce: {request_nonce}\n"); |
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.
log it in one line, it will make sifting through logs a lot easier in the future when we need to triangulate problems
relayer/src/listeners/azero.rs
Outdated
if let Some(name) = &event.name { | ||
if name.eq("CrosschainTransferRequest") { | ||
info!("handling A0 contract event: {event:?}"); | ||
info!("Handling A0 contract event..."); |
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.
either log some data or remove this log line, imo it's useless unless it carries some information to identify the request
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.
leaving some comments, but looks quite good already
…ptography/membrane-bridge into A0-3392-eth-finality-checks
Made a slight rework of how to limit number of tasks so that more requests can be handled at the same time. |
Adding finality checks for Ethereum side.
Comes with some fixes to encoding/decoding, enables performing funds "round trip", so bridging in both directions using relayer (tested manually).
This does not provide a proper finished implementation of crash recovery, what's to be added in later PRs:
Bounding number of tokio tasks that handle the events.(done)receive_request
transaction to reduce number of unnecessary calls during crash recovery.