TRUSTED EVENT & SETTLEMENT NETWORK

One Smart Chain

A public chain for trusted events, smart contracts, and transaction settlement

An open, verifiable evidence and settlement layer for apps, DApps, smart contracts, transactions, digital assets, AI computing, and real-world services.

Start reading ↓ Architecture draft · 2026.09

ONESMART CHAIN

APPSCONTRACTS

ASSETSAI

VERIFIABLE BY DEFAULT

Execution environmentEVMEcosystem compatible

Core domains6Apps · Contracts · Transactions · Assets · AI · Services

Network statusR&DArchitecture and technical evaluation

01 / EXECUTIVE SUMMARY

Executive summary

One Smart Chain is a general-purpose network for trusted events, smart contracts, and settlement across digital applications and real-world businesses.

Important facts in digital systems are often scattered across applications, databases, public chains, and service providers. Participants can see outcomes but cannot easily verify an event's source, sequence, integrity, or responsible party at low cost.

Using a standard event model, cryptographic hashes, actor signatures, on-chain ordering, and searchable indexes, One Smart Chain connects app releases, contract upgrades, transaction settlement, asset changes, and AI outcomes into a continuous trail of evidence.

NORTH STAR Make important digital events
verifiable, traceable, and settleable by default

Proof first

On-chain records verify hashes and state without exposing sensitive source content.

Open compatibility

Compatible with EVM tools, wallets, Solidity contracts, and common data standards.

Minimal trust

Signatures, permissions, multisig, timelocks, and audits jointly constrain high-risk actions.

Progressive governance

Gradually expand from a controlled network to multi-party validation and transparent on-chain governance.

02 / MISSION & SCOPE

Connect facts, not another data silo

The network supports cross-system verification and settlement. Source business records, private data, and high-frequency process data remain with the responsible systems.

Apps and DApps

Application identity, version fingerprints, publishers, dependency inventories, reviews, and distribution records.

APPLICATION

Smart contracts

Source and build fingerprints, deployment, verification, proxy implementations, permissions, and upgrade history.

CONTRACT

Transactions and assets

Evidence linking on-chain transactions, off-chain orders, external payments, and changes in asset rights.

SETTLEMENT

AI and computing

Models, policies, input commitments, execution environments, result hashes, and billing receipts.

COMPUTE

Real-world services

Verifiable statements and state events submitted by devices, institutions, auditors, and oracles.

REAL WORLD

03 / UNIVERSAL EVIDENCE PROTOCOL

A unified evidence event model

Different businesses use the same minimal event envelope, preserving consistent identity, time, relationships, and verification semantics on-chain.

STANDARD EVENT ENVELOPEEvidenceEventCanonical · Signed · Versioned

eventIdGlobally unique event identifier

subjectApp, contract, transaction, or asset

actorSubmitting actor and signing identity

actionCreate, deploy, upgrade, transfer, and more

contentHashCanonical content hash

sourceRefSource system or external-chain reference

timestampOn-chain ordering and business time

relationParent event, prior state, and dependencies

01CollectStructured business event

→

02NormalizeStable serialization and versioning

→

03SignActor identity and authorization

→

04AnchorHash, order, and state

→

05QueryIndexes, proofs, and verification

Public on-chain

Content hash
Actor address
Signature and time
State relationships
Protocol version
Verification result

Controlled off-chain

Source business record
User privacy
Commercial data
Access credentials
Large file contents
Internal logs

04 / NETWORK ARCHITECTURE

MODULAR EVM ARCHITECTURE

Network architecture

A modular, EVM-compatible design reuses mature tooling while adding native support for evidence batching, cross-system verification, and dedicated indexing.

Application and access layer

Wallets, block explorers, DApps, SDKs, APIs, enterprise gateways, and mobile clients.

Protocol services layer

Evidence registration, contract directory, asset registry, compute settlement, identity and reputation, and governance.

Smart contract layer

EVM contracts, account permissions, multisig, timelocks, proxy upgrades, and protocol governance.

Execution and data layer

Transaction execution, state storage, event logs, batch proofs, indexing, and archives.

Network and consensus layer

Validators, P2P networking, consensus security, RPC, monitoring, and high-availability infrastructure.

EVM compatibility

Reuse wallets, Solidity, Hardhat, and the established DApp ecosystem.

Low-cost evidence

Merkle roots and batch submission reduce the cost of high-frequency events.

Fast finality

Improve the experience of transaction confirmation and cross-system state coordination.

Open observability

Make nodes, contracts, events, governance, and fund flows publicly inspectable.

05 / SMART CONTRACT EVIDENCE

Evidence across the smart-contract lifecycle

A contract address is not a complete identity. Source code, builds, deployment, permissions, implementation versions, and governance actions must be verifiably linked.

Build

Source commits, compiler version, optimizer settings, dependency lockfiles, and bytecode hashes.

Deploy

Deployer, factory contract, CREATE2 salt, transaction, and network environment.

Verify

Source verification, audit reports, ABI, implementation address, and risk labels.

Operate

Permission changes, pauses, parameter updates, abnormal events, and fund flows.

Upgrade and retire

Proposals, multisig, timelocks, proxy changes, migration, and final state.

Verifiable contract profileSource fingerprintReproducible buildDeployment proofProxy relationshipPermission graphAudit version

06 / TRANSACTIONS & ASSETS

Cross-system transaction and asset proofs

The network executes native transactions and can provide verifiable anchors for external chains and off-chain systems without pretending to be their authoritative ledgers.

NATIVE

Native-chain transactions

The network directly executes accounts, contract calls, token transfers, gas, events, and final state.

EXTERNAL CHAIN

External-chain proofs

Link facts from other networks through light clients, proof protocols, or governed attestors.

OFF-CHAIN

Off-chain business proofs

Authorized actors sign order, payment, delivery, and reconciliation events while preserving provenance and responsibility boundaries.

BOUNDARY The reliability of cross-chain and off-chain proofs depends on verification mechanisms, signers, and governance constraints. One Smart Chain does not automatically equate external claims with objective facts.

07 / NODES & GOVERNANCE

Multiple node roles and transparent governance

Different nodes handle consensus, access, indexing, archives, and attestations. Permissions and incentives depend on verifiable service quality.

VALIDATOR

Validator nodes

Participate in consensus, block production, and network security.

RPC

Access nodes

Provide constrained, observable chain access.

INDEXER

Indexer nodes

Parse contracts, events, relationships, and business queries.

Archive nodes

Preserve historical state and long-term verification material.

ATTESTOR

Attestor nodes

Verify external chains, devices, and off-chain claims.

OBSERVER

Observer nodes

Monitor the network, governance, anomalies, and transparent metrics.

PROPOSAL

Proposal

Publicly register proposals for protocol parameters, funding, nodes, and upgrades.

REVIEW

Review

Disclose impact, risk, compatibility, budgets, and rollback plans in advance.

VOTE

Vote

Constrain voting through delegation, participation thresholds, and conflict-of-interest rules.

EXECUTION

Execute

Multisig and timelocks make changes observable, cancelable, and accountable.

08 / TOKEN ECONOMY

An allocation framework for network security and long-term ecosystem growth

The proportions below are a whitepaper proposal, not an issuance commitment. Supply, symbol, vesting schedule, and legal structure require formal disclosure before launch.

100%PROPOSED ALLOCATION

Network and AI computing incentives30%Validation, RPC, indexing, attestation, and computing services

Market and ecosystem development18%Developers, applications, liquidity, and partners

Technology and core team15%Long-term R&D with lockups and linear vesting

Foundation and governance reserve15%Public infrastructure, audits, research, and contingency

Investors and strategic resources12%Phased fundraising and long-term resource support

Community and airdrops10%Genuine participation, early contributions, and public activities

Team and investor principles≥36m

Proposed long-term lockups and linear vesting to avoid concentrated short-term circulation.

Community allocation principlesProof

Favor verifiable contribution and anti-Sybil rules over unconditional equal distribution.

Foundation spending principlesOn-chain

Budgets, milestones, beneficiaries, and outcome evidence should be publicly inspectable.

01Network gas

Pay for transactions, contract execution, evidence registration, and state storage.

02Node staking

Support service quality and penalize double-signing, fraud, and serious negligence.

03Service settlement

Settle RPC, indexing, attestation, AI computing, and specialized data services.

04Protocol governance

Support proposals, delegation, voting, and transparent governance of public funds.

09 / ROADMAP

Advance the network through verifiable milestones

The roadmap advances by capabilities and acceptance evidence, not by unverified launch dates masquerading as engineering progress.

PHASE 01

Protocol and prototype

Event model, threat model, EVM approach, node prototype, and block explorer.

Current phase

PHASE 02

Private development network

Multi-node deployment, contract directory, evidence SDK, indexing, monitoring, and recovery drills.

To be verified

PHASE 03

Public testnet

External nodes, wallet access, developer documentation, faucet, audits, and incentivized testing.

To be planned

PHASE 04

Mainnet candidate

Genesis parameters, validator mechanism, token and governance contracts, stress testing, and security review.

Gate review

PHASE 05

Ecosystem expansion

Cross-chain proofs, Swap, asset protocols, AI compute market, and progressive decentralization.

Long-term evolution

STATUS Client selection, consensus parameters, gas token name, validator count, and mainnet launch timing remain undecided. Tests, audits, and governance readiness will determine them.

10 / RISK DISCLOSURE

Risk disclosure

A public chain does not automatically guarantee truth, security, or asset value. Every trust assumption must be identified, disclosed, and continuously tested.

Consensus, clients, and cryptographic implementations may contain unknown flaws.
Smart contracts, cross-chain proofs, oracles, and permission configurations may be attacked.
Node concentration, governance capture, and key compromise can weaken trust in the network.
Public metadata may enable link analysis and privacy leakage.

Token issuance, trading, and services may be regulated differently across jurisdictions.
External chains, trading venues, and service providers have independent operational risks.
Roadmap, performance, and ecosystem goals may change based on validation results.
Any allocation ratio or feature design is subject to final legal documents and on-chain rules.

This whitepaper is for technical and product discussion. It is not investment advice, a securities offering document, a return promise, or a guarantee of any token's value.