Tyler

> @technicallyty could you share your connection open and close logic and how long your typical match is? the match is never intended to close, it should be alive as...

> How long does your match typically run before you see this issue? usually 10-15 seconds

> Would be great to have a decision here. I'm mostly leaning towards the approach in [#2 (comment)](https://github.com/cosmos/cosmos-proto/issues/2#issuecomment-984762597) for the reasons outlined there. I also think it will be quite...

we can do lists by just using `[]interface{}` but i believe this would require a good amount of reflection - is speed not as important for this or should we...

it works in the `main` branch, but you need to pass` --experimental_allow_proto3_optional`

iceboxing this as we are not planning to support optional fields at this time

seems the markdown lint job is faulty.

> i left some comments, but I'd prefer if we hold back on merging this because a lot of this are not up to date with my config PR. okay...

> Looks fine, however it's missing the "BASE_SHARD_ROUTER_KEY", and "CARDINAL_ROLLUP_ENABLED" config as well as the TELEMETRY_* configs (TELEMETRY_ENABLED, TELEMETRY_STATSD_ADDRESS, and TELEMETRY_TRACE_ADDRESS). updated

> > code looks good to me. does this have any implications for smart contracts, or other modules that may query from bank? > > Now code will consider locked...