Business model overview · regulatory-driven cryptographic audit infrastructure · peter@kenosian.com
The TTTPS audit chain is not a software subscription. It is a legal evidence repository that accumulates over the customer's regulatory retention horizon. Continuity of evidence is preserved across the multi-year obligation period defined by the underlying regulations.
Built for global interconnection fabrics · leveraging carrier-neutral global footprint · CAPEX-free model
Deployable across carrier-neutral metros worldwide. Enterprises facing EU AI Act / MiFID II / MiFIR / DORA are a natural fit for TTTPS and HYDRA-AUDIT. No hardware installation. No CAPEX. Activated via carrier-neutral virtual interconnect once on fabric.
EU AI Act GPAI / Art.53 — August 2, 2026 · D-??
A purpose-built IETF-track cryptographic AI audit solution aligned with EU AI Act Art.12/53 — training data provenance, tamper-evident audit chain, and regulatory-structured evidence.
GPAI/Art.53 obligations: 2026-08-02 (no change). High-risk/Art.12 obligations: 2026-08-02 (current law) → deferred to 2027-12-02 under EU Digital Omnibus provisional agreement (pending formal adoption).
→ 2026 Global AI Regulatory Enforcement Timeline — jurisdiction-by-jurisdiction breakdown
€15M or 3% turnover penalty · To our knowledge, none of the established ML observability tools — nor timing-only services — provides this.
| Regulation | Enforcement | Penalty | Who Is Affected |
|---|---|---|---|
| EU AI Act Art.53 (GPAI)Art.12 (high-risk): 2026-08-02 current law → 2027-12-02 deferred (Digital Omnibus provisional, pending formal adoption) | 2026-08-02 (D-67) | €15M or 3% global turnover | All GPAI providers |
| EU AI Act Art.12 (high-risk) | 2026-08-02 current law → 2027-12-02 deferred (Digital Omnibus provisional, pending formal adoption) | €15M or 3% global turnover | High-risk AI operators |
| DORA Art.17 | 2025-01-17 LIVE | €10M or 2% | EU financial services firms globally |
| MiFID II RTS 25 (clock sync; extended under 2024 MiFIR review) | pending application date | FCA/ESMA discretion | Every EU financial institution with algo trading |
| Korea AI Basic Act | 2026-01-22 LIVE | KRW 300M | AI companies operating in Korea |
| MAS TRM (Singapore) | LIVE | SGD 1M | Financial institutions operating in Singapore |
TTTPS is a purpose-built IETF-track solution for this gap — few competing implementations exist at this compliance depth.
| Layer | Product | Function | Status |
|---|---|---|---|
| Layer 00 | TTTPS | Cryptographic time anchor (all products) | ✅ GCP live · 🔜 fabric integration-ready |
| Layer 10 | HYDRA-KV | LLM inference acceleration — lattice + CRDT | ✅ GCP live · 🔜 fabric integration-ready |
| Layer 20 | HYDRA-CDN | Edge delivery, India/APAC, lattice-coded | Phase 2 |
| Layer 30 | HYDRA-GRID | Power grid monitoring | Phase 3 |
| Layer 40 | HYDRA-AUDIT | AI regulatory audit chain (EU AI Act Art.12/53) | ✅ GCP live · 🔜 fabric integration-ready |
Single 100GbE port → multiple product layers simultaneously · Customer virtual interconnect → recurring infrastructure revenue
| Metric | Value | Condition |
|---|---|---|
| seal_batch_keyed throughput | 17.3M events/s | GCP CPU in-memory microbench |
| lattice compression | 3.2× (lossy, CPU round-trip) | cosine 0.79 vs FP16; top-1 token preserved |
| CRDT prefix dedup | prefix-sharing sim / 95.6% theoretical | QUIC measured 2026-05-16 (GCP) |
| CRDT + Lattice combined | ~93% at 90% shared prefix | 3.2× compress × prefix dedup (analytic) |
| Cross-node QUIC latency | 95.9ms (GCP) → <1ms (target) | carrier-grade 100GbE metro target |
| Lattice-coded India 30% loss | ~99.8% theoretical | lattice-coding bound · simulated |
| chain_integrity (restart) | true — 796/796 events | Redis AOF · Art.12 90-day proven |
| k6 load test — KV | 941 req/s (rate-limited) → ~7,000 req/s projected | GCP 2-core · carrier-grade 100GbE 2-node sim · integration-ready |
| k6 load test — CDN | 922 req/s, 0% error | 100 VU |
| Full-stack scenario coverage | 22/23 (96%) | Full stack · one gap = GCP firewall |
| Test baseline | 783 PASS / 0 FAIL | cargo test --workspace · 2026-05-23 |
| Chain Age | Engagement Driver | Revenue Pattern |
|---|---|---|
| Month 1–3 | Contract activation · chain initiated | Standard subscription revenue |
| Month 4–12 | 90-day Art.12 chain complete — first regulatory submission filed | Subscription + precision time source |
| Month 13–24 | Annual audit report anchored — compliance officer signed off | Fabric traffic increases |
| Month 25–36 | MiFID II 7-year retention begins — chain becomes legal record | Cross-connect upsell |
| Year 7 | MiFID II 7-year obligation complete | Permanent compliance anchor |
TTTPS customer engagement is anchored by regulatory retention obligations rather than by contract alone. Continued use is aligned with the customer's legal evidence requirements over the multi-year horizon.
| Dimension | Timing-only services | TTTPS (Kenosian) | Winner |
|---|---|---|---|
| Hardware required | Physical timing hub per metro | None — pure software | TTTPS |
| Install time | 4–6 weeks physical | Instant via virtual interconnect | TTTPS |
| CAPEX | High (customer + vendor) | Zero | TTTPS |
| MiFID II RTS 25 (clock sync) | ✅ | ✅ via precision time source | Equal |
| EU AI Act Art.12/53 | ❌ None | ✅ Full: Art.11/12/15/19/53 | TTTPS |
| Cryptographic evidence chain | ❌ Plain logs | ✅ Ed25519 + blake3 | TTTPS |
| Throughput | Est. <1M events/s (timing-only service) | 17.3M events/s (batch seal, CPU in-memory, GCP)HTTP E2E: 2,589 req/s (k6 1000VU) · different measurement basis | TTTPS |
| Recurring infrastructure revenue contribution | ❌ Cross-connect only | ✅ Per customer | TTTPS |
| 7-year compliance retention horizon | ❌ | ✅ Chain accumulation | TTTPS |
| Regulatory reporting | MiFID II RTS 25 (clock sync) only | JSON-LD, all jurisdictions | TTTPS |
Timing-only services focus on cross-connect delivery. TTTPS adds a cryptographic audit chain on top of precision time, generating perpetual recurring revenue per customer that compounds as the chain deepens — a differentiated, additive capability rather than a replacement. The model is an illustrative tiered subscription; see Products for current pricing tiers.
Revenue scales with regulatory expansion: each new applicable regulation (DORA, EU AI Act, multi-jurisdiction) adds upsell to the existing chain. Net retention expands rather than contracts because compliance scope grows over the customer lifecycle. Pricing tiers are published on the Products page.
| Capability | Fabric-native | Hyperscaler |
|---|---|---|
| EU AI Act audit | ✅ TTTPS | ✗ |
| MiFID II RTS 25 (clock sync) | ✅ Precision time | Partial |
| Cryptographic chain | ✅ Ed25519 | ✗ |
| 7-yr legal evidence | ✅ Redis AOF | ✗ |
| Multi-year compliance retention | ✅ Structural | ✗ |
| Zero CAPEX deploy | ✅ Virtual interconnect | Requires setup |
Illustrative target segments — pre-engagement. Not contracted customers. Revenue figures are estimated potential ARR and illustrative only, not contracted.
| Target Segment | Region | Regulatory Exposure | Tier |
|---|---|---|---|
| Global investment banks | EU + US + APAC | MiFID II RTS 25 + DORA + EU AI Act | Institutional |
| Universal banks with algo desks | EU + US + APAC | MiFID II RTS 25 + DORA + EU AI Act | Institutional |
| Tier-1 brokerage and prime services | EU + US | MiFID II RTS 25 + DORA | Institutional |
| GPAI model providers | EU + US | EU AI Act GPAI + DORA | Institutional |
Illustrative ROI: for a large institution, EU AI Act maximum exposure (3% of global revenue, max-penalty scenario) dwarfs annual audit subscription cost — the audit cost is a fraction of one percent of penalty exposure.
| Target Segment | Region | Regulatory Exposure | Tier |
|---|---|---|---|
| Proprietary trading / market-making firms | EU + US | MiFID II RTS 25 (clock sync, ±1µs via precision time source) — pending application date | MiFID Pro |
| HFT and electronic liquidity providers | EU | MiFID II RTS 25 | MiFID Pro |
| Cross-border algo trading firms | US + EU | MiFID II RTS 25 + FINRA CAT | MiFID Pro |
| GPU cloud / AI inference providers | US | EU AI Act GPAI | MiFID Pro |
Thousands of cloud/AI SaaS companies across carrier-neutral metros. EU AI Act GPAI/Art.53 enforcement Aug 2, 2026; high-risk/Art.12 deferred to 2027-12-02 (Digital Omnibus provisional, pending formal adoption). Compliance tier covers all GPAI operators below system-risk threshold.
DORA Art.17 mandates cryptographic audit trails for 22,000+ EU financial institutions. TTTPS is a purpose-built IETF-track solution. A 5% conversion implies a multi-tens-of-millions ARR opportunity.
Adding EU AI Act (Aug 2026) + MAS TRM + Korea AI Basic Act expands the total addressable market materially. These projections are illustrative. Enforcement, however, is not optional.
Major interconnection and cloud operators have been designated Critical Third-Party Providers under DORA (ESA, Nov 2025). Every financial tenant is already legally required to document and audit their dependency on critical infrastructure providers. TTTPS is the audit layer.
| Date | Event | Penalty | Product |
|---|---|---|---|
| 2025-01-17 | DORA Art.17 — live | €10M or 2% | HYDRA-AUDIT |
| 2025-11 | Major cloud operators designated DORA CTPP | Upstream risk | HYDRA-AUDIT |
| 2026-01-22 | Korea AI Basic Act — live | KRW 300M | TTTPS |
| 2026-03-01 | Vietnam Law 134 — live | 5% revenue | TTTPS |
| 2026-08-02 | EU AI Act Art.53 (GPAI) — D-68Art.12 (high-risk): 2026-08-02 current law → 2027-12-02 deferred (Digital Omnibus provisional, pending formal adoption) | €15M or 3% | TTTPS + AUDIT |
| 2026-08-02 | GPAI Code of Practice enforcement | 26 cos. signed | TTTPS |
| 2027 | MiFID II 7-year retention review | Ongoing | Full chain |
TTTPS provides cryptographic proof-of-time designed to satisfy timestamp integrity requirements across financial, AI, and infrastructure regulations. HYDRA-AUDIT provides the event chain and provenance layer for AI system compliance.
| Regulation | Requirement | Coverage | Product |
|---|---|---|---|
| EU AI Act Art.12/53EU 2024/1689 | AI event logging, GPAI training data provenance, tamper-evident audit chain | Cryptographic event chain · chain_integrity: true · JSON-LD cryptographically-verifiable | HYDRA-AUDIT |
| MiFID II RTS 25 (clock synchronization)EU MiFID II RTS 25 (clock-sync mandate, ±1ms; extended under the 2024 MiFIR review) — pending application date | ±1ms clock synchronization for HFT; ±100µs for trading venue gateways | Multi-source PoT via precision time source (±1µs target) · cryptographic divergence detection · ESMA-aligned | TTTPS |
| DORA Art.17EU 2022/2554 | ICT incident reporting, audit log integrity, operational resilience | 7 Byzantine attack vectors detected and logged (6 roadmap) · 7-year tamper-evident chain | HYDRA-AUDIT · TTTPS |
| FINRA Rule 4590CAT NMS Plan, US | Clock synchronization audit trail for order routing | Tamper-evident PoT log, queryable per-event · Prometheus alert integration | TTTPS |
| MAS TRM 2021 + AIRG 2025Section 6.4.1 + AI Risk Mgmt Guidelines, Singapore | Financial infrastructure time audit; AI system risk management and audit trail requirements | Multi-anchor PoT · precision time source (±1µs); high-precision GEO source ±10ns — roadmap · MAS AIRG AI audit trail alignment | TTTPS |
| FCA PS17/14 & MAR 7AUK MiFID II equivalent | Clock synchronization, audit trail integrity for trading venues | Ed25519-signed PoT chain · structured for FCA submission | TTTPS |
| SEC Rule 17a-3US Securities and Exchange Commission | Records of orders, confirmations, and audit trail integrity | Tamper-evident PoT per transaction · Byzantine detection alert | TTTPS |
| Korea AI Basic ActLive 2026-01-22 | High-impact AI system logging and accountability records | Cryptographic event chain · JSON-LD provenance · Korea metro deployment | HYDRA-AUDIT |
| TRAI / CERT-InIndia | Telecom timestamp integrity, incident reporting | PoT format aligned with TRAI requirements · structured for CERT-In submission | TTTPS |
| FINRA AI Governance 2026FINRA Annual Report 2026, US | Audit trails of AI agent actions, human oversight checkpoints, model version tracking, prompt/output logs | Cryptographic PoT per AI agent action · tamper-evident log · Prometheus checkpoint alert | HYDRA-AUDIT · TTTPS |
| MiFID III (forthcoming)EU — successor to MiFID II | Rich metadata stream: exact timestamp, participant identity, device, location per order event | Sub-µs PoT via precision time source · Ed25519-signed metadata chain · designed to support forensic submission | TTTPS |
| MAS Agentic AI GovernanceIMDA/MAS 2026, Singapore | Distributed accountability logging for AI agents; decision traceability for financial AI | Cryptographic event chain · JSON-LD provenance · Singapore metro deployment | HYDRA-AUDIT |
| Japan FIEA + FSA AI ActFinancial Instruments and Exchange Act + AI Promotion Act 2025 | HFT order management timestamp records; AI system accountability and transparency obligations | Per-event PoT log queryable per-order · JSON-LD export for FSA submission · cryptographic AI event chain | TTTPS · HYDRA-AUDIT |
| HKMA / SFC AI GovernanceHong Kong — 2026 GenAI Rules | AI model governance, audit trails for AI-driven financial decisions; HKD 10M penalty for non-compliance | Cryptographic event chain · JSON-LD provenance · Hong Kong metro deployment | HYDRA-AUDIT |
| APRA CPS 234 / 230Australian Prudential Regulation Authority | Information security incident reporting; operational risk management for financial institutions | 7 Byzantine attack vectors (6 roadmap) · tamper-evident audit chain · Prometheus incident alert | HYDRA-AUDIT · TTTPS |
The chain is purpose-built to serve the customer's full regulatory retention horizon. Continuity of evidence is preserved across the obligation period.
Revenue scales with regulatory expansion across the customer's compliance lifecycle. Pricing tiers are published on the Products page.
Qualitative pattern — illustrative, not contracted.
| Cohort | Pattern over 12–60 months | Driver |
|---|---|---|
| Standard enterprise SaaS | Contracting (contract expiry, competition) | Vendor switching cycles |
| Timing-only services | Contracting (renewal-only) | MiFIR renewal scope |
| TTTPS — Financial | Expanding | Upsell: DORA + AI Act + multi-metro |
| TTTPS — AI/GPAI | Expanding | Upsell: training pipeline + KV |
| TTTPS — Blended | Expanding | Regulatory scope grows over the lifecycle |
The compliance mandate falls on existing enterprise tenants across carrier-neutral metros — no new customer acquisition is required to source this demand.
Segment sizes are external market estimates; conversion and revenue figures are illustrative projections, not contracted.
| Segment | Addressable Tenants | Regulatory Mandate | Illustrative Conversion (10%) |
|---|---|---|---|
| Financial services | 1,250+ firms | MiFID II RTS 25 + EU AI Act + DORA | ~125 customers |
| Cloud/AI/SaaS | 2,900+ companies | EU AI Act Art.12/53 (GPAI) | ~290 customers |
| Enterprise IT | 3,000+ tenants | DORA + sector-specific | ~300 customers |
| Gaming/Media | 500+ companies | EU AI Act + CERT-In | ~50 customers |
| Total addressable | 7,650+ tenants | All above | ~765 customers |
Conversion of existing tenants at single-digit-to-double-digit percentages implies a multi-tens-of-millions ARR opportunity. All figures are illustrative projections, not contracted.
Available on request via kenosian.com · Demonstrating IETF -03 wire format, replay defense, and audit chain integrity:
# Step 1: Generate PoT (143-byte IETF -03 wire format)
curl -X POST https://api.kenosian.com/pot/generate \
-H "Content-Type: application/json" \
-d '{"eventId":"partner-demo"}'
# → {"pot_hash":"a3f1...","signature":"ed25...","timestamp_ns":1748...,"mode":"turbo","event_id":"partner-demo","current_mode":"turbo"}
# Step 2: Replay defense → HTTP 409
curl -X POST https://api.kenosian.com/pot/query \
-H "Content-Type: application/json" \
-d '{"eventId":"partner-demo"}'
# → {"pot_hash":"a3f1...","event_id":"partner-demo","timestamp_ns":1748...}
# Step 3: Audit chain integrity
curl https://api.kenosian.com/audit/report \
-H "Authorization: Bearer $TOKEN" | python3 -c \
"import sys,json; d=json.load(sys.stdin); \
print('chain_integrity:', d['chain_integrity']) # → true
print('total_events_lifetime:', d['total_events_lifetime']) # → 796+"
Every enterprise customer that starts the audit chain generates recurring revenue anchored by the multi-year regulatory retention horizon, and a structural moat that hyperscalers cannot replicate.
The compliance mandate falls on existing enterprise tenants — no new customer acquisition required.
Net retention pattern: expanding rather than contracting as regulatory scope grows.
GPAI/Art.53 enforcement: August 2, 2026. High-risk/Art.12: 2026-08-02 (current law) → deferred to 2027-12-02 under EU Digital Omnibus provisional agreement (pending formal adoption).
A purpose-built IETF-track cryptographic AI audit solution ready for EU AI Act enforcement. GPAI/Art.53: August 2, 2026. High-risk/Art.12: 2026-08-02 (current law) → deferred to 2027-12-02 under EU Digital Omnibus provisional agreement (pending formal adoption).
EU AI Act Art.12/53 · DORA Art.17 · MiFID II RTS 25 (clock sync) / MiFIR review (Regulation (EU) 2024/791) · IETF draft-helmprotocol-tttps-03