Trading intelligence
you can verify.
Helionex records every decision — including abstentions — and makes tampering detectable. No curated history. No performance hype. Just evidence.
Verify Helionex
“Trustless” starts with recomputation. Helionex publishes proof bundles and anchor references so anyone can verify behaviour independently.
Decisions + Abstentions
Every BUY/SELL/HOLD and every “no trade” is recorded with reasons and hashes.
Execution Reality
Attempts, outcomes, broker responses, reconcile-before/after — nothing hidden.
Proof Bundles
Download the day’s bundle and run the verifier offline: PASS or FAIL.
Observer (v0.1)
Observer is the first paid tier: read-only access to verification dashboards, proof bundles, and lineage history. No execution. No signals sold. Just transparency.
What you get
- Integrity dashboard (PASS/FAIL/INCOMPLETE)
- Decisions feed + intent drill-down
- Trades feed (including aborted/frozen)
- Abstentions log (discipline is visible)
- Proof bundles (ZIP) + offline verifier
- Lineage (models/config changes + anchors)
What you don’t get
- Auto-trading access
- Copy-trading funnels
- “Guaranteed performance” claims
- Hidden backtests
- Sales hype dressed as science
Roadmap (truth-first)
We build in the order that protects credibility.
Now
- Landing page + waitlist
- Event schema + append-only logs
- Daily roots + proof bundles
Next
- Verify Helionex UI (Observer v0.1)
- Public verification snapshots (limited)
- Hedera anchoring (HCS) for roots
Later
- Enterprise integrations
- Immutable audit APIs
- NFT receipts for proof bundles (optional)
FAQ
The questions engineers ask first.
What does “verify” actually mean?
Verification means recomputing integrity checks from immutable event records: schema validity, hash-chain continuity, daily root recomputation, and (later) anchor matching to Hedera Consensus Service. The output is deterministic: PASS/FAIL/INCOMPLETE.
Are you selling trade signals?
No. Observer is read-only. Helionex is built for transparency and auditability — not hype funnels.
Can Helionex rewrite history?
The design is append-only. Corrections publish new bundles/roots; old bundles remain immutable. Tampering is detectable because hashes and anchors will not match.
Is execution autonomous?
Intelligence may suggest; execution must be explicitly invoked and is gated by safety doctrine (reconcile-before, idempotency, fail-closed if audit write fails).
Will you use Hedera Testnet or Mainnet?
We start on Testnet for integration and cost control. Mainnet anchoring happens only when the verification spine is stable and governance gates are satisfied.
Join the waitlist
Observer access is read-only and capped. You’ll be invited when verification is strong enough to withstand scrutiny.