Christophe Le Bars

One problem i see with your PR is that we remove warning even when the provider is not compliant. Ideally this whole block should disappear when all provider would upgrade...

I'm not sure this is really related to svelte-web3. Could you commit a small test case that reproduce this somewhere ?

I'm not sure this is the correct direction. The whole package is about store. In my opinion the correct pattern should be to subscribe to the selectedAccount and //do something...

Keeping open so we improve the documentation to explain how to do that the right way...

No but I would be happy to any suggestions. I was wondering if a series of small medium article on store + web3.js would be a good complement of this...

I'm convinced a roadmap is a good thing. Just adding that having input from what is needed is a way the start it.

Yes, that's how store works. Data is not persistent when reloading. You will have to implement that yourself on your side. By example saving the account and connection type in...

@PythoniCode is correct, if you create a contract store locally, you can only use it inside that file. But there are ways to go around that and use is somewhere...

In the meantime this part is improving, here is a small example how to create your own contract store form a separate file that can be imported everywhere: Let's define...