julienrbrt
julienrbrt
I believe it closes https://github.com/cosmos/cosmos-sdk/issues/13782 too right?
Can we add a changelog? Then, given the discussion from the community call, we can add automerge.
I will re-open this when we'll start working on this.
We cannot change the number of arguments in `address.Module()` I think, as we don't want all group policy addresses to change.
> I have done a pass to generalize it and include @josef-widder comment. The only pending comment is whether to use agnostic-language pseudocode or simply go. Also, we should decide...
LGTM as well. One thing I'd like to do eventually it is still a migration of a v0.46 chain with data to v0.47 for checking if all params are properly...
For the IAVL Viewer, we've already created a tracking issue here: https://github.com/cosmos/iavl/issues/567 as it was as well requested in our DEV UX calls.
Given that `TallyResut` just call `keeper.Tally`, closing this as dup of https://github.com/cosmos/cosmos-sdk/issues/10353, so we have one tracking issue for the improvements.
From the SDK perspective what were you thinking of? I don't think we can do much more that adding an advice in the docs. A small `:::warning` https://docs.cosmos.network/main/run-node/run-production here should...
Now Cosmovisor depends on x/upgrade directly, which will probably be tagged after v0.48. Let's wait for shortly after Eden then. EDIT: prob ok to use a pseudo version actually