Table of Content

Read Data From The Solana Network

Lesson Objectives

By the end of this lesson, you will be able to:

  • Explain accounts
  • Explain SOL and lamports
  • Explain public keys
  • Explain the JSON RPC API
  • Explain web3.js
  • Install web3.js
  • Use web3.js to create a connection to a Solana node
  • Use web3.js to read data from the blockchain (balance, account info, etc.)


  • Accounts are like the files in Solana’s network ledger. All state data is stored in an account. Accounts can be used for many things, but for now we’ll focus on the aspect of accounts which store SOL.

  • SOL is the name of Solana’s native token.

  • Lamports are fractional SOL and are named after Leslie Lamport.

  • Public keys, often referred to as addresses, point to accounts on the Solana network. While you must have a specific secret key to perform certain functions within accounts, anyone can read account data with a public key.

  • JSON RPC API: all interactions with the Solana network happens through the JSON RPC API. This is effectively an HTTP POST with a JSON body that represents the method you want to call.

  • @solana/web3.js is an abstraction on top of the JSON RPC API. It can be installed with npm and allows you to call Solana methods as JavaScript functions. For example, you can use it to query the SOL balance of any account:

    async function getBalanceUsingWeb3(address: PublicKey): Promise<number> {
        const connection = new Connection(clusterApiUrl('devnet'));
        return connection.getBalance(address);
    const publicKey = new PublicKey('7C4jsPZpht42Tw6MjXWF56Q5RQUocjBBmciEjDa8HRtp')
    getBalanceUsingWeb3(publicKey).then(balance => {



Solana accounts are similar to files in operating systems such as Linux. They hold arbitrary, persistent data and are flexible enough to be used in many different ways.

In this lesson we won’t consider much about accounts beyond their ability to store SOL (Solana’s native token - more on that later). However, accounts are also used to store custom data structures and executable code that can be run as programs. Accounts will be involved in everything you do with Solana.

Public Keys

Public keys are often referred to as addresses. The addresses point to accounts on the Solana network. If you want to run a specific program or transfer SOL, you’ll need to provide the necessary public key (or keys) to do so.

Public keys are 256-bit and they are often shown as base-58 encoded strings like 7C4jsPZpht42Tw6MjXWF56Q5RQUocjBBmciEjDa8HRtp.


Illustration depicting how client-side interaction with the Solana network happens through the JSON RPC API

All client interaction with the Solana network happens through Solana’s JSON RPC API.

Per the JSON-RPC 2.0 specification

JSON-RPC is a stateless, light-weight remote procedure call (RPC) protocol. Primarily this specification defines several data structures and the rules around their processing. It is transport agnostic in that the concepts can be used within the same process, over sockets, over http, or in many various message passing environments. It uses JSON (RFC 4627) as data format.

In practice, this specification simply involves sending a JSON object representing a method you want to call. You can do this with sockets, http, and more.

This JSON object needs four members:

  • jsonrpc - The JSON RPC version number. This needs to be exactly &quot;2.0&quot;.
  • id - An identifier that you choose for identifying the call. This can be a string or a whole number.
  • method - The name of the method you want to invoke.
  • params - An array containing the parameters to use during the method invocation.

So, if you want to call the getBalance method on the Solana network, you could send an HTTP call to a Solana cluster as follows:

async function getBalanceUsingJSONRPC(address: string): Promise<number> {
    const url = clusterApiUrl('devnet')
    return fetch(url, {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
        body: JSON.stringify({
            "jsonrpc": "2.0",
            "id": 1,
            "method": "getBalance",
            "params": [
    }).then(response => response.json())
    .then(json => {
        if (json.error) {
            throw json.error

        return json['result']['value'] as number;
    .catch(error => {
        throw error

Solana’s Web3.js SDK

While the JSON-RPC API is simple enough, it involves a significant amount of tedious boilerplate. To simplify the process of communication, Solana Labs created the @solana/web3.js SDK as an abstraction on top of the JSON-RPC API.

Web3.js allows you to call the JSON-RPC API methods using JavaScript functions. The SDK provides a suite of helper functions and objects. We’ll cover a lot of the SDK gradually throughout this course, but we won’t go over everything in depth, so be sure to check out the documentation at some point.


Throughout this course, we’ll mostly be using npm. How to use npm is outside the scope of this course and we’ll assume it’s a tool you use regularly. Check this out if that’s not the case.

To install @solana/web3.js, set up your project the way you normally would then use:

npm install @solana/web3.js.

Connect to the Network

Every interaction with the Solana network using @solana/web3.js is going to happen through a Connection object. This object establishes a JSON-RPC connection with a Solana cluster (more on clusters later). For now, we’re going to use the url for the Devnet cluster rather than Mainnet. As the name suggests, this cluster is designed for developer use and testing.

const connection = new Connection(clusterApiUrl('devnet'));

Read from the Network

Once you have a Connection object, querying the network is as simple as calling the appropriate methods. For example, to get the balance of a particular address, you do the following:

async function getBalanceUsingWeb3(address: PublicKey): Promise<number> {
    const connection = new Connection(clusterApiUrl('devnet'));
    return connection.getBalance(address);

The balance returned is in fractional SOL called lamports. A single lamport represents 0.000000001 SOL. Most of the time when dealing with SOL the system will use lamports instead of SOL. Web3.js provides the constant LAMPORTS_PER_SOL for making quick conversions.

...and just like that, now you know how to read data from the Solana blockchain! Once we get into custom data things will get more complicated. But for now, let’s practice what we’ve learned so far.


Let’s create a simple website that lets users check the balance at a particular address.

It’ll look something like this:

Screenshot of demo solution

In the interest of staying on topic, we won’t be working entirely from scratch. You can find the starter code here. The starter project uses Next.js and Typescript. If you’re used to a different stack, don’t worry! The web3 and Solana principles you’ll learn throughout these lessons are applicable to whichever frontend stack you’re most comfortable with.

1. Get oriented

Once you’ve got the starter code, take a look around. Run the app with npm run dev. Notice that no matter what you put into the address field, when you click “Check SOL Balance” the balance will be a placeholder value of 1000.

Structurally, the app is composed of index.tsx and AddressForm.tsx. When a user submits the form, the addressSubmittedHandler in index.tsx gets called. That’s where we’ll be adding the logic to update the rest of the UI.

2. Install dependencies

Use npm install @solana/web3.js to install our dependency on Solana’s Web3 library.

3. Set the address balance

First, import @solana/web3.js at the top of index.tsx.

Now that the library is available, let’s go into the addressSubmittedHandler and create an instance of PublicKey using the address value from the form input. Next, create an instance of Connection and use it to call getBalance. Pass in the value of the public key you just created. Finally, call setBalance, passing in the result from getBalance. If you’re up to it, try this independently instead of copying from the code snippet below.

import type { NextPage } from 'next'
import { useState } from 'react'
import styles from '../styles/Home.module.css'
import AddressForm from '../components/AddressForm'
import * as Web3 from '@solana/web3.js'

const Home: NextPage = () => {
  const [balance, setBalance] = useState(0)
  const [address, setAddress] = useState('')

  const addressSubmittedHandler = (address: string) => {
    const key = new Web3.PublicKey(address)
    const connection = new Web3.Connection(Web3.clusterApiUrl('devnet'))
    connection.getBalance(key).then(balance => {
      setBalance(balance / Web3.LAMPORTS_PER_SOL)



Notice that we are taking the balance returned by Solana and dividing it by LAMPORTS_PER_SOL. Lamports are fractional SOL (0.000000001 SOL). Most of the time when dealing with SOL, the system will use lamports instead of SOL. In this case, the balance returned by the network is in lamports. Before setting it to our state, we convert it to SOL using the LAMPORTS_PER_SOL constant.

At this point you should be able to put a valid address into the form field and click “Check SOL Balance” to see both the Address and Balance populate below.

4. Handle invalid addresses

We’re just about done. The only remaining issue is that using an invalid address doesn’t show any error message or change the balance shown. If you open the developer console, you’ll see Error: Invalid public key input. When using the PublicKey constructor, you need to pass in a valid address or you’ll get this error.

To fix this, let’s wrap everything in a try-catch block and alert the user if their input is invalid.

const addressSubmittedHandler = (address: string) => {
  try {
    const key = new Web3.PublicKey(address)
    const connection = new Web3.Connection(Web3.clusterApiUrl('devnet'))
    connection.getBalance(key).then(balance => {
      setBalance(balance / Web3.LAMPORTS_PER_SOL)
  } catch (error) {

Notice that in the catch block we also cleared out the address and balance to avoid confusion.

We did it! We have a functioning site that reads SOL balances from the Solana network. You’re well on your way to achieving your grand ambitions on Solana. If you need to spend some more time looking at this code to better understand it, have a look at the complete solution code. Hang on tight, these lessons will ramp up quickly.


Since this is the first challenge, we’ll keep it simple. Go ahead and add on to the frontend we’ve already created by including a line item after “Balance”. Have the line item display whether or not the account is an executable account or not. Hint: there’s a getAccountInfo method.

Your standard wallet address will not be executable, so if you want an address that will be executable for testing, use CenYq6bDRB7p73EjsPEpiYN7uveyPUTdXkDkgUduboaN.

Screenshot of final challenge solution

If you get stuck feel free to take a look at the solution code.

Table of Content