Digital asset infrastructure glossary
Definitions are provided for learning and do not amount to financial advice.
Technical words often look more certain than the systems they describe. Zafara uses this glossary to state the ordinary meaning first, then identify the boundary a reader should ask about. Definitions may vary by protocol, vendor, jurisdiction and document version.
“Before comparing a number, compare the definition attached to it.”
Core terms
ASIC
An application-specific integrated circuit designed for a defined computational task. The relevant comparison may include algorithm, generation, power draw and firmware.
Validator
A protocol participant that performs network duties under stated consensus rules. A validator description should identify responsibilities, uptime rules and upgrade procedures.
Delegation
An arrangement where a participant assigns a protocol role or weight according to network rules. Terms may address lockups, withdrawal and governance participation.
Uptime
A measure of availability whose meaning depends on the stated observation window, exclusions and monitoring method.
Hashrate
The amount of computational work performed over time, usually defined by an algorithm. A hashrate figure should be paired with measurement conditions.
Cooling load
The energy and engineering requirement associated with moving heat away from equipment. It may be reported separately or within facility load.
Terms that need a boundary
| Term | Ask for | Reason |
|---|---|---|
| Capacity | Rated, installed or active capacity | Labels may describe different states |
| Efficiency | Unit, load and test condition | Results depend on operating mode |
| Reward | Protocol rule, historical amount or estimate | Future values are not established by past records |
| Uptime | Window and outage exclusions | Maintenance can change the reported percentage |
Readers should preserve the source's original wording when a term is disputed. A translation may be helpful, but it should not hide a qualification or a different technical meaning.
Using the glossary in practice
- Find the term in the article or project document.
- Read the plain-language definition.
- Check the unit, date, operator and boundary attached to it.
- Compare only with records that use a compatible definition.
- Keep protocol vocabulary separate from marketing language.
- Ask whether a translated term has a local technical equivalent.
- Record version changes when a rule or specification is updated.
- Contact Zafara when a definition appears inconsistent with its source.
Quick reference questions
Can one word have several meanings?
Yes. Capacity, uptime, reward and efficiency are common examples. The document's definition and measurement boundary control the useful meaning.
Are glossary entries recommendations?
No. They are educational definitions and do not assess suitability, profitability or personal circumstances.
How are entries updated?
Material changes are reviewed against current public documentation and dated in the editorial record.