bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 6쪽 중 3쪽
d to rely on opaque, third-party systems. Onyx approach
to Token Contracts varies by deployment model.
Token Contracts
Accounts are uniquely identified entities such as public keys or user IDs that hold token balances
and can participate in sending or receiving tokens. These accounts may be controlled by
individuals, organizations, or automated systems. Depending on the use case, tokens can be
used for payments, access to services, or transferring ownership.
Accounts
Utilizes Onyx-native accounts
managed by the Onyx mainnet.
Relies on custom account identifiers,
typically public keys, defined within
the permissioned network.
The token contract is embedded
directly within the token’s
definition parameters.
The token contract is implemented
in application logic, executed by
permissioned nodes that maintain
the network state.
Onyx Layer 1 Onyx Mesh
Onyx Layer 1 Onyx Mesh
Onyx.org 29
Onyx supports two primary models for tokenization: the Onyx Layer 1 for issuing tokens natively
on the Onyx public ledger, and the Onyx Mesh for constructing permissioned networks that
synchronize state with publicly verifiable ordering.
These models offer distinct benefits tailored to different deployment scenarios, ranging from
public-facing stablecoins and NFTs to private, regulator-compliant asset networks.
Tokenization, the process of converting real-world assets or rights into digital representations on
a distributed ledger, is reshaping trillion-dollar industries from finance to supply chains. The
primary benefit of tokenization is the creation of more transparent, efficient, and accessible
markets.
Assets can be fractionalized, transferred, and settled with unprecedented speed and minimal
friction. As use cases for tokenization expand across securities, utility tokens, stablecoins, NFTs,
and more, the infrastructure supporting it must offer enterprise-grade performance, compliance
features, and low operational cost.
Onyx’s dual tokenization architecture addresses these demands through:
Onyx Layer 1 for native tokenization
with high throughput and
decentralized trust.
Onyx Mesh for customizable,
permissioned token networks using
Onyx’s consensus ordering.
Onyx.org 30
The Onyx Layer 1 allows token issuers to define, issue, and manage tokens directly on Onyx’s
public mainnet. These tokens inherit key characteristics of the Onyx network: asynchronous
Byzantine fault tolerance (aBFT), finality in seconds, and low-cost transaction fees fixed in USD.
Onyx Layer 1: Native Tokenization on Onyx
Key Features:
Thousands of
token transactions
per second.
Transactions cost
less than $0.01.
Every transaction is
recorded in the ledger
and can be audited via
consensus nodes.
Unlike many
blockchain platforms,
Onyx’s consensus does
not fork.
TOKEN
High Throughput Low and Predictable
Costs
Public Verifiability No Forks
Onyx.org 31
The Onyx Layer 1 provides an API-driven interface that developers use to define token properties.
All tokens are issued as native objects on the network.
The Onyx Layer 1 supports a comprehensive set of on-chain operations that enable flexible and
secure asset management. Some of the transaction types available to token issuers and holders
include lifecycle actions such as creation and updates, supply control through minting and
burning, compliance features like KYC and token association, as well as advanced capabilities
like atomic transfers involving multiple tokens and XCN in a single transaction.
Name and
Symbol
Decimals
(degree of
divisibility)
Administrative Keys (optional):
freeze, wipe, KYC, and supply
manager roles
Initial Supply
Auto-renew Settings
Treasury Account
(holder of the
initial supply)
API
Onyx.org 32
Consensus nodes track all activity on the Onyx Layer 1, allowing third parties to independently
verify token balances, transfer histories, and metadata with full transparency.
These nodes are designed for ease of deployment and provide seamless integration support for
external systems such as wallets, custodians, and exchanges. By reflecting the consensus-
established state of the Onyx network, consensus nodes offer a decentralized source of truth that
enhances auditability and trust.
Additionally, they serve as a critical foundation for interoperability, enabling future
cross-network bridges and integration with other distributed ledger technologies (DLTs).
Create, Update,
Mint, Burn
Wipe and
Freeze/Unfreeze
KYC and
Association
Atomic Transfers
of multiple
tokens and XCN
Onyx.org 33
The Onyx Layer 1 also features the Onyx API which is defined using protocol buffers and serves as
the interface for interacting with Onyx network services and functions. Publicly accessible and
designed for broad applicability, The Onyx Layer 1 API enables a wide range of commercial and
technical use cases.
The Onyx Layer 1 builds on existing network primitives, allowing users to create and interact with
tokens as native entities within the Onyx ecosystem. Like other Onyx entities such as accounts,
files, smart contracts, and threads, tokens are uniquely identified using the shard.realm.num
format. The Onyx Layer 1 introduces a new entity type: the token type entity, which uses this same
identifier structure.
Each Onyx account can hold XCN (the native cryptocurrency) alongside multiple custom token
types. However, accounts must explicitly opt in to each token type by signing and associating with
it before holding or transacting that token. XCN transfers remain independent of token
interactions, users can continue to send and receive XCN regardless of the other tokens held by
their account.
The Onyx Layer 1 API
Ease of
Deployment
Interoperability
with future bridges
and other DLTs
Decentralized
Trust from the
Onyx network’s
consensus
Integration Support
with wallets,
custodians, and
exchanges
Onyx.org 34
The Onyx Layer 1 functions inherit Onyx advanced key architecture, supporting flexible
configurations including single keys, key lists, threshold keys, and even nested key structures,
enabling fine-grained control over token issuance, management, and transfer.
In addition, The Onyx Layer 1 introduces new fields within transaction receipts, records, and state
proofs. These responses can be independently captured, verified, and stored by third parties,
allowing token operations to inherit Onyx ABFT (Asynchronous Byzantine Fault Tolerance)
security model. Token transfer consensus is reached fairly, without the need for a central leader,
and transaction finality is achieved within seconds, resulting in an immutable, verifiable log of
token activity.
Consensus nodes receive updated record streams and account balance files that include token
balances and transfers for Onyx Layer 1 issued tokens.
Onyx Mesh allows applications to submit messages to the Onyx network, which timestamps and
orders them using Onyx consensus. The ordered messages can then be consumed by
permissioned networks that maintain their own ledger state. This approach is ideal for use cases
requiring enhanced control, privacy, or jurisdictional governance such as regulated financial
markets or central bank digital currencies (CBDCs).
Onyx Mesh: Tokenization for Permissioned Networks
Architecture Overview:
Clients submit
messages
(e.g., token
transfers) to a
specified Onyx
Mesh thread
Permissioned Nodes
apply application
logic (the token
contract) to update
their local state
Consensus Nodes
relay the message
stream to
permissioned
nodes
Onyx Mainnet
timestamps,
orders, and
cryptographically
verifies these
messages
Onyx.org 35
A token contract defines the core logic of a token, handling minting, burning, role management,
and permissions. Unlike the standardized model used in Onyx Layer 1, Onyx Mesh supports fully
customizable contracts that can be tailored to meet specific commercial, regulatory, or
jurisdictional needs.
These contracts listen to a specific ThreadID on the Onyx Mesh, receiving ordered messages that
are validated against the token’s rules. Nodes execute the logic to update local state verifying
signatures, enforcing restrictions, and managing balances.
Beyond basic operations, contracts can support advanced features like atomic swaps, event
triggers, or oracle integration, offering both flexibility and consistency within a permissioned
environment.
Onyx Mesh tokenization, known as the Token Message Standard, provides a foundational
approach for issuing, transferring, and managing digital tokens in a consistent and secure manner
across distributed networks. This standard ensures that all token-related messages are
well-structured and tamper-proof, enabling seamless synchronization among participating
nodes. It not only guarantees message integrity and interoperability, but also unlocks powerful
capabilities such as atomic swaps, hold-and-release mechanisms, and automated commercial
logic.
These features allow for complex transaction flows, regulatory compliance, and customizable
token behaviors, making the Token Message Standard a key enabler for enterprise-grade
tokenization and decentralized finance solutions.
The Token Message Standard provides a detailed and flexible framework for defining and
enforcing roles and behaviors within a tokenized system. These roles are optional and can be
selectively implemented based on the governance, regulatory, or commercial requirements of a
specific deployment. The design closely mirrors the capabilities of the Onyx Layer 1 but is
extended to support custom implementations, particularly within permissioned environments
using the Onyx Mesh. Through this model, token issuers can incorporate fine-grained controls
around token creation, distribution, compliance, and lifecycle management, all while maintaining
a consistent and interoperable taxonomy across network participants.
Token Contract
Token Message Standard
Onyx.org 36
At the center of this system is the Administrator role. The Administrator is responsible for
initializing the token contract by defining core attributes such as the token’s name, symbol,
decimal precision, and which roles are enabled for governance. In addition to initial setup, the
Administrator has authority to update the token contract, including modifying role assignments,
changing governance policies, or rotating keys tied to specific roles. Any such updates require
not only the Administrator’s signature but also that of the new Keypair Owner, the entity
controlling the private key associated with the updated role. This dual-signature requirement
ensures deliberate and secure governance transitions. Administrators can also propose and
execute changes to other role-based keys (e.g., for the Supply Manager, Compliance Officer, or
Enforcement role), further enabling structured yet flexible control over the token’s lifecycle.
The Supply Manager role governs the creation (minting) and destruction (burning) of tokens. This
role is particularly useful for tokens that require dynamic supply adjustments, such as
stablecoins, securities, or programmable financial instruments. Supply Managers can also initiate
token transfers, allowing them to manage treasury operations, distribute rewards, or settle
internal flows. The token contract can be designed so that minting or burning is only triggered
under specific commercial conditions or events, ensuring that the supply logic aligns with the
broader operational context of the tokenized asset.
The Compliance role enforces the regulatory requirements of the token network. It provides
mechanisms to manage identity verification (KYC), freeze or unfreeze accounts, and remove or
reinstate compliance status. These capabilities are essential in environments where Anti-Money
Laundering (AML) regulations, sanctions enforcement, or access controls are required. Typically,
the Compliance role may be assigned to a trusted third-party provider, such as a financial
institution or compliance service, that performs identity verification and monitors for suspicious
activity.
The Enforcement role enables more direct intervention in token balances through a process
known as clawback. This is executed via a wipe transaction, which irreversibly removes a
specified number of tokens from a user’s account and simultaneously burns them from the total
supply. This function may be used in exceptional situations such as regulatory enforcement
actions, fraud recovery, or dispute resolution processes. The ability to revoke tokens directly
enhances the network’s responsiveness to legal and operational risks.
Lastly, the Token Holder is the most common and fundamental role in any token ecosystem.
Token Holders are end users or systems that own tokens and can transfer them up to the balance
they control. Each Token Holder manages access to their tokens through a cryptographic key pair,
enabling decentralized custody and user-level control without intermediaries. This role ensures
that participation in the network remains open and permissionless for users, while still being
governed by the rules enforced through the token contract.
37
Altogether, the Token Message Standard offers a powerful and adaptable model for structuring token
systems. Its role-based architecture provides enterprises and developers with a comprehensive
toolkit for implementing secure, compliant, and commercial-aligned token functionality, whether in
public, permissioned, or hybrid network environments. By decoupling token behavior from rigid
infrastructure, it allows each role to be flexibly defined, updated, and enforced according to evolving
requirements, enabling sustainable token ecosystems with built-in governance.
The platform offers extensive customization options, allowing for jurisdictional constraints,
enhanced privacy, and seamless integration with enterprise blockchain frameworks.
Customization Possibilities
COMPLIANCE
KEYPAIR OWNER ENFORCEMENT
TOKEN HOLDER
ADMIN SUPPLY
• Freeze/Unfreeze Token Holder Accounts
• Change KYC Status of Token Holder
• Accept Changes by Admin
to Public Keys
• Wipe Tokens from
Holders Accounts
• Transfer Token
• Change Asset Protection
Public Key
• Change Supply Manage
Public Key
• Initialize Token
• Propose Admin Public
Key Changes
• Mint
• Burn
• Transfer Token
Onyx.org
Onyx.org 38
Token Nodes maintain ledger state, expose APIs for clients, and sync via Onyx Mesh.
Onboarding new nodes involves deploying the token contract and subscribing to the relevant
thread. Nodes can reconstruct state from historical Onyx Mesh messages via consensus nodes.
This has several benefits.
Onyx offers a powerful dual approach to tokenization through its two core services: Onyx Layer 1
and Onyx Mesh.
Onyx Layer 1 provides the simplicity, speed, and transparency of public network deployment, ideal
for issuing stablecoins, loyalty points, and governance tokens that users can easily access via
Onyx wallets or integrated applications. In contrast, Onyx Mesh delivers the flexibility, privacy,
and custom governance required for complex enterprise use cases such as private marketplaces,
regulated financial networks, and supply chain consortia, offering full control over token logic,
onboarding, compliance, and data residency.
Both models are underpinned by the same core strengths: fast finality, aBFT security, and
predictable pricing. Whether launching consumer-facing assets or building sovereign-grade
token economies, Onyx provides the trusted infrastructure to do so with performance and
flexibility.
Token Node Operation
Define bespoke token
behavior without
mainnet constraints
Sensitive data can
be encrypted and
handled only by
trusted nodes
High throughput
with decentralized
ordering
Determine who can
join and maintain
the network
Full Control Privacy Scalability Governance
Flexibility
Onyx.org 39
Security
Onyx.org 40
All communications within the Onyx network are secured using TLS 1.2, and all transactions are
authenticated through digital signatures. The Onyx data structure itself is formed using
cryptographic hashes.
All cryptographic algorithms and key lengths implemented in the Onyx platform conform to the
Commercial National Security Algorithm (CNSA) Suite, the standard mandated for securing U.S.
government Top Secret information. These algorithms include RSA 3072 for digital signatures,
AES-256 for encryption, ECDSA/ECDH with the P-384 curve, and SHA-384 for hashing in addition
to using ephemeral keys for ensuring perfect forward secrecy.
The Onyx algorithm provides asynchronous Byzantine Fault Tolerance (aBFT), ensuring that no
individual node or colluding subset of nodes can prevent the network from reaching consensus or
alter it after finalization.
Each Onyx node deterministically arrives at a point of certainty, recognizing that consensus has
been definitively achieved across the network. In contrast, blockchain systems lack formal
Byzantine agreement guarantees; consensus is probabilistic and subject to reversal. Additionally,
blockchain protocols are not inherently resilient to network partitions, isolated subsets of miners
may independently extend conflicting chains, resulting in forks and inconsistencies in
transaction ordering.
It is important to clarify that the term Byzantine Fault Tolerant (BFT) is occasionally applied in a
weakened form to describe limited resistance to adversarial behavior in some consensus
protocols. In contrast, Onyx adheres to the original, stronger definition of BFT: even under
conditions where (1) a subset of malicious actors colludes to disrupt or distort consensus, and (2)
adversaries exert partial control over the network infrastructure, such as delaying or obstructing
message delivery, the system will still reach consensus, and all nodes will eventually have
certainty that consensus has been achieved.
Asynchronous Byzantine Fault Tolerance (aBFT)
Cryptography
Onyx.org 41
Onyx satisfies this robust definition of Byzantine Fault Tolerance. Provided that malicious entities
control less than one-third of the total staked XCN, they cannot halt consensus, manipulate
transaction ordering, or bias consensus timestamps.
Byzantine Fault Tolerance (BFT) encompasses varying degrees of robustness, determined by the
underlying assumptions about network behavior and message transmission. Weaker forms of BFT
assume synchronous or partially synchronous networks with bounded message delays, while
stronger forms, such as asynchronous BFT, make no timing assumptions and tolerate arbitrary
delays in message delivery. The strength of a BFT protocol is directly correlated with its ability to
maintain consensus in increasingly adversarial or unpredictable network conditions.
The strongest form of Byzantine Fault Tolerance is asynchronous BFT, which ensures that
consensus can be reached even if adversaries have the capability to delay or selectively suppress
message transmission across the network. This model assumes only that more than two-thirds of
nodes behave honestly and that, over time, messages repeatedly sent between nodes will
eventually be delivered. Unlike partially asynchronous systems which rely on assumptions such
as fixed maximum message delays (e.g., ten seconds), asynchronous BFT remains secure even
under unpredictable network conditions. Partially asynchronous protocols may fail under
real-world threats such as botnets, Distributed Denial of Service (DDoS) attacks, or malicious
firewalls, as these can invalidate the timing assumptions critical to their correctness.
Onyx is ACID compliant when employed as the consensus layer for a distributed database.
ACID, Atomicity, Consistency, Isolation, Durability, defines a set of properties required for reliable
transaction processing.
Onyx enables a network of nodes to reach final consensus on the chronological order of
transactions. Once consensus is achiev프로젝트로 돌아가기