Verified Network Access.
This page explains safe network access material for NewGenEngine, including release verification, follower-node documentation, and controlled public access paths.
It does not expose unsafe operational procedures. It explains what users should check before running network software and which material will be published together when public release packages are ready.
Public documentation, release verification, and controlled access paths.
The access model separates public documentation, release verification, and private test access so users can understand what is public, what must be checked, and what remains coordinated directly.
Public documentation explains the architecture, authority boundaries, verification model, and safe access material without exposing sensitive operational details.
Network software should be accompanied by release notes, checksums or hashes, expected network targets, and verification steps that users can inspect before running anything.
Selected private testers receive coordinated access paths while final external testing is running. This keeps configuration, release material, and network targets aligned.
What users should check before running network software.
Network access should never depend on blind trust. Public material should make it clear which package is being used, what it targets, and how users can check it.
The public release package link is intentionally not listed until the package, checksums, release notes, and verification instructions are ready to be published together.
Follower nodes can observe the network, but they do not decide canonical state.
Follower-node access is intended for users and operators who need to observe chain progress, inspect public state, and follow finalized data safely.
A follower node can read chain progress, follow finalized data, and inspect public state. It is useful for visibility, verification, integration work, and safer network observation.
A follower node does not define canonical state. Consensus and finality remain on NewGen L1.
The public follower package will be linked only when release material, checksums, and verification notes are ready to be published together.
Until then, access material stays coordinated through controlled channels instead of exposing incomplete or unverifiable packages.
Running network software does not make local state canonical.
Local observations are useful, but final authority remains on the canonical chain.
A local node can observe and verify data, but local state is not canonical by itself.
Records and receipts from E2 Compute Hub can support verification. When certainty is required, those records must be checked against chain finality.
The final state accepted by the ecosystem is defined on NewGen L1.
Public documentation without sensitive operational detail.
Public documentation focuses on architecture, verification, and safe access material. Sensitive operational details stay outside the public website.
Use public documentation to understand the architecture, access model, release verification approach, and safe boundaries around network access. Private infrastructure details, sensitive validator procedures, and unsafe runbooks are intentionally excluded.