What is AETERNA?
AETERNA is not a health app. It is a Sovereign Biological Operating System — a privacy-first, decentralized longevity platform where users own their biological data absolutely, and an AI reasons across their full biological context to slow aging.
No cloud servers. No corporate data harvesting. No subscriptions. You are the only key to your Vault.
Why ICP — and only ICP
This project could not exist on any other chain or cloud infrastructure. Here’s why ICP was the only viable choice:
Per-user canister architecture — every user gets their own dedicated 400GB canister. Not a shared database, not a shared smart contract. One user, one sovereign canister. Data isolation is architectural, not policy-based.
vetKeys — used for Chronicle Ledger block sealing. Every 24-hour biological record is cryptographically sealed on-chain using ICP’s threshold key derivation. Tamperproof by design.
Internet Identity — sovereign login with no password, no OAuth, no third-party auth provider. The user’s II Principal is bound to their Soulbound Token at registration.
HTTP outcalls — the 70B AI model (Llama 3.3-70B via OpenRouter) is called directly from the Motoko backend canister, with no intermediary server. All prompts are anonymized and no-logging headers are enforced.
On-chain SBT — a non-transferable Soulbound Token is minted at registration, binding the user’s biometric palm scan ZK-proof (Humanity Protocol) to their II Principal. Identity is biometric, sovereign, and quantum-resistant.
Core Architecture
Backend: Motoko — all sensitive logic, encryption, key storage, free tier enforcement, SBT minting, and vetKey Chronicle sealing
Frontend: React + TypeScript, mobile/tablet-first PWA
Encryption: Hybrid PQC — X25519 + ML-KEM/Kyber (quantum-resistant), ephemeral session re-derivation every 15 minutes
AI: Llama 3.3-70B via HTTP outcalls for biological directives and Oracle reasoning. On-chain 8B LLM for lightweight confirmations at zero fuel cost.
Biometrics: Humanity Protocol palm scan SDK for liveness detection, ZK-proof generation, and anti-Sybil protection at registration and high-value wallet transactions
Wallet: Real on-chain ICP, ckBTC, ckUSDC balances. NNS neuron staking, ckBTC liquidity. Pay-as-you-go AI fuel model — no subscription.
Data sources: Apple HealthKit (iOS) and Health Connect (Android) for wearable ingestion. Raw biometrics only — no proprietary scores.
What the AI Actually Does
The Oracle reasons across the user’s entire vault context simultaneously — DNA (23andMe/VCF), microbiome (BIOM), bloodwork (PDF extraction), wearable data (HRV, RHR, SpO2, BBT), supplement stack, chronotype, cycle phase (female users), and seasonal context.
From this it generates:
Daily personalized longevity directives (non-repetitive, supplement-stack-aware)
A dynamic AETERNA Vitality Score derived from raw biomarkers
Discovery Signals — breakthrough correlations between genetic markers and biomarker variables, logged with confidence scores and anti-hallucination gates
Circadian Re-Alignment directives when wearable data contradicts DNA anchor
Longevity — slowing biological age — is the explicit north star of every inference.
Hard Problems Solved
Per-user canister spawning at registration with automatic cycle monitoring and one-tap ckUSDC top-up
PQC key derivation with 15-minute ephemeral session re-keying
vetKeys Chronicle sealing — 24-hour blocks, immutable, verified on mainnet
Founder-only admin methods for post-deployment key injection (Humanity SDK key, AI key) stored in canister stable memory, never exposed to the frontend
Free tier enforcement (2 directives + 3 chats/day) fully in Motoko backend — not client-side
Double-match recovery — lost device restoration requires both II login and Humanity palm scan ZK-proof, verified by the canister before Vault access is granted
Status
Approaching mainnet. All core logic is built and verified. Final steps are post-deployment key injection and mobile PWA testing on real devices.
Happy to discuss technical questions — especially around vetKeys integration, per-user canister architecture, or the PQC encryption layer.