Network layer
Certified and deterministic state
The specification requires validator-certified finality to bind accepted blocks to voting power, signatures, the active validator set and a state root; runtime conformance requires separate Evidence.
Enterprise Technical Documentation
Testnet 2 ExplorerCurrent testing environment ↗Technical ReferenceProtocol Architecture · Asset Standards · Application Interfaces
Enterprise Network Foundation
確定性のある台帳、決定論的実行、資産標準、相互接続、公開検証を一つのプロトコル基盤に統合します。
Certified finality, deterministic execution, asset standards and observable interfaces form one coherent foundation for enterprise applications.
Certified finalityDeterministic executionObservable public interfaces
Enterprise network foundation
One protocol foundation for applications, assets and verified records.
The CURRENT specifications define certified finality, deterministic execution, native network fees, application assets, interoperability controls and observable evidence. Mainnet source presence is not acceptance, runtime wiring, deployment or activation; the machine-readable Mainnet status remains authoritative.
確定性、実行、ネットワーク利用料、アプリケーション資産、相互接続統制、公開証跡が一つのNetwork IdentityとState Modelで接続されます。
Application layer
Shared execution and asset standards
The specification defines a common deterministic execution foundation for applications, fungible assets, NFTs, credentials and network fees while retaining distinct schemas and authorities.
Evidence layer
Observable public interfaces
Public Testnet RPC, Health, Explorer JSON and Operational API surfaces are evidence routes; current runtime claims require successful readback from the identified environment.
| Domain | Evidence classification | Enterprise value | Public evidence |
|---|---|---|---|
| Consensus | Validator-based certified finality | Accepted state has an explicit certificate boundary. | Finalized block, signed power and certificate hash |
| Execution | Deterministic state transition | Identical valid input produces identical accepted state. | Block hash and state root |
| Applications | Contracts, assets, credentials and event records | Business logic and digital records share one execution model. | RPC and Explorer surfaces |
| Interoperability | Identity-bound message and asset routes | External connectivity remains governed by finality, replay and quantity controls. | Route state and execution records |
| Operations | Canonical health and network evidence | Infrastructure state is observable without private operational access. | Health, Explorer JSON and Operational API |