On this page
Obyte is an operating distributed-ledger project that uses a directed acyclic graph, or DAG, instead of arranging transactions into a conventional sequence of blocks. Its native currency is expressed in bytes, with GBYTE used for a larger denomination. It supports an operating ledger and application ecosystem.
The project's timeline dates its network launch to December 25, 2016. As of October 8, 2026, its documentation and public explorer show an established application ecosystem and recorded activity. That supports an active-network classification without implying that every listed application is secure or heavily used.
How a DAG differs from a blockchain
A graph is a structure of connected records. In Obyte, transactions reference earlier records, forming a directed structure that cannot loop back on itself. The absence of conventional blocks changes the way transactions enter the ledger and the role normally played by miners or block producers.
It does not eliminate the need to agree on transaction order. Conflicting attempts to spend the same money still need a resolution. Obyte uses a consensus design involving order providers. Understanding who performs that role and how the protocol uses their activity is more informative than simply calling the system completely decentralized.
The architectural choice also does not make contracts unbreakable. A ledger can apply code consistently even when the code contains a mistake. It can preserve a record faithfully even when the record refers to inaccurate information from outside the network.
GBYTE and transaction costs
Bytes serve as the native payment unit for using the ledger. One GBYTE represents one billion bytes. This denomination can make prices and balances look unfamiliar, but it is a unit convention rather than a different asset.
Obyte charges transaction fees despite having no conventional mining. Its documentation describes fees associated with adding data, and its governance pages describe an additional fee mechanism tied to transaction load. Users therefore need native currency to pay for relevant operations, even when interacting with another asset.
It is useful to separate native-currency supply from the supply of tokens issued on the platform. An application can create a token with its own rules. That asset does not become equivalent to GBYTE merely because both appear in the same wallet. Public explorer information can help identify the asset and the transactions associated with it.
Autonomous agents make applications possible
Obyte calls its on-ledger programs autonomous agents. They receive transactions, apply programmed conditions and respond with asset transfers or recorded data. The official documentation identifies Oscript as the language used to write them and describes applications including exchanges, prediction markets and lending mechanisms.
This is programmable execution, not human judgment. An agent can implement a rule precisely without knowing whether the rule is sensible or whether an external data feed is accurate. Applications that depend on an oracle inherit an additional dependency: somebody or something must provide the outside information.
The public explorer can display an agent's definition and responses. That is useful transparency, but a visible program is not a substitute for understanding its economic assumptions. A stablecoin mechanism, for example, needs analysis of how its backing, redemption and stress behavior work, not just confirmation that its transactions exist.
Privacy, wallets and linked systems
Obyte also documents distinct private-transfer functionality through Blackbytes. That does not make every GBYTE transaction private. The asset and transfer method need to be identified before making a privacy claim. A user should not assume that an ordinary public transfer receives protections described for another feature.
Bridged assets add another layer. A token representing value from an external network depends on the bridge's rules and operation as well as the Obyte ledger. A successful transaction on one side is not necessarily the final step in a cross-network transfer.
Architecture and practical use
Obyte’s value as a technical subject lies in its alternative ledger architecture and application model. These choices change transaction ordering and programming without removing the need to evaluate software, economic assumptions and outside information. An operating network can support useful experiments without making every experiment dependable.
A useful assessment now asks how transactions are ordered, what fees apply and what an individual application actually does. Those questions lead to a clearer understanding than treating the absence of blocks as a guarantee of cost-free, risk-free operation.