Submit content
Send any AI-generated text, image hash, or code to the API with model name and metadata attached.
Helios Ledger cryptographically seals the origin and integrity of AI-generated content using Ed25519 signatures and Merkle-tree attestations. Tamper-proof. Independently verifiable. No trust required.
Every submission is permanently sealed — Ed25519 signed, Merkle-included, independently verifiable. This is the real ledger, not a simulation.
From raw AI output to cryptographically sealed, independently verifiable record — in under a second.
Send any AI-generated text, image hash, or code to the API with model name and metadata attached.
Helios computes a SHA-256 hash and signs it with Ed25519. The private key never leaves the node.
The signed hash is inserted into the append-only Merkle tree. Tampering with any historical entry breaks the root.
Anyone can verify using the public key and Merkle proof — no trust in Helios required. Pure cryptographic truth.
A minimal, composable toolkit — nothing more, nothing less.
Submit, verify, and audit provenance records from any language or platform. JSON in, JSON out.
POST /api/records64-byte signatures, sub-millisecond verification. Modern elliptic-curve cryptography — fast and battle-tested.
cryptographyAppend-only Merkle structure. Historical records are mathematically immutable — silent tampering is impossible.
tamper-evidentIncentivize contributors who submit provenance records. Configurable reward logic with per-account balances.
optionalDeploy a network of Helios nodes. Each node broadcasts records to peers with Ed25519 signature verification — federated trust without a single point of failure.
federated · GET /api/v1/peersMIT licensed. Audit every line. Self-host on your own infrastructure or contribute to the public instance.
MITThe ability to cryptographically prove the origin, creation context, and post-creation integrity of AI-generated content. Helios records a tamper-proof signed entry for each piece of content, creating an immutable audit trail.
Helios hashes your content and signs the hash with Ed25519. The signature and metadata are stored in a Merkle tree. Anyone with the public key can independently verify the record — no need to trust Helios at all.
Yes. MIT-licensed, freely available on GitHub. Self-host on your own infrastructure or use the public instance at ai.oooooooooo.se.
All of them. Helios is model-agnostic — GPT-4, Claude, Gemini, Llama, Mistral, or any custom model. Only the content hash matters.
No. Only cryptographic hashes and metadata — never the raw content itself. Your data stays with you; Helios only records proof of its existence and integrity.
Yes. Clone the repo, deploy a Cloudflare Worker with D1, and you have your own node in minutes. Add the public node as a peer to join the federated network — records propagate automatically with cryptographic verification.