Glossary
The exact vocabulary, and the words Elgora deliberately does not use.
Roles
Poster — the party that approves and funds one challenge. Owns the wording and the wallet, never the result.
Solver — the party that does the work and submits it. Sometimes described loosely as "the submitter"; Solver is the term used everywhere in payloads and commands.
Guardian — an independent judge on a bounty's pinned roster. Publishes one written Verdict and records one on-chain Verdict per bounty.
Coordinator — an address given the first opportunity to call settlement, where one is configured. Improves liveness; supplies no decision.
Protocol owner — the address that holds the Hub's configuration powers. Cannot decide a bounty result. See Limits and control.
Roster admin — the single address that may add, remove, or replace Guardians.
Objects
ElgoraHub — the smart contract. The sole authority for escrow, lifecycle,
Verdict agreement, settlement, claims, and refunds.
bounty_challenge.md — the approved challenge page. One UTF-8 Markdown
file whose exact bytes are committed on-chain.
Submission — one Solver's sealed artifact package for one bounty. One active Submission per Solver per bounty; a re-submission replaces it.
Verdict — a Guardian's judgement. Say written Verdict for the published document and on-chain Verdict for the recorded decision, but only when the distinction matters. There is no second word for a Guardian's judgement.
VerificationRecord — an advisory summary derived after finality. Evidence,
never a claim receipt, never proof of payment, never an authority.
Guardian roster — the ordered committee of Guardians who judge one bounty. Never a single Guardian. Each bounty pins the roster that was live when it was created, recorded on-chain as a hash, so the committee cannot be substituted afterwards and both its membership and its history stay queryable.
Values
spec_commitment — keccak256 of the approved challenge bytes.
submission_commitment — keccak256 of a Solver's canonical sealed
envelope.
report_commitment — keccak256 of a Guardian's written Verdict document.
The contract, the subgraph, the API route, and the VerificationRecord all
spell it the same way.
guardian_roster_hash — a hash over the ordered roster, pinned per bounty.
Base units — the escrow token's smallest units. USDC has 6 decimals, so
1 USDC is 1000000. Amounts are always integer strings.
Basis points (bps) — hundredths of a percent. 250 bps is 2.5%.
Outcomes
open — accepting Submissions, or being judged, or awaiting settlement.
awarded — a winning Solver and Submission were agreed by two thirds of
the pinned roster.
no_valid_submission — two thirds agreed nothing met the criteria. The
Poster is refunded in full if nobody submitted, otherwise minus the Guardian
fee; no treasury fee is charged.
timed_out — nothing settled in time. The Poster is refunded in full, with
no fees.
Words Elgora does not use
| Not used | Why |
|---|---|
| Vote | Guardians record Verdicts. It is a judgement against written criteria, not an opinion poll |
| Appeal, dispute, veto | None exists. Settlement is final |
| Score, rating, reputation | There is no scoring framework, no Solver ranking, and no reputation system |
| Stake, slash, bond | Solvers risk nothing but their time |
| Account, login, session | There are none. A wallet signs each request |
| Cancel, withdraw | A funded bounty cannot be cancelled and escrow cannot be pulled back before an outcome |
| Draft bounty, edit bounty | A published challenge is immutable. A change is a new bounty |