@eesheng I’d just like to re-iterate that it seems for your use case generateTestWallet is not appropriate, as it primarily for unit tests. Also, we are going to be deprecating that utility in short order in favour of launchTestNode
You should either install a browser wallet or instantiate a browser wallet as shown here with useBrowserWallet
- Let say I generate a new wallet
const unlockedWallet: WalletUnlocked = Wallet.generate();, do I still need to connect to a provider?
More than likely any wallet you generate you will want to interact with the chain, and thus that would require connecting to a provider, which can be passed in as a parameter to the generate function.
- How do you add faucets to our locally instantiated wallets? Not the connected provider
I’m not sure I understand the question, if you would like to send testnet assets to a generated wallet then you can send it to that wallet’s address.