-
Notifications
You must be signed in to change notification settings - Fork 31
Client type #57
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
Comments
does it make sense to make this an option? It could make sense to do one as a default but have an option to use the pardon my naivety, but would there be a reason that some developers would want to use |
For less code? (by not making |
@pyramation |
oh, so does this mean we can close this issue and it will be updated in cosmjs? I think requiring a signer from cosmjs or cosmwasm feels more official than the relayer repo. |
Yes, you can, please.
I also think so. hope it will be treated well there. |
Currently ts-codegen use
SigningCosmWasmClient
for the client instead ofCosmWasmSigner
?CosmWasmSigner
is just a wrapper ofSigningCosmWasmClient
in ts-relayer.But, I think it's more useful.
One of the reasons to prefer
CosmWasmSigner
is that it contains senderAddress to include as an argument of the many methods whichSigningCosmWasmClient
has.The text was updated successfully, but these errors were encountered: