Documentation for agents: an index at /llms.txt, every docs page in one file at /llms-full.txt, and Markdown for any docs page by adding .md to its URL.

Skip to Content
ensforgeReact

Read many at once

Run a changing list of reads with useReads, such as an avatar for every row, and share multicall batches between components.

Use useReads when the number of reads changes, such as one address or avatar per row of a list. Their RPC calls share the client's multicall batches, so a long list does not send a request per row.

Pass a list of reads

Each read is a pair of an action and its options. Mark the array as const so each pair keeps its types. Results come back in the same order.

Example (Addresses Of Several Names)

Addresses.tsx
import { useReads } from "@ensforge/react";
import { Actions } from "@ensforge/sdk";

export function Addresses({ names }: { names: readonly string[] }) {
  const results = useReads(names.map((name) => [Actions.record.getAddress, { name }] as const));

  return (
    <ul>
      {results.map((result, index) => (
        <li key={names[index]}>
          {names[index]}: {result.isLoading ? "..." : result.data}
        </li>
      ))}
    </ul>
  );
}

Each entry is a ReadResult with its own data, error, status and refresh. One failed read does not fail the others.

Mix actions in a fixed set

For a fixed set, separate hooks work equally well. Use useReads with different actions when you want them in one tuple. Each result is typed by its own action.

Example (An Address And An Avatar Together)

Card.tsx
import { useReads } from "@ensforge/react";
import { Actions } from "@ensforge/sdk";

export function Card({ name }: { name: string }) {
  const [address, avatar] = useReads([
    [Actions.record.getAddress, { name }],
    [Actions.record.getAvatar, { name }],
  ] as const);

  return (
    <figure>
      <img src={avatar.data ?? undefined} alt="" />
      <figcaption>{address.data}</figcaption>
    </figure>
  );
}

Read an HCA account

The @ensforge/hca reads, such as Actions.hca.get, work in useReads like any other read. Pass the pair [Actions.hca.get, {}].

Settings

useReads takes a config as its second argument: staleTime, idleTTL, refetchInterval, refreshOnWindowFocus and client. It applies to every read in the list. There is no enabled: leave a read out of the list instead.

Reads are shared with other hooks

A read in useReads is the same read a useAddress elsewhere makes for that name. Both share one request and one cached result. See Caching and refreshing.

Outside React, the SDK batches reads the same way. See Look up many at once.

Was this page helpful?