Current release status
Public document hashing and exact integer aggregation are live with signed results. Native consensus, mining, issuance, COMPUTE payments and rewards are inactive. Independent operation is not yet demonstrated.
Configuration scope
Only pinned off-mainnet qualification configurations are currently offered. Verify source/bootstrap/dependency/runtime hashes and use your own private qualification keys/TLS trust. No founder credentials are needed.
Public/server boundary
Browsers use the same-origin HTTPS routes. Private upstream origins, CA settings and credentials remain server-side; users cannot choose arbitrary upstream URLs or invoke a server-side signing API.
No ready mainnet profile
Production difficulty, epochs/spacing, confirmation policy, funding and resource assumptions are not approved by fixture defaults. Unsupported/mixed versions fail closed. Do not edit guards to activate mainnet.
Existing systems and their interfaces
The website is one part of ComputeNet. Execution evidence, historical reads, the isolated native candidate and research systems have distinct deployments and guarantees.
| Boundary | Implementation / evidence | Meaning |
|---|---|---|
| Website / CVC | Existing original v0 / Vercel application | Public same-origin HTTPS interface |
| Bounded execution service | Gamma fixed-work lane and signed results | Real profiles; initial processes under one administration |
| Historical ledger API | Preserved computenet-mainnet-1 history | Read-only eight-block accounting, not active native consensus |
| Truth Stack / native candidate | Recovered components and isolated tests | General proof and independent-security claims remain scoped |
Practical procedure
- 1Identify which component actually produced the data.
- 2Inspect the source/runtime/policy commitment for execution evidence.
- 3Verify the historical ledger separately from public receipts.
- 4Do not infer production integration from a frontend diagram or a simulated topology.
Browser → HTTPS gateway → bounded execution / signed evidence
↘ historical read API → protected 8-block ledger
Isolated native consensus / settlement: not activated
Separate historical dashboard: demonstration onlyLimits and failure cases
- Direct-IP HTTP examples are not supported browser production guidance.
- Private TLS roots and credentials stay server-side.
- A distinct machine or key does not establish a distinct administrator.