-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[Refactor]: x/auth/tx and x/tx should converge on gogoproto usage. #20431
Comments
@tac0turtle i would like to take on this |
yes, we would love the help ❤️ |
hey guys, I’m having a hard time with this. I don’t see an easy way to avoid a dependency on the SDK in x/tx. If we move tx there, there’s a dependency with coin and multisigs bitarray, so those should be defined in x/tx. Furthermore, there are functions defined over types in tx.proto that make use of codec and pubkey interfaces. I see two options here:
There’s also a call to AccAddressFromBech32 that may need an address.Codec to avoid. |
Is there an RFC coming? Is it still in progress? |
I have this on hold to be honest. |
There is duplicate logic in both x/tx/decode and the x/auth/tx packages. Since the decision to support gogoproto throughout the SDK (as specified in
core/transaction
below)cosmos-sdk/core/transaction/transaction.go
Line 8 in 1f06f5b
These two packages can be simplified and collapsed into one simple implementation in x/tx. An initial exploration of this was done here in #20424 and integrated in #20428.
The result will be a lot of deleted code and much less mental overhead when reasoning about transactions in the SDK. The signing code in x/tx can and should remain the same, as shown in #20424 reflection over gogotypes as input is possible through the use of dynamic messages.
The text was updated successfully, but these errors were encountered: