> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lumera.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get started with Lumera

> Connect to a Lumera network, fund an address, and pick the path for what you are building.

Lumera Protocol is a Cosmos SDK Layer 1 blockchain. The chain coordinates requests, payments, and proofs, while economically bonded SuperNodes perform storage, verification, and retrieval. You reach all of it through SDKs, smart contracts, or plain REST and gRPC.

This page gets you connected to a network and points you at the right section for what you are building. It takes a few minutes and needs nothing but `curl`.

<Note>
  This page is for application developers. Node operators can start with the [validator quickstart](/quickstart-validator) or the [SuperNode quickstart](/quickstart-supernode).
</Note>

## What you can build

Lumera exposes four surfaces. Most applications use more than one.

| Surface           | What it gives you                                                     | Start here                                   |
| ----------------- | --------------------------------------------------------------------- | -------------------------------------------- |
| Protocol services | Permanent storage, identity, and verifiable execution through Actions | [Cascade](/cascade/overview)                 |
| Smart contracts   | Solidity through Cosmos EVM and Rust through CosmWasm                 | [Smart contracts](/smart-contracts/overview) |
| Read APIs         | Chain state, SuperNode metrics, and Action metadata                   | [API reference](/api/overview)               |
| Network operation | Run a validator or a SuperNode                                        | [Operate the network](/validators/overview)  |

## Choose a network

Build on testnet first. Testnet tokens are free and the EVM is available there today.

|            | Testnet                                   | Mainnet                   |
| ---------- | ----------------------------------------- | ------------------------- |
| Chain ID   | `lumera-testnet-2`                        | `lumera-mainnet-1`        |
| RPC        | `https://lumera-testnet-rpc.polkachu.com` | `https://rpc.lumera.io`   |
| LCD (REST) | `https://lumera-testnet-api.polkachu.com` | `https://lcd.lumera.io`   |
| gRPC       | `grpc.testnet.lumera.io:443`              | `grpc.lumera.io:443`      |
| SN-API     | `https://snapi.testnet.lumera.io`         | `https://snapi.lumera.io` |
| Tokens     | Free from the [faucet](/faucet)           | Real LUME                 |
| Cosmos EVM | Available                                 | Not yet available         |

Public endpoints are rate limited. Run your own node or use a dedicated provider for production traffic. See [Networks and endpoints](/networks) for genesis files and seed nodes.

## Connect to the network

<Steps>
  <Step title="Confirm you can reach the chain">
    Query the RPC endpoint and check which network answers.

    ```bash theme={null}
    curl -s https://lumera-testnet-rpc.polkachu.com/status | jq -r '.result.node_info.network'
    ```

    You should see `lumera-testnet-2`. If you get nothing back, the endpoint is rate limiting you or is down. Try another provider from [Networks and endpoints](/networks).
  </Step>

  <Step title="Check the running version">
    The REST endpoint reports the application version the network is on.

    ```bash theme={null}
    curl -s https://lumera-testnet-api.polkachu.com/cosmos/base/tendermint/v1beta1/node_info \
      | jq -r '.application_version.version'
    ```

    Match this version when you install `lumerad` or pin an SDK. Mainnet and testnet run different versions.
  </Step>

  <Step title="Create an address">
    Lumera uses bech32 addresses with the `lumera` prefix. Get one from [Lumera Hub](/hub/wallet), from a Cosmos wallet such as Keplr or Leap, or from the CLI.

    ```bash theme={null}
    lumerad keys add my-key
    ```

    Save the mnemonic somewhere safe. See the [`lumerad` CLI reference](/sdk/lumerad-cli) for keyring backends.
  </Step>

  <Step title="Fund the address">
    Most operations cost gas, and protocol services escrow a service fee on top. Request testnet LUME from the [faucet](/faucet), then confirm the balance arrived.

    ```bash theme={null}
    curl -s https://lumera-testnet-api.polkachu.com/cosmos/bank/v1beta1/balances/<your-address> | jq
    ```

    Balances are in `ulume`, where 1 LUME is 1,000,000 `ulume`.
  </Step>
</Steps>

You are connected. Pick the path that matches what you are building.

## Choose your path

<CardGroup cols={2}>
  <Card title="Store data permanently" icon="database" href="/cascade/overview">
    Use Cascade to store files that stay retrievable. Pay once at upload and the network keeps the data available.
  </Card>

  <Card title="Deploy a smart contract" icon="file-code" href="/smart-contracts/overview">
    Deploy Solidity through the Cosmos EVM with MetaMask and Remix, or Rust through CosmWasm.
  </Card>

  <Card title="Build with an SDK" icon="code" href="/sdk/javascript">
    JavaScript for browsers and Node.js, Go for backends with direct SuperNode access, and Rust for system integrations.
  </Card>

  <Card title="Query the chain" icon="server" href="/api/overview">
    Read chain state, SuperNode metrics, and Action metadata over REST, gRPC, and JSON-RPC.
  </Card>
</CardGroup>

## Next steps

<CardGroup cols={3}>
  <Card title="Protocol architecture" icon="sitemap" href="/architecture">
    How consensus, SuperNodes, and protocol services fit together.
  </Card>

  <Card title="Install the SDKs" icon="download" href="/cascade/installation">
    Set up the JavaScript or Go SDK and configure your bundler.
  </Card>

  <Card title="The Intelligence Layer" icon="brain" href="/intelligence-layer/overview">
    The capabilities Lumera is building for autonomous software.
  </Card>
</CardGroup>