REFERENCE DESK

Solana terms in plain language

This glossary is a reading aid for Gajema articles. Definitions are intentionally compact, but compact does not mean universal: a term can carry a more specific meaning inside a particular implementation, release, or research paper. Use the linked guides and current primary documentation when a detail affects software, security, compliance, or a production decision.

Readers can use the glossary in two directions. Start with a familiar word and follow related entries, or begin with an article and return here whenever a sentence introduces a new concept. The table below groups terms by the kind of question they help answer.

How to use this reference

Read the definition first, then check the related concept in the second column.
Notice whether the word describes a person, a data object, a software instruction, or a period of network activity.
Use the source links in longer articles to confirm details that may change over time.
Do not treat a glossary definition as operational, legal, financial, or security advice.

Core vocabulary

Term	Plain-language meaning	Useful question
Account	A data container associated with an address and used to hold information for the network or an application.	What data does this account contain?
Block	A recorded unit of ordered network activity containing transactions or related metadata.	When was this activity recorded?
Epoch	A defined period used for network scheduling and operational accounting.	Which period does this record belong to?
Program	Code deployed to the network that responds to instructions according to its rules.	What permissions and inputs does it require?
Validator	A participant that processes and helps confirm activity under the protocol.	How is this participant configured?
Transaction	A signed request that asks the network to process one or more instructions.	What instructions and accounts are involved?
Token account	An account structure used by an application to associate token-related state with an owner or authority.	Who controls the relevant authority?
RPC endpoint	A service interface through which software requests network data or submits instructions.	Who operates the endpoint and what are its limits?

Read the terms by layer

Network layer: blocks, epochs, validators, and consensus-related language.
Data layer: accounts, addresses, instructions, and program state.
Application layer: interfaces, permissions, indexes, and user flows.
Research layer: measurements, samples, assumptions, and source quality.

Layering helps avoid a common mistake: assuming that a user interface, a program, and the network itself are the same thing. They interact, but they have different owners, failure modes, and records.

Checklist for unfamiliar terms

Can the term be defined without using another undefined term?
Does the source use the word in a specialized way?
Is the definition tied to a particular software version?
What would change if the associated authority or endpoint changed?
Which part is observed fact and which part is interpretation?

Writing these questions down can make a technical conversation easier to follow and can reveal when two people are using the same word differently.

“A glossary is not a shortcut around technical reading; it is a map that helps readers return to the source with fewer assumptions.”

Terms need context

Words such as “ownership,” “account,” and “authority” can sound familiar while carrying precise meanings in a protocol or application. Gajema therefore treats definitions as entry points. Follow the related architecture, developer, or infrastructure pages for examples, and check current documentation before relying on a term in code or a formal analysis.

Continue to the architecture guide →

Common reader questions

Why are some definitions qualified?

Because technical terms can vary by implementation, release, or context. A qualified definition is more useful than a broad statement that hides those boundaries.

Are these definitions official?

No. They are independent educational explanations. The relevant project documentation remains the appropriate source for exact behavior and current interfaces.

How can I suggest a correction?

Send the term, the page address, the wording that seems unclear, and a source or explanation through contact.php.