> For the complete documentation index, see [llms.txt](https://docs.eclipse.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eclipse.xyz/developers/tutorials-and-guides/developer-guides/dapp-deployment-tutorial-eclipse-devnet/solana-cli-and-solana-keypair/step-1-set-solana-cli-to-use-eclipse-devnet.md).

# Step 1: Set Solana CLI to Use Eclipse Devnet

When developing for the Eclipse blockchain, connecting to the appropriate network environment is crucial. For this tutorial, we'll be using the Eclipse devnet, specifically targeting its staging environment. This environment offers a testing ground that closely mirrors the mainnet, providing a realistic backdrop for development, testing, and deployment of your projects without the need for real cryptocurrency. Here's how to configure your Solana CLI to connect to this environment.

**Prerequisites**

* Solana CLI installed on your machine. Refer back to earlier sections if you need guidance on installing the Solana CLI.
* Windows users should utilize WSL (Windows Subsystem for Linux) for full compatibility.

**Configuration Instructions**

1. **Open Your Terminal**:
   * Launch your terminal application. Windows users are advised to use WSL by opening the Ubuntu application or any other Linux distribution you've installed through WSL.
2. **Execute the Configuration Command**:
   * To configure the Solana CLI to communicate with the Eclipse blockchain's staging environment, enter and run the following command in your terminal:

     ```bash
     solana config set --url https://staging-rpc.dev2.eclipsenetwork.xyz
     ```
   * This command sets the Solana CLI's RPC URL to the Eclipse blockchain's devnet staging environment. It ensures all commands issued through the CLI are directed to this specific network.

**Understanding the Command**

* **RPC URL Configuration**: The `--url` parameter specifies the RPC endpoint that the Solana CLI will interact with. By setting it to `https://staging-rpc.dev2.eclipsenetwork.xyz`, you're telling the CLI to route all network requests to the Eclipse blockchain's devnet staging environment.
* **Target Network**: This staging environment is designed for developers to test their applications in a setting that simulates the actual conditions of the Eclipse blockchain's mainnet without the risk associated with real transactions.

**Verification and Next Steps**

* It's good practice to verify that your CLI is correctly configured after updating its settings. You can do this by running `solana config get` in your terminal. This command displays the current configuration of your Solana CLI, including the newly set RPC URL.
* With your CLI now pointing to the Eclipse blockchain's staging environment, you're set to begin the next phase of development, such as creating a wallet, deploying smart contracts, and interacting with the network.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.eclipse.xyz/developers/tutorials-and-guides/developer-guides/dapp-deployment-tutorial-eclipse-devnet/solana-cli-and-solana-keypair/step-1-set-solana-cli-to-use-eclipse-devnet.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.