Read account summary

Use this recipe when an application needs a compact account view rather than raw RPC objects.

For exact types and method signatures, use the API reference. This page explains why the read model exists and how to use it safely.

Safety

Safety level: read-only.

This recipe reads public account, profile, mana and chain data. It does not require a private key and does not broadcast a transaction.

Why use a read model?

Raw account data is useful, but application screens often need a grouped summary:

• account identity and activity;
• wallet and stake information;
• follower/following counts;
• witness-vote count;
• lifetime reward totals.

client.read.getAccountSummary() composes existing Layer 1 and Nexus reads into a structured SDK data model. It does not create UI text, calculate fiat prices or make application policy decisions.

Example

import { Client } from '@beblurt/dblurt';

const client = new Client(rpcList, { timeout: 15_000, failoverThreshold: 3 });
const summary = await client.read.getAccountSummary('beblurt');

console.log({
  account: summary.account.name,
  mana: summary.account.mana_percent,
  balance: summary.wallet.balance.toString(),
  vestingToBlurt: summary.wallet.vesting_to_blurt
});

API symbols

• ReadModels.getAccountSummary
• AccountReadModel

Validated source

Executable source: examples/node/read-account-summary.cjs.

Run locally from the repository:

node examples/node/read-account-summary.cjs beblurt

This example is included in npm run docs:check.

What to verify in your app

• Choose an endpoint strategy suitable for your app.
• Treat Nexus profile fields as indexed social context, not as a replacement for Layer 1 authorities.
• Format balances and stake in the UI layer.
• Handle missing accounts and transport failures.

Related: Blurt mental model, Layer 1 and Nexus Layer 2, Read models guide.