Account
A record that can hold data or value and can be referenced by instructions.
TERMS AND DEFINITIONS · 2026
Solana Glossary
A glossary is a map for a technical conversation. The definitions below use plain language first, then point toward the system relationship that makes each term meaningful.
Words can have narrower meanings in a specific implementation or document. When precision matters, open the linked architecture, developer, or source material and check the version context.
Core terms
Program
Deployed logic that can be invoked under defined conditions.
Transaction
A signed request describing one or more intended actions.
Validator
An operator and machine participating in network processing or verification.
Slot
A unit in an ordering model used to describe a possible place for an update.
Finality
A condition under which a record is treated as settled within stated assumptions.
Terms in relationship
| Term | Relates to | Reader question |
|---|---|---|
| Account | State and ownership. | What information is stored and who can change it? |
| Program | Execution and permissions. | What inputs does the logic expect? |
| Transaction | Signing and ordering. | What action was requested and in what context? |
| Validator | Operations and consensus. | How is participation observed and maintained? |
How to use a definition
- Read the short definition without assuming it covers every edge case.
- Open the related term to see the surrounding system.
- Check the article date and source version.
- Replace the plain-language definition with the technical one when implementing.
“A definition is a doorway; the surrounding relationships are the room.”— Tymbra glossary note
Why vocabulary changes the reading
Technical words carry structure. If a reader confuses an account with a program, or a request with a confirmed result, later explanations become difficult to evaluate. A shared vocabulary allows disagreements to focus on evidence rather than hidden meanings.
- Define a term at first use.
- Keep synonyms separate from exact equivalents.
- Note when a word is used differently in another source.
- Return to the definition when a paragraph becomes ambiguous.
Find a missing term
Send Tymbra a suggestion with the term, the context in which you found it, and a source if one is available. We review suggestions for clarity, relevance, and attribution before adding them to the archive.
Suggest a termGlossary questions
Why do definitions include limitations?
A short definition can orient a reader, but limitations prevent it from being mistaken for a complete specification.
Should every unfamiliar word be added?
Not necessarily. The archive prioritizes terms that recur, carry technical meaning, or create confusion across related pages.
Definitions need examples
A definition becomes useful when a reader can recognize the term in a paragraph, diagram, or transaction description. Examples should clarify the relationship without pretending to cover every implementation.
When a source uses a term differently, the difference should be named rather than silently harmonized. This keeps the glossary useful across documentation styles and publication dates.
- Use the surrounding sentence as context.
- Check whether the term is a formal interface name.
- Follow related terms before drawing a conclusion.