Byteball (Obyte / GBYTE): The Cryptocurrency With No Blockchain
Byteball (rebranded Obyte, token GBYTE) is a cryptocurrency that records transactions on a Directed Acyclic Graph (DAG) rather than a blockchain. It has no blocks and no Proof-of-Work mining; instead, each transaction references earlier ones and a small set of Witnesses orders history. GBYTE was airdropped to Bitcoin holders starting in December 2016. Byteball is notable for human-readable smart contracts that enable conditional payments, oracle-based insurance, prediction and P2P betting, plus an optional private currency called Blackbytes. Fees are charged at roughly one byte of GBYTE per byte of stored data, which is why the unit is named after data size.
Byteball is a cryptocurrency that stores transactions on a Directed Acyclic Graph (DAG) instead of a blockchain. Created by Anton Churyumov and launched around Christmas 2016, it replaces blocks and Proof-of-Work mining with a graph where each new transaction confirms several earlier ones. Its native token is GBYTE (gigabytes of data). The project later rebranded to Obyte, but the architecture and the no-blockchain premise are unchanged. Byteball is best known for human-readable conditional payments, oracle-driven insurance and betting contracts, and an optional private currency called Blackbytes.
What Is Byteball?
Byteball began as a research effort in 2014, when Anton Churyumov set out to fix scaling and finality limits he observed on Bitcoin. The result was a ledger with no chain of blocks at all. Every transaction is a node in a DAG and references one or more previous transactions, so the act of transacting also helps validate the network. There is no separate class of miners and no fixed block interval.
The coin distribution was unusual: instead of an ICO, GBYTE was airdropped to Bitcoin holders. The first distribution happened on 25 December 2016, followed by roughly ten further rounds through 2017 that linked Bitcoin and Byteball wallet balances. By the end of that cycle around 65% of the total supply had been handed out this way.
How DAG Replaces the Blockchain
In Bitcoin, blocks are appended one at a time roughly every ten minutes, and miners compete to produce them. That single-file structure is part of why fees and confirmation times spike during congestion. Byteball removes the block entirely. New transactions attach directly to earlier ones, and confirmation comes from later transactions piling on top.
To keep the graph converging on a single history, Byteball uses a small set of reputable nodes called Witnesses. Users reference the witness list, and the order of transactions is derived from a "main chain" pulled through the most-witnessed path. Fees are deliberately simple: you pay roughly 1 byte of GBYTE per byte of data your transaction occupies, which is why the unit is named after data size.
Byteball vs. Bitcoin vs. Ethereum
| Property | Byteball (GBYTE / Obyte) | Bitcoin | Ethereum |
|---|---|---|---|
| Data structure | DAG (no blocks) | Blockchain | Blockchain |
| Consensus | Witnesses + main chain | Proof-of-Work | Proof-of-Stake |
| Mining | None | Required | None (post-Merge) |
| Smart contracts | Human-readable conditions | Limited script | Solidity (Turing-complete) |
| Native privacy | Optional Blackbytes | None | None |
| Fee model | ~1 byte per byte of data | Fee market (sat/vByte) | Gas fees |
Smart Contracts You Can Actually Read
Byteball's smart contracts are intentionally less powerful than Ethereum's Solidity. Instead of a full programming language, they use chained IF / AND / OR conditions that ordinary users can compose. The trade-off is deliberate: less expressiveness, far fewer ways to write a catastrophic bug like the Parity wallet freeze. Common patterns include:
- Risk-free conditional payments. Funds are "bound" to a condition and only released when it is met; otherwise they bounce back to the sender — a peer-to-peer escrow with no middleman.
- Insurance. A counterparty agrees to pay out if a defined event occurs, with the trigger fed in by an oracle.
- Prediction and P2P betting. Two parties stake on a binary outcome (a match result or a price move); the loser pays the winner per the contract.
- Identity management. Users can store a verified ID in the wallet and choose exactly who to share it with — useful for KYC-style flows.
Many of these depend on oracles, trusted data feeds that post real-world facts (a flight status, a closing price) into the network so a contract can settle automatically.
A Worked Example: Flight-Delay Insurance
Suppose Maya wants insurance on a flight. She enters a contract with an underwriter, Sam, structured like this:
- Maya locks 5 GBYTE as the premium and Sam locks 50 GBYTE as the payout pool.
- The contract names a flight-status oracle as the data source.
- IF the oracle reports the flight as "cancelled" by the agreed date, the full 50 GBYTE is released to Maya.
- ELSE (flight departs on time), Sam reclaims his 50 GBYTE and keeps Maya's 5 GBYTE premium.
Neither party can renege: the rules are immutable once posted, and settlement happens the moment the oracle publishes its result. There is no claims department to argue with — the code either pays or it does not.
Blackbytes, Custom Assets and Atomic Swaps
Byteball ships a second, optional currency called Blackbytes for private transfers. Blackbytes move off the public DAG through encrypted messaging: the ledger records that the sender no longer holds the coins but does not record who received them. This is closer in spirit to privacy coins than to Bitcoin, where every transfer is permanently visible.
The network also supports user-issued assets, so an institution could mint its own token (say, a tokenized loan) and attach KYC requirements to it. Finally, Byteball supports atomic swaps — a two-sided trade that either completes simultaneously on both ends or not at all, with no counterparty risk in between.
Where GBYTE Came From and How to Hold It
Because GBYTE was airdropped rather than sold, early Bitcoin holders received it for free in proportion to their balances. After the distributions, you could only acquire more on exchanges, historically thin venues with low daily volume — meaning a careless market order could move the price against you. The safer routine is the same one that applies to any small-cap coin:
- Buy GBYTE on a reputable exchange that lists it, using a limit order to control your fill.
- Withdraw it to the official Obyte (formerly Byteball) wallet, available for desktop and mobile.
- Back up your seed phrase offline and treat it like cash.
For a broader primer on getting started safely, see our cryptocurrency beginner's guide and the overview of crypto wallet types.
Risks and Pitfalls
- Witness centralization. Consensus leans on a curated witness list. If those nodes collude or go offline, neutrality and liveness suffer — a different risk profile than open mining.
- Liquidity risk. GBYTE trades thinly. Wide spreads and slippage make large orders costly, and delisting risk is real for low-volume assets.
- Network effect gap. DAG peers like IOTA and Nano captured more attention; Byteball/Obyte prioritized engineering over marketing, leaving it comparatively obscure.
- Oracle trust. Conditional contracts are only as honest as the oracle feeding them. A faulty or manipulated feed can settle a contract incorrectly.
- Unproven scale. DAG throughput is promising in theory but has not been battle-tested at Bitcoin- or Ethereum-level load.
COINOTAG Perspective
Byteball matters less as a price bet and more as a working proof that you can build a usable ledger without a blockchain or mining. Its insistence on contracts a non-developer can read is a genuine usability idea that the wider industry is still catching up to. The honest counterweight is adoption: superior architecture did not translate into network effects, and witness-based consensus trades some decentralization for speed and finality. For most readers, GBYTE is best understood as a piece of DAG history alongside IOTA and Nano — instructive to study, but a thin, speculative holding to size accordingly.