-
Notifications
You must be signed in to change notification settings - Fork 720
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
Invalid CosmWasm Core Contract Implementation of TransferFees Payload #4211
Comments
Worth noting that there are likely other implementations of this governance across the other runtimes. For example, Solana appears to conform to the whitepaper. wormhole/solana/bridge/program/src/types.rs Lines 188 to 194 in 56cf37a
|
Other implementations ✅ Algorandwormhole/algorand/wormhole_core.py Lines 283 to 301 in 83224c5
❓ AptosI couldn't immediately find where SetMessageFee or TransferFees are handled. ❌ CosmWasmwormhole/cosmwasm/contracts/wormhole/src/state.rs Lines 386 to 397 in 83224c5
✅ Ethereumwormhole/ethereum/contracts/GovernanceStructs.sol Lines 139 to 161 in 83224c5
✅ Nearwormhole/near/contracts/wormhole/src/lib.rs Lines 302 to 325 in 83224c5
✅ Solanawormhole/solana/bridge/program/src/types.rs Lines 188 to 194 in 56cf37a
✅ Suiwormhole/sui/wormhole/sources/governance/transfer_fee.move Lines 84 to 99 in 83224c5
❌ TerraTo be expected, as this was the source for CosmWasm wormhole/terra/contracts/wormhole/src/state.rs Lines 348 to 359 in 83224c5
❔ Wormchain ModuleUnsupported
|
I was looking through the white papers to determine how the
TransferFees
payload should be structured and noticed it did not match the implementation in the CosmWasm Core Contract.Links:
If you notice in the whitepaper, it defines the struct with the
Amount
first and then theRecipient
. However, the CosmWasm Core Contract defines the structure asRecipient
first and thenAmount
.The text was updated successfully, but these errors were encountered: