You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ethereum bridge endpoints currently returning a borsh encoding of the ABI encoding of the requested data should just return the borsh encoded raw data (i.e. going from borsh(abi(data)) to borsh(data)). This will greatly simplify code in Namada, and avoid some serialization roundtrip costs in Namada clients.
The text was updated successfully, but these errors were encountered:
Ethereum bridge endpoints currently returning a borsh encoding of the ABI encoding of the requested data should just return the borsh encoded raw data (i.e. going from
borsh(abi(data))
toborsh(data)
). This will greatly simplify code in Namada, and avoid some serialization roundtrip costs in Namada clients.The text was updated successfully, but these errors were encountered: