-
Notifications
You must be signed in to change notification settings - Fork 1
feat: match across zero address output tokens #29
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
Conversation
Go Test coverage is 56.0 %\ ✨ ✨ ✨ |
chains/evm/message/across.go
Outdated
@@ -237,6 +245,15 @@ func (h *AcrossMessageHandler) minimalConfirmations(d *events.AcrossDeposit) (ui | |||
return 0, err | |||
} | |||
|
|||
if common.Bytes2Hex(d.OutputToken[:]) == ZERO_ADDRESS { |
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.
isn't output token actually bytes32 and not an address?
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 checked contract and tested on sepolia.
It is address right now.
I guess they didn't update it yet.
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.
but you have defined it as bytes32:
OutputToken [32]byte |
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.
The event is [32]byte, but the function on hub pool returns address.
I convert the address to back to [32]byte to assign to the event if needed.
Go Test coverage is 56.0 %\ ✨ ✨ ✨ |
Description
Related Issue Or Context
Closes: #24
How Has This Been Tested? Testing details.
Types of changes
Checklist: