As I followed the instructions, I noticed that it wasn’t entirely clear that before running solana-test-validator, you should first set up a wallet using solana-keygen new ... to generate a private key (from which you can also derive the public key using solana-keygen pubkey).
My Issue
When working with JavaScript, I already had a test wallet .json file that contained both keys. This file was generated in a format different from what solana-keygen produces, which made it difficult to understand that this step needed to be done using the Solana CLI. Also the CLI sets the default keypair that solana config set --url localhost references.
To keep things general, I suggest including information about the need to generate a keypair with solana-keygen new or mentioning that solana-test-validator references the keypair set by default, which can be configured using solana config set --keypair /path/to/other/location/wallet.json.
As I followed the instructions, I noticed that it wasn’t entirely clear that before running
solana-test-validator, you should first set up a wallet usingsolana-keygen new ...to generate a private key (from which you can also derive the public key usingsolana-keygen pubkey).My Issue
When working with JavaScript, I already had a test wallet .json file that contained both keys. This file was generated in a format different from what solana-keygen produces, which made it difficult to understand that this step needed to be done using the Solana CLI. Also the CLI sets the default keypair that
solana config set --url localhostreferences.To keep things general, I suggest including information about the need to generate a keypair with
solana-keygen newor mentioning thatsolana-test-validatorreferences the keypair set by default, which can be configured usingsolana config set --keypair /path/to/other/location/wallet.json.