Dan Lynch

keplr is requiring old versions of cosmjs libraries ``` "@cosmjs/launchpad" "^0.24.0-alpha.25" "@cosmjs/proto-signing" "^0.24.0-alpha.25" ``` I talked to @webmaster128 and it seems if we upgrade to 0.27, launchpad is still available...

missing chain data needed for keplr (api/rpc info, slip44, or stakeCurrency)

2

## no api/rpc info - [ ] microtick ## no stakeCurrency - [ ] nomic - [ ] stateset-1-testnet - [ ] theta - [ ] thorchain ## no `slip44`...

should we make `testnets` -> `_testnets`

3

since the assets are all w/o underscore it could create confusion, and additionally, the other folders (`_IBC` and `_non-cosmos`) have leading underscores.

add `additionalProperties: false` to schemas

4

https://github.com/cosmos/chain-registry/blob/350840e766f7574a120760a13eda4c466413308a/testnets/stateset/assetlist.json#L24

should we enforce testnets have unique names?

2

``` "chain_name": "cheqd", ``` appears in both main and testnets... the problem is that assetlist has no way of telling if network_type is mainnet or testnet. I would suggest instead...

`SigningStargateClient.signAndBroadcast` when a node has transaction indexing disabled

2

apparently most public RPCs turn of transaction indexing. it's on by default in config.toml (per node setting) I was using the https://cosmos.directory/ proxy (which proxies available chain-registry endpoints) If you...

referencing json-schema-ref-parser to git hash causes yarn3 issues

1

Not able to use the library in it's current state when using yarn 3: ``` ➤ YN0018: │ @apidevtools/json-schema-ref-parser@https://github.com/bcherny/json-schema-ref-parser.git#commit=984282d34a2993e5243aa35100fe32a63699164d: The remote archive doesn't match the local checksum - has the...

added functionality

4

It’s not complete, but has a lot more functionality than before. I implemented ``` CreateStmt ConstraintStmt Constraint ReferenceConstraint ExclusionConstraint FunctionParameter CreateFunctionStmt CreateSchemaStmt TransactionStmt ``` On a high level you can...

how to upgrade pg_query?

17

the version of pg_query is old and cannot parse quite a few statements now that are valid. I'm happy to help and make a PR, are can somebody provide some...