Harpocrates

Core App

Confidential inference with client-side encryption and ETH-settled metering on Horizen L3.

Network

Target: Horizen L3 (Chain ID 2651420)

RPC: https://horizen-testnet.rpc.caldera.xyz/http

Billing contract: 0xea30409f2f4a49d55B674B95CA0DCacD7b41Fd4c

Authentication

API keys and wallet auth are not wired yet. This space will host key management and session controls.

Use docs and the Dev Health page to verify env configuration.

Privacy Demo

Client-side encryption flow

Keys stay on this page. Data is encrypted before send and decrypted only after attestation and billing.

Request ciphertext

Not generated yet

IV: Not generated yet

Response ciphertext

Not generated yet

IV: Not generated yet

Attestation (demo)

Run the demo to see a stub attestation.

ZK Billing Proof

Generate a Groth16 proof that cost = (input + output) * price without revealing token counts on-chain.

Privacy note: The key never leaves your browser. Only ciphertext is shown and would be sent to the service. Enclave execution is simulated, but the billing proof is a real Groth16 proof verified on-chain.

Decrypted output

Output is decrypted locally using the same ephemeral key generated on this page.

Inference Workspace

This is where you will send encrypted prompts, invoke models running in TEEs, and receive encrypted outputs.

Attestation & Receipts

View attestations, verify proofs, and reference on-chain receipts posted to Horizen L3.

Billing & Usage

Track token usage, costs, and funding status. Settlement will occur in ETH on Horizen L3.

Privacy Workflow

Review security model
  1. Encrypt prompts locally (keys stay client-side).
  2. Send encrypted payload to the Harpocrates TEE-backed service.
  3. Receive encrypted output + attestation + usage.
  4. Verify attestation and on-chain receipt, then decrypt output locally.

This dashboard will orchestrate that flow; business logic is intentionally stubbed in this phase.