Glossary

Balances live on accounts (addresses), not UTXOs—friendlier for wallets/programs.

Trying to manipulate randomness; mitigated with VRF aggregation and committee rules.

Byzantine Fault Tolerant consensus: continues working even if some nodes act maliciously.

A signature scheme that lets many validator signatures be combined into one compact proof.

A small VRF‑sampled validator group that signs and finalizes blocks.

How the network agrees on the next block. JEM uses PoE + VRF and a HotStuff‑style committee finality.

Proof from your OS/secure hardware that a device and action are genuine (WebAuthn/OS APIs).

Adjusting the selection threshold each epoch so block rate/emissions stay on target.

A public randomness beacon network we can import while bootstrapping.

Exponential Moving Average: a smoothing method JEM uses to avoid oscillations in difficulty.

How new JEMs are minted over time (leader/committee/honey‑pot/ecosystem splits).

A fixed window of time in JEM. Engagement is measured per epoch and affects proposer weight.

When a block is confirmed and won't be reverted. JEM uses a HotStuff‑style two‑phase vote with aggregated signatures.

A flexible query API; JEM’s gateway can stream live blocks/tx.

A randomized bonus pool created from orphaned blocks; unlocks extra tickets when a hidden trigger occurs.

A modern BFT protocol family with simple phases and clear safety/liveness properties.

Peer‑to‑peer messaging for blocks/tx/tickets; resilient and decentralized.

A lightweight proof you’re a real, present human (e.g., passkey prompt/biometric).

Pending transactions/tickets waiting to be included in a block.

Forwarding actions over local radios (Bluetooth/Wi‑Fi) when offline—relays can earn tickets.

A valid block that lost a fork race; in JEM, orphans seed honey pot events.

Proof of Engagement: a system where verified human actions mint temporary, decaying lottery chances (tickets) to propose blocks.

Proof of Engagement + Verifiable Random Function: real user activity gives temporary 'tickets' (weight), and a cryptographic lottery (VRF) fairly picks block leaders.

Combining attestations/vouches to limit Sybil influence per human.

The minimum validator votes required to finalize a block.

A public randomness source for leader/committee selection—derived from prior VRFs (or drand while bootstrapping).

Per‑epoch caps and timing rules that prevent spam or runaway advantage.

Embedded databases for node storage.

JSON‑RPC: the HTTP API for wallets and apps to talk to a node.

Developer toolkit to emit actions, handle quotas, and submit tickets.

Penalties for validators who misbehave (e.g., double‑vote).

A small time slice where a block proposer may produce a block.

Sends lightweight 'witness' proofs so mobile clients don’t need full state.

Many fake identities controlled by one actor; JEM limits them with caps/attestation.

A cryptographic, non‑transferable 'lottery chance' minted from verified actions; decays over time.

Verifiable Random Function: produces a random output with a proof anyone can check—used to pick leaders/committees fairly.

Your per‑epoch block lottery strength, derived from valid tickets; capped and decays.