Onyxcoin 백서

Onyxcoin

원문

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 6쪽 중 2쪽

ONTRACTS FILE SERVICE CONSENSUS SERVICE INTERNET Internet layer Onyx.org 16 Each node within the Onyx network is uniquely identified by its IP address and port number rather than relying on domain names or the Domain Name System (DNS). By avoiding DNS entirely, the network eliminates a significant point of vulnerability common in many distributed systems, namely, DNS hijacking, poisoning, or other forms of name resolution attacks. This architectural decision enhances the network’s resilience against censorship, surveillance, and disruption, making it more robust and more challenging to tamper with or take offline using conventional attack vectors. Nodes in the Onyx network act as active participants in both the intake and distribution of transactions submitted by clients. When a client submits a transaction to any node, that node immediately begins disseminating the transaction to its peers through a fast and fault-tolerant algorithm. This ensures that every valid transaction is rapidly propagated throughout the network in a redundant and decentralized manner, making the system highly resilient to node failures or network partitions. Once transactions are widely disseminated, each node independently executes the Onyx consensus algorithm, a deterministic protocol designed to establish a unified view of the network’s history. Through this process, nodes collaboratively determine a consensus timestamp for each transaction and reach an agreement on a definitive, total ordering of all transactions across the network. This ensures that, regardless of when or where a transaction is first received, all nodes reach the same conclusion about its place in the Onyx network. After consensus is achieved, each node applies the transactions to its local copy of Onyx in the exact order defined by the consensus. This synchronized application process updates the shared state in a consistent and verifiable way. As a result, all nodes within a given shard maintain identical views of Onyx current state, ensuring complete data consistency and enabling trustless coordination across the network. Onyx Consensus Layer Onyx.org 17 The Onyx Services Layer represents the operational heart of the platform, a modular suite of network-native capabilities built atop Onyx’s consensus protocol. These services expose core functionality to developers and applications, enabling decentralized execution, secure storage, digital asset management, and trustless event ordering. Each service is designed to leverage the performance, fairness, and security guarantees of the underlying consensus engine, while remaining flexible enough to support diverse enterprise and public-sector use cases. Onyx native cryptocurrency is XCN. This bridged implementation of XCN is engineered for high throughput and low latency, resulting in low transaction fees that make microtransactions economically viable. Network participation will be open to any user, who may operate a node and receive compensation for contributing to consensus. Users can create accounts by generating a public-private key pair, with no requirement to associate personally identifiable information such as a name or address. However, the platform supports optional identity binding through the attachment of hashed identity certificates, issued by third-party certificate or identity authorities selected by the user. This mechanism is intended to facilitate regulatory compliance in jurisdictions requiring adherence to Know Your Customer (KYC) or Anti-Money Laundering (AML) obligations. Native Currency DIGITAL ASSETS SMART CONTRACTS FILE SERVICE CONSENSUS SERVICE Services Layer Onyx.org 18 Onyx offers robust support for executing smart contracts written in Solidity, the industry-standard programming language widely used across Ethereum-compatible ecosystems. Thanks to this compatibility, developers can seamlessly deploy existing Solidity codebases, including extensive libraries and complex smart contracts onto Onyx without the need for modification or refactoring. This interoperability not only preserves the value of established tooling and frameworks but also significantly accelerates the development and deployment of decentralized applications. As a result, teams can leverage familiar development workflows while taking advantage of Onyx’s performance and consensus guarantees. Onyx file system enables users to store data with network-wide consensus on both the content and existence of each file. All nodes within a shard store identical copies, ensuring fault tolerance and preventing data loss if any single node fails. Deletion permissions are enforced through access control, allowing only authorized parties to remove stored data. This functionality allows the file system to operate as a revocation service. For example, consider a scenario where a professional certification body issues a digital accreditation to a licensed engineer. A hash of the certification document, co-signed by both the certifying authority and the engineer, is submitted to the ledger. Both parties are granted the right to remove the hash if necessary. To verify the credential, the engineer may present the certification file to an employer or client, who can then check whether the hash remains recorded on the ledger. If the certification is later revoked due to expiration or disciplinary action, the certifying body can delete the hash, indicating the credential is no longer valid. If the engineer attempts to resubmit the hash without the certifier’s signature, it will be evident that the entry was not authorized, and thus not a valid representation of the original certification. Files on the Onyx network are internally represented as Merkle trees, but developers interact with them through a simplified interface. Onyx provides Java classes that abstract the underlying structure, enabling developers to manipulate files as if working within a conventional file system with directories, subdirectories, and files. File Storage Smart Contracts Onyx.org 19 Developers can rename directories, modify file contents, and perform operations like moving, copying, and pasting. Behind the scenes, all changes are automatically structured and stored as Merkle trees. This architecture enables the platform to generate cryptographic proofs that a file is part of the consensus state. Entire directory structures can be stored in this manner. Additionally, Onyx supports Merkle Directed Acyclic Graphs (DAGs). This allows for deduplication: when two files share identical byte segments, only one copy of the shared data is physically stored, improving storage efficiency. The Onyx Mesh provides a powerful, high-performance alternative to traditional smart contracts and on-chain data storage, offering decentralized, trust-based ordering of events. Through The Onyx Mesh, applications can submit messages to the Onyx public network, where each message is deterministically timestamped and ordered using the Onyx Mesh algorithm. This process ensures fairness, transparency, and cryptographic verifiability while offloading commercial logic and data storage to external systems. This dual-access model means files are both immutable and updatable, depending on how they are accessed. Access by hash ensures permanence, while access by File ID ensures that the latest version is always retrieved. By hash, guaranteeing immutability, since the hash directly reflects the file’s contents. By File ID, enabling mutability, as the File ID can be redirected by the file’s owner to point to a newer version. Files can be accessed in two distinct ways: The Onyx Mesh Onyx.org 20 The Onyx Mesh is part of the broader Onyx Network, a public distributed ledger governed by the Onyx DAO composed of XCN holders and built on Onyx. Alongside cryptocurrency, file storage, and smart contracts, The Onyx Mesh serves as a key network service enabling decentralized consensus for various use cases. Clients submit messages tagged with a thread ID to the Onyx mainnet. These messages, containing data such as bids, logs, or event notifications, are distributed across nodes until consensus is reached. Each message receives a consensus timestamp, sequence number, and is incorporated into a running hash that provides a cryptographic fingerprint of all messages for that thread. Once consensus is established, the message and metadata are streamed to consensus nodes. These consensus nodes are read-only and do not participate in consensus. They receive messages from the mainnet, and depending on configuration, can store full transaction records, selected threads, or even all consensus data, offering flexibility in data management. This decoupled architecture empowers applications to process data off-chain while relying on Onyx for trusted ordering. Developers can build commercial logic into consensus nodes or application servers, using consensus timestamps to drive real-time operations or generate cryptographic proofs of event ordering. Onyx Mesh architecture defines three roles. Reach consensus and assign timestamps to messages. Propagate, store, and allow querying of consensus messages. They cannot submit transactions or vote. Maintain local state, execute commercial logic, and manage access to decrypted content. Mainnet Nodes Consensus Nodes Commercial Nodes Onyx.org 21 A commercial application network may subscribe to an Onyx Mesh thread to receive and decrypt encrypted messages. These networks benefit from Onyx’s decentralized ordering while maintaining control over sensitive data and execution. Onyx Mesh is particularly well-suited for use cases where data privacy regulations, such as GDPR, apply. In the Onyx Mesh model, personal data is encrypted before being submitted to the mainnet. The Onyx network stores this encrypted payload briefly (approx. 3 minutes), while consensus nodes may store it longer. Because only commercial application nodes hold the decryption keys, control over data access is preserved. This architecture ensures that raw personal data is stored only where legally justified, while consensus nodes retain encrypted, immutable records that support compliance through cryptographic proofs. If deletion is required, commercial nodes may delete the data and keys, rendering encrypted records effectively inaccessible while maintaining the integrity of the consensus history. The Onyx Mesh bridges the gap between public decentralized trust and private enterprise control. It delivers fast, fair, and secure consensus without requiring full on-chain data storage, dramatically reducing operational costs and complexity. Whether used in financial services, healthcare, IoT, or identity management, Onyx Mesh brings auditability, integrity, and efficiency to distributed systems. As adoption grows, Onyx Mesh stands to become a cornerstone in the evolution of compliant, scalable, and decentralized application infrastructure. Onyx.org 22 Despite their restricted role in consensus, Consensus Nodes may implement custom APIs to offer enhanced services or tailored data access. The consensus network provides a scalable and efficient mechanism for disseminating ledger state and transaction data to external clients and distributed applications without burdening the throughput of the main network. This architecture enables decentralized applications (dApps) to operate their own consensus nodes, allowing them to monitor specific events, filter relevant transactions, and respond to network activity in near real-time. For example, a dApp managing smart contracts may deploy a consensus node to listen for contract-specific events, ignore unrelated data, and trigger appropriate application logic in response. The Onyx consensus network comprises a set of nodes that replicate the core validation and state-tracking functions of the main Onyx network while excluding the ability to influence consensus or submit transactions. Consensus nodes participate in the network’s peer-to-peer communication protocol, receiving all transaction data in real-time, performing signature verification, and computing consensus outcomes. However, they do not create events and, therefore, do not alter the structure of Onyx. As such, consensus nodes possess no voting authority and are unable to submit transactions through the Onyx API, functioning effectively as read-only nodes. Consensus Network Onyx.org 23 The Onyx network will initially operate as a single shard composed of a limited number of nodes. As the network matures and more nodes join, it will evolve to support multiple shards, each functioning independently to establish consensus. Sharding boosts performance by enabling parallel processing, as each node processes only the transactions relevant to its shard. Each shard contains a randomly assigned subset of nodes that maintain a consistent shard-specific state, a portion of the full network ledger. These nodes utilize the Onyx consensus algorithm to determine the transaction order within their shard. Every shard can store accounts and files and execute smart contracts. Transactions that involve only one shard (e.g., transferring XCN within that shard or storing a file) are processed immediately upon reaching consensus. To support cross-shard activity, the network implements trust-based inter-shard communication. A transaction that spans multiple shards, such as moving cryptocurrency from an account in shard X to an account in shard Y, triggers the generation of inter-shard messages. Each shard maintains a queue of outbound messages tagged with sequence numbers to ensure ordered processing. Messages are “pushed” by randomly selected nodes from the source shard to nodes in the destination shard, accompanied by cryptographic proof of consensus. The receiving shard verifies the message, checks its sequence number, and integrates it into its consensus state if valid. Duplicate messages are ignored, and processing occurs strictly in sequence. Once confirmation is received that a message has been processed, the source shard removes it from its outbound queue. Complex, multi-shard transactions (e.g., one-to-many or many-to-one transfers) may involve atomic operations, such as placing “holds” on balances until all conditions are met. For example, a transaction that transfers coins from two source accounts in different shards to one destination account involves holds being placed on both sources. Only if all holds are successful are balances updated and funds transferred to the destination. If any hold fails, all are released, and no transfer occurs. This guarantees atomicity across shards. Sharding Onyx.org 24 A master shard oversees node assignment, ensuring balanced stake distribution and periodically reallocating nodes to shards. The system ensures no single node controls too much stake within a shard, preserving Byzantine fault tolerance. Finality is often achieved as quickly as consensus within the initiating shard. For most single-source transactions, this means users can rely on near-instant certainty. In more complex, multi-shard interactions, finality may take slightly longer due to required inter- shard confirmations, but it remains efficient and secure. By ensuring every inter-shard message is cryptographically bound to the consensus state of the originating shard, the network preserves asynchronous Byzantine fault tolerance across the entire platform. This architecture allows Onyx to scale horizontally while maintaining security, consistency, and trust. Onyx.org 25 Onyx.org Tokenization Onyx.org 26 Before exploring how Onyx implements tokenization, it’s important to first understand several foundational concepts, including the different types of tokens and the technical parameters that define their behavior. Fungible tokens such as stablecoins, governance tokens, and other value-pegged assets are inherently interchangeable, with each unit holding equal value, much like the dollars in a bank account. While every dollar might be represented digitally or tracked with different identifiers, each functions identically in practice. These tokens are typically managed through account- based models, where an account reflects a balance of indistinguishable units. Thanks to their uniformity and simplicity, fungible tokens are ideal for high-throughput use cases such as payments, rewards, and liquidity provisioning. Non-fungible tokens (NFTs) are inherently unique, with each token distinguishable by attributes such as a name, serial number, or embedded metadata. This uniqueness makes NFTs individually identifiable and non-interchangeable. Often linked to specific digital or physical assets like digital art, virtual real estate, or proof of ownership. NFTs are typically implemented using a token-based model, where each token stands alone with a defined owner. Due to their individualized nature, NFTs are best suited for lower throughput use cases that involve high-value or asset-specific interactions, particularly in scenarios where traceability and uniqueness are essential. The range of token use cases continues to expand rapidly, touching nearly every industry from finance and gaming to supply chains, identity, and governance. This growing diversity has shaped the design of platforms like the Onyx Layer 1, which supports multiple token types tailored to distinct purposes and audiences. At one end of the spectrum are utility tokens, which grant holders access to specific products or services such as cloud computing credits, event tickets, or subscription-based offerings. At the other are security tokens, which represent ownership in real-world assets like company equity, real estate shares, or other financial instruments. These tokens are regulated and must comply with securities laws, as their value is directly tied to the assets they represent. Fungible Tokens Non-fungible tokens (NFTs) Use Cases Onyx.org 27 Another emerging category includes memecoins, which are often created for community-driven engagement, experimentation, or entertainment. While they may lack intrinsic utility or asset backing, memecoins frequently serve as cultural artifacts or social signals within digital communities. Despite their lighthearted origins, some have demonstrated significant economic impact and adoption. Together, these varied token types highlight the flexibility and breadth of tokenization, enabling both practical and expressive use cases across permissioned and public networks. Once a token contract is developed and deployed, it results in the creation of a token that can be transferred between accounts, typically as part of a commercial process or triggered event. Each account’s balance and transaction history are captured within the overall state of the token system. A Token Contract is the code that defines a token’s roles, rules, and behaviors. It is typically authored by the token issuer and made publicly accessible either by open-sourcing the code or deploying it as a smart contract on a public network. This transparency ensures that the token’s behavior is verifiable, eliminating the need to rely on opaque, third-party systems. Onyx approach to Token Contracts varies by deployment model. States Token Contracts Token state resides on permissioned network nodes, which stay synchronized using Onyx Mesh messages published to a specific thread. Onyx Mesh Token state is maintained on the public ledger by Onyx mainnet nodes. Onyx Layer 1 Onyx.org 28 A Token Contract is the code that defines a token’s roles, rules, and behaviors. It is typically authored by the token issuer and made publicly accessible either by open-sourcing the code or deploying it as a smart contract on a public network. This transparency ensures that the token’s behavior is verifiable, eliminating the nee
프로젝트로 돌아가기