fix: ensure recipients on Sealevel warp transfers are 32 bytes (#4760)
### Description Ran into an issue trying to send from Sealevel -> Cosmos where the recipient was 20 bytes. This hasn't been an issue so far because: - no previous Sealevel -> Cosmos transfers have been done in the UI - Sealevel -> EVM transfers are successful bc `addressToBytes` actually pads the 20 byte EVM addresses to 32 bytes - Sealevel -> Sealevel transfers are fine because Sealevel addys are always 32 bytes ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->pull/4751/head
parent
a36fc5fb27
commit
5fd4267e79
@ -0,0 +1,6 @@ |
||||
--- |
||||
'@hyperlane-xyz/utils': patch |
||||
'@hyperlane-xyz/sdk': patch |
||||
--- |
||||
|
||||
Supported non-32 byte non-EVM recipients when sending warps from Sealevel |
Loading…
Reference in new issue