Saksham

This happens because we try to auto login the user on loading the page for the first time. This results in normal loading circle which appears when you aren't authenticated...

I think we can do this. I added APIs for updating metadata for keys and locks earlier on `v2` endpoints. We can use those assuming that's what the default token...

@julien51 I think you are misunderstanding. I'm talking about tackling the same issue above by having a function which can be used to create networkConfigs with private api keys but...

1. For clarification, we don't need explicit signature here. As long as user is logged in via SIWE, we know which address is updating metadata. 2. I think we should...

@clemsos I'm gonna try yarn build on the new examples repo so will report how that turns out. @julien51 no because we need this locally when someone clones and make...

@julien51 No, that wouldn't work because user can buy multiple memberships for different recipients than themselves. Which is why we do not warn them until they enter the recipient and...

We can close this one. Uncompleted individual issue should be separated due to their bigger scope.

We don't control this. It is part of stripe UI library. https://github.com/stripe/stripe-js/issues/150

I think their payment element supports it so I will see if it will work there when we add more payment options

I think auto complete works with the new payment element so this should be resolved.