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
{{ message }}
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
#183 bumped the SDK version to 0.38.1 but since simulation logic was broken I had to switch to a specific commit from master. Because of this, protobuf changes also affected Ethermint and I'm now getting an annoying panic because the Ethereum Secp256k1 key is not supported by the codec:
I traced the error and is due to the fact that StdSignature on the SDK uses the amino codec to marshal the pubkey bytes. I then tried to register the key type to the amino codec using the following:
add support to include the concrete options on the SDK codec. Not sure if this is counterintuitive since amino is being deprecated.
use application-specific hybrid codec instead of the Codec defined on cosmos/cosmos-sdk/codec/amino.go.
not use amino at all and switch to proto. Will likely depend on SDK work and we'll have to provide support with that and ensure things don't break unexpectedly.
@alexanderbez if you have some ideas or thoughts on how to fix this and what's the best way to proceed from the SDK
#183 bumped the SDK version to 0.38.1 but since simulation logic was broken I had to switch to a specific commit from
master
. Because of this, protobuf changes also affected Ethermint and I'm now getting an annoying panic because the Ethereum Secp256k1 key is not supported by the codec:I traced the error and is due to the fact that
StdSignature
on the SDK uses the amino codec to marshal the pubkey bytes. I then tried to register the key type to the amino codec using the following:Nevertheless, this caused another issue with priorities:
The SDK doesn't allow you tho set
amino.ConcreteOptions
to define priorities. I'm still wondering what's the best way to proceed from hereThe text was updated successfully, but these errors were encountered: