---
# System prepended metadata

title: SDK Architecture Review - 2021-09-24
tags: [Cosmos SDK]

---

###### tags: `Cosmos SDK`

# SDK Architecture Review - 2021-09-24

The **SDK Architecture Review** meeting is a bi-weekly meeting focused on architecture discussions of ADRs and features currently in development (any issues tagged with the label "Status: Needs Architecture Review").

## Agenda

- [x] Working Group Check In (groups in DESIGN phase)
    - https://github.com/cosmos/cosmos-sdk/issues/9058
- [x] Structurize x/upgrade.Plan
    - https://github.com/cosmos/cosmos-sdk/discussions/10149
- [x] ADR 043 Interchain Identifiers
    - https://github.com/cosmos/cosmos-sdk/pull/9589
- [x] Determinism problem https://github.com/cosmos/cosmos-sdk/pull/10189#issuecomment-925814209
- [x] Tx Working Group -- amino aux vs direct aux for ledger support
- [x] ADR-38 gRPC service vs general plugin to be utilized with market standards (RabbitMQ, Kafka, ...).
    - https://github.com/cosmos/cosmos-sdk/issues/10096#issuecomment-926206565


## Notes

- Otter-ai Transcription: https://otter.ai/u/OxOaXqYjwyGQJYajUTO-nyc6cK8

### Working Group Check In

**Tx improvements**

- Amaury: had a conversation yesterday with Juan from Zondax
    - One possibility we were considering was to not work on proto-json or textual for the next release, but possibly add only amino_aux for transactions and think about real sign-mode further in the future

**ADR040 / SMT Work**
- Roy: SMT portion of ADR040 is up for review
- Multistore refactor (also part of ADR040)
    - there's been some updates to the design there, mostly complete and i'm working on implementation at the same time

**Upgrade Module & Cosmovisor Improvements**
- We have an agenda item for Structured upgrade Plan

**Staking Module Improvements**
- No updates


**Decimal Improvements**
- No updates


### Agenda Items

- Structurize x/upgrade.Plan
    - Aaron: Currently in the upgrade module we just have an info string which can be used for anything
    - We've defined some conventions in cosmovisor for how one uses that
    - Robert is trying to prevent someone making an upgrade proposal with a plan that cannot be understood by Cosmovisor
    - Aaron: I think there's some good motivations, and have proposed alternatively that we keep an unstructured info field, but Cosmovsior has the ability to verify the contents of the info-field
        - Reason being: it makes sense to leave state machine as it is
        - Cosmovisor can verify a lot more (that download links work, that hashes are valid, etc.)
    - Draft PR: #10032
- ADR043 Interchain Identifiers
    - Shaun: We now have some more resources to move this forward. The ADR has been sitting on the SDK for some time
    - Joe: there are a couple more items we need to clarify (aka what ADR number it should be)
    - Biggest piece we need input on is whether IIDs would use DID Cosmos (cosmos as method name for IIDs). We may have confused the use of DIDs for people and businesses, with what IIDs are.
        - IIDs are primarily about on-chain assets
        - Currently, we think we should reserve DID cosmos for cosmos cash's use of real persons & organizations
    - Aaron: it seems like there needs to be a chain name service that resolves this, and this should probably inform how the naming works
- Determinism Problem
    - Aaron: If there's non-determinism in v0.44.0 there should be a patch release to an v0.44.1
    - Robert: Personally i'm also supporting that decision
    - Marko: This doesn't affect v0.42, correct?
        - Robert: I think not, as we added this in v0.42 (the support for migrations)

- Tx Working Group - DIRECT_JSON_AUX vs AMINO_AUX
    - Due to Juans feedback, proto-json seems less ideal now since parsing JSON is difficult
    - Now we've discussed creating an AMINO_JSON_AUX where instead of the fee field we would add a tip field.
    - 


- 

## Follow Up

- [ ] ...