What Is Byteball Bytes?

Byteball is a decentralized system that allows tamper proof storage of arbitrary data, including data that represents transferrable value such as currencies, property titles, debt, shares, etc. Storage units are linked to each other such that each storage unit includes one or more hashes of earlier storage units, which serves both to confirm earlier units and establish their partial order. The set of links among units forms a DAG (directed acyclic graph).

There is no single central entity that manages or coordinates admission of new units into the database, everyone is allowed to add a new unit provided that he signs it and pays a fee equal to the size of added data in bytes. The fee is collected by other users who later confirm the newly added unit by including its hash within their own units. As new units are added, each earlier unit receives more and more confirmations by later units that include its hash, directly or indirectly.

There is an internal currency called ‘bytes’ that is used to pay for adding data into the decentralized database. Other currencies (assets) can also be freely issued by anyone to represent property rights, debt, shares, etc. Users can send both bytes and other currencies to each other to pay for goods/services or to exchange one currency for another; the transactions that move the value are added to the database as storage units.

If two transactions try to spend the same output (double-spend) and there is no partial order between them, both are allowed into the database but only the one that comes earlier in the total order is deemed valid. Total order is established by selecting a single chain on the DAG (the main chain) that is attracted to units signed by known users called witnesses. A unit whose hash is included earlier on the main chain is deemed earlier on the total order.

Users choose the witnesses by naming the user-trusted witnesses in every storage unit. Witnesses are reputable users with real-world identities, and users who name them expect them to never try to double-spend. As long as the majority of witnesses behave as expected, all double-spend attempts are detected in time and marked as such. As witnesses-authored units accumulate after a user’s unit, there are deterministic (not probabilistic) criteria when the total order of the user’s unit is considered final.

Users store their funds on addresses that may require more than one signature to spend (multisig). Spending may also require other conditions to be met, including conditions that are evaluated by looking for specific data posted to the database by other users (oracles). Users can issue new assets and define rules that govern their transferability.

The rules can include spending restrictions such as a requirement for each transfer to be cosigned by the issuer of the asset, which is one way for financial institutions to comply with existing regulations. Users can also issue assets whose transfers are not published to the database, and therefore not visible to third parties. Instead, the information about the transfer is exchanged privately between users, and only a hash of the transaction and a spend proof (to prevent double-spends) are published to the database.

In Orwell’s 1984, the protagonist Winston Smith works in the Records Department of the Ministry of Truth as an editor, revising historical records, to make the past conform to the ever-changing party line and deleting references to unpersons – people who have been "vaporised," i.e. not only killed by the state but denied existence even in history or memory [1]. What we present here is data storage that is not rewritable. It is a distributed decentralized database where records can neither be revised nor deleted entirely.

Bitcoin [2] was the first system to introduce tamper proof records designed for the specific purpose of tracking the ownership of electronic currency units known as bitcoins. In Bitcoin, all transfers of the currency are represented as transactions that are digitally signed by the current owner of the coin, transactions are bundled into blocks, and blocks are linked into a chain (blockchain) secured by proof of work (PoW) that assures that large computing resources have been invested into building the chain.

Any attempt to rewrite anything contained in the chain would therefore require even larger computing resources than those that have already been expended. Soon after Bitcoin appeared, it became clear that this was more than just a trust-free P2P electronic currency. Its technology became a source of new ideas for solving other problems. At the same time, Bitcoin’s deficiencies and limitations equally became clear.

Byteball is designed to generalize Bitcoin to become a tamper proof storage of any data, not solely transfers of a single electronic currency, and remove some of the most pressing deficiencies that impede a wider adoption and growth of Bitcoin. Blocks. In Bitcoin, transactions are bundled into blocks, and blocks are linked into a single chain. Since the blocks are linked linearly, their spacing in time and their size are optimized for near-synchrony among nodes, so that the nodes can share a new block with each other much faster than it typically takes to generate a new block.

This ensures that nodes most likely see the same block as the last block, and orphaning is minimized. As Bitcoin grows, blocks become increasingly unwieldy. They are either capped in size, in which case the growth is also capped, or they take too long to propagate to all nodes of the network, in which case there is greater uncertainty about which block is last, and more resources are wasted on extending chains that would later be orphaned.

In Byteball, there are no blocks, transactions are their own blocks, and they need not connect into a single chain. Instead a transaction may be linked to multiple previous transactions, and the whole set of transactions is not a chain but a DAG (directed acyclic graph). DAG-based designs have received much attention recently [3-5]. Cost. Bitcoin transactions are secure because it is prohibitively expensive to redo all the PoW included in the blocks created after the transaction.

But that also means that it is necessary to pay to build the legitimate PoW that is strong enough to ward off any attackers. This payment is spent for the electricity required to build the PoW. What is important to note here, is that this money goes outside the Bitcoin ecosystem – to energy companies – meaning that the community of Bitcoin holders as a whole is bleeding capital. In Byteball, there is no PoW, instead we use 3 another consensus algorithm based on an old idea that was known long before Bitcoin. Finality. Transaction finality in Bitcoin is probabilistic.

There are no strict and simple criteria for when you can say that a transaction will never be reversed. Rather, you can only argue that the probability of a transaction being reversed exponentially decays as more blocks are added. While this concept is perfectly clear to those versed in math, it might be a difficult sell to an average Joe who is used to expecting a black-or-white picture in matters of money ownership. To complicate things even further, transaction finality also depends on its amount. If the amount is small, you can be reasonably sure nobody will try to double-spend against you.

However, if the amount at stake is greater than the block reward (12.5 BTC at the time of writing), you might speculate that the payer could temporarily rent hashpower to mine another chain of blocks that doesn’t contain the transaction that pays to you. Therefore, you have to wait for more confirmations before being sure enough that a high-value transaction is final. In Byteball, there are deterministic criteria for when a transaction is deemed final, no matter how large it was.

Exchange rate. The Bitcoin price is known to be quite volatile. The bigger problem is that this price is not only volatile, it is not bound to anything. Share and commodity prices are also very volatile but there are fundamentals behind them. Share price is largely a function of company earnings, revenue, debt-to-capital ratio, etc. Commodity prices depend, among other factors, on costs of production with various suppliers. For example, if the oil price falls below the production costs of some suppliers for a long time, these suppliers will eventually shut down, decreasing production and causing the price to go up.

There is a negative feedback loop. In Bitcoin, there are no fundamentals, and no negative feedback. A Bitcoin price of $500 is no more justified than a price of $50,000 or $5. If the Bitcoin price moves from where it is now, this movement alone will not create any economic forces that would push the price back. It’s just wild. In Byteball, the base currency, bytes, is used to pay for adding data into the Byteball database. You pay 1,000 bytes to add 1Kb of data.

It is a measure of the utility of the storage in this database, and actual users will have their opinion on what is a reasonable price for this. If the price of byte rises above what you think is reasonable for your needs, you will find ways to store less bytes, therefore you need to buy less bytes, demand decreases, and the price falls. This is negative feedback, common for all goods/services whose demand is driven by need, not speculation. Besides paying in bytes, one can issue other assets and use them as means of payment.

These assets might represent, for example, debt expressed in fiat currencies or in natural units (such as kWh or barrels of oil). The price of such assets is naturally bound to the underlying currencies or commodities. Privacy. All Bitcoin transactions and balances of all addresses are visible on the blockchain. Although there are ways to obfuscate one’s transactions and balances, it is not what people have come to expect from a currency.

Transactions in bytes (the base currency) in Byteball are equally visible, but there is a second currency (blackbytes), which is significantly less traceable. Compliance. Bitcoin was designed as an anonymous currency where people have absolute control over their money. That goal was achieved; however, it made 4 Bitcoin incompatible with existing regulations, and hence inappropriate for use in the financial industry.

In Byteball, one can issue assets with any rules that govern their transferability, from no restrictions at all, like Bitcoin, to anything like requiring every transfer to be cosigned by the issuer (e.g. the bank) or restricted to a limited set of whitelisted users.

Byteball enables trust where trust couldn’t exist before.

When a contract is created on Byteball platform, it can be trusted to work exactly as agreed upon. Why? Because it is validated by multiple nodes on the decentralized network, which all follow the same immutable rules. The counterparty, even if it is a total stranger, has to behave honestly because only the rules have authority. Such a contract is called a smart contract. See below for examples of working smart contracts available today.

Why Use Byteball?

Risk-free conditional smart payments - Byteball allows you to do something that traditional currencies can't: conditional payments. You set a condition when the payee receives the money. If the condition is not met, you get your money back.

byteball bytes

P2P insurance - Hedge against negative events. Buy insurance from peers to get paid in case a negative event occurs. Sell insurance for profit. Insurance is just a simple smart contract that can be unlocked by the insured — if the event in question did occur, or by the insurer — otherwise.

To insure against flight delay, find your counterpart in #p2p_insurance channel on our Slack, create a contract, and if your flight arrives late, chat with flight delays oracle to have it post the data about the delay, then unlock the contract.

byteball bytes

Prediction markets - Make money by correctly predicting future events. Create a P2P smart contract that can be unlocked if a specific event occurs. Use it for betting on price movements, sports betting, and insurance. Find your counterpart in #prediction_markets channel on our Slack.

byteball bytes

P2P betting - Bet against other users on sports events. Find your counterpart in #prediction_markets channel on our Slack and create a contract that can be unlocked by you or your peer depending on the results of a future game. After the result is known, chat with sports oracle to have it post the data about the outcome, then unlock the contract.

byteball bytes

P2P payments in chat - Chat and pay in the same app just by clicking links.

byteball bytes

Chatbots - Talk to a bot like you would talk to a human. Shop by chatting with a merchant's bot, pay in two clicks. Exchanges and other services are also easy to use in conversational interface.

byteball bytes

Bot Store - Easily discover and add new chatbots via the built-in Bot Store. Developers have instant access to all users by publishing their chatbot on the Bot Store. See the developer guide about building chatbots.

byteball bytes

Untraceable currency - Blackbytes Cash-like privacy. When you want complete privacy, pay in Blackbytes, a cash-like untraceable currency whose transactions are not visible on the public database, they are sent peer-to-peer instead. Use built-in TOR switch straight from the wallet to increase your privacy even further.

Users Help Each Other - Secure each other's transactions. There is no central entity that stores and processes all the payments. Instead, transactions created by users are cryptographically linked to each other, and once you add your new transaction, other users start adding theirs on top of yours, and the number of other transactions that link to your transaction grows like snowball (that's why we call it Byteball).

byteball bytes

Core Features

Atomic exchange - When two parties sign a single unit that executes both legs of the exchange, the two transactions either happen simultaneously or don't happen at all. It is no longer necessary to trust any centralized exchanges.

Multi signature - For security, you can require that your funds be spendable only when several signatures are provided, e.g. from your laptop and from your phone. For shared control of funds, signatures from different people may be required.

Immutable storage - Once stored in the Byteball database, the data can neither be revised nor removed.

Regulated assets - Regulated institutions can issue assets that are compatible with KYC/AML requirements. Every transfer of such asset is to be cosigned by the issuer, and if there is anything that contradicts the regulations, the issuer won't cosign.

On-chain oracles - When dealing with untrusted counterparties, you can lock the funds on an address that is spendable either by you or by the counterparty, depending on the events registered to the database by trusted data providers — oracles.

Settlement finality - After certain criteria are met, a new transaction becomes final. It cannot be revised even by a powerful attacker. No guesswork about the right number of confirmations, no 51% attacks.

Getting Started With Byteball Bytes

Byteball has two build-in currencies: bytes and blackbytes. Bytes can be traded at Bittrex, blackbytes are untraceable and can't be traded at an exchange (yet). They can only be exchanged after pairing wallets. The Byteball wallet has a chat in which you can do this.


bytes = base unit

kB = 1 thousand bytes

MB= 1 million bytes (currently worth about $0.50)

GB/GBYTE = 1 billion bytes (currently worth about $500)

blackbytes = base unit

kBB = 1 thousand blackbytes

MBB = 1 million blackbytes

GBB = 1 billion blackbytes (currently worth about 0.02 GBYTE ($10) according to Slack)


Byteball requires 1 byte fee (paid to the Witnesses) per byte of data it stores in the DAG. A GBYTE transaction costs about 600 bytes fee ($0.0003) without special conditions, a GBB transaction can be larger, say up to 10,000 bytes ($0.005), depending on your exact payment. Low enough to neglect, just remember keep a few bytes in your wallet if you want to send blackbytes.

Blackbytes trading

Slack channel #trading_blackbyte has a bot that shows BID and ASK orders, but you need to do manual pairing. Byteball Wiki explains how.

The Design

There are no blocks in Byteball, and no block size issue. Instead, every new transaction references one or more earlier ones (parents) by including and signing their hashes. The links among transactions form a DAG (directed acyclic graph):

byteball bytes

By including its parents, each new transaction also indirectly includes and confirms all parents of the parents, parents of the parents of the parents, and so on. As more transactions are added after your transaction, the number of confirmations you receive grows like snowball, that’s why the name Byteball (our snowflakes are bytes of data).


There is no PoW, no PoS, and no mining. Instead, we have the DAG, which already establishes partial order between transactions, plus we add the main chain within the DAG:

byteball bytes

The main chain (MC) allows to define total order between transactions: the transaction which gets included (directly or indirectly) earlier on the MC, is deemed earlier in the total order. When there is a double-spend, the version of the transaction that comes earlier in the total order is deemed valid, all others are deemed void.

The main chain is defined deterministically based on the positions of transactions in the graph. Refer to the white paper for details, but as a general rule, the MC gravitates towards transactions authored by well known users, which we call witnesses. The list of witnesses is defined by users themselves as they include the list in every transaction they post. The MC then follows the path within the DAG such that:

1. the witness lists of the neighboring transactions on the chain are either identical or differ by only one mutation,

2. the chain goes through the most number of witness-authored transactions, compared with alternative chains.

The above is very brief and sketchy description with many important details omitted, refer to the white paper for a full technical story.

Fees and intrinsic value

The fees paid for storing one’s transactions (or any other data) in the Byteball database are equal to the size of the data being stored. If the size of your transaction data is 500 bytes, you pay exactly 500 bytes (the native currency of Byteball) in fees. This means there is intrinsic value in bytes: it is the utility of permanently storing that size of data in a decentralized immutable database. For data that represents financial transactions, the value is social rather than personal, because you absolutely need to store the full coin history in order to be able to prove the value and authenticity of the coin to each subsequent owner.

The fees are collected partially by those who are first to reference your transaction as parent and partially by witnesses. The former incentivizes referencing the most recent transactions as parents, which results in the DAG growing in one direction only, like the trunk of a tree, and being as narrow as network latency permits. If new transactions are rare enough, such that all nodes have enough time to sync before a new transaction appears, the DAG will look almost like a chain, with only occasional forks and quick merges.

Money supply

The total number of bytes is 1015, all bytes were issued in the genesis transaction. Since the fees paid are returned into the circulation, the money supply will remain the same.

Exchanges list the currency as gigabytes (GB, GBYTE), 1 gigabyte is 1 billion bytes. The total money supply in gigabytes is 1,000,000.

Deterministic finality

In Byteball, there is a protocol rule that a transaction must include the previous transaction (if any) sent from the same address, i.e. there must be partial order between subsequent transactions from the same address. Breaking this rule is considered equivalent to double-spending, therefore at least one of such unordered transactions will become void.

If we assume that most witnesses follow this rule (that’s what they are elected for), they have to reference only sufficiently recent transactions as parents and can’t inherit from old enough parents. Therefore, they can no longer influence the MC (which is attracted to witnesses) in the old enough part of the DAG, and that part of the MC becomes stable, hence the total order relative to this MC also becomes stable.

See the white paper for discussion of exact criteria of reaching stability, here it is important that the criteria are deterministic, and once a transaction appears on the stable part of the MC, it is final, and, unlike all other cryptocurrencies, no re-orgs are possible.

This is extremely important for applications in financial industry and for wider adoption in general, as most people are used to expect certainty in matters of money and property ownership, and the concept of probabilistic finality is a difficult sell.

Assets and on-chain exchange

Bytes is the native currency of Byteball. Users can issue any other tokens (assets), e.g. to represent debt. The debt can be expressed e.g. in fiat currencies or in natural units (barrels, ounces, kWh, etc). The issuers of the debt can reveal their real-world identities and/or be voluntarily attested (i.e. their real-word identities be verified by a well known third party such as CA). This enables the use of the existing legal system to secure against fraud.

The issued assets can be used as means of payment, along with bytes. Assets can be exchanged against bytes and other assets by both parties signing a single unit that executes both legs of the exchange, thus the two transactions either happen simultaneously or don't happen at all. This kind of signing is called multilateral signing. No centralized exchange is needed, hence no trust is necessary and no exchange fees (apart from the usual fees for the size of the data).

Private untraceable payments

Assets can be either public or private. All transactions in public assets are visible to everyone on the public decentralized database, just like Bitcoin. Bytes is a predefined public asset.

Payments in private assets are not published to the public database. Instead, only the hash of the transaction is stored to the database, while the plaintext of the transaction is sent directly from the payer to the payee. To protect against double-spends, a spend proof is also published to the Byteball database. The spend proof is constructed as a hash of the output being spent, so that if the same output is spent twice, the spend proofs will be necessarily the same.

I’ve already described this design at https://bitcointalk.org/index.php?topic=1574508.0, see more details in the white paper.

Regulated assets

Regulated institutions can issue assets that are compatible with KYC/AML requirements. Every transfer of such asset is to be cosigned by the issuer, and if there is anything that contradicts the regulations, the issuer won't cosign.

This way, banks can issue fiat-pegged assets and stay fully compliant. They can open demand deposit accounts and track them on Byteball as assets. These assets are easily exchangeable against bytes and other assets (with bank’s approval).

Other features

- Spending conditions (AKA smart contracts) in an easy to understand declarative language https://bitcointalk.org/index.php?topic=1617816.0

- Multisig: a special case of spending conditions

- On-chain oracles can post data (such as timestamps, exchange rates, weather, various events) directly to the database, then that data can be referenced from spending conditions

- Private end-to-end encrypted messaging: used to convey private payment data, communicate in multisig scenarios, and chat with a merchant’s bot.

Initial distribution

There will be no ICO, no crowdsale. I believe the success of a currency depends on the number of people who own it, in fact Peter R’s research suggests that historical marketcap of Bitcoin follows Metcalfe's law: https://bitcointalk.org/index.php?topic=572106.0, i.e. it is proportional to the square of the number of active users. That’s why I want Byteball to be in the hands of as many people as possible:

98% of all bytes and blackbytes (the private untraceable currency) are to be distributed for free.

1% I reserve for myself

Free distribution

There are two ways to participate in the free distribution:

Make purchases at the merchant stores we partner with and receive 10% cashback on the amount of your purchase, in Bytes. The cashback program has just started, follow our announcements to learn about merchants who join the program. If you are a merchant and want to join, contact us.

Hold bytes and/or BTC and receive additional bytes proportional to your holdings. No investment required, you keep your bitcoins and bytes, plus receive new bytes and blackbytes. See below how to receive the coins.

Current status

The network was launched on December 25, 2016, and 10% of bytes and blackbytes distributed to those who linked their Bitcoin and Byteball addresses. The total balance linked was over 70,000 BTC. In the 2nd to 9th rounds, we distributed another 48.4%, almost 1,400,000 BTC was linked.

Proving your holdings for Byteball distribution

If you missed earlier rounds of distribution, you can still participate in the further rounds.

If you already participated or bought bytes on an exchange or received as cashback from a participating merchant, you can multiply your holdings with 10% monthly interest.

What you receive, is proportional to your balances in BTC and Bytes on the Full Moon of November, on November 4, 2017 at 05:23 UTC:

Putting this another way, to receive 1 GB from the distribution, you need to already hold 160 BTC or 10 GB. These same holdings also give you 2.1111 GBB (giga-blackbyte).

How To Get An Byteball Bytes Wallet?

1. Download and install the wallet by following the above links.

2. Start a chat with the Transition Bot (you find it in the Bot Store in the wallet). Follow the instructions of the Transition Bot to prove your Bitcoin balance.

byteball bytes

You have two options to prove your Bitcoin balance:

a. By making a micropayment. The bot will see your address the payment came from, will know that it is your address, and will instruct you to move your Bitcoins to this address. By making several micropayments, you can link several Bitcoin addresses to the same Byteball address.

b. By signing a message (if your Bitcoin wallet supports this function). You tell the bot your Bitcoin address and sign your Byteball address with the Bitcoin address. After you prove one address (a typical Bitcoin wallet has dozens of them), you can either move all your coins to this single proven address or prove all other addresses in the same way -- by signing a message.

If you try to link the same Bitcoin address to multiple Byteball addresses by sending a micropayment, both links are ignored. If you did this by mistake, link another Bitcoin address or link by signing a message.

If you prove by micropayment, remember to check that the Bitcoin address that the bot received the micropayment from, is indeed your address. An attacker might see your payment on the blockchain and repeat the same micropayment from his address trying to trick you to move your funds to him.

3. If you make any Bitcoin payment, your coins will most likely be moved to a new change address. Chat with the bot again, see the balance on your linked address(es) and move the coins back to the linked address(es) if necessary.

The linking phase will end on November 4, 2017 at 05:23 UTC, after which we'll do the distribution in proportion to BTC and bytes balances on this date.

In the 10th round, we'll distribute as much as is linked and calculated by the above rules, the exact % is not known in advance.

The 11th and subsequent rounds (yet to be announced) will follow similar rules. The rules and speed of distribution will be adjusted to maximize the value of bytes and keep the speed of distribution in sync with the growth of user base and the actual use of the network.

We'll have as many rounds as is necessary until all 98% of bytes are distributed, most likely a new round every full moon.

My 1% doesn't participate in the 2nd and further rounds.

Earlier adopters have the opportunity to participate in greater number of distribution rounds and receive new bytes in each round by using the same BTC balance and bytes received in the previous rounds. You are effectively multiplying your stake in each additional round you take part in.

Track the progress of linking at http://transition.byteball.org.

More information at https://wiki.byteball.org/airdrop



#1 Installing Electrum

Note that for Ubuntu 16.04 an additional dependency appears to be necessary

#2 Making bitcoin addresses visible in Electrum - Tutorial for ALL PLATFORMS

Part 3 Signing - Tutorial for ALL PLATFORMS


Byteball Bytes Resources

How To Buy Byteball Bytes?

Step 1: Buy Bitcoin (BTC)

Exchange your fiat currency for Bitcoin at a top exchange.

I use Coinbase because it is one of the longest running and most reputable places to buy Bitcoin. It also has a well designed and easy-to-use interface.

byteball bytes

After signing up and ID verification, you can buy Bitcoin with major currencies (USD, EUR, GBP, etc.) via online bank transfer or with credit/debit card.

Coinbase is currently available in these countries.

Other good places to buy Bitcoin are:

Step 2: Open an account with an exchange that trades Byteball Bytes

Now that you have some Bitcoin, you need a place to trade it for GBYTE.

Here is a list of online exchanges where GBYTE can be bought and sold:

Exchanges are listed in order of trade volume (descending).

This list is current as of December 2017.

Step 3: Get your Bitcoin address

After opening an account at one of the exchanges above, obtain your BTC wallet address.

The details for obtaining a wallet address vary from exchange to exchange, but it is usually relatively straightforward.

Make sure to get your “deposit” or “receiver” address.

It will be a long string of random characters, looking something like this:


Copy this address for the next step. (Your own unique address of course, not the address above!)

Step 4: Send Bitcoin to your new wallet address

Send Bitcoin from your Coinbase account (or any other account/wallet funded with BTC) to your receiver BTC address from the step above.

Step 5: Trade BTC for GBYTE

After you receive the BTC in your “secondary” exchange account (it usually takes a few minutes) you can trade it for Byteball Bytes within the exchange.

The details for trading currencies vary depending on the exchange.

Generally, you will look for the GBYTE/BTC trading pair and buy or “place an order” to buy GBYTE with your BTC balance.

Your order may fill immediately or after a short while. If there is a delay, it is usually to find sufficient matching “sell” order(s) for your buy order.

Voila! Now you have some Byteball Bytes

Step 6 (Optional): Store your Byteball Bytes in a private

Now that you’ve got some coin, you can just leave it at the exchange where you bought it. Maybe you want to hold your GBYTE or maybe you want to trade it for other coins.

Another option is to move your coins to a wallet.

Here is a list of wallets that hold GBYTE:

In general, there are different types of wallets – hardware, desktop/software, mobile, web or paper. Some have cross-functionality but most are dedicated to single platform. Each type of wallet has different pros and cons but they all provide the benefit of having an additional place to store your digital currency.

Increased security may be advantage of storing your coins in a private wallet, since exchanges have been hacked in the past. It can also be good to have a backup location to store your GBYTE and will give you options for moving your coins in the future.

Where To Spend Byteball Bytes?

You can buy or sell bytes without leaving the wallet by chatting with a trading bot. You can also trade on Bittrex, Cryptox, Cryptopia, Changelly, and Bitsquare exchanges.

To buy or sell blackbytes, see or post orders in #trading_blackbyte channel on our Slack, then exchange peer-to-peer using bound (conditional) payments.

Latest Byteball Bytes News

Byteball version 2.1 released: paper wallets, sending all public assets as #textcoins, and display of dollar amounts.

byteball bytes