Account detail — header from `accounts` + balances from `balances` (`queries::fetch_account` + `queries::fetch_balances`).

An account's signing configuration: who may sign, and how much weight each operation class demands.

The master key is NOT in signers. The ledger keeps the account's own key out of that list and expresses its weight as master_weight; Horizon synthesises an extra entry, we do not. A client showing only signers therefore reads 3-of-4 where the chain says 3-of-5 — compose the master key into the display, do not expect it here.

A master_weight of 0 is a permanently DISABLED master key, not a signer with a low weight. It is a common, deliberate configuration.

The CAP-33 counters the network keeps on the account itself, copied as stored. A reserve is the base reserve the network locks per ledger entry (2 for the account, 1 per sub-entry, 1 per claimant of a claimable balance); a sponsor can pay it for someone else.