-
Notifications
You must be signed in to change notification settings - Fork 212
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
Smart wallets can get balances with zero transactions (for small # of users) #5356
Comments
@samsiegart what's a good ticket for "chain selection/signing frontend" ? @dckc what's a good ticket for "Add cosmjs client to wallet dapp" ? @gibson042 what's a good ticket for tracking that "backend subscriptions can reach frontend notifiers" ? |
I think this was it #4421. That allows us to select the chain and get a cosmjs signer |
@samsiegart cool. is there any other frontend work needed for this story? let's try to have it all as part of this epic |
I'm not sure I understand that. How can a user tell whether they're using the on-chain wallet or not? I suspect an acceptance test will involve looking at the network traffic and / or block explorer to verify that we didn't add any cosmos transactions to get our balance. Another place to look might be the IST balance, since sending a swingset message costs (a little bit of) IST. p.s. I was using #3756 to track pretty much the same thing. I wonder whether having two separate epics is cost-effective. I don't have much experience using epics, though. In my experience, enhancement (or bug) tickets with blockers is necessary and sufficient. |
They'll know when they connect to keplr in the wallet UI, or more concretely, if everything works and they don't have an ag-solo running. |
Yes but I'm not sure what it looks like yet. We have to sign some sort of message to get the wallet bridge, all the purse balances, etc. in the UI. |
Epic milestone to #3995
Acceptance criteria
The text was updated successfully, but these errors were encountered: