Glossary (reference)

Locked

This page mirrors the learn glossary so reference pages can deep-link to terms without dragging readers out of the reference section. Every Monolythium-specific term is defined once, in the learn glossary; this is the same content, surfaced in the reference context. If the two ever drift, the learn glossary is canonical.

A — D

Anchor — Canonical commit unit. A finalized point in the DAG-BFT consensus, chosen from a wave. Replaces “block” in user-facing prose. See Anchors, waves, vertices.
bech32m — The address format. Addresses are BLAKE3(domain || algo_id || pubkey)[..20] encoded as bech32m with a typed HRP discriminator (mono, monos, monoc, monok, monom, monox, plus reserved). The bech32m representation is the address, not a display preference.
Cluster: Group of operators running a single DVT consensus identity (one committee seat). The current public shape is 10 operator positions with 7-of-10 threshold signing (7 active + 3 standby).
DVT — Distributed Validator Technology (the industry term): one consensus seat run by many independent operators. The chain has no solo-operator path.

E — L

Mempool ordering — The registered public-testnet profile uses a plaintext mempool. There is no encrypted, sealed, private-send, or threshold-decrypted lane.
ERC-8004 — A standard considered for future agent identity work. No supported on-chain Stele identity or economic path is released. See Agent identity.
FRI/STARK — A roadmap proof direction, not an active verifier or value path in the current public product boundary. See Post-quantum cryptography.
Gap record — Conceptual compact representation of a quiet finalized range. Exact triggers, payloads, retention, and storage behavior are release-specific and are not a public operator contract.
Genesis: The first anchor. Testnet 69420 genesis: 0xe22733f4…. Mainnet genesis: TBD. See Genesis reference.
HRP — Bech32m human-readable prefix. Discriminates account types: mono (EOA), monos (system), monoc (contract), monok (custodial), monom (multisig), monox (extension). Reserved: monor, monop, monoi, monoa.
LYTH — Native asset display unit of Monolythium, with 18 decimals. A proposed private-denomination design is not released; current docs certify no private-value transfer or conversion path.

M — R

ML-DSA-65: The account transaction signature scheme. FIPS-204 post-quantum. Also the consensus signature: each operator signs independently with its own ML-DSA-65 key, and a cluster round certificate is a 7-of-10 bitmap multisig (a popcount of individual per-operator signatures), where any 7 of the cluster’s members’ signatures form a valid certificate.
ML-KEM — The key encapsulation mechanism used for transport security (libp2p Noise-PQ, ML-KEM-768).
Monarch OS — A planned immutable node-appliance design. No public production image or certified operator procedure is available.
Monarch Desktop — A planned human-approved Monarch OS operator console. It is separate from the consumer Monolythium Wallet and is not publicly operational.
Name registry — Planned human-readable-name design. No registration, resolution, pricing, transfer, reserve-policy, or wallet transaction path is currently released. See Addresses and names.
Recovery phrase (BIP-39) — The wallet backup standard. A standard 24-word BIP-39 mnemonic whose BIP-39 seed is expanded by a SHAKE256 KDF (monolythium.mldsa65.v1) → ML-DSA-65 keygen → 20-byte address.
protocore — The Monolythium node runtime name. No generated, versioned public command catalog is certified. See CLI boundary.
Agent runbook — A planned design document. No supported economic draft, signing, or submission contract is released. See Runbooks.

S — Z

Starfish-C — The DAG-BFT consensus algorithm Monolythium uses, based on the 2025 paper by Polyanskii, Muller, and Vorobyev.
Finality evidence — The registered consensus profile uses 7-of-10 ML-DSA-65 cluster certificates. Public RPC currently exposes status and provenance; no receipt-proof or checkpoint-proof API is certified here.
Vertex — One operator’s proposal in the DAG. Many vertices may contribute to a wave, and waves may contribute to an anchor.
Wave: A round of vertex proposals, ~4 seconds. Anchors are chosen from waves.
Provider-listing draft — A durable, wallet-owned private Studio record. It is not published, discoverable, transactable, or exposed through MCP, and it does not satisfy a hosted booking draft’s published-listing prerequisite.
Hosted Stele MCP — A live keyless OAuth resource at https://stele.monolythium.com/mcp whose authenticated tools/list response is authoritative for the runtime inventory. Deployed baseline operations include stele_search_services and non-economic stele_create_booking_draft; no fixed tool count is promised. Production currently has 0 published services, so no successful booking-approval draft can be created. Booking-draft calls fail closed unless their listing, durable backend, and release-readiness gates are healthy.
Local lyth_mcp Stele profile — The public v0.1.0 GitHub prerelease with exactly three read/status tools: stele_connection_status, stele_search_services, and stele_agent_wallet_status. The profile has no key, signing, or transaction authority. See MCP status.
lyth_* — The native JSON-RPC namespace. These docs verify a read-only subset for chain identity, round, peers, and runtime provenance.