-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding Lit Protocol Support #277
Comments
@mvid sorry for the delay. we're investigating it and will figure it out asap |
hi there this is an open source project and most teams have added their own wallets — we're open to grants to help support this or if the Lit team is willing to add a PR. |
Hi @pyramation i am likely the one writing this, mostly looking for advice on how to approach the issue of Lit implementing WalletConnectv2 but requiring the customer to create and manage their own Wallet ID, and how that would best mesh with Cosmoskit. This would basically be the first wallet that isn't statically defined, but dynamically defined |
I am trying to leverage the WalletConnect support that Lit Protocol have implemented so that I can use Lit wallets to operate against my cosmos network with CosmosKit.
I am trying to figure out the cleanest and most idiomatic way to do this, since Lit doesn't have a WalletConnect ID, clients are required to pass that in themselves. Also, they require some extra client information passed in, potentially based on user input.
Are there any recommendations on how to approach this?
The text was updated successfully, but these errors were encountered: