Reference desk

Key terms for ecosystem reading

A glossary is a starting point, not a replacement for technical documentation. Definitions below use plain language and identify nearby questions a reader may want to investigate.

“A term becomes useful when its boundaries are as clear as its short definition.”

Account

A location or record used to hold data, authority, or state. Ask who owns it, what data it contains, and which program can change it.

Instruction

A structured request describing an intended action. Review its inputs, signers, destination, and expected result.

Program

Code that defines behavior under protocol rules. A program may read accounts, validate inputs, and write permitted state.

Transaction

A package carrying one or more instructions and the signatures needed for submission. Its final status should be checked independently.

Validator

An operator participating in network processes. Requirements, software, and operational duties can change over time.

RPC

A service interface used by applications to request network data or submit requests. Availability and terms depend on the provider.

Term relationships

Start withThen askRelated terms
AccountWho can change its state?Owner, authority, data layout
InstructionWhat state transition is requested?Signer, input, transaction
ProgramWhich interface does it expose?Instruction, account, error
ValidatorHow is participation monitored?Uptime, software, commission

How to use a definition

  1. Read the short definition without assuming it is complete.
  2. Open the related terms and identify the missing relationship.
  3. Check the current primary source and version context.
  4. Write an example in your own words.
  5. Record the question that remains unresolved.
  • Do not confuse a display label with an authority.
  • Do not assume two interfaces use the same terminology.
  • Do not treat an example as a complete implementation.

Definition

What the term means in the context of the page.

Boundary

What the term does not mean or cannot establish.

Next source

Where a reader can verify technical detail.

Living reference

Terminology can change with software and documentation. Send corrections with the relevant source and date through the contact page.