Difference between revisions of "Overview"
obytewiki_>Admin (Prepared the page for translation) |
obytewiki_>Admin (Marked this version for translation) |
||
Line 1: | Line 1: | ||
<languages/> | <languages/> | ||
<translate> | <translate> | ||
+ | <!--T:1--> | ||
'''Byteball''', listed on Coinmarketcap as ''Byteball Bytes'', is a DAG-based cryptocurrency developed by Anton Churyumov. | '''Byteball''', listed on Coinmarketcap as ''Byteball Bytes'', is a DAG-based cryptocurrency developed by Anton Churyumov. | ||
− | ==Features== | + | ==Features== <!--T:2--> |
− | ===Smart/conditional payments=== | + | ===Smart/conditional payments=== <!--T:3--> |
+ | <!--T:4--> | ||
[[File:Send-zingos.jpg|thumb|upright=0.66]] The killer feature is the Smart/Conditional Payment. You set a condition for how the payee receives the money. If the condition is not met, you get your money back. This substitutes for trust between strangers because neither is able to scam the other. | [[File:Send-zingos.jpg|thumb|upright=0.66]] The killer feature is the Smart/Conditional Payment. You set a condition for how the payee receives the money. If the condition is not met, you get your money back. This substitutes for trust between strangers because neither is able to scam the other. | ||
+ | <!--T:5--> | ||
This [[Special:MyLanguage/Smart_contract|smart-contract]] feature has many real-world peer-to-peer applications, including: | This [[Special:MyLanguage/Smart_contract|smart-contract]] feature has many real-world peer-to-peer applications, including: | ||
+ | <!--T:6--> | ||
* no-fee crypto exchanges | * no-fee crypto exchanges | ||
* sports betting | * sports betting | ||
Line 18: | Line 22: | ||
− | ===Textcoin=== | + | ===Textcoin=== <!--T:7--> |
+ | <!--T:8--> | ||
One can [[Special:MyLanguage/send|send]] Bytes (Byteball funds) by email or WhatsApp etc, even if the recipient is not in Byteball yet. For email, the sender just writes an email address where he would normally write a Byteball address. When he hits "Send", his email app is opened with pre-filled text for the recipient. The sender can edit the [[Special:MyLanguage/textcoin|textcoin]] text before sending. The recipient receives an email with a link. Example: | One can [[Special:MyLanguage/send|send]] Bytes (Byteball funds) by email or WhatsApp etc, even if the recipient is not in Byteball yet. For email, the sender just writes an email address where he would normally write a Byteball address. When he hits "Send", his email app is opened with pre-filled text for the recipient. The sender can edit the [[Special:MyLanguage/textcoin|textcoin]] text before sending. The recipient receives an email with a link. Example: | ||
+ | <!--T:9--> | ||
<blockquote>Here is your link to receive 0.001 GB: https://byteball.org/openapp.html#textcoin?pact-volume-lazy-midnight-mix-cool-fiction-symbol-tag-fiction-coral-sibling</blockquote> | <blockquote>Here is your link to receive 0.001 GB: https://byteball.org/openapp.html#textcoin?pact-volume-lazy-midnight-mix-cool-fiction-symbol-tag-fiction-coral-sibling</blockquote> | ||
− | ===Identity verification for cryptos=== | + | ===Identity verification for cryptos=== <!--T:10--> |
+ | <!--T:11--> | ||
Starting 18 January, every Byteball user can link his Byteball address to his real world identity. The user’s personal data is verified by Jumio, the leading provider of [[Special:MyLanguage/identity verification|identity verification]] services, and stored in the user’s Byteball [[Special:MyLanguage/wallet|wallet]]. At the same time, a hash of the personal data is stored on the public DAG and signed by a trusted attestor. The attestor also serves as a [[Special:MyLanguage/witness|witness]], so it is already trusted. | Starting 18 January, every Byteball user can link his Byteball address to his real world identity. The user’s personal data is verified by Jumio, the leading provider of [[Special:MyLanguage/identity verification|identity verification]] services, and stored in the user’s Byteball [[Special:MyLanguage/wallet|wallet]]. At the same time, a hash of the personal data is stored on the public DAG and signed by a trusted attestor. The attestor also serves as a [[Special:MyLanguage/witness|witness]], so it is already trusted. | ||
+ | <!--T:12--> | ||
This attestation allows the user to prove to anybody that his Byteball address is linked to a verified person, without disclosing any personal information. It also allows to reveal the private information to individual service providers on demand, and the service provider can easily verify authenticity of this information using the hash stored on the public DAG.<ref>https://medium.com/byteball/bringing-identity-to-crypto-b35964feee8e</ref> | This attestation allows the user to prove to anybody that his Byteball address is linked to a verified person, without disclosing any personal information. It also allows to reveal the private information to individual service providers on demand, and the service provider can easily verify authenticity of this information using the hash stored on the public DAG.<ref>https://medium.com/byteball/bringing-identity-to-crypto-b35964feee8e</ref> | ||
− | ===Blackbytes=== | + | ===Blackbytes=== <!--T:13--> |
+ | <!--T:14--> | ||
Private payments can be made using [[Special:MyLanguage/blackbytes|blackbytes]], a cash-like untraceable currency. Its transactions are not visible on the public database that shows all payments made with (white)bytes. Blackbytes are sent peer-to-peer instead in an encrypted chat session. | Private payments can be made using [[Special:MyLanguage/blackbytes|blackbytes]], a cash-like untraceable currency. Its transactions are not visible on the public database that shows all payments made with (white)bytes. Blackbytes are sent peer-to-peer instead in an encrypted chat session. | ||
− | ===Chatbots=== | + | ===Chatbots=== <!--T:15--> |
+ | <!--T:16--> | ||
[[File:Betting-bot.jpg|thumb|left]][[Special:MyLanguage/Chatbot|Chatbot]]s are fun and facilitate real-world transactions, including shopping with a merchant and paying with two clicks. Current chatbots are: Real name attestation bot, Flight delay insurance, Transition bot, Byte-BTC exchange, Flight delays [[Special:MyLanguage/oracle|oracle]], Sports oracle, BTC oracle, Rosie bot, Byteball Asset Manager, Zork | game, Poll bot, Blackbytes Exchange BEEB (Trustful^), Blackbyte Exchange [freebe] (Semi-trustless^), Buy blackbytes (trustless), Slice&Dice MUD, Betting bot (Semi-trustless), Luckybytes Lottery (provably fair), TitanCoin ICO, Byteball-Altcoin Exchange Bot, [[Special:MyLanguage/Fun-coins|Fun-coins]] faucet, SilentNotary ICO. | [[File:Betting-bot.jpg|thumb|left]][[Special:MyLanguage/Chatbot|Chatbot]]s are fun and facilitate real-world transactions, including shopping with a merchant and paying with two clicks. Current chatbots are: Real name attestation bot, Flight delay insurance, Transition bot, Byte-BTC exchange, Flight delays [[Special:MyLanguage/oracle|oracle]], Sports oracle, BTC oracle, Rosie bot, Byteball Asset Manager, Zork | game, Poll bot, Blackbytes Exchange BEEB (Trustful^), Blackbyte Exchange [freebe] (Semi-trustless^), Buy blackbytes (trustless), Slice&Dice MUD, Betting bot (Semi-trustless), Luckybytes Lottery (provably fair), TitanCoin ICO, Byteball-Altcoin Exchange Bot, [[Special:MyLanguage/Fun-coins|Fun-coins]] faucet, SilentNotary ICO. | ||
+ | <!--T:17--> | ||
^Note that in the cryptosphere, "trustless" is generally preferable to "trustful" -- the reverse of what one might expect. And neither word equates to "trusted" or "untrusted". | ^Note that in the cryptosphere, "trustless" is generally preferable to "trustful" -- the reverse of what one might expect. And neither word equates to "trusted" or "untrusted". | ||
− | ==Platform== | + | ==Platform== <!--T:18--> |
+ | <!--T:19--> | ||
Byteball has its native currencies, Bytes and Blackbytes. It is also a [[Special:MyLanguage/platform|platform]] for new assets (coins/[[Special:MyLanguage/token|token]]s) you can create yourself at minimal cost in five minutes. You can simply send your [[Special:MyLanguage/asset|asset]] to anyone with a Byteball wallet, or you can use your asset in many smart contracts.<ref>https://wiki.byteball.org/asset</ref> | Byteball has its native currencies, Bytes and Blackbytes. It is also a [[Special:MyLanguage/platform|platform]] for new assets (coins/[[Special:MyLanguage/token|token]]s) you can create yourself at minimal cost in five minutes. You can simply send your [[Special:MyLanguage/asset|asset]] to anyone with a Byteball wallet, or you can use your asset in many smart contracts.<ref>https://wiki.byteball.org/asset</ref> | ||
+ | <!--T:20--> | ||
Some examples: | Some examples: | ||
*'''Fun-coins:''' You can get millions of [[Special:MyLanguage/Tingos|Tingos]], [[Special:MyLanguage/Tangos|Tangos]], [[Special:MyLanguage/Zingos|Zingos]] and [[Special:MyLanguage/Zangos|Zangos]] from the free faucet in the Bot Store. The idea is use them to practise with textcoins, smart contracts etc without worrying if you lose them somehow. | *'''Fun-coins:''' You can get millions of [[Special:MyLanguage/Tingos|Tingos]], [[Special:MyLanguage/Tangos|Tangos]], [[Special:MyLanguage/Zingos|Zingos]] and [[Special:MyLanguage/Zangos|Zangos]] from the free faucet in the Bot Store. The idea is use them to practise with textcoins, smart contracts etc without worrying if you lose them somehow. | ||
Line 54: | Line 67: | ||
− | ==Basic info== | + | ==Basic info== <!--T:21--> |
− | ===Native currencies=== | + | ===Native currencies=== <!--T:22--> |
+ | <!--T:23--> | ||
*'''Bytes:''' Total supply = 10^15 bytes. Unit on exchanges is the GBYTE. 1 GB = 1,000 MB = 1,000,000 KB = 1,000,000,000 Bytes. | *'''Bytes:''' Total supply = 10^15 bytes. Unit on exchanges is the GBYTE. 1 GB = 1,000 MB = 1,000,000 KB = 1,000,000,000 Bytes. | ||
*'''Blackbytes:''' Total supply = 2.1111 x 10^15. 1 GBB = 1,000 MBB = 1,000,000 KBB = 1,000,000,000 Blackbytes. | *'''Blackbytes:''' Total supply = 2.1111 x 10^15. 1 GBB = 1,000 MBB = 1,000,000 KBB = 1,000,000,000 Blackbytes. | ||
+ | <!--T:24--> | ||
All Bytes and Blackbytes were created at the genesis unit. So far approx 65% have been issued for use. | All Bytes and Blackbytes were created at the genesis unit. So far approx 65% have been issued for use. | ||
− | ===Date introduced=== | + | ===Date introduced=== <!--T:25--> |
+ | <!--T:26--> | ||
*First announced 5 September 2016.<ref>https://bitcointalk.org/index.php?topic=1608859.msg16156239#msg16156239</ref> | *First announced 5 September 2016.<ref>https://bitcointalk.org/index.php?topic=1608859.msg16156239#msg16156239</ref> | ||
*Platform went live on 25 December 2016. | *Platform went live on 25 December 2016. | ||
− | ===DAG=== | + | ===DAG=== <!--T:27--> |
+ | <!--T:28--> | ||
Byteball data is stored and ordered using a [[Special:MyLanguage/Directed_acyclic_graph|directed acyclic graph]] <ref>https://en.wikipedia.org/wiki/Directed_acyclic_graph</ref> rather than a blockchain. This allows all users to secure each other's data by referencing earlier data units created by other users, and also removes scalability limits common to blockchains such as the blocksize issue. | Byteball data is stored and ordered using a [[Special:MyLanguage/Directed_acyclic_graph|directed acyclic graph]] <ref>https://en.wikipedia.org/wiki/Directed_acyclic_graph</ref> rather than a blockchain. This allows all users to secure each other's data by referencing earlier data units created by other users, and also removes scalability limits common to blockchains such as the blocksize issue. | ||
+ | <!--T:29--> | ||
There are no blocks: there are only transactions. You just add your transaction to the end of the DAG yourself, without waiting for the miners to (hopefully) include it in some future block. | There are no blocks: there are only transactions. You just add your transaction to the end of the DAG yourself, without waiting for the miners to (hopefully) include it in some future block. | ||
+ | <!--T:30--> | ||
The Byteball DAG is about 20 GB in March 2018. | The Byteball DAG is about 20 GB in March 2018. | ||
− | ===FAQs=== | + | ===FAQs=== <!--T:31--> |
+ | <!--T:32--> | ||
There is a wiki [[Special:MyLanguage/FAQ-general|general FAQ]] and [[Special:MyLanguage/FAQ-technical|technical FAQ]]. | There is a wiki [[Special:MyLanguage/FAQ-general|general FAQ]] and [[Special:MyLanguage/FAQ-technical|technical FAQ]]. | ||
− | ==Zurich presentation== | + | ==Zurich presentation== <!--T:33--> |
+ | <!--T:34--> | ||
A presentation given by Tony on 2 February 2018, that gives an excellent overview of Byteball.<ref>https://docs.google.com/presentation/d/1dpbE1l4Aj8Te2_i9wjVsW48igZMhdyjKJVcWY-45qd8/edit#slide=id.p5</ref> | A presentation given by Tony on 2 February 2018, that gives an excellent overview of Byteball.<ref>https://docs.google.com/presentation/d/1dpbE1l4Aj8Te2_i9wjVsW48igZMhdyjKJVcWY-45qd8/edit#slide=id.p5</ref> | ||
− | ==Videos== | + | ==Videos== <!--T:35--> |
+ | <!--T:36--> | ||
<youtube>https://www.youtube.com/watch?v=2ZuYZOitKfQ</youtube> | <youtube>https://www.youtube.com/watch?v=2ZuYZOitKfQ</youtube> | ||
+ | <!--T:37--> | ||
<youtube>https://www.youtube.com/watch?v=zOayZ2_6cN4</youtube> | <youtube>https://www.youtube.com/watch?v=zOayZ2_6cN4</youtube> | ||
+ | <!--T:38--> | ||
<youtube>https://www.youtube.com/watch?v=RT-pA_KHz4U</youtube> | <youtube>https://www.youtube.com/watch?v=RT-pA_KHz4U</youtube> | ||
+ | <!--T:39--> | ||
<youtube>https://www.youtube.com/watch?v=SnXuylxUKqo</youtube> | <youtube>https://www.youtube.com/watch?v=SnXuylxUKqo</youtube> | ||
− | ==External links== | + | ==External links== <!--T:40--> |
+ | <!--T:41--> | ||
* [https://byteball.org Main website] | * [https://byteball.org Main website] | ||
* [https://byteball.org/Byteball.pdf White paper] | * [https://byteball.org/Byteball.pdf White paper] | ||
Line 114: | Line 140: | ||
− | ==References== | + | ==References== <!--T:42--> |
+ | <!--T:43--> | ||
<references /> | <references /> | ||
+ | <!--T:44--> | ||
[[Category:Browse]] | [[Category:Browse]] | ||
[[Category:Features]] | [[Category:Features]] | ||
</translate> | </translate> |
Revision as of 08:52, 16 March 2018
<languages/> <translate> Byteball, listed on Coinmarketcap as Byteball Bytes, is a DAG-based cryptocurrency developed by Anton Churyumov.
Contents
Features
Smart/conditional payments
The killer feature is the Smart/Conditional Payment. You set a condition for how the payee receives the money. If the condition is not met, you get your money back. This substitutes for trust between strangers because neither is able to scam the other.
This smart-contract feature has many real-world peer-to-peer applications, including:
- no-fee crypto exchanges
- sports betting
- selling or buying insurance concerning negative events like a flight delay.
Textcoin
One can send Bytes (Byteball funds) by email or WhatsApp etc, even if the recipient is not in Byteball yet. For email, the sender just writes an email address where he would normally write a Byteball address. When he hits "Send", his email app is opened with pre-filled text for the recipient. The sender can edit the textcoin text before sending. The recipient receives an email with a link. Example:
Here is your link to receive 0.001 GB: https://byteball.org/openapp.html#textcoin?pact-volume-lazy-midnight-mix-cool-fiction-symbol-tag-fiction-coral-sibling
Identity verification for cryptos
Starting 18 January, every Byteball user can link his Byteball address to his real world identity. The user’s personal data is verified by Jumio, the leading provider of identity verification services, and stored in the user’s Byteball wallet. At the same time, a hash of the personal data is stored on the public DAG and signed by a trusted attestor. The attestor also serves as a witness, so it is already trusted.
This attestation allows the user to prove to anybody that his Byteball address is linked to a verified person, without disclosing any personal information. It also allows to reveal the private information to individual service providers on demand, and the service provider can easily verify authenticity of this information using the hash stored on the public DAG.[1]
Blackbytes
Private payments can be made using blackbytes, a cash-like untraceable currency. Its transactions are not visible on the public database that shows all payments made with (white)bytes. Blackbytes are sent peer-to-peer instead in an encrypted chat session.
Chatbots
Chatbots are fun and facilitate real-world transactions, including shopping with a merchant and paying with two clicks. Current chatbots are: Real name attestation bot, Flight delay insurance, Transition bot, Byte-BTC exchange, Flight delays oracle, Sports oracle, BTC oracle, Rosie bot, Byteball Asset Manager, Zork | game, Poll bot, Blackbytes Exchange BEEB (Trustful^), Blackbyte Exchange [freebe] (Semi-trustless^), Buy blackbytes (trustless), Slice&Dice MUD, Betting bot (Semi-trustless), Luckybytes Lottery (provably fair), TitanCoin ICO, Byteball-Altcoin Exchange Bot, Fun-coins faucet, SilentNotary ICO.
^Note that in the cryptosphere, "trustless" is generally preferable to "trustful" -- the reverse of what one might expect. And neither word equates to "trusted" or "untrusted".
Platform
Byteball has its native currencies, Bytes and Blackbytes. It is also a platform for new assets (coins/tokens) you can create yourself at minimal cost in five minutes. You can simply send your asset to anyone with a Byteball wallet, or you can use your asset in many smart contracts.[2]
Some examples:
- Fun-coins: You can get millions of Tingos, Tangos, Zingos and Zangos from the free faucet in the Bot Store. The idea is use them to practise with textcoins, smart contracts etc without worrying if you lose them somehow.
- TitanCoin ICO: Independent ICO, where coins can be bought via the bot paying with GB, BTC, or Ethereum.
- SilentNotary ICO: Independent ICO, where coins can be bought via the bot paying with GB, BTC, or Ethereum.
Basic info
Native currencies
- Bytes: Total supply = 10^15 bytes. Unit on exchanges is the GBYTE. 1 GB = 1,000 MB = 1,000,000 KB = 1,000,000,000 Bytes.
- Blackbytes: Total supply = 2.1111 x 10^15. 1 GBB = 1,000 MBB = 1,000,000 KBB = 1,000,000,000 Blackbytes.
All Bytes and Blackbytes were created at the genesis unit. So far approx 65% have been issued for use.
Date introduced
- First announced 5 September 2016.[3]
- Platform went live on 25 December 2016.
DAG
Byteball data is stored and ordered using a directed acyclic graph [4] rather than a blockchain. This allows all users to secure each other's data by referencing earlier data units created by other users, and also removes scalability limits common to blockchains such as the blocksize issue.
There are no blocks: there are only transactions. You just add your transaction to the end of the DAG yourself, without waiting for the miners to (hopefully) include it in some future block.
The Byteball DAG is about 20 GB in March 2018.
FAQs
There is a wiki general FAQ and technical FAQ.
Zurich presentation
A presentation given by Tony on 2 February 2018, that gives an excellent overview of Byteball.[5]
Videos
External links
- Main website
- White paper
- Transactions explorer
- Medium articles
- Bitcointalk thread
- Byteball Asset Manager (for you to create your own coin on the Byteball platform)
- Byteball Wiki
- Community Subreddit
- Community Slack
References
- ↑ https://medium.com/byteball/bringing-identity-to-crypto-b35964feee8e
- ↑ https://wiki.byteball.org/asset
- ↑ https://bitcointalk.org/index.php?topic=1608859.msg16156239#msg16156239
- ↑ https://en.wikipedia.org/wiki/Directed_acyclic_graph
- ↑ https://docs.google.com/presentation/d/1dpbE1l4Aj8Te2_i9wjVsW48igZMhdyjKJVcWY-45qd8/edit#slide=id.p5
</translate>