Every blockchain needs to agree on time. Not wall-clock time — nobody trusts a validator's system clock — but an ordering that lets the network say "this happened before that" without a central referee. Different chains solve it differently. EmpoorioChain's answer is deliberately simple, and this post explains what it is and what it is not.
Slots, not proofs
EmpoorioChain produces blocks with Aura (Authority Round). Time is divided into fixed 6-second slots (SLOT_DURATION = 6000 ms in the runtime). The validator set is known in advance, and each slot has exactly one designated author, chosen round-robin. If the author for slot n is offline, slot n is simply empty and the chain continues at slot n+1.
That gives the chain a clock with three properties:
- Predictable. Anyone can compute who should author the next block and when.
- Cheap to verify. A block claims a slot; validators check that the claimed author owns that slot and that the slot is not in the future. There is no verifiable delay function to grind through.
- Independent of finality. Aura orders blocks; GRANDPA decides which of them are irreversible. Keeping the two separate is what lets the chain keep producing blocks even while finality is temporarily behind.
The timestamp inherent
Each block carries a timestamp set by its author through the Timestamp pallet. It is an inherent, not a transaction: the author includes it, and the other validators accept it only if it falls within a tolerance window around their own clock and is strictly greater than the previous block's. This is what pallets use when they need a date — staking eras, vesting schedules, the public sale window, subscription renewals. Nothing in the runtime reads the operating system clock.
Eras: economic time
On top of slots and timestamps sits a coarser unit: the era, 24 hours long, 365 per year. Eras are where economic time is measured. Staking rewards are computed per era, and DMS emission follows a gap-decay rule evaluated once per era:
emission_per_era = (supply_cap − current_supply) × 0.0083446 %
That is roughly 3 % of the remaining gap per year, decreasing forever and never reaching the cap. The nominal APY for stakers is capped at 20 %. Details are in the tokenomics post; the point here is that the clock, the calendar and the economics are all derived from the same slot counter.
What EmpoorioChain deliberately does not do
There is no cryptographic proof of elapsed time embedded in the block stream. Some chains use one to let validators pipeline transactions before consensus. EmpoorioChain gets its throughput elsewhere — parallel execution inside the block and a DAG-ordered mempool in front of it — and keeps the clock as the simplest component in the system, because the clock is the one thing you never want to debug at three in the morning.
The repository does contain experimental consensus modules (DAG ordering, HotStuff-style research code). They are research, not production. The chain you can connect to at rpc.testnet.empooriochain.org is Aura and GRANDPA, and the documentation says so explicitly.
Based on the runtime constants in runtime/src/lib.rs, CONSENSUS_STATUS.md and TOKENOMICS.json.