Solana accounts and programs

EN source master · P02-L03 · 30 minutes estimated · needs_review

Read-only study. No wallet connection, real money, seed phrase, private key, signature or live trade. Duration is an editorial estimate; visual assets are specifications, not deployed components.

The word ‘owner’ appears at different layers of Solana records. Reading every owner field as a human wallet creates incorrect balance and control claims.

Identify the record layer

Solana stores state in accounts with addresses and program ownership [SOLACC]. A token account's data also names a mint and a token-owner authority [SOLTOKEN]. These fields answer different questions: which program governs the state representation, and which authority is associated with the token holding.

The Token Program appearing as base owner does not mean every token account belongs economically to one person. Likewise, an authority field is not an authenticated legal identity. Write the full field path rather than the unqualified word ‘owner’.

Distinguish mint from holding

A mint identifies a token and its relevant state. A token account holds units of one mint. Multiple token accounts can refer to the same mint or authority. Count only the accounts within the requested scope and only at comparable context.

Lamports are the smallest units of SOL (10^9 lamports per SOL). Do not add native lamports to token units. Do not add different mints because the UI groups them on one screen. Any conversion into a common value needs a separate pricing method, which this lesson does not provide.

State enumeration coverage

The exercise stipulates a complete set for one authority and mint. In a real response, a list may be paginated, filtered or incomplete. A partial sum is a returned-record total, not automatically every holding. A missing account is not a zero balance.

Preserve typed edges

Use program-owner, token-authority and mint-reference arrows. Each supports a narrow relation. A mint-reference edge links holders of one asset without proving common control. If human identity is asked, the graph supplies INSUFFICIENT EVIDENCE even when all technical fields are known.

• Program owner: base account's governing program.
• Token authority: owner field inside token-account data.
• Mint reference: exact token linkage.
• Enumeration scope: records included in a total.
• Slot: a numbered opportunity for block production; a slot marker is not automatically a wall-clock timestamp.

ILLUSTRATIVE at slot marker S0. T1: program P-TOKEN, mint M-A, token owner W, amount30. T2: same program/mint/owner, amount20. T3: program P-TOKEN, mint M-B, owner W, amount90. T4: mint M-A, owner V, amount50. Amounts normalized; T1/T2 stipulated exhaustive for W/M-A.

Contract-permissions map with T1/T2→W and M-A, T3→M-B, T4→V; separate program-owner arrows to P-TOKEN. Alt: only T1 and T2 contribute to W/M-A=50.

A correctly scoped holding total from the exhaustive fictional subset.

Human ownership, complete real-world holdings or token safety.

• Summing all accounts shown.
• Treating program owner as beneficiary.
• Assuming one account per mint/authority.

Draw typed relationships and calculate W/M-A. Explain why neither90 nor50 enters that total. What does program P-TOKEN establish about humans?

Submit a short evidence table and reasoning, using only the provided material. Suggested allocation: study 12 min, inspection/calculation 8 min, correction/quiz 10 min.

• Base field or decoded token field?
• Exact mint.
• Authority scope.
• Same slot/context.
• Completeness explicit.

The word ‘owner’ appears at different layers of Solana records. Reading every owner field as a human wallet creates incorrect balance and control claims. The supplied material supports a correctly scoped holding total from the exhaustive fictional subset. It does not establish human ownership, complete real-world holdings or token safety.

• Distinguish base program ownership from token authority.
• Identify mint and token-account roles.
• Aggregate only a defined mint/authority scope.

P02-L04 after reviewing this exercise and its prerequisites.

NONE. The authoritative catalog requires no product access for this lesson. Use the frozen/offline material.

• [SOLACC] Solana accounts — Base program ownership and account state. Checked 2026-10-01.
• [SOLTOKEN] Solana token accounts — Mint reference and token-owner authority are distinct from program owner. Checked 2026-10-01.

Synthetic values are author-created exercise inputs. Historical values, if any, must use the linked dataset and its narrower provenance. Source inspection is not independent editorial acceptance.