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.
Reference desk
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.”
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.
A structured request describing an intended action. Review its inputs, signers, destination, and expected result.
Code that defines behavior under protocol rules. A program may read accounts, validate inputs, and write permitted state.
A package carrying one or more instructions and the signatures needed for submission. Its final status should be checked independently.
An operator participating in network processes. Requirements, software, and operational duties can change over time.
A service interface used by applications to request network data or submit requests. Availability and terms depend on the provider.
| Start with | Then ask | Related terms |
|---|---|---|
| Account | Who can change its state? | Owner, authority, data layout |
| Instruction | What state transition is requested? | Signer, input, transaction |
| Program | Which interface does it expose? | Instruction, account, error |
| Validator | How is participation monitored? | Uptime, software, commission |
What the term means in the context of the page.
What the term does not mean or cannot establish.
Where a reader can verify technical detail.
Terminology can change with software and documentation. Send corrections with the relevant source and date through the contact page.