Documentation

TOK9 is designed as a layered infrastructure for real-world asset tokenization. The architecture separates the blockchain base, protocol contracts, operational services, and end-user applications, allowing multiple operators to build solutions on top of common and auditable rules.

Besu Network Layer

The base network layer is built on Hyperledger Besu, providing EVM compatibility, permissioned operation, and enterprise-grade node management. This allows integration with standard Ethereum tooling while preserving controlled validator participation and operational governance.

Besu supports robust observability, predictable deployment patterns, and private infrastructure controls required for regulated environments. In TOK9, this layer underpins protocol contracts and service orchestration with a clear separation between infrastructure responsibilities and application logic.

QBFT Consensus

TOK9 uses QBFT (Istanbul Byzantine Fault Tolerant) consensus to provide deterministic block production and immediate finality once a block is committed. This model is suitable for institutional and permissioned networks where predictable settlement and validator accountability are required.

QBFT also improves operational reliability by reducing fork uncertainty and supporting controlled validator sets under governance policy. In practice, this enables auditable, low-variance execution behavior for protocol operations and marketplace settlement flows.

The lifecycle of an asset in TOK9 starts with off-chain valuation and conversion into TOK under an operational logic of 1 TOK = 1 EUR. After that, the asset is represented on-chain through a fractional NFT, where tokenId corresponds to 100% of a unique physical asset. The Tok9NFT contract manages issuance, metadata, fractional supply, declared valuation, and potential deactivation operations required by legal or compliance conditions.

After issuance, fractions can be held, transferred between wallets, or traded through the ecosystem marketplace. In market context, royalties and platform fees are distributed atomically, while declared value can be updated by an authorized operator when confirmed appreciation signals exist. This model ensures full traceability from initial tokenization to secondary trading.

The TOK9 network operates on permissioned infrastructure with controlled governance, suited for regulated contexts and compliance requirements. The model is designed to ensure immediate block finality, operational predictability, and control over validator network participants.

Validator governance is centralized at the current stage to guarantee stability, security, and response capacity. This enables stricter management of admissions, revocations, operational policies, and service continuity, while preserving EVM compatibility and full protocol auditability.

TOK9 economic design relies on simple and predictable fees linked to real ecosystem activity, avoiding inflationary tokenomics or speculative mechanisms. Protocol revenue comes from operations such as asset creation, peer-to-peer transfers, premium listings, marketplace sales, and redemption flows for ecosystem exit.

In marketplace sales, the system applies royalties and platform fee, while direct operations may include reduced transfer fees. The logic is designed so applications built on the protocol can operate with transparent costs and clearly defined financial distribution.

TOK9 architecture is designed for integration with compliance workflows, including KYC/AML processes, operational controls, and automated declared-value updates. The protocol service layer supports auxiliary components such as event indexing, metadata gateways, APIs, and automated workflows that strengthen supervision and operational reconciliation.

This approach allows institutional operators and regulated applications to work on a common infrastructure, preserving traceability, separation between protocol and application layers, and the ability to respond to regulatory requirements without depending on open public infrastructure.

The target protocol architecture is designed for an EVM-compatible network, enabling integration with wallets, frontends, automation pipelines, and event-observability tools. Any future RPC access layer must avoid exposing internal endpoints, private node topology, or sensitive infrastructure details.