SOON RPC Configuration & New Key Pair

Now that you've set up your development environment, it's time to configure the RPC endpoint. This is crucial because it allows your development environment to interact with a specific Solana cluster. In this case, you will be connecting to the SOON Devnet rather than the Solana local cluster or default Solana Devnet.

Configuring the Solana CLI to Use SOON Devnet

Instead of pointing your Solana CLI to the default local cluster or Solana Devnet, you’ll need to configure it to use the SOON Devnet RPC.

RPC Link: https://rpc.devnet.soo.network/rpc

Run the following command to set the RPC URL to SOON Devnet:

solana config set --url https://rpc.devnet.soo.network/rpc

You can verify that the Solana CLI is properly configured to use the SOON Devnet by running:

solana config get

You should see an output that includes the following URL:

Config File: /home/xxxx
RPC URL: https://rpc.devnet.soo.network/rpc
WebSocket URL: wss://rpc.devnet.soo.network/rpc (computed)
Keypair Path: /home/xxxxx
Commitment: confirmed

If this is your first time using the Solana CLI, you will need to generate a new key pair. This key pair will serve as your identity when interacting with the SOON Devnet. To generate a new keypair, run the following command:

solana-keygen new

You should see output similar to:

Generating a new keypair

For added security, enter a BIP39 passphrase

NOTE! This passphrase improves security of the recovery seed phrase NOT the
keypair file itself, which is stored as insecure plain text

BIP39 Passphrase (empty for none):

Wrote new keypair to /home/xxxxx
============================================================================
pubkey: AEG18Z4ESnzEh1rcgUHk1dLwVY4LyfZ6TWzgShGry5UN
============================================================================
Save this seed phrase and your BIP39 passphrase to recover your new keypair:

Important Security Considerations

• Private Key Security: The private key in your keypair should never be shared or exposed. It grants access to your account and the ability to sign transactions on your behalf. Always keep this file secure.

• Public Key: The public key, derived from the keypair, will serve as your wallet address and can be shared with others to receive funds or interact with contracts.