tailwind styles overridden

since it has been indicated that tailwind styles don't break when using 0.24.7, seems that the commit after this one: https://github.com/cosmology-tech/cosmos-kit/commit/02ba6b02c2bb4fa4f32edf5574a5e50a755b30e8

which is this one: https://github.com/cosmology-tech/cosmos-kit/commit/3afd3e868ae7533dc6072e74b1732bd25ee5be7c

could likely be the reason why styles are being overridden

Okay guys here it goes, we're integrating xstate and turning the side effects to a first class citizen.

• [x] Make the UI work with Wallet connect and Wallet Extension;
• [x] Polish the states to make them work on mobile; Right now it does deep link you to the app but it probably won't fully connect a mobile wallet from safari iOS. Plus reset action is not there just yet.
• [ ] Rethink context utils and config props;
• [ ] Clean up the UI & the context;
• [ ] Better dev scripts.
• [ ] Tests.

It'd be awesome if all the packages in this monorepo were versioned and published at the same time, so users can just consume one version (ie. 0.27.5) instead of having to manually check each dependency to ensure we're on the latest.

See the cosmos-kit example project for how projects will look with different versions of everything. A little messy

This is the error users are experiencing:

It looks like one has to do a bit of special handling when using keplr, ledger live devices

Related Issue: https://github.com/BitCannaGlobal/web-wallet/issues/4

I just updated to the latest version of cosmos-kit and found out, that your ChakraProvider used in the modal overrides my custom theme entirely. I even replaced the modal with a custom one and it still overrides my entire chakra config. Any ideas?

I'm running into the following type errors

Type error: Could not find a declaration file for module '@cosmos-kit/core'. '/0xArb/proposals-interface/node_modules/@cosmos-kit/core/main/index.js' implicitly has an 'any' type.
  Try `npm i --save-dev @types/cosmos-kit__core` if it exists or add a new declaration (.d.ts) file containing `declare module '@cosmos-kit/core';`

My versions are as follows

    "@cosmos-kit/core": "0.27.10",
    "@cosmos-kit/keplr": "0.32.11",
    "@cosmos-kit/react": "0.27.5",

Existing apps that uses Chakra UI will encounter an issue where the base theme will be overridden with cosmos-kit's default modal because it wraps its own ChakraProvider.

Having the option to disable provider wrapping or provide an escape hatch to pass custom themes would be better.

https://github.com/cosmology-tech/cosmos-kit/blob/8eff22dcdc01fae2eacae57d26952892a50232d3/packages/react/src/modal/get-modal.tsx#L48-L60

let's look into using chain-registry to make this type of thing

https://github.com/cosmology-tech/cosmos-wallet/blob/2e66939d241f06516673598f035dbaa00ed6e828/packages/core/src/chainInfo.ts

oh, actually... @NoahSaso I just got an idea if we should parse JSON and generate objects, or if I should look into using ASTs + codegen haha

https://github.com/cosmology-tech/chain-registry and https://www.npmjs.com/package/chain-registry

I haven't tested this, because I found it quite hard to yarn link all the cosmos-kit packages locally, but I believe it resolves https://github.com/cosmology-tech/cosmos-kit/issues/99.

What happens is that getOfflineSigner in Keplr defaults to returning a wallet that supports Amino and Direct signing. This is obviously false in the case of Ledger devices and is leading to some of the errors we've been seeing.

1. connect wallet
2. let sit for 10 mins
3. change the chain
4. without refreshing, change chains and wallets

You should see Keplr will work, Leap seems to just show spinning loaders.

some wallets, like trust, want to manage their own endpoints. We should provide a way for them to broadcast the messages after we sign w the provider offlineSigner.

https://github.com/trustwallet/trust-web3-provider/blob/12b20e3fd995394e456f6b7fa0b5d37e7d381ea8/src/cosmos_provider.js#L95-L104

https://github.com/trustwallet/trust-web3-provider/blob/master/src/cosmjs_adapter.js

you can request offline signer from window.trustwallet https://github.com/trustwallet/trust-web3-provider/blob/12b20e3fd995394e456f6b7fa0b5d37e7d381ea8/src/cosmos_provider.js#L48-L58

I know this might sound controversial, but I actually want to be able to import keplr mobile/extension separately because wallet connect brings in a ton of stuff that has awful commonjs modules that need pre-transpiling for non-react/next projects. I also don't necessarily want a WS ping/ack added for simply adding a keplr query provider.

See this line specifically: https://github.com/cosmology-tech/cosmos-kit/blob/main/packages/keplr/src/keplr.ts#L9

SO! I am proposing that they get split into 2 packages, so it can be independently added. I realize this is a breaking change for some projects, but I believe for future work, this pattern of context splitting for any provider (cosmostation, leap, you name it) is necessary for more granular inclusion.

Thoughts? If there's a way to disable keplr wallet already - would love to know :)

Add ICNS integration for cosmos-kit. This PR contains

• @cosmos-kit/icns as a separated package
• icns hooks in react package, let me know if it makes more sense to separate the hook logic out as it's own package (eg. @cosmos-kit/icns-react) or moved to @cosmos-kit/icns

The goal is to make it modular and not imposed itself as a default name service so developer can choose what they want.

Overview

Basic attempt at rendering a .stars domain in place of a users "wallet username" if they have one.

Notes

• IMO it's pretty uncommon that wallets actually expose a "username" to dapps. MetaMask, WalletConnect, etc all do not support this, seems to be a Keplr implementation detail
• This approach is nice because consumers don't have to change anything to start having this data come through. Another way would be introducing another field on the cosmos-kit API like stargazeName so consumers can do stargazeName ?? username
• Next step would be to bubble up the image associated with the name NFT, if the user has set one

Telescope and CosmJS support HttpEndpoint which allows users to pass headers into requests, cosmos-kit should support this. Perhaps we just need to make a modified version of chain-registry/types to allow for this

https://github.com/osmosis-labs/osmojs/blob/843b315fa0bc304eebc7664c152c18cc1871792c/packages/osmojs/src/codegen/osmosis/rpc.query.ts#L6

export interface HttpEndpoint {
  /**
   * The URL of the HTTP endpoint.
   *
   * For POST APIs like Tendermint RPC in CosmJS,
   * this is without the method specific paths (e.g. https://cosmoshub-4--rpc--full.datahub.figment.io/)
   */
  readonly url: string;
  /**
   * HTTP headers that are sent with every request, such as authorization information.
   */
  readonly headers: Record<string, string>;
}

environment

brave browser (loaded with extensions, ad blockers, etc)

Seems that somehow the detection for whether or not we're mobile was triggering, even though the user agent was still chrome!

issue

errors happen with connecting

steps to reproduce

1. create template

create-cosmos-app --name cnfts-frontend --example --template cosmwasm

2. attempt to connect wallet

However, it looks that the browser was somehow choosing the keplr mobile — so this is maybe why the offlineSigner was undefined... but why was it 1. using mobile and 2. trying get get a signer before actually connecting?

idea to debug

Perhaps we should test using keplr mobile as the chosen wallet inside of chrome and see what happens

important note

as soon as developer removed all extensions by creating fresh profile only with keplr extension, everything worked fine

related

• [ ] https://github.com/CosmWasm/ts-codegen/issues/77
• [ ] https://github.com/CosmWasm/ts-codegen/issues/84
• [ ] https://github.com/osmosis-labs/telescope/issues/276