Documentation

AncientHub — reference

The public reference, organised into five pillars: About, Hub, Tools, Releases, and Roadmap. Start with About §1 for the legal scope; the rest is ordered from foundational context outward to forward-looking work.

vH.1.23phase: Chronos — The H.1.x benchmark/scoring rehaul arc

Scope of services

AncientHoldings GmbH is a software engineering and IT infrastructure services company. We build management tooling and operate commodity infrastructure for a community of server operators. We do not operate or own any blockchain protocol, wallet, exchange, custody service, mining service, or financial service.

Read full §1 Legal scope of services →

PILLAR I

About

Legal scope, project overview, technology stack, versioning, fix pool — foundational documentation for AncientHoldings GmbH and the StoaChain partnership.

§1

Legal scope of services

Authoritative scope: what AncientHoldings GmbH is (a software + infrastructure company) and explicitly is NOT (not a wallet / exchange / blockchain operator / custodian).

§2

What the hub is

The one-paragraph answer to "what does this thing do?"

§3

Technology stack

Runtime, storage, crypto, SSH, auth, styling, deploy.

§4

Versioning

MAJOR.MINOR.PATCH + z‑suffix convention + phase bumps.

§5

Fix-up pool

Accumulate small fixes; process in batches.

PILLAR II

Hub

Operating chainweb day-to-day: architecture, account tiers, sign-in, nodes, the Stoic system, backups, jobs, scaling, benchmarking, validator mechanics, VPS tunnels, Windows path, audit integrity, and mail.

§1

Architecture

Hub + worker + SSH fleet + Mailcow — how the pieces fit.

§2

Hub account tiers

Ancient / Modern / Baron / Operator — what each tier can do inside the hub itself. (Distinct from cluster roles.)

§3

Signing in

Signup, dual-auth login, single-active-scope model.

§4

Nodes

Registry, benchmarks, monitoring, per-role visibility.

§5

The Stoic System

Philosophy, eligibility engine, ledger, shadow vs live, mint model.

§6

Backups & seeds

Encrypted archives, donor snapshots, restore flow.

§7

Jobs & the worker

Background execution, parallelism, leases, SSH pool.

§8

Scaling plan

7-tier trigger-gated plan to 500k operators. Current tier state.

§9

Benchmarking

Full pipeline reference — what’s measured, hw_type classification, the ServerScore formula, upgrade procedure.

§10

System requirements

Operating system, kernel, package dependencies, minimum hardware. Ubuntu 24.04 Noble is the primary target.

§11

Cluster roles — Miner · Ouronet Validator · Hub

Formalises the three distinct roles in the StoaChain cluster: what each is, what each isn’t, and how they interlock.

§12

Validator mechanics

Validator Operators vs Delegator Entities, Quintessence thresholds (10k / 20k), slot math, reward formula with worked examples, Hub-acting-as-Delegator flow.

§13

VPS tunnel setup (for CGNAT operators)

Step-by-step walkthrough: rent a 1 €/mo VPS, run the two installer scripts, set up DuckDNS, point chainweb-node at the new hostname. Includes telemetry-backed sizing tables for Tunneler vs Tunnelee.

§14

Codex Cronotons

The Ancient-Admin surface for constructing StoaChain transactions and running them on a schedule (or manually) — signed server-side by the master-key-sealed Hub Codex. Builder, comprehensive schedule engine, autonomous worker-tick execution, and the per-fire audit trail.

§15

Audit integrity

Ed25519 signing key + SHA-256 body hash used to attest signed audit exports. Public key, fingerprint, and a 30-line Node verification script.

§16

Mail

Mailcow integration for Baron-tier mailboxes — multi-account sessions, dual-auth (IMAP + scrypt fallback), and in-app password rotation.

§17

Onboarding — zero to earning node

The complete operator journey in order: account, machine, the three internet types (fixed IP / rotating IP / CGNAT) and why the node needs a domain + certificate, DuckDNS, adding the server, firewall, install topologies (Prime vs multiple containers), benchmarking, storage commitment, warmup + staying at tip, Ouronet account verification, and earning real Stoicism.

§18

StoaChain Mining Pool

Point a rig at mining.ancientholdings.eu and earn automatic daily native-STOA payouts. How to participate (hub account, enable Pooled Mining, create workers, add a verified payout address), the 2.5% fee + whole-STOA no-withdraw push model, the per-account dashboard + pool frontend, and the Capacity & Health verdict. Built and operator-gated until switched on.

§19

SSO integration (OIDC)

Integrate an app with AncientHoldings single sign-on. The hub is a central OpenID Provider: users log in with their hub account and are recognised by role (ancient / modern / baron / operator). Register a client, run the authorize→callback→token flow against the exact endpoint URLs, and validate the RS256 id_token via JWKS — with a copy-paste Node/Hono verify snippet that pins issuer, audience, RS256, a random nonce, keys the local user on the opaque sub, and gates on roles.includes("ancient"). Token introspection is intentionally absent; consumers feature-detect via discovery.

§20

Pythia node pool integration (M2M)

The machine-to-machine contract by which the Pythia RPC service reads the hub node-pool FEED and reports back per-slot USAGE so operators earn for the reads their nodes serve. Both endpoints are POST folder-routes authenticated by ONE dedicated HMAC credential (a signed { signature, nonce, timestamp, payload } envelope — not the OIDC login). Covers the feed schema (bare-IP id, https url, refreshAfter), the usage report ({ period, slots:[{ id, keyedRequests, anonRequests, ok }] } where ok is a COUNT), the non-overlapping immutable-window contract with first-write-wins idempotency, the exact error shapes, the per-endpoint 120/60s rate limits, and operator earning. Metering is live; reward accrual is armed-and-rated by an ancient admin, off by default.

PILLAR III

Tools

Related public tools — calculator, Caduceus, Ouronet wallet, IPFS gateway.

Browse tools →