Skip to content
Ephernity

§ 05 · Request for comments

The RFC suite.

Fifteen documents that together describe the protocol. EPH-NNN governs the storage pillar (the timed micro-ledger); EPH-CMP-NNN governs the compute pillar (the deterministic contract dialect). Each RFC is normative for one part of the system; the suite, taken as a whole, is the specification.

All · 15 Storage · 11 Compute · 4 Status · DRAFT License · CC BY-SA 4.0 Source ↗

§ 05.01 — Storage pillar

The timed micro-ledger.

  1. RFC-EPH-000

    Suite Overview & Architecture

    01/11

    Roadmap for the entire RFC suite — relationships, dependencies, the canonical reading order.

    Status · draft Read ↗

  2. RFC-EPH-001

    The bytes type and chunked I/O

    02/11

    Variable-length binary blobs as a first-class Borz type; the prerequisite for everything downstream.

    Status · draft Read ↗

  3. RFC-EPH-002

    std/blake3 content addressing

    03/11

    BLAKE3-256 hashing primitive; tree-hashing semantics; chunked verification.

    Status · draft Read ↗

  4. RFC-EPH-003

    Micro-ledger core

    04/11

    The 131-byte canonical entry header; append / read / chain-verify; storage backends.

    Status · draft Read ↗

  5. RFC-EPH-004

    std/merkle — checkpoints & proofs

    05/11

    RFC-6962-style trees over BLAKE3; periodic checkpoints; inclusion + consistency proofs.

    Status · draft Read ↗

  6. RFC-EPH-005

    HATP attestation binding

    06/11

    Root → tenant → host key delegation; measured boot; offline verification chain.

    Status · draft Read ↗

  7. RFC-EPH-006

    Timed-ledger tiers

    07/11

    T0–T4 tier specification; retention policies; promotion / demotion; crypto-shred.

    Status · draft Read ↗

  8. RFC-EPH-007

    std/chain — proof-only anchoring

    08/11

    OpenTimestamps + L2 + EBSI back-ends; anchor cadence; tamper-proof time.

    Status · draft Read ↗

  9. RFC-EPH-008

    Ledger node — networking & replication

    09/11

    libp2p gossip; per-ledger Raft; consistency model; gossip-then-fetch retrieval.

    Status · draft Read ↗

  10. RFC-EPH-009

    DENSE crypto-accelerator verify

    10/11

    Verification inside a flat KVM guest; microsecond-class hot path; sealed-host execution.

    Status · draft Read ↗

  11. RFC-EPH-010

    Falcon post-quantum signing

    11/11

    Falcon-1024 on durable tiers; hybrid Ed25519+Falcon during transition; constrained-target notes.

    Status · draft Read ↗

§ 05.02 — Compute pillar

The deterministic contract dialect.

The CMP series specifies the contract dialect as an interface. Any runtime that conforms can host contracts that other Ephernity verifiers will accept. The reference dialect surface is Borz; the reference implementation is closed-source (see stewardship), but the interface, the wire, and the ledger commitments are open.

  1. RFC-EPH-CMP-000

    Execution engine — overview

    01/04

    Compute pillar map: how the deterministic contract dialect, ledger-backed state, and per-call accounting compose on top of the storage pillar.

    Status · draft Read ↗

  2. RFC-EPH-CMP-001

    Deterministic contract dialect

    02/04

    The interface a "verifiable workflow" must conform to: no ambient inputs, seeded randomness, total ledger commitment. Reference surface in Borz.

    Status · draft Read ↗

  3. RFC-EPH-CMP-002

    Ledger-backed contract state

    03/04

    How a contract's state lives as ledger entries: head-of-state read, next-state write, replay semantics, snapshot-and-truncate.

    Status · draft Read ↗

  4. RFC-EPH-CMP-003

    Per-call accounting

    04/04

    Protocol-level unit-of-work accounting: bytes in, bytes out, deterministic operations counted. Pricing is operator-defined and out of scope.

    Status · draft Read ↗

The suite is intentionally small. Each RFC stands on its own; together they compose. Errata are tracked per document; superseded text is replaced rather than amended.