H◆

Helios · $HELI

◆Revenue verifiedValid · 12 months

zkTLS revenue attestationzkVerify proof recordUpdated 2026-10-19 10:12

Verdict

Verification passed

4 / 4 checks passed · 0 missing months · coverage 2025-10 → 2026-09

This record proves the source and amount of revenue for the coverage window. It does not prove profit, the absence of refunds or chargebacks, or future revenue.

Verified annual revenue

$284,000

ARR · Stripe 68% · App Store 32%

◆Revenue verified

Snapshot

Source Stripe, App Store
Coverage 12 months · 0 gaps
Verified 2026-10-19 10:12
Proof ID #0x7f3a…9c2e

ConclusionPassed

SourceStripe · App Store

Coverage12 mo · 0 gaps

4 checks4 / 4 passed

On-chain proof#0x7f3a…9c2e

RecheckWhy it matters

◆Pass Account ownership Credential was issued by the claimed Stripe account · GitHub OAuth proves project ownership

◆Pass Revenue total 12 monthly totals sum to the $284,000 annual figure · no duplicated invoices

◆Pass Missing months 0 of 12 months missing · 2025-10 → 2026-09 complete

◆Pass On-chain credential Credential hash equals the zkVerify record #0x7f3a…9c2e · checked 2026-10-19 10:12

4 / 4 All checks passed Snapshot preserved as a public audit trail · no later edits can change this record

How the proof was produced

zkTLS browser session · raw data never left the project's device · only the result was written on-chain

Completed

1 · Detect login

2 · Fetch invoices

3 · Local proving

4 · On-chain check

zkTLS transcript ≤ 20 KB · TLS 1.2 required · notary ≥ 2 instances · chain revenue read directly (no attestation needed)

Export & share

A fixed URL and a downloadable evidence pack — for auditors, reporters and investment memos

Share link: launchpad.example/proof/0x7f3a…9c2e · no login required

Recheck this proof locally optional · advanced

The record is already public and complete. Rechecking is a second-level tool for verifiers, not required for buyers.

Drop credential file here (.json / .zip)

Checks run locally in your browser — the original data never leaves your device. The public record above stands on its own.

Who verifies, and what is open

Designated verifiers issue proofs · anyone can recheck them

Open scope

What this record covers

L1 ownership (GitHub OAuth) · L2 revenue (Stripe, App Store) · L3 quarterly re-verification every quarter while the token is listed.

Who can verify

Proofs are issued by designated verification partners. The result, the checks and the on-chain hash are public, so any third party can recheck or cite them. Verifier reward program is pending approval — no reward amount is promised on this page.