thank you! Do you know which wallets use the same principals across all dapps? For my dapp, it would be nice if at least one payment method would not require the users to first top-up their app-specific wallet. Plug was nice for that.
Thank you, I rather meant though which wallets use the same principals. I think plug uses the same for all apps. This means once the user has a balance on the default account for that principal, they can make a payment with one click (confirming the transfer after having already signed in). This would be nice for my use case and to get initial traction. The alternative is that they have to first top-up their app-specific principal which is how II and many other auth methods seem to work.
I think what you say makes sense (I forgot if it’s just null for the default account or how that works but it sounds right to me).
Yes, something like that is very much needed. An identifier / address with automatic compatibility for all apps by default (and of course retaining an ability to create many of those independent identifiers if the user so wishes).
I ended up creating my own in-app wallet yesterday after realising there is no third party GUI wallet capable of sending ICRCs to accounts of non-null subaccount, which are effectively needed (it can be done differently but I’d also call it wrongly) when administering user funds in your app in segregated accounts (most of defi).
I think we’re going to have to find a way to simplify the environment in practice, as well as have basic things like wallets with full functionality that map to the complete capabilities of the IC, for things to develop.
That sounds really cool! Yeah, I agree there is a lot of stuff that is missing or could be improved or be more clear. In case you have a link to what you’re building (or social media), let me know, I’m always curious to follow and see new projects.