RE4CTOR is a sealed entropy appliance with an open, verifiable perimeter.
It delivers signed outputs (ECDSA + ML-DSA-65) and is engineered for
protocol fairness, measurable security, and audit-grade evidence.
Live gateway calls + a fast frontend entropy diagnostic (Shannon bits/byte + monobit ratio).
This is not a replacement for offline BigCrush/NIST reports, but it shows “non-degenerate output” in real time.
Background sampler pings /v1/random periodically (no /health).
Live API Playground
Calls: /v1/random and /v1/vrf.
After /v1/random, the page computes a quick entropy estimate from returned bytes.
{ "hint": "Click a button to call the RE4CTOR gateway with X-API-Key: demo." }
Browser note: CORS must allow your origin (your prod Caddy already supports preflight for X-API-Key).
Figure 1.1 · Latency distribution (gateway → VRF node)
prod VPS (representative)
Architecture
RE4CTOR treats randomness as an engineered system: sealed entropy core, auditable gateway,
and verifiable protocol surfaces. This replaces “hand-wavy randomness” with measurable, testable, deployable infrastructure.
Sealed core
Fail-closed entropy
If health tests fail, output stops instead of silently degrading. This is the operational property most RNG stacks omit.
Verifiable perimeter
Signed outputs
Signing (ECDSA + ML-DSA-65) supports today’s chains and an explicit PQ migration track.
Protocol envelope
Measured surfaces
Benchmarks include protocol surfaces (not only “verify gas”) so the weakest-link can be reasoned about quantitatively.
Figure 2.0 · Protocol Envelope Dominance
model: weakest-link / surfaces
Compliance & Validation
Public pages keep claims conservative. Detailed artifacts live in your audit bundle (reports, SBOM, integrity manifests).
This section is intentionally minimal and “adult”: only what you can stand behind.
TestU01 BigCrush
160 / 160
Offline validation on large samples; reports shipped per release.
NIST SP 800-22
STS suite
Release-gated QA plus continuous health tests (RCT/APT).
Public page avoids over-claiming. Full reproducible detail lives in the benchmark lab and audit artifacts.
Product surfaces
Everything you consume is an explicit surface: entropy bytes, dual-signed VRF, and verification helpers.
The site keeps wording conservative; the artifacts live in Test Reports and SBOM.
RNG surface
GET /v1/random
Raw high-entropy bytes via the gateway. Designed for fairness-sensitive protocols, gaming, L2 sequencing, and AA.
Tip: the website playground uses /api/ (same-origin reverse proxy). For direct calls, use https://api.re4ctor.com.
Security posture
RE4CTOR is built around an operational invariant: fail-closed entropy. If health/quality degrades, output stops.
The perimeter stays auditable via signed responses and reproducible artifacts.
Fail-closed
Stop & alert
No silent degradation: health tests gate output instead of letting “maybe-random” leak into production.
Audit bundle
Reports + SBOM
Artifacts are versioned and shippable: test reports, SBOM, and integrity notes.
PQ track
Explicit migration
Dual-signing supports today (ECDSA) and an explicit PQ lane (ML-DSA-65) with measured surfaces and benchmarks.
Pricing
Choose a plan and get redirected to Stripe Checkout.