Layer1Labs is raising seed funding — $1–1.5M on a SAFE, seeking a lead investor. Talk to us →
Guide · ChronoHive

Applying ChronoHive Admission Control to Existing Storage Workflows

How ChronoHive admission control fits the storage workflows you already run: where the decisions attach, what applying it does not change, and the published evidence it stands on.

Version 1.0 · October 26, 2026 · PDF · 8 pages · Layer1Labs Silicon Inc.

Key figures

+9.85%

admission gating measured on an Amazon EC2 g5.xlarge instance (NVIDIA A10G) — positive on all three platforms tested, and under the 10% confirmation bar on each

Measured — preregistered A/B; an observation, not a proof

401 admitted

operations admitted under the coordinated policy in the contention demonstration, with 119 refused exactly as programmed; an unmanaged baseline admitted all 480

Demonstrated

0.3–1.5 s

per-run checkpoint stall in the large-checkpoint campaign, down from 10.5–11.7 s

Measured

3×

the bound on the asynchronous checkpoint writer’s memory, as a multiple of checkpoint size — the previous transport reached ~7×

Measured — 40 preregistered isolated trials

What it covers

  1. The problem admission control answers
  2. Where the decisions attach
  3. What applying it does not change
  4. The published evidence
  5. What a pilot measures
  6. Prerequisites and limits
  7. Questions to ask before you start

Basis

This guide assembles what the ChronoHive page and the FAQ publish about admission control in existing storage workflows. It makes no new claims: the depth limit is the site’s own — where the decisions attach and what a pilot measures, with no implementation internals.

Every measurement behind it is single-node, on at most two GPUs. The guide’s limits are the published ones, in the same terms as the FAQ: the regimes where ChronoHive currently trails the conventional approach are stated, not softened.