How I personally check cosmos chain quality

Checking Code Quality in Cosmos …including highly opinionated stuff that people I respect might disagree with Steps 1-8 are below, and cover the easy, boring stuff that everyone should attend to regardless . • the chain should specify the latest version of go in go.mod – this ensures that all validators are using the latest version of go. Long-run this means that the chain won’t rando apphash for stuff like the crypto changes between 1.18 and 1.19. Alos devs have latest. use it. Currently, this means that a new chain should be using go v1.20. This means it may be necessary to bump the golang in one of the older proto-builder containers, that you can find here: • lint with golangci-lint if you enable gofumpt (usually by replacing gofmt and goimports) in .golangci.yml, then you can fumpt and fix common issues like: golangci-lint run ./… --fix now your editor warns more. Typicially you’ll want a .golangci.yml file that includes: ``` run: tests: true timeout: 10m sort-results: true allow-parallel-runners: true skip-dirs: - "legacy_ibc_testing" - "testutil" linters: disable-all: true enable: - depguard - dogsled -…

Excerpt (1190 of 6394 characters). Read the whole post on the forum ↗

Great insight! At CryptoCrew we’re adopting these steps, additionally we’re working with Notional and SG-1 on a best-practice guideline for consumer-chains and sovereign chains