Obyte Wiki - User contributions [en]

PolloPollo

2021-01-28T15:44:53Z

Punqtured:

== Overview ==
PolloPollo is an Obyte project run by Casper Niebe to:
*Facilitate charitable donations being used as the donor intended, initially in Venezuela
*Showcase the use of standard Obyte tools to do this

=== Basic principles ===
As part of the effort to go mainstream, Casper was required to provide a somewhat in-depth description of how PolloPollo works to the Danish Financial Supervisory Authority, so he wrote a rather extensive document for them. A translation of this appears as a 23 Feb 2020 Medium article, which goes into all the details about how the PolloPollo platform works, why it is possible for one entity to set up a shared wallet between other entities without having access to funds on it itself. It also outlines the basic features of Obyte that are being used, so hopefully it can also serve as inspiration to others wanting to get starting developing applications on Obyte.<ref>https://medium.com/@casper_43503/basic-principles-of-dlt-based-charity-platform-pollopollo-7ed59f65de3e</ref>

== Website ==
The project website at www.pollopollo.org is online, but not yet fully up to speed.

{{#ev:youtube|https://www.youtube.com/watch?v=z4BTYo3-YDk|200|right}}
*Here is a short 2-minute video in English explaining how the platform works
{{clear}}

=== Grant ===
On 5 June 2019 a grant proposal<ref>https://docs.google.com/document/d/1OSlqa3hZLdzwByE4BYHrYotJVjvF_6Qa5a8kqikoGO8/view#</ref> was submitted to improve the website. The intro:
<blockquote>The real-world PolloPollo project aims to show how a charity platform built on Obyte, by eliminating the need for trust in intermediaries, would allow a donor to see his money being spent as intended. This is not currently possible and would disrupt the entire global charity industry.

A minimum viable product was realized by students from IT University of Copenhagen, Denmark as part of a course. Since launch, the platform has proven to work, and the project is ready to move to the next level.</blockquote>

The grant was approved. The detailed website improvements are listed in four phases. To date (Feb 2020), Phase 1 has been completed, and Phase 2 is ongoing.

== Independent witness ==
On 6 Feb 2020, PolloPollo was announced as the 4th default independent [[witness]] (order provider).<ref>https://medium.com/obyte/pollopollo-approved-to-become-a-default-witness-on-the-obyte-public-network-9ee32238142f</ref>

== The future for PolloPollo ==
During 2020, it is our goal to contribute our knowledge and experience to educational institutions, charitable organizations and also regulatory authorities in Denmark. At the same time, we seek to acquire as much knowledge as possible in a variety of areas to better understand what improvements and additions can be made without risking regulatory conflict. We should avoid things that may be possible but which could bring the platform into legal trouble or undermine the integrity of the entire system.

These are some of the key goals for the platform in the current year:
* Establish our legal position with the Danish Board of Charitable Organizations “ISOBRO”
* Establish our legal position for current functionality with Danish FSA
* Acquire knowledge of the regulations if donations are done using a stablecoin
* Acquire knowledge of the requirements for KYC of donors and producers
* Determine who, how, where and when to store KYC information
* Establish the requirements to enable direct fiat-crypto-fiat donation facilities.<ref>https://medium.com/@casper_43503/basic-principles-of-dlt-based-charity-platform-pollopollo-7ed59f65de3e</ref>

== External links ==
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]
*[https://es.ambcrypto.com/bitcoin-btc-proyecto-humanitario-en-blockchain-lleva-comida-a-venezuela/ AMBCrypto article (in Spanish) Nov 19 2019 about PolloPollo]
*[https://es.cointelegraph.com/news/blockchain-solutions-to-help-venezuelans-were-awarded-at-the-b4h-awards-2019 CoinTelegraph article 20 Dec 2020 in Spanish about B4H award for PolloPollo]
*[https://www.criptonoticias.com/comunidad/beneficencia/travesia-bitcoiner-venezolano-premio-labitconf/ Criptonoticias article (Spanish) 26 Jan 2020 about B4H award for PolloPollo]
*[https://es.cointelegraph.com/news/pollopollos-representative-venezuela-blockchain-demonstrated-allows-implementation-decentralized-donation-without-intermediaries CoinTelegraph article 28 Jan 2020 (in Spanish), interview with Santiago Law about PolloPollo]

== References ==
<references />

[[Category:Browse]]

User talk:Punqtured

2019-01-21T20:43:43Z

Punqtured: Created page with "Let's talk on Slack or Discord instead"

Let's talk on Slack or Discord instead

User:Punqtured

2019-01-21T20:43:18Z

Punqtured: Created page with "User acquisition manager"

User acquisition manager

File:Punqtured.png

2019-01-21T13:55:18Z

Punqtured: File uploaded with MsUpload

File uploaded with MsUpload

MediaWiki:Sidebar

2019-01-21T12:51:45Z

Punqtured:

MediaWiki:Sidebar

2019-01-21T12:51:25Z

Main Page

2019-01-19T22:23:47Z

Punqtured: 66 revisions imported

<languages/>
<translate>

__NOTOC__
[[File:Byteball-logo.png|thumb|250px]]
'''Welcome to the Byteball Wiki. See first a one-page [[Special:MyLanguage/overview|OVERVIEW]], the [[Special:MyLanguage/glossary|GLOSSARY]], and the [[Special:MyLanguage/wallet|WALLET]] page. See [[Special:AllPages|ALL PAGES here]].'''

==Introduction== 


Byteball, listed on CoinMarketCap<ref>https://coinmarketcap.com</ref> as ''Byteball Bytes'', is a DAG-based cryptocurrency developed by Anton (Tony) Churyumov. The main page, the overview, glossary and wallet pages are being translated into many languages. You can see which ones are completed on the [[Special:MyLanguage/All_translations|All translations]] page.


This wiki is aimed at general cryptocurrency users, as well as Byteball users, who want to become better informed about Byteball.


The wiki content is currently generated by invited contributors, and not randomly.

==License== 


All content of this wiki is available under a Creative Commons Attribution-ShareAlike 3.0 Unported [[Special:MyLanguage/License|License]].

== External links == 


*[https://byteball.org Main official site]
*[https://explorer.byteball.org Transactions explorer]
*[https://byteball.org/Byteball.pdf White paper]
*[https://medium.com/@Byteball ''Medium'' articles]
*[https://byteball.market Byteball Asset Manager for you to create a new asset]
*[https://github.com/byteball/byteball Repository]
*[https://byteball.co A Byteball data explorer]

===Forums=== 


*[https://slack.byteball.com [[Special:MyLanguage/Slack|Slack]] channel invitation]
*[https://bitcointalk.org/index.php?topic=1608859.0) Bitcointalk thread]
*[https://bitcointalk.org/index.php?action=profile;u=412662;sa=showPosts;start=0) Tony's posts on bitcointalk]
*[https://reddit.com/r/byteball Subreddit]
*[https://telegram.me/byteball Telegram]
*[https://twitter.com/ByteballOrg Twitter]

==Latest [[Special:MyLanguage/News|News]]== 
</translate>
*Jan 17: Byteball rebranded to Obyte<ref>https://medium.com/byteball/byteball-rebrand-the-next-step-to-real-world-adoption-6a0a924390de</ref>
*Dec 12: Announced third Byteball Use-a-thon, a Bot War<ref>https://steemit.com/byteball/@byteball.org/introducing-the-great-byteball-bot-war</ref>
*Dec 1: Byteball developer resources site launched at https://developer.byteball.org<ref>https://twitter.com/slackjore/status/1069216217691508736</ref>
*Oct 15: Smart Vouchers for Real Name Attestation introduced<ref>https://bitcointalk.org/index.php?topic=1608859.msg46911901#msg46911901</ref>
*Oct 14: Filter added to Explorer<ref>https://twitter.com/slackjore/status/1051452800696238080</ref>
<translate>

== References == 


<references />


[[Category:Browse]]
</translate>

Template:Clear

2019-01-19T22:20:28Z

Punqtured: 4 revisions imported

<div style="clear: {{{1|both}}};"></div><noinclude>
{{Documentation}}</noinclude>

Zingos

2019-01-19T22:20:27Z

Punqtured: 4 revisions imported

[[File:Zingos-1000077.jpg|thumb|upright=0.65]] Zingos are very much like [[Tangos]], except...

==Zingos have two decimal places==
Four dollars can be written as $4 or $4.00, and we can have $4.57 too. Similarly, a hundred Zingos (Z for Zingos here) can be Z100 or Z100.00, and we can have Z100.57 too. How this works in Byteball is:

* Z40,000.00 total in your wallet shows on the home screen as 40,000 Zingos by Johre etc
* Z39,164.81 total in your wallet shows on the home screen as 39,164.81 Zingos by Johre etc
* Z100 entered in the Send screen sends Z100.00, which shows in Explorer as "10,000"
* Z100.00 entered in the Send screen sends Z100.00, which shows in Explorer as "10,000".

Be careful not to send 100x the amount you wish to. With Zingos, having zero monetary value, it doesn't matter too much. But you are practising here for when you will be working with an asset of value having two decimal places.

==Read the Tangos article!==
All the general dos and don'ts in the [[Tangos]] article apply equally to Zingos, so make sure you understand what is written there.

==Differences between Zingos and Zangos==
* There are 10^15 Zingos and 9 x 10^15 [[Zangos]]
* Ummm...

==Definition==
Source<ref>https://explorer.byteball.org/#FPboi/y+Vo008aCHgPsEpSDQe1dogkKH0e1Z/iCcH84=</ref> 
cap: 1000000000000000 
is_private: false 
is_transferrable: true 
auto_destroy: true 
fixed_denominations: false 
issued_by_definer_only: true 
cosigned_by_definer: false 
spender_attested: false

==Registry publication==
Source<ref>https://explorer.byteball.org/#iOsJ4a+OWyvcFbk6NdLWnl/v+QxIk5VaxqwA9Hl7pfk=</ref> 
asset: FPboi/y+Vo008aCHgPsEpSDQe1dogkKH0e1Z/iCcH84= 
decimals: 2 
name: Zingos by Jore Bohne 
shortName: Zingos 
issuer: Jore Bohne 
ticker: ZINGO 
description: A token of no monetary value to practise with, to be spread around, not worth hoarding because there are so many of them.

==External links==
*[https://byteball.market Byteball Asset Manager, where you can create your own token in 5 minutes]

==References==
<references />

[[Category:Fun-coins]]
[[Category:Tokens]]

Witness

2019-01-19T22:20:27Z

Punqtured: 15 revisions imported

==What is a witness?==
A witness is a highly reputable user with a real-world identity, who acknowledges each transaction seen. There are 12 witnesses involved in every transaction. In exchange for the work involved, a witness collects part of the transaction fee (the payload fee). This list varies very little from transaction to transaction. There cannot be more than one change in the witnesses list. The witnesses majority (6+1) show the path to the main chain. Some witnesses may even be down for a period of time without affecting the network. The security of the network would only be threatened if 7 witnesses colluded together, which is almost unthinkable.<ref>https://byteball.org/Byteball.pdf</ref>

==How to replace a witness==
Wallet menu > Settings > Witnesses > then either

*Turn on "Auto-update the witness list from the hub"; or
*Turn it off. Click the witness (just one) you want to change, then paste in the new ID and click Save. Note that if your hub suggests a different witness list, it will notice the difference and prompt you to change it back.

==Non-default witnesses==
===Why change?===
The platform was set up with 12 witnesses all being the founder, Anton Churyumov (Tony). He is, of course, "a highly reputable user with a real-world identity", and totally trustworthy. Byteball is his baby, after all. But this couldn't get more centralized, unwelcome in a going-to-become decentralized system. So we need to diversify, to start trusting others willing to stand up publicly and put their reputation on the line.

===@portabella, the first independent witness===
No real-world identity posted. Known in the Byteball community as a veteran Byteball developer and contributor, who started and maintains this very wiki. Has also operated the first independent Byteball hubs (see [[hub]] list) since January 2017.

<blockquote>
Based in Stockholm, Sweden, a software developer by day, Byteballer by night. Replace the default witness JED... with '''7ULGTPFB72TOYA67YNGMX2Y445FSTL7O'''. You can do so in the Global settings menu - Witnesses, or by changing hub to byteroll.com/bb and accepting the witness-list it suggests, which is the above JED... to 7ULGT... change. Operational security is of highest importance, as such it will never run in a cloud or somebody else server, it is currently in a physically secure location with auto-destruct if tampered with. There are no backups for high-availability, as any restart requires the manual entering of passphrase. The passphrase and keys have been generated and not ever copied anywhere else.</blockquote>

Contact info: @portabella at our Slack.

==@seb486, the cashback witness==
No real-world identity posted. Known in the Byteball community as seb486 on Slack and Bytefan on BitcoinTalk. With a partner operates 4 hubs globally (see [[hub]] list). Main website is https://byteball.fr.

In his own words:

<blockquote>We are based in France and operate the first Byteball redistributive witness, also know as "the cashback witness". Each time you post a unit to the byteball network you pay a Payload fee which is proportional to the weight (in bytes) of your unit. The 12 witnesses your unit is authored on receive each 1/12th of the Payload fee. Use the Cashback Witness as one of your witnesses and '''50% of the payload income it earned from you is given back to you'''. The process is fully automated and 100% anonymous, no registration is needed.

'''You earn back bytes for free.''' It is as simple as that!<ref>https://byteball-cashback-witness.com</ref>
</blockquote>

Contact info: #cashback_witness channel at our Slack

==Witness monitoring service==
This is a useful page<ref>https://byteball.fr/stats.html</ref> created and maintained by @seb486

==Witness list==
{| class="wikitable"
|-
! Witness ID !! Owner !! Slack ID !! Started
|-
| BVVJ2K7ENPZZ3VYZFWQWK7ISPCATFIW3 || Anton Churyumov || @tonych || 2016-12-25
|-
| DJMMI5JYA5BWQYSXDPRZJVLW3UGL3GJS || Anton Churyumov || @tonych || 2016-12-25
|-
| FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH || Anton Churyumov || @tonych || 2016-12-25
|-
| GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN || Anton Churyumov || @tonych || 2016-12-25
|-
| H5EZTQE7ABFH27AUDTQFMZIALANK6RBG || Anton Churyumov || @tonych || 2016-12-25
|-
| I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT || Anton Churyumov || @tonych || 2016-12-25
|-
| JEDZYC2HMGDBIDQKG3XSTXUSHMCBK725 || Anton Churyumov || @tonych || 2016-12-25
|-
| JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC || Anton Churyumov || @tonych || 2016-12-25
|-
| OYW2XTDKSNKGSEZ27LMGNOPJSYIXHBHC || Anton Churyumov || @tonych || 2016-12-25
|-
| S7N5FE42F6ONPNDQLCF64E2MGFYKQR2I || Anton Churyumov || @tonych || 2016-12-25
|-
| TKT4UESIKTTRALRRLWS4SENSTJX6ODCW || Anton Churyumov || @tonych || 2016-12-25
|-
| UENJPVZ7HVHM6QGVGT6MWOJGGRTUTJXQ || Anton Churyumov || @tonych || 2016-12-25
|-
| MEJGDND55XNON7UU3ZKERJIZMMXJTVCV || anon || @seb486 || 2017-05-25
|-
| 4GDZSXHEFVFMHCUCSHZVXBVF5T2LJHMU || Rogier Eijkelhof || @Rogier || 2018-10-23
|}

<hr />

==FAQ about witnesses, double spending, finality==

===Witnesses and consensus===

Q: Those witnesses that wallet has chosen that will try to determine the validity of the transaction/message? 
A: Actually, No. Witnesses are not sole validators. All full nodes perform validation, witnesses are a small subset of full nodes. They are not special in regards to validation.
Witnesses play other role. Remember we are on a DAG, there is no strict order between units. All full nodes look at witnesses in the recent history to establish the path of the Main Chain. The Main Chain is chosen such that it goes through as many witness-authored units as possible. Total order is then determined relative to the Main Chain, and total order resolves conflicts caused by double-spends -- the earlier version wins. That's the role of the witnesses -- to draw the Main Chain through them.

Q: Are witnesses required to validate all transactions? 
A: Witnesses are required to be full nodes, hence validate all transactions

Q: So in effect, a witness has the same role as any other full node, except when attempts of double spends without partial order occur? 
A: Yes but even in this case witnesses don't decide anything, rather their positions on the DAG are used by all nodes to resolve double-spends. (Actually the position of the units that are authored by the witnesses)

Q: Does a full node need to receive and validate all transactions? 
A: Yes, that's the definition of a full node

Q: To illustrate how little a witness has to decide: 
A: A witness doesn't even has to know that it is a witness. For example, you can set bittrex address QR542JXX7VJ5UJOZDKHTJCXAYWOATID2 as one of your witnesses, you don't need to ask bittrex for permission, and bittrex doesn't need to know it and do anything else in addition to what it already is doing.

Q: The witnesses together they decide which branch of the transaction tree is the real one? 
A: More accurate wording: they don't decide but enable others to decide, by looking at witnesses as markers of reality

Q: A witness’ task is to "stamp" [i.e., “comment upon"] every legitimate transaction it sees by issuing a transaction "on top of it", that means by choosing the witnessed transaction (unit) as a parent for the fresh transaction (unit) of the witness? 
A: Correct.

Q: Are the “witnessing” units specialised by any means? 
A: There are no specialised witnessing units. Any witness-authored unit counts as “witnessing” unit

Q: If the witness was already about to issue a unit -- maybe the witness wants to send some Byteball bytes to someone for example -- that unit does double duty? First: with that unit the witness sends the bytes to the intended recipient, second: that unit counts as witnessing unit? 
A: Correct

Q: The protocol requires that transactors have an overlap of 11 (out of 12) witnesses, correct? 
A: The requirement applies to neighbors and all units on the on the chain built by following best parent links starting from the current unit until the stability point

Q: 6 witnesses can determine the chain state entirely, with no need to internal considerations (contrarily to most other blockchains that use biggest block height, with some weighting). Correct? 
A: No, witnesses do not determine the chain state

Q: is there an option of organic replacement of one or more witnesses? 
A: Edit the list in the wallet settings

Q: Is it possible that 24 active witnesses exist in the DAG and some users have completely different witness lists than the other? If not, why not? 
A: If we define users as those who post transactions to the DAG, No.

Q: Is it possible to choose 12 completely new witnesses for my wallet? What would happen? 
A: Possible but you won’t be able to post any transactions until all active users migrate to roughly the same list

Q: What does “predominant witnesses” mean? 
A: Those that you see on the most recently posted units (they can be slightly different)

Q: According to the White Paper, “general consensus is required for a change bigger than one position”. What does this general consensus mean? It means the consensus of the current 12 predominant witnesses? 
A: Yes, the majority of the current predominant witnesses

Q: If an individual, company or government seizes a witness (or all), would they be able to censor transactions? 
A: If "a" witness, no, they will only censor out themselves. If all witnesses, yes.

Q: What happens if all witnesses are shut down? 
A: There will be no confirmations. The MC will still be there but the “stability point” will stop advancing.

Q: Is it possible that for the majority of witnesses they stop posting because they funds became pending (waiting for confirmation in the DAG)? And hence we lose the majority of witnesses? 
A: Theoretically possible if the majority of witnesses are negligent enough to allow this. Not a concern after we activate the update that allows spending unconfirmed funds.

===Double spending===
Q: Are full (or light) nodes capable of identifying and solving double spend attempts without the use of witnesses? 
A: No, they need the witness-authorized units’ positions on the DAG to build the MC, and they use the MC to resolve doublespends

Q: If a user violates the rule that requires all his txns to have partial order, what's to stop him? For example, if I introduced a pair of conflicting double spending txns, would one be accepted eventually? or would both be discarded? 
A: One of the two conflicting transactions will be censored: the one that is later on the “Main Chain”. Not just censored by witnesses, but censored by every full node who follows the protocol.

Q: What about if the attacker shuffles the order of the two conflicting txns, and sends to two different sets of users? Wouldn't one group censors one, then the other censors the other? how would this be mediated? 
A: This is a basic requirement for every working consensus algo that it should be protected from partitioning. The answer is that both sets of users must accept both txs. The order of transactions (hence voiding of the tx that appears to be later) is decided only after they become “final”, i.e. when reordering of these transactions becomes impossible.

===Finality in Byteball===
Q: What is “finality” in Byteball? 
A: Finality means that the transactions cannot be reordered and all nodes agree about the order of transactions before the “stability point” (“before the stability point” = “between the Genesis unit and stablitiy point unit in the DAG”)

Q:.What is “stability point” in Byteball? 
A: A stability point is the position of a specific unit in the DAG. Between the Genesis unit and the stability point all nodes have a consistent view of the ledger. If a node does not received all the fresh units yet, then that node still has an “older” version of the stability point, that is closer to the Genesis unit.

Q: Is it possible that the "Stability point" is moving backwards, I mean towards the Genesis unit? (By any means, may it be a misbehaving witness, or some other attack). 
A: No, it is not allowed.

Q: So based on this, is it correct to say that if misbehaving witnesses are colluding to build a shadow chain and suddenly connecting the shadow chain to the main chain and trying to "hijack" the main chain "behind" the stability point (that is between the genesis unit and the stability point), they will fail?
A: if the colluding witnesses are a majority, the network will get into undefined state once they publish the shadow chain

Q: If there is a new full node, he does calculate the current stability point by himself, or he is receiving it from some other nodes? 
A: Every full node replays the entire history and recalculates the stability point itself

==Additional comments==
[Slack 11:00 PM 2017-06-22] 

<blockquote>'''markcross:''' And it's those witnesses that wallet has chosen that will try to determine the validity of the transaction/message?</blockquote>

<blockquote>'''tonych:''' To make sure there is no misunderstanding, actually, No. Witnesses are not sole validators. All full nodes perform validation, witnesses are a small subset of full nodes. They are not special in regards to validation.

Witnesses play other role. Remember we are on a DAG, there is no strict order between units. All full nodes look at witnesses in the recent history to establish the path of the Main Chain. The Main Chain is chosen such that it goes through as many witness-authored units as possible. Total order is then determined relative to the Main Chain, and total order resolves conflicts caused by double-spends -- the earlier version wins. That's the role of the witnesses -- to draw the Main Chain through them.
</blockquote>

[Bitcointalk 2017-02-06]

<blockquote>'''Tonych:''' When changing your witness list you remove one old witness and replace it with a new one. If the removed witness is the same on all nodes (which is more likely in practice, e.g. if negative information about a witness is released), all nodes stay compatible: only one mutation relative to the old list and relative to each other. The nodes can perform more changes as long as their new lists stay compatible.<ref>https://bitcointalk.org/index.php?topic=1608859.msg17755806#msg17755806</ref></blockquote>

===Decentralizing witnesses===
[Bitcointalk 2018-03-21]
<blockquote>'''Tonych:''' Looking for reputable well known people/orgs/businesses who satisfy all the criteria https://github.com/byteball/byteball-witness. Any help with approaching them is appreciated.<ref>https://bitcointalk.org/index.php?topic=1608859.msg32823145#msg32823145</ref></blockquote>

===Witness functions===
[Slack 2018-05-14]

<blockquote>'''tonych:'''
> · Are witnesses required to validate all transactions? 
witnesses are required to be full nodes, hence validate all transactions 
> · What happens if all witnesses are shut down? 
there will be no confirmations. The MC [main chain] will still be there but the stability point will stop advancing 
> · If an individual, company or government seizes a witness (or all), would they be able to censor transactions? 
If "a" witness, no, they will only censor out themselves. If all witnesses, yes. 
> So in effect, a witness has the same role as any other full node, except when attempts of double spends without partial order occur? 
Yes but even in this case witnesses don't decide anything, rather their positions on the DAG are used by all nodes to resolve double-spends 
> Every full node validates all transactions? 
Yes, that's the definition of a full node
> · Are full (or light) nodes capable of identifying and solving double-spend attempts without the use of witnesses? 
No, they need witness positions on the DAG to build the MC, and they use the MC to resolve doublespends</blockquote>

<blockquote>'''Tsonko Mirchev:''' Is that mean that full node doesn't need MC to resolve doublespends?</blockquote>

<blockquote>'''tonych:''' no, it needs the MC</blockquote>

<blockquote>'''tonych:''' another thing to illustrate how little a witness has to decide:
A witness doesn't even has to know that it is a witness. For example, you can set bittrex address QR542JXX7VJ5UJOZDKHTJCXAYWOATID2 as one of your witnesses, you don't need to ask bittrex for permission, and bittrex doesn't need to know it and do anything else in addition to what it already is doing.</blockquote>

<blockquote>'''slackjore:''' My reaction is "What?!!!". I've been trying to understand witnesses for 10 months, but get lost in the "Main Chain" statements. I'm not much of a techie, so I try to keep things simple. I thought that a witness "stamped" every legitimate transaction it sees by issuing a transaction "on top of it", parent/child relationship of some kind. Looking at Explorer, this is what I see: most of the units are witness units. Now, with regard to Bittrex (for example), it's obvious that one can send any Byteball token to any Byteball address. But surely one can't send into the DAG a transaction *from* any address, as that would imply one has the private key. So, someone please explain in simple terms what I don't get.</blockquote>

<blockquote>'''slackjore:''' I'll itemise my assumptions, one or more of which must be wrong. Repeating a higher-level general explanation doesn't help me. (1) a witness "stamps" [i.e., comments upon"] every legitimate transaction it sees by issuing a transaction "on top of it", parent/child relationship of some kind. (2) these "stamps" are units injected into the DAG, visible on Explorer (3) the source of these must be a full wallet with additional software, running on some hardware controlled by someone (4) this someone has also been called a "witness", as in "how to become a witness" or "a witness must be reputable" etc. (5) the name "witness" also refers to the Byteball address the witness (person, company) is using as a unique identifier -- although one entity can also obviously control more than one. (6) One can't send into the DAG a unit *from* any address, as that would imply one has the private key.

Which of these is wrong?</blockquote>

<blockquote>'''tonych:''' no, witnesses do not "stamp", stamping would make them gatekeepers</blockquote>

<blockquote>'''tonych:''' the functions are just to 1) be honest, and 2) be there

> because together they decide which branch of the transaction tree is the real one
more accurate wording: they don't decide but enable others to decide, by looking at witnesses as markers of reality
> Hm, I added Bittrex as a witness and the explorer considers the tx stable, but my wallet doesn't

if your wallet is light, it sees stability later</blockquote>

<blockquote>'''slackjore:''' OK. I was using the word "stamp" wrongly, to mean basically "comment upon". How about my other assumptions?</blockquote>

<blockquote>'''tonych:'''(2) correct 
(3) correct, the "additional software" is anything responsible for frequent posting of transactions 
(4) correct 
(5) correct 
(6) of course</blockquote>

<blockquote>'''slackjore:''' Thank you. So how can Bittrex act as an unknowing witness, if a witness has to author units?</blockquote>

<blockquote>'''tonych:''' they do withdrawals and other txs from this address</blockquote>

<blockquote>'''slackjore:'''yes, but you said: https://byteball.slack.com/archives/C9GDDLW0N/p1526293317000487
tonych
another thing to illustrate how little a witness has to decide:
A witness doesn't even has to know that it is a witness. For example, you can set bittrex address QR542JXX7VJ5UJOZDKHTJCXAYWOATID2 as one of your witnesses, you don't need to ask bittrex for permission, and bittrex doesn't need to know it and do anything else in addition to what it already is doing.
Posted in #marketing_discussionToday at 11:21 AM</blockquote>

<blockquote>'''tonych:''' yes, any contradiction?</blockquote>

<blockquote>'''slackjore:''' A witness (entity) authors specialised witnessing units into the DAG that have nothing to do with its own regular non-witnessing transactions. Only the designated witnesses do this. How can Bittrex do this if it knows nothing about the duties of a witness (entity)?</blockquote>

<blockquote>'''tonych:''' there are no specialised witnessing units, any witness-authored unit counts</blockquote>

<blockquote>'''slackjore:''' I mean a unit like this: https://explorer.byteball.org/#OaMFZKr+2zQp4Ce0Oxz0tpTaB4Jb2jLDYcrLACxt+jA=
arbitrary, first one I saw</blockquote>

<blockquote>'''tonych:''' nothing special in it</blockquote>

<blockquote>'''slackjore:''' Let's say I send someone 50,000 Tangos. I'll call this a substantive transaction, not because 50,000 is big compared to 5, but because it has, er, substance. This DAG entry floats around the globe and gets seen by all full wallets. Almost all of them passively do nothing more than validate it and add it to their databases. The 12-14 functioning witnesses, however, author units related to it: if the witness was already about to issue a unit -- maybe the timestamp oracle, for example -- that unit does double duty. If the witness does not have its own substantive unit to issue, it simply issues a non-substantive unit, what I called a "witnessing unit" to say it has seen the valid Tangos unit, plus details of it.

Is that correct?</blockquote>

<blockquote>'''tonych:''' correct. Note however that issuing non-substantative units is not required, it is just one of the ways for a witness to show its presence. And there might be other new units that would trigger a non-substantative unit.</blockquote>

<blockquote>'''slackjore:''' ok, great, now I understand how Bittrex could be an unknowing witness. Thank you very much indeed.</blockquote>

-----

Hi @tonych please help to answer some questions. I would like to understand the WP :slightly_smiling_face: 1: WP Chapter 6. Witnesses: “travel along the MC back in time and count the witness-authored units. [...] We would stop traveling as soon as we had encountered the majority of witnesses.” - Here you consider any witness? Or only the witnesses of the candidate parent? Or only the witnesses currently defined in the user’s wallet? How the majority is calculated?
2: WP Chapter 6. Witnesses: “We would then measure the length of the longest path on the graph from the point at which we stopped to the genesis. We’ll call this length the level of the unit where we stopped, and the witnessed level of the parent whose MC we are testing.” - Why don’t you use the notion MCI that was already used before in the WP? Is there any difference between “level of unit” and “MCI”?
3: WP Chapter 7. Finality: “Let’s travel back in time along the current MC from the tip until we meet the majority of witnesses” - Here by “meeting a witness” you mean that we find a witness-authored unit on the current MC? And, “majority of witnesses” you mean 7 out of 12 witnesses defined by the current stability point, correct?
4: WP Chapter 7. Finality: “If at least one of them lies earlier than the current stability point” - Here earlier means “between the the genesis unit and the current stability point?

tonych [12:18 PM]
1. the witnesses of the newly added unit
2. level and witnessed level are different from MCI. In particular, they are constant for each unit, they are just a function of its position in the DAG, while MCI is recalculated every time a new unit is added and can change while the unit is unstable.
3. correct
4. correct

tony:
1.
> Is it correct to state that the “current MC” is determined by the witnesses of the unit in the current stability point?
No, no witness list matters at all at this step. You just define the best parent using witnessed level and level
2. Not at all. More accurate: replace "among these witnesses" with "among these units" (authored by witnesses). We just look at these units and find the minimum witnessed level

===Experiment===
<blockquote>slackjore [2018-05-26 1:16 PM]:
I just sent 35 million Tingos (not to Bittrex!) using Bittrex as a witness [replacing the JED... witness with QR542JXX7VJ5UJOZDKHTJCXAYWOATID2]. Let's see what happens: https://explorer.byteball.org/#tD2ZQSFizOacYpVBeeVNQgvInOktM1yGHEgOQxb0knI= (edited)

6 minutes later the tx is confirmed on Explorer, not confirmed yet in my light wallet. Tony said it takes longer in a light wallet.
now it's confirmed in my wallet, 11 minutes after the tx

Bittrex is still set as a witness, as I had turned off the update-witnesses-from-hub switch</blockquote>

==How to become a witness==
To become a winess, you are expected to:

*have a publicly known real name, no anonymity
*be well known in the community
*be trusted
*have a lot to lose (material and/or nonmaterial) in case of misbehavior. The loss is your business (outside Byteball) and/or reputation
*have enough technical expertise to ensure uninterrupted operation 24/7 and security of your private keys (they must not be stolen and used to post on your behalf)
*be prepared to adapt your own witness list when you feel the community wants to change the list in some way and the new candidate satisfies the above rules. This includes removing your witness from the witness list.

If you think that you satisfy these criteria, this is your course of action: <snip><ref>https://github.com/byteball/byteball-witness</ref>

==External links==
*[https://www.youtube.com/watch?v=N1aWPAm0SdY&feature=youtu.be Video: Byteball Witnesses - the basics explained]

==References==
<references />
[[Category:Features]]

Zangos

2019-01-19T22:20:27Z

Punqtured: 4 revisions imported

[[File:Zangos-9000099.jpg|thumb|upright=0.66]]

==Zangos have two decimal places==
Four dollars can be written as $4 or $4.00, and we can have $4.57 too. Similarly, a hundred Zangos (Z for Zangos here) can be Z100 or Z100.00, and we can have Z100.57 too. How this works in Byteball is:

* Z40,000.00 total in your wallet shows on the home screen as 40,000 Zangos by Johre etc
* Z39,164.81 total in your wallet shows on the home screen as 39,164.81 Zangos by Johre etc
* Z100 entered in the Send screen sends Z100.00, which shows in Explorer as "10,000"
* Z100.00 entered in the Send screen sends Z100.00, which shows in Explorer as "10,000".

Be careful not to send 100x the amount you wish to. With Zangos, having zero monetary value, it doesn't matter too much. But you are practising here for when you will be working with an asset of value having two decimal places.

==Read the Tangos article!==
All the general dos and don'ts in the [[Tangos]] article apply equally to Zangos, so make sure you understand what is written there.

==Differences between Zingos and Zangos==
* There are 10^15 Zingos and 9 x 10^15 Zangos
* Ummm...

==Definition==
Source<ref>https://explorer.byteball.org/#3qacTCGOkrzYRyekq8yRIT/Pc30Pb/BcmTEHDY/aTz0=</ref> 
cap: 9000000000000000 
is_private: false 
is_transferrable: true 
auto_destroy: true 
fixed_denominations: false 
issued_by_definer_only: true 
cosigned_by_definer: false 
spender_attested: false

==Registry publication==
Source<ref>https://explorer.byteball.org/#9OPMHyhSR+ddntJlGlSSFHj9etFj4vEB7FE/7DJxR4s=</ref> 
asset: 3qacTCGOkrzYRyekq8yRIT/Pc30Pb/BcmTEHDY/aTz0= 
decimals: 2 
name: Zangos by Jore Bohne 
shortName: Zangos 
issuer: Jore Bohne 
ticker: ZANGO 
description: Like Zingos, they have zero monetary value and are for zero-risk practice with textcoin, smart contracts, and other Byteball features.

==External links==
*[https://byteball.market Byteball Asset Manager, where you can create your own token in 5 minutes]

==References==
<references />

[[Category:Fun-coins]]
[[Category:Tokens]]

Wallet

2019-01-19T22:20:26Z

Punqtured: 20 revisions imported

<languages/>
<translate>
'''Terminology:''' What you download and install on a device (smartphone, laptop, pc etc) is here referred to as the Byteball software platform, or more commonly "platform". The platform comes with a default wallet, and you can create more wallets on this platform on a device.


[[File:wallet-dad.jpg|thumb|upright=0.67]] The main/hamburger menu (top left) is for the whole platform. Each cogwheel menu (halfway up on the right) works on the displayed wallet only.

==Byteball platform== 


To start, download and install a platform from those listed at byteball.org or Github: releases<ref>https://github.com/byteball/byteball/releases</ref> (includes win32, but not for XP).


The installation now comes with a default single-address wallet, called "Small Expenses Wallet". You can create additional main wallets. A main wallet can also have sub-wallets (smart wallets) inside it, created by conditional-payment [[Special:MyLanguage/smart contract|smart contract]]s.

===Multiple devices=== 


If you want a connected Byteball wallet on your pc and another one on your Android smartphone, choose the multi-device option [[Special:MyLanguage/wallet#add_wallet|as shown below]]. Don't try to build a second platform from the seed of the first: it will probably not function as expected, especially regarding blackbytes.

====Convenience vs security==== 


A 1of3 set-up is very convenient, and if one device fails (it happens) it's not a problem when you forgot to back it up. However, it is easier for a thief to get hold of your coins. Encrypting the platforms makes them more secure.


A 3of3 set-up is dangerous, because if one device fails -- and the back-up fails too -- you have lost your coins. So try to strike a balance between convenience and security. Different people have different circumstances. Someone living in a college dormitory has a different situation to someone working from their secure home.

===Independent or connected?=== 


'''Independent:''' Useful for experimenting, seeing what happens when you interact with another Byteball user in chat. Use (plain) default Small Expenses Wallet on each device.


'''Connected:''' Useful for security. Will show the same balance and history across all devices.

===Pairing=== 


Alice has Byteball on two devices, a smartphone and a laptop. Her smartphone platform has two wallets, a Small Expenses 1of1 wallet, and a Savings 1of2 wallet. She has [[glossary|pair]]ed the smartphone with her laptop, which only has one wallet, the shared Savings 1of2 wallet.

Alice emails an address in her 1of2 wallet to Bob. Bob sends some Bytes to it. The transaction appears automatically in both her 1of2 wallets, on the smartphone and on her laptop.

Later, Alice pairs her smartphone with Bob's device, a desktop. She does not pair her laptop with his device. They chat. The chat shows in her smartphone only. It does not show in her laptop because the pairing is between devices only, Alice's smartphone and Bob's desktop.

===Light/easy or full/hard platform?=== 


Always select the light option unless you REALLY need the full version. If you have funds sent to an address on a full platform you will be unable to spend them until it finishes synchronizing, and this can take a very long time. The bottleneck seems to be the read/write speed to the hard drive, with an SSD being preferred by far.<ref>https://bitcointalk.org/index.php?topic=1608859.msg19676106#msg19676106</ref>

===Single-address wallet=== 


A single-address wallet (platform version 1.11.0 on) you create will not generate the usual new [[Special:MyLanguage/change address|change address]]. Change will always go to the one-and-only address the wallet contains.


You can use a single-address wallet to run a manual oracle right from your platform, without having to run a node on a server. This allows you to run a [[Special:MyLanguage/Trading prediction markets|prediction market]] for a future event, enable users to make contracts (bets) referencing your address as an [[Special:MyLanguage/Oracle#Personal_oracles|oracle]], and when the outcome of the event is known you post its result from your wallet.


In this version you can also manually attest other users and post arbitrary data into the Byteball DAG.

====Attestation==== 


To facilitate [[Special:MyLanguage/Identity verification|Identity verification]], starting with version 2.1, the default ("Small expenses") wallet of new users is created as single-address (nothing changes for old users). Users can still easily add another wallet and make it multi-address for better privacy. The second wallet is not linked to the user’s verified identity and can be used anonymously.<ref>https://medium.com/byteball/distribution-to-verified-users-and-referrals-ed00b9b2a30e</ref>

==Multiple screens== 


The default wallet is named "Small Expenses Wallet", and has two screens: one for bytes, one for blackbytes. Every [[Special:MyLanguage/Asset|new asset]] you receive (CK1's, [[Special:MyLanguage/Tingos|Tingos]] etc) will create an additional screen just for that asset. If you add a wallet to the default set-up -- maybe "Savings" -- it will start out with two screens again.

==Update== 


When doing a routine update, first do a full back-up using the Byteball menu option (see below) just in case, then simply download the latest version and install it over the top of the existing version. So when you get a prompt saying "you already have [this], do you want to replace it?" click yes.

==Main menu options== 

===Add wallet=== 


Choose between PLAIN WALLET and MULTI-DEVICE WALLET, and give it a name. If multi-device (m of n) wallet, choose the total number of co-signers (n), and the required number of signatures (m). For each co-signer (not you), you need to select from the list of paired devices in your library. If the device is not there yet, share a pairing code with it and then select it.


A multi-device wallet is duplicated across each of the paired devices, showing the same transactions, addresses, balances etc.

====Signatures==== 


*A 1-of-2 set-up means two devices and either one is sufficient to send a transaction.
*A 2-of-2 set-up means two devices and both signatures are needed to send a transaction.
*A 2-of-4 set-up means four devices and two signatures are needed to send a transaction.

===Paired devices=== 

====Contacts==== 


This shows a list of all devices paired with yours, both the user-chosen name (''myputer'' etc) and the permanent device number (0VC...ARM etc). Some devices you will be able to remove, some you won't. However, if you enter the chat window for that device, there's an Edit button at the top right. One of the options is ''rename'', so at least you can rename "AnnoyingDevice" to "zzAnnoyingDevice" and it will move to the end of your alphabetical list and be out of the way.

====Bot store==== 


Currently shows about 20 bots. See wiki article [[Special:MyLanguage/Chatbot|Chatbot]] for details.

===Settings = Global preferences=== 


'''Device name:''' Change it if you wish. If you chat to someone, they will see this name


'''Hub:''' Default is <code>byteball.org/bb</code>. You can change it


'''TOR:''' This option is desktop/laptop only. For Android, use the Orbot app. Sometimes you will not be able to send transactions when Tor is switched on


'''Language:''' Select from 18 or so


'''Unit for bytes:''' Select from kB, MB or GB. For safety, use the unit matching your usual expenditures. Otherwise you might intend to send 100kB (0.1 MB) and you send 0.001 GB (1 MB) instead because all the leading zeroes are confusing


'''Unit for blackbytes:''' Select from kBB, MBB or GBB


'''Enable push notifications:''' (Android) toggle on or off


'''TRUSTED NODES'''


'''Witnesses:''' Easiest to select "Auto-update the witness list from the hub". See wiki [[Special:MyLanguage/Witness|Witness]] article for harder options


'''Email attestor''' <code>H5EZTQE7ABFH27AUDTQFMZIALANK6RBG</code> is the default. You can change this, but don't unless you know what you are doing


'''DEVICE ADDRESS:''' <code>0VCPO8MYDRN2E3N5JDRHRSTVEVZSZYARM</code> for example. This doesn't change, and will be visible to anyone you pair with for chat


SPENDING RESTRICTIONS 
'''Request password:''' Lets you set up a password that will encrypt your platform/wallets. Don't forget it! There is no password recovery option


'''Backup wallet seed:''' The seed alone will back up your bytes (and any public tokens/assets like Tangos etc) but not your blackbytes (or other private assets that aren't detailed in the DAG). This is important! (It means "backup platform seed")


'''Recovery from seed:''' Recovery is available in single-sig (i.e., not multi-sig) light wallets from version 1.10.1.


'''Full backup:''' Lets you set a password (don't forget it!) and export a full backup file. You should do a full backup every time you do a blackbytes transaction. Many people have lost funds because they didn't do a backup.


'''Restore from full backup:''' Note this will permanently delete all your existing wallets and replace them with whatever is in your backup file. If you created this backup on another device, you should have stopped using the original device platform immediately after creating the backup. Never clone platforms/wallets. If you must access your funds from several devices, use multisig.


'''About Byteball:''' Version number, commit hash (developer thing), terms of use, translators credits, session log

==Cogwheel preferences== 


'''Wallet alias:''' change local name (it means "platform alias")


'''Color:''' 12 to choose from


'''Advanced:''' (under next heading)

===Wallet information=== 


'''Wallet name (at creation):''' whatever name you gave the wallet first


'''Wallet ID:''' note this does not change, and is different to all the wallet addresses. If this is a shared multi-sig wallet, the ID will be the same on each of the paired devices


'''Wallet configuration (m-n):''' multiple-signature configuration, like 1 of 1, 1 of 2, 2 of 2, 2 of 3 etc


'''Derivation strategy:''' BIP44: standard method of deriving new keys for addresses<ref> [https://en.bitcoin.it/wiki/BIP_0044 Improvement Proposal 44]</ref>


'''Account (BIP44):''' BIP44 allows the creation of more than one account. If you create a second multi-sig account with a paired device it will show as #2. If this is the 5th wallet on this device/platform it will show as #5.


'''CO-SIGNERS'''


Shows the co-signers (if any) for this wallet configuration, and which wallet is currently in use. Note the original wallet names are used, not what they may have been changed to


'''EXTENDED PUBLIC KEYS:'''


*'''Me''' xpub... (this wallet's xpub)


*(Other wallet's name, if multi-sig) xpub... (that wallet's xpub)


'''ALL WALLET ADDRESSES:''' (examples shown)


65C...AW6 
m/44'/0'/1'/0/0 · April 19th 2017, 3:00 pm


7SV...MMM 
m/44'/0'/1'/0/1 · April 22nd 2017, 5:47 pm


MR3...APD 
m/44'/0'/1'/1/0 · April 26th 2017, 1:34 pm


The m/44'/0'/1'/... designation is part of the BIP44 protocol. Here, the 1' means the second wallet -- the first (small expenses) wallet is designated 0'. The final 0/0 (0/1, 0/2 etc) means the 1st (2nd, 3rd etc) visibly-generated receive addresses; and the final 1/0 (1/1, 1/2 etc) means the 1st (2nd, 3rd etc) automatically-generated [[Special:MyLanguage/change address|change address]]es.


'''BALANCE BY ADDRESS:''' (examples shown)


7SV...MMM 
0.04 GBB


O3J...YL5 
0.024402 MB


RAZ...LIM 
0.05966 MB 
55 Zwib by Jore Bohne (new [[Special:MyLanguage/asset|asset]], registered) 
576 of 3kc7H8A2oiWr8mv7AcWJeLCA0Cp8c3BLK04kYQ+5pfU= (new asset, unregistered) 
0.085248 GBB


UQX...EC6 
0.117889 MB

===Sweep paper wallet=== 


*This gives an option to scan QR code of paper wallet private key
*If anyone sees a Byteball paper wallet generator, please tell me (Slackjore)

===Delete wallet=== 


What it says, big red button on the next screen

==Smart wallets== 


When you transact using a smart contract, the funds may go into a smart wallet. One or both parties will be able to unlock this and spend the funds.

===Confirmed funds=== 


You need transactions to confirm before
*A smart wallet first becomes visible
*You can spend funds from it

===Transaction fees are paid in bytes=== 


If you are in a new smart wallet and trying to send blackbytes, or some [[Special:MyLanguage/asset|new asset]] (like [[Special:MyLanguage/Zangos|Zangos]]), it won't have any regular bytes in it to cover the transaction fee. So open the Receive tab, copy the address, paste it into your regular wallet and send some bytes, maybe 0.1 MB. You can easily recover any unspent bytes from this.

====Zero out the smart wallet==== 


Lots of little smart wallets can get confusing. So send all funds, in all currencies, to your regular wallet(s). Send the (white)bytes last, or you won't be able to pay the transaction fees.


When all balances in a smart wallet are zero, it will disappear (hooray!).


If you cannot spend the funds, maybe they are locked because the other party needs to spend them. Or some other condition has not been satisfied.

==Backup== 


Full backup is WAY more important than a seed. Full backup keeps your blackbytes, and even better, it means a simple and quick full restore, whereas a restore from seed may require a full node.

==Convert== 


There's no simple way to change from a full platform to a light one. Usually the need becomes apparent when one has sent GBytes from an exchange to a full platform and the funds don't show in a wallet because the platform hasn't sync'd up to the date/time of the transaction.


In this case, follow these steps to get access to your bytes (not blackbytes):


#On a separate device, download and install a light platform
#Find someone you trust that has a fully-sync'd full platform that has zero funds in it. Send that person your seed. They will then restore your platform on their computer
#That person then sends your funds to your new light platform
#Continue to use the light platform


To get access to your blackbytes, either


*Wait until the full platform syncs, then send the blackbytes to the light platform (after pairing); or
*Send that nice person you trusted with your seed the "User data" data directory (see below), and he can then send you the blackbytes (after pairing).


User data directory in Windows, for example, is found at C:\Users\Alice\AppData\Local\byteball\User Data

==Reinstall platform== 


To start from scratch, you have to rename or delete the Byteball user data folder before reinstalling. '''Be aware that deleting the user data folder results in any existing coins getting lost.''' After you've renamed or deleted this folder, you can do a re-install and choose the platform type (light/full) again.

===Rename or delete this folder before reinstall=== 


*Windows: %LOCALAPPDATA%\byteball
*MacOS: ~/Library/Application Support/byteball
*Linux: ~/.config/byteball

===Changing operating systems=== 


It is apparently possible to make a full backup on Windows, and then restore it on Linux. Everything reportedly gets copied including the device address.

==Wallet and explorer differ== 


Does explorer.byteball.org show some new bytes have arrived, but they don't show in your wallet?


'''Platform not connected properly?''' Your internet connection needs to allow communications to get to and from the platform: an easy check is do the chatbots work? If the chatbots don't work, maybe showing a Socket Closed [[Special:MyLanguage/error|error]], this lack of proper connection must get fixed.


*Firewall problem?
*Tor turned on by mistake? ('''Check''' this at Settings > TOR, don't just assume it isn't turned on)
*Something else wrong?


'''Platform not sync'd?''' If have a full platform it needs to sync up to the date of a transaction to show it. Then, transfer your coins to a light platform and when you're sure the coins are in the light platform dump the full platform.


'''Weird platform?''' If you have done something weird like "copied"/cloned a platform from one device to another, or are running more than one instance on a single computer, then you may or may not be able to access these coins.


'''Latest version?''' You '''are''' running the latest version, right?

==Sync problems== 

===Android=== 


If your phone is taking too long to sync, even with a light platform, it could be due to blackbytes, and because when the screen fades out it often stops syncing. Activate Developer Mode on Android to get under Settings a new option to keep the screen awake/on when plugged in, and this allows you to sync overnight.

===Full platform may be better=== 


If you want to do many blackbyte transactions, a light platform is less efficient than a full platform to sync blackbytes. So in this case you are better off with a full platform and thus must have an SSD drive on your laptop/desktop.

==External links== 


*Bitcoin Improvement Proposal 44<ref>https://en.bitcoin.it/wiki/BIP_0044</ref>

*Paper Wallet generator: https://bonuschain.github.io/byteball-paperwallet/

==References== 


<references />
[[Category:Features]]
</translate>

Videos

2019-01-19T22:20:25Z

Punqtured: 21 revisions imported

Some general (non-technical) videos in English about Byteball. There is also a wiki [[interviews]] page.

==YouTube==
{| class="wikitable"
|-
! Date uploaded !! Channel !! Title !! Length !! Notes !! Preview
|-
| 2016-10-14 || Coin Interview || Coin Interview Episode 27: Anton Churyumov of Byteball.org || 58:16 || Talking heads throughout but mainly Tony; 4505 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=zjT7wQNg_s4|200}}
|-
| 2016-12-23 || Marc De Mesel || Byteball: The most amazing crypto for free || 5:03 || Talking head throughout; 5159 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=bPicDP-ehfU|200}}
|-
| 2017-04-26 || DashMeister || Byteball: The most amazing crypto for free || 5:03 || Narrated; shots from coinmarketcap and Byteball main page; 14,205 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=IFP0rPgMu_Q|200}}
|-
| 2017-06-11 || Wekkel Ekkel || Byteball - Making Byteball Payments || 6:21 || Music; no narration but some onscreen explanations; handheld video of monitor showing byte and blackbyte payments; 808 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=6VI_-JIDyUI|200}}
|-
| 2017-06-26 || h3ym0nk3y || Join Byteball || 1:48 || Music; no narration; VideoScribe presentation of basic Byteball features; 606 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=fUd5LM9C6AM|200}}
|-
| 2017-06-29 || h3ym0nk3y || byteball || 0:24 || No sound; nifty rotating graphic of 3D "Byteball" made of 0s and 1s; 140 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=IiXBiwVCFOI|200}}
|-
| 2017-12-02 || Marc De Mesel || Interview with Byteball founder Tony Part 1: Why DAG Better Than Blockchain? || 23:31 || Talking heads throughout; background noise; 2375 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=M-gmFnh24Lc|200}}
|-
| 2017-12-05 || Marc De Mesel || Interview with Byteball founder Tony Part 2: How Private are Blackbytes? Spend Crypto with Cashback! || 19:47 || Talking heads throughout; background noise; 638 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=PAB6K85QmnQ|200}}
|-
| 2017-12-06 || Marc De Mesel || Interview with Byteball founder Tony Part 3: What Crypto Can & Fiat Not: Conditional Payments || 15:33 || Talking heads throughout; background noise; 558 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=71QadbG-sSM|200}}
|-
| 2017-12-13 || Marc De Mesel || Byteball Wallet Tips & Tricks || 12:19 || Talking heads throughout; with gorgeous beach and girl; 1128 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=oGxOQAS54vk|200}}
|-
| 2017-12-16 || Marc De Mesel || Part 2 - Byteball Wallet Tips & Tricks - Caveats & Cows || 7:40 || Talking head throughout; with gorgeous beach and cattle [sic]; 497 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=OUzIfBhRDnA|200}}
|-
| 2017-12-22 || A.C. || The ground is shifting || 0:27 || Text onscreen; upbeat music; 29,778 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=VIOBsmLA6jo|200}}
|-
| 2017-12-27 || Byteball || Byteball | Smart Payments Made Simple - part 1 of 4 - Why? || 8:28 || Graphics with narration; 1336 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=2ZuYZOitKfQ|200}}
|-
| 2017-12-27 || Byteball || Byteball | Smart Payments Made Simple - part 2 of 4 - The DAG || 11:16 || Graphics with narration; 990 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=zOayZ2_6cN4|200}}
|-
| 2017-12-27 || Byteball || Byteball | Smart Payments Made Simple - part 3 of 4 - Smart contracts || 3:48 || Graphics with narration; 1857 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=RT-pA_KHz4U|200}}
|-
| 2017-12-27 || Byteball || Byteball | Smart Payments Made Simple - part 4 of 4 - Adoption || 8:28 || Graphics with narration; 388 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=SnXuylxUKqo|200}}
|-
| 2018-01-21 || The Billion Dollar Secret || Exclusive Interview with the Byteball Founder Tony Churyumoff (Part 1) Legends of crypto || 31:05 || Talking heads throughout; 1897 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=tB0AUpiF9B4|200}}
|-
| 2018-01-28 || The Billion Dollar Secret || Byteball Founder Tony Churyumoff - Part 2 of the Exclusive Interview Legends of Crypto || 31:06 || Talking heads throughout; 797 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=7Fau1bg9-jg|200}}
|-
| 2018-01-21 || The Billion Dollar Secret || Byteball Founder Tony Churyumoff - Part 3 of the Exclusive Interview Legends of Crypto || 24:18 || Talking heads throughout; 721 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=ocB5oJdxuuY|200}}
|-
| 2018-04-05 || InnMind Community || Byteball workshop: Crypto solutions for the real world || 35:06 || Workshop presentation at Blockchain Leadership Summit 2018 in Zurich; 270 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=C2MtBXqUcvk|200}}
|-
| 2018-05-11 || Byteball || Introduction to the Byteball Use-a-Thon at Simon Bolivar University, Venezuela || 33:07 || Presentation of Byteball features, with commentary; 83 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=4pI_ccX0aZU|200}}
|}

===Masha videos===
{| class="wikitable"
|-
! Date uploaded !! Channel !! Title !! Length !! Notes !! Preview
|-
| 2018-04-10 || Byteball || Byteball hires first PR agency, plus Blackbytes tutorial and a Woobytes update || 2:42 || Talking head throughout, delivering newsletter content; 584 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=u9rl_bd6CB0|200}}
|-
| 2018-04-11 || Byteball || Worldopoly ICO with a bonus for people that invest using the Byteball platform || 4:05 || Talking head throughout, delivering newsletter content; 268 views at 2018-05-12 || {{#ev:youtube|https://www.youtube.com/watch?v=fDl58qQJoPw|200}}
|-
| 2018-05-14 || Byteball || Crypto newcomer Masha explores the Byteball wiki || 14:56 || Talking head with wiki pages throughout, as she learns in real time; 74 views at 2018-05-15 || {{#ev:youtube|https://www.youtube.com/watch?v=jy-gM2i9Cq8|200}}
|-
| 2018-06-01 || Byteball || Buying cryptocurrency on her own for the first time (2018) || 5:20 || Talking head with her computer screenshots in real time; 1371 views at 2018-06-02 || {{#ev:youtube|https://www.youtube.com/watch?v=4KRp0IxI72U|200}}
|-
| 2018-06-11 || Byteball || Buying cryptocurrency on her own for the first time (2018 - Part 2) || 6:26 || Talking head with her computer screenshots in real time; 783 views at 2018-06-13 || {{#ev:youtube|https://www.youtube.com/watch?v=3M6siUq3rBU|200}}
|-
| 2018-06-19 || Byteball || Buying cryptocurrency on her own for the first time (2018 - Part 3) || 6:26 || Talking head with her computer screenshots in real time; 81 views at 2018-06-19 || {{#ev:youtube|https://www.youtube.com/watch?v=hzc45W2UQ-M|200}}
|}

===Video competition winners===
{| class="wikitable"
|-
! Date uploaded !! Channel !! Title !! Length !! Notes !! Preview
|-
| 2018-04-30 || Louis Thomas || Interview with Marc De Mesel - Bear Markets, Bitcoin Cash, Byteball, Stock Market & More! || 17:24 || Talking heads throughout; 6940 views at 2018-06-27 || {{#ev:youtube|https://www.youtube.com/watch?v=ZlSjFqwcw7U|200}}
|-
| 2018-05-02 || Milán Horváth || How to buy Byteball bytes with your Visa or Mastercard? || 1:50 || Clearly shows wallet/website to match the narrative given by pretty girl in the corner of the screen, excellent diction; 161 views at 2018-06-27 || {{#ev:youtube|https://www.youtube.com/watch?v=93jnbZsudmw|200}}
|}

==Vimeo==

{| class="wikitable"
|-
! Date uploaded !! Channel !! Title !! Header text !! Length !! Preview
|-
| 2017-06-12 || Jore Bohne || Byteball: 1. Smart payments made simple || 2:13 || Narrated with subtitles; shows live wallet chat of buying zwibs with MB; 4435 views at 2018-05-12 || {{#ev:vimeo|https://vimeo.com/221317149|200|right}}
|-
| 2017-06-14 || Jore Bohne || Byteball: 2. Betting on random numbers || 4:03 || Narrated with subtitles; shows live betting and using oracle feed; 142 views at 2018-05-12 || {{#ev:vimeo|https://vimeo.com/221655112|200|right}}
|-
| 2017-06-17 || Jore Bohne || Byteball: 3. Betting on flight delays || 4:10 || Narrated with subtitles; shows live betting, using flightstats data and oracle feed; 185 views at 2018-05-12 || {{#ev:vimeo|https://vimeo.com/222006250|200|right}}
|-
| 2017-07-04 || Jore Bohne || Byteball: 6. Making a dead-man contract || 4:41 || Narrated with subtitles; shows live wallet use and timestamp oracle etc; 185 views at 2018-05-12 || {{#ev:vimeo|https://vimeo.com/224224884|200|right}}
|-
| 2018-02-xx || Jore Bohne || Byteball InfoGIF 3: Textcoins || 3:26 || No audio (it's also a GIF); shows creating and sending and receiving a textcoin, installing a light wallet on Android, a textcoin of Tingos ; 153 views at 2018-05-12 || {{#ev:vimeo|https://vimeo.com/254898717|200|right}}
|}

[[Category:Browse]]

WCG distribution

2019-01-19T22:20:25Z

Punqtured: 9 revisions imported

See:
*https://wiki.byteball.org/Chatbot#World_Community_Grid_linking_bot
*https://wiki.byteball.org/Distribution#From_the_WCG_linking_bot
*https://wcg.report/ Byteball completed distributions

If you participate in WCG distribution, please join Byteball.org<ref>https://byteball.org</ref> team and post into this thread: https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,40783 (no further registration needed)

==New to Byteball?==
The most important facts in a nutshell:

*Download Byteball wallet from https://byteball.org/#download
*Open Bot Store [Chat tab] and add 'World Community Grid linking bot', chat with the bot and link your WCG name to your wallet address
*Payout rate is currently set at $1.00 (in Bytes) for every 150,000 points (daily payout)

==A quick guide to linking your wallet with WCG==
(copied/edited from Steemit article)<ref>https://steemit.com/byteball/@punqtured/processing-for-good-get-rewarded-for-crunching-numbers-to-cure-diseases</ref>

Assuming you already installed the Byteball [[wallet]]...

===1. Find the WCG bot in the Bot Store===
Click the Chat tab at the bottom of the wallet. Select the "Bot Store" tab and locate the WCG Bot. Click on it and hit the huge ADD BOT button.

===2. Create or edit your WCG account===
Whether you have an existing account at World Community Grid or not, the bot will give you a username. If you don't already have an account, create a new one and be sure to use the username given by the bot. If you already have an account, go to "Settings" and click the "My Profile" button on the left. It will ask for your username and password before allowing you to change anything. When logged-in, you can change your username to that given by the bot. Also, make sure that you enable the bot to access the data, choose "Display my data" option (like it is shown on screenshot below) on that same page and then click "Save" at the bottom of the page.

[[File:display-my-data.png|600px]]

===3. Link your wallet and WCG account===
Go back to the bot and click "Check my account". The bot will then connect to World Community Grid and look for the account with the username it gave you. If it finds a matching account, it will then respond with "Your WCG account is successfully linked.". If linking failed then double-check that you entered the username as asked and that you have chosen to "Display my data" like on screenshot above.

===4. Choose your payout address===
The bot will then ask which address you want rewards sent to. If you want rewards sent to the wallet that is active when entering the chat with the bot, simply click the three little dots at the bottom left and click "Insert my address".

===5. Change name as needed===
When everything is done and set up, the bot will tell you that set-up has been completed. You can then go to WCG and change your account name to whatever you like (see steps above) -- remember to also change the name with the bot by clicking the "Change account name" link. The bot will then ask what your new account name is, and validate that this was indeed your new account name.

== Notes ==
=== Multiple devices ===
The link is per WCG account and you can have multiple machines running.

==References==
<references />
[[Category:Browse]]

Use-a-thon/usb

2019-01-19T22:20:24Z

Punqtured: 29 revisions imported

==Use-a-Thon #1: Simón Bolívar University, Venezuela==
[[File:usb-useathon2.jpg|thumb|upright=0.71]]
*Dates: May 14 to June 24, 2018
*Local co-ordinator: FCEUSB at La Casita, email: <code>fceusb@usb.ve</code>
*Final team approval: Msc. Professor Carlos Castañeda, Social Science Department
*Byteball co-ordinator: Casper Niebe, @Punqtured on Slack, email <code>use-a-thon@byteball.org</code>
*Byteball jurors and helpers: (in Slack) @Punqtured, @Suirelav, @Slackjore

===Prize money===
4.3 GB (plus 5000 bytes for transaction fees) are set aside for the prizes plus expenses See Explorer link.<ref>https://explorer.byteball.org/#REP2XPZJRM33VRJD74RBFCTZOSY5U244</ref>
*Prizes: 1st place 2 GB; 2nd place 1 GB; 3rd place 500 MB (0.5 GB); 4th place 200 MB (donation); Documentary team 100 MB (donation).

Prizes paid 4 July 2018 from third-party wallet in https://explorer.byteball.org/#2azkgEKokAbSPH4nhmCznEbwmcKDot+9BMUF+P13PS0=, and reimbursed from the correct address same day in https://explorer.byteball.org/#zcotOnYeTfFV5kaxJ71Or0OOOZgInYpdhmmlF0R+N4o=.

The documentary reward of 100 MB was not paid. The extra 5x100 MB were fast sign-up bonuses for the first five team signups.

===Teams===
*One team member must be a current student at USB
*The team's contact must be a current USB student
*The team's contact must be proficient in English and able to communicate with Byteball organizers on Slack
*The team's contact must be registered with FCEUSB with this information:
**Team number (assigned by FCEUSB in the order that the teams register so first team gets #101 etc)
**Team name (optional)
**Full name of team's contact
**Email of team's contact
**Wallet address for the team
*Team may get help from any external source they find relevant
*Team members who are current students must all be listed with name and email
*Information about identity of team members won't be shown on the wiki website, but is required for registering the team

===General Rules===
*Register team as above by May 24, 2018
*The project must describe a real-world use case that the Byteball cryptocurrency platform could provide a solution to, to solve an actual problem in your community (can include the university)
*Project entries in PDF format must be written in English, summary of 150 words or less, in a normal project format showing main goal, sub-goals, details and milestones as applicable
*All entries shall be available under a Creative Commons Attribution-ShareAlike 3.0 Unported License
*Deadline for handing in projects is June 24, 2018 (email with attached PDF to local co-ordinator)
*If less than five projects are handed in, the competition will be cancelled
*If a team wants to submit more than one project, that is fine. Each project will be considered on its merits, whoever submits it
*Byteball reserves the right to (but really hopes it won't need to) cancel the competition at its own discretion

====Help====
*See the presentation linked just below, including three videos showing Byteball features
*Download the platform/wallet from https://byteball.org, get millions of free tokens from the fun-coins faucet in the wallet, and enough Bytes (Byteball currency) for transaction fees from @Punqtured or @Slackjore or some other local person, and try out things
*Team contacts may ask questions directly on the Byteball Slack^ at http://slack.byteball.org (Channel #byteball_use-a-thon). Display the username "USB_TeamNNN", where NNN is your team number. Note that anyone can see these messages (there is no private help available). The three main people answering your Use-a-Thon questions are Punqtured, Suirelav and Slackjore. They are all in the UK/EU time zones (UTC +1/+2), although others may be able to answer general Byteball questions when these three are not available
*The rest of [[Main_Page|this wiki]] is very informative too.

^ To get on Slack, Team contacts can either:
*Go through slack.byteball.org and click one of the social media buttons Twitter, Facebook, Reddit or Linkedin. Depending on several factors (account age, number of followers etc.) you can get an immediate invite; otherwise you will receive an email from @cryptkeeper in which he will ask for other means of authentication. OR
*Email Punqtured at <code>use-a-thon@byteball.org</code> from your usb.ve account giving your name and Team number. Ask for the invitation. He will forward your info to @cryptkeeper.

===Presentation===
*[https://docs.google.com/presentation/d/e/2PACX-1vRfcZzg3e4WGI9YvN-jJZniOEBpWAWZCqfBAl-LasmEmfsScaZpjOvwmq9aX8dA9U0thM7LpCQxGEHF/pub?start=true&loop=false&delayms=10000 Presentation (use arrow keys to move between slides)]
*[https://www.youtube.com/watch?v=4pI_ccX0aZU (Video) Presentation with commentary by Punqtured]

===Documentary===
The organizers will also give a reward of 1 GB for documentary material about this Use-a-Thon. No details worked out yet, but potential media-people should prepare material (videos, photographs, interviews etc) while it is taking place.

===Approved teams===
These are teams that have registered, and been approved to take part. "999" is a separate student team documenting the event.

{| class="wikitable sortable"
|-
! # !! Team name (optional) !! Address !! Notes
|-
| 01 || Byteboys || EIU6AI3UZZIXM3PAHVOKRKU6DAQVRNBR || Sartenejas
|-
| 02 || Cryptoworld || KTAO53WE2T3A3DGBCEDBYJKWRGANNPEC || Sartenejas
|-
| 03 ||   || XILLEJ2OZYT4LXY2RRAMLP4TO7EVXL2T || Sartenejas
|-
| 04 || Cryptoponquesitos || IOVF22FOSWKK73NZAZYP3NQVDYP7VDAD || Sartenejas
|-
| 05 ||   || PVFPLWWY3255S53XBLMBG5LNQ5XWY3L7 || Sartenejas
|-
| 06 ||   || GBDALRBKMVSWVTG5E3RWE6Y2RYENK6GW || Sartenejas
|-
| 07 ||   || XAXVWMU6KAMUEEOZUMI6T7MHX7WOKSI3 || Sartenejas
|-
| 08 ||   || NZ2W57ZAMRX2VNI54NPMTLIV2WV575RE || Sartenejas
|-
| 09 ||   || IGXXAMY3GT4MH55POCGGYSNLKUFKO7HE || Sartenejas
|-
| 10 ||   || V3UJFIBENK7OGVOO22YGNPW7SDOSXXUA || Sartenejas
|-
| 11 ||   || AG5SV7BJHS6VSZ5CCNVUCMX2DQ62PVAD || Sartenejas
|-
| 12 ||   || YER5JU7NWJORJCJS2TO4OKGMBBY2YV3M || Sartenejas
|-
| 13 || Filis Albicollis || 7NZ5WTI2IOQLKXL5LJODVHJMMKY66VSW || Litoral
|-
| 14 ||   || JTTLL6SI3MVI3DIRNO6YVF7RX2ZJLES5 || Sartenejas
|-
| 15 ||   || 63DU4B7SFR5PTBM6DDBJK4UJG7FMMV25 || Sartenejas
|-
| 16 ||   || 4XCJMV6VJXVN4H2DGJIKFET6LCYQ3ZGG || Sartenejas
|-
| 17 ||   || Z2WSQL2GQ4UE7W5SZ7JREZJPLIRJXVPB || Sartenejas
|-
| 18 ||   || MBME4SGRQV5XUVC2CA4YWUC4AS4J5WHU || Sartenejas
|-
| 19 ||   || YTL72K6MYY6BNWRCE74GCSCSIOG3ZXF7 || Sartenejas
|-
| 20 ||   || SNXRV3KDL7A7X5ONLEMKVYOYYMAHVTWQ || Sartenejas
|-
| 21 ||   || AFKQGX3PDAYKQ3N4JTSGPDBCASNBADJ4 || Sartenejas
|-
| 22 ||   || 2CY3IULFANRJVO2N3CL7JLTERCAJKCIS || Sartenejas
|-
| 23 ||   || ISNUXLBIIQUJEC5F6YRIEKL2AJH25NBB || Sartenejas
|-
| 24 ||   || GQJ4EK2OSKO73HI2W7CXUNWY5IESWOWT || Sartenejas
|-
| 25 ||   || H2JK3SWWAJ3WLB37G45TMGIHJOLA4IXH || Sartenejas
|-
| 26 ||   || FRQHJTU3473INMVB7DU6KJ25HAO6FUOQ || Sartenejas
|-
| 27 ||   || 5YFUHEPDYX6TRIS4YVQPFX6FKJKWFVD3 || Sartenejas
|-
| 28 ||   || X3Y4FPO2GHNF55TSYUTUZPGIT7XLRJKN || Sartenejas
|-
| 29 ||   || PDT7BZ7FEGGTGZNE7TOPT4S7V2IEHF5J || Sartenejas
|-
| 30 ||   || FDJEST5OYXECMYVRQVEDPMLUVNSB6XEA || Sartenejas
|-
| 31 ||   || KSBUZTUK75QXTFQ33NSYERMVU575XSGU || Sartenejas
|-
| 32 ||   || SBXS5L2ZZKYEBD7AEX6WG7QCCG6AAJDS || Litoral
|-
| 33 ||   || WJMFBSIOKZEE4MNR3FDHV4WQQL3HGNXY || Litoral
|-
| 34 ||   || OTTHLPXFFWB2V4QM6LR7KACWF6CT4NY7 || Sartenejas
|-
| 35 ||   || AWBPCFC7TC6K4EAEZY352NG3QCL6QCDP || Sartenejas
|-
| 36 ||   || 6ONH3IXO64EJYRIMFDR33XWNR2PHDIEM || Litoral
|-
| 99 ||   || VWRICREBI4GI32RFQD6Z2JUS2HJ55YO5 || Documenting
|}

==References==
<references />

[[Category:Browse]]

Use-a-thon/steem

2019-01-19T22:20:23Z

Punqtured: 70 revisions imported

[[File:useathon-banner-2.png|thumb]]
== Here’s your chance to get more Bytes ==
Since the airdrop, almost 70,000 Steem users have linked their Steem username to their Byteball wallet. 5,400 GBYTE was distributed to users while 8,500 GBYTE are locked in smart contracts to be released next year.

To encourage users to explore the Byteball platform and the possibilities it offers, Byteball hereby announces a contest in creating innovative use cases during the contest period. Steem users are encouraged to compete.

===Main prizes===
*1st place: 10 GBYTE
*2nd place: 5 GBYTE
*3rd place: 2 GBYTE

===Weekly prizes===
Users are encouraged to share their progress on their Steem blog. Every Sunday during the contest period (Sept 2, 9, 16, 23), a jury of Byteball staff and veterans will pick the most interesting, promising, fun, ingenious or remarkable progress report and the user will be rewarded with 1 GBYTE. The weekly winner will be announced in a weekly contest update posted on the @Byteball blog<ref>https://steemit.com/@byteball.org</ref>. All prizes will be transferred to the wallet used when paying the entry fee.

== How to participate ==
To join the contest, participants pay an entry fee of 25 MB. The entry fee must be paid from a publicly attested Steem user’s Byteball wallet. This allows us to keep track of participants and to follow your progress on your blogs. All entry fees are added to the prize pool and distributed on a 10:5:2 ratio between the prizes.

Send your 25 MB entry fee from your publicly-attested Steem address to <code>EPZEMB73FGY7O6XMTGA2SFQIDUUV4NT5</code>

== What is a Use-a-Thon? ==
You have probably heard about hack-a-thons, where developers and engineers develop new features for a given product by altering code, hardware or tweaking the product.

A Use-a-Thon doesn’t require development or engineering skills. The aim is to explore, experiment and apply the existing features to solve a real-world problem or fulfill an existing need either online or offline in a local community. So while creating new chat bots and oracles is an option, it’s not required at all. A previous Byteball Use-a-Thon proved that users are able to apply the platform to real-world use cases without knowing programming or underlying technologies at all.

== What is a use case? ==
A use case is a real-world problem or need that can be addressed with the given tool. Some (but not all) examples could be: introducing smart contracts to enable trustless value exchange between two parties, a web-based mini-game, disrupting an existing market, creating a new service allowing Byteball users to purchase products, allowing Steem users to send tips to each other, creating a private token to be used in an incentive program, or even creating a small business that potentially generates profit for you.

Basically, anything goes as long as it involves using the Byteball platform and its features.

== When is the contest? ==
NOW! From the date of this announcement, users can join by paying the entry fee. You can enter as an individual or gather a team to help explore, develop and realize your use case. Each participant is free to create more than one entry.

The contest ends 30 September 2018, 11:59:59 UTC. You must create a post on your blog by this date, describing your use case, current progress, plan for realization, milestones and any relevant information allowing the Jury to evaluate your project. The post must be in English, with the title “Byteball Use-a-Thon: [plus your own title]”, start with a summary (150 words or less), and then the additional information as described above. First tag must be “#byteball” and second tag must be “#useathon”.

After the deadline, a Jury consisting of @Punqtured, @Slackjore, @Tarmo888 and @Suirelav will evaluate all contributions and determine the winners, who will be announced about a week later.

== Where can I get more information? ==
With a constantly growing community, there is a vast library of available resources. Here are some relevant resources:
*'''Use-a-Thon presentation:''' https://docs.google.com/presentation/d/e/2PACX-1vSIX6sQtVjM-zD9aPzGqNj2dIexehHb2UOArZgIqi1sYX7go_MLOXM_BSJSp7or6xwhiFmG76AnoE9n/pub?start=true&loop=false&delayms=3000 (Use arrow keys to pause and navigate between slides)
*'''Steem Use-a-Thon Wiki page''' (this page you are currently reading) where all relevant information for the contest can be found
*'''Byteball Slack''' where users can seek help, ask questions and collaborate: https://slack.byteball.org - please state that you are a participant in the Use-a-Thon.
*'''Byteball Wiki''' (you're reading it) contains information about all features, references to external sources etc

Additional resources for techies:
*'''Developer guides''' for those wanting to build new stuff: https://github.com/byteball/byteballcore/wiki/Byteball-Developer-Guides
*'''Easy-to-use JavaScript library''' to easily integrate Byteball features on websites without the need of headless wallets: https://bonustrack.gitbook.io/byteball/getting-started/quick-start
*'''Byteball main GitHub repository''' for those wanting to dig deep: https://github.com/byteball/byteball

==Known participants==
*List derived from each publicly-attested source of a 25 MB payment as above.<ref>https://explorer.byteball.org/#EPZEMB73FGY7O6XMTGA2SFQIDUUV4NT5</ref>
*Look up username at byteball.co, for example <code>https://byteball.co/@2EVEJTQWQGP3IGPVG24D7AP732TUN6N4/attestations</code>
*'''Notes''' includes links to blog Use-a-Thon posts, and also winners of the 1 GB weekly prizes (Sept 2, 9, 16, 23)

{| class="wikitable sortable"
|-
! User/Link to blog !! Registered address/Link to 25 MB unit !! Notes
|-
| [https://steemit.com/@lightsplasher @lightsplasher] || [https://explorer.byteball.org/#N2ZjrylgDGUqpih3vj01uwnQnBsFCNKJ9OqWbu5oGGc= I4DFPFSWUOYAS4D3VN3KJ5BFI74W3L62] || [https://steemit.com/byteball/@lightsplasher/byteball-use-a-thon-vote-selling blog post #1]
|-
| [https://steemit.com/@mimikombat @mimikombat] || [https://explorer.byteball.org/#ATn9wH1fz82ikAmy9FM+EQzRegy33calUuhZ0wsk/Bk= J7GAT6F5LSX6MUO3EUMOTBZ5BMSPJ63P] ||  
|-
| [https://steemit.com/@rrmaxq @rrmaxq] || [https://explorer.byteball.org/#uzERWCrst2oQDjLx5OSvj2CI30RUqvghZV+QgPmOBxw= 5CAFLSOL42UT6CGBTYEQ7G6LB6QWLYHW] ||  
|-
| [https://steemit.com/@grow-pro @grow-pro] || [https://explorer.byteball.org/#bl2en4YBR2fNb7QqBQFhC1tCgaPEX8KGpxHvMhHD4nY= JIBCMLOKLO26JAMKA36OCNPAZCJ4ZSDD] || [https://steemit.com/byteball/@grow-pro/byteball-use-a-thon-the-gb-to-steem-exchange-our-working-concept-is-30-days-into-testing blog post #1]
|-
| [https://steemit.com/@drsensor @drsensor] || [https://explorer.byteball.org/#RKmu1z6WiI2sO5AIXYkyYgn5GOQSIc7KVLdDbiVjPbM= ZO3JNGYEKG7AH4YKV43EHEK5YEAVJ4IF] || [https://steemit.com/byteball/@drsensor/byteball-use-a-thon-a-way-to-contract-reward-contributor-efficiently-1535124849136 blog post #1], [https://steemit.com/byteball/@drsensor/byteball-use-a-thon-a-way-to-contract-reward-contributor-efficiently-architecture-1535847980842 #2], [https://steemit.com/byteball/@drsensor/byteball-use-a-thon-a-way-to-contract-reward-contributor-efficiently-high-level-detail-and-the-direction-1536974947293 #3], [https://explorer.byteball.org/#4n00raXPbPAhN5lqRrYcjP2J0g85jT6lH1+01vITzTc= 9 Sept 1 GB award]
|-
| [https://steemit.com/@genievot @genievot] || [https://explorer.byteball.org/#qE6uA6xhNU2Sorak8FQuZlPkJIms41ESn5dtXUpTeyc= D6Z5A3AC4O7IMFBKUNUDMFL33SGE5J2Z] || [https://busy.org/@genievot/byteball-use-a-thon-freelancing-platform-on-byteball blog post #1], [https://steemit.com/byteball/@genievot/byteball-use-a-thon-listing-my-entries-and-plans-for-use-a-thon-1536858742505 #2], [https://steemit.com/byteball/@genievot/byteball-use-a-thon-1st-entry-progress-discord-byteball-bot-1537003476638 #3], [https://steemit.com/byteball/@genievot/byteball-use-a-thon-1st-entry-progress-discord-byteball-bot-2-1537086563513 #4], [https://busy.org/@genievot/byteball-use-a-thon-1st-entry-submission-request-discord-byteball-bot-completing-my-first-entry-1537618092396 #5], [https://explorer.byteball.org/#5iRUzR9/v4A0L9IxBylNiw9V2kIvQMz3dvrEKb1RSnQ= 2 Sept 1 GB award], [https://explorer.byteball.org/#YLeKvn8o/TVqfoW21E8IrKPd8ApfSYjC/iBdP8vwRTU= 23 Sept 1 GB award]
|-
| [https://steemit.com/@phyowaiaung @phyowaiaung] || [https://explorer.byteball.org/#LxtSd7gZGOG/80oXY+us1cRIxu/rLurj5X9onMg8aUc= KBWNEDIHCU5WTCZQI6ABCTIYG2ZUKA4L] ||  
|-
| [https://steemit.com/@chrisaiki @chrisaiki] || [https://explorer.byteball.org/#LzuGKl6AYfuQ6qnLX2pqWplKO6b6yOI8ijq6qsPbTi0= ENDVW3WYOMFG5BY5BWO5CVZSUQY3FPHB] || [https://steemit.com/byteball/@chrisaiki/byteball-use-a-thon-byteball-askanything-partnership blog post #1]
|-
| [https://steemit.com/@altcoinb @altcoinb] || [https://explorer.byteball.org/#u4gdiI1PHwcgJ7st4YLuauwWag+8cnflPpptAM8QfB0= NFJ7Z6DRYWT3P277JQQ7XAU3TMPPOR76] || [https://steemit.com/byteball/@altcoinb/byteball-use-a-thon-secure-domain-transfer-with-smart-contracts blog post #1], [https://steemit.com/byteball/@altcoinb/byteball-use-a-thon-paid-surveys-polls #2], [https://steemit.com/byteball/@altcoinb/byteball-use-a-thon-send-sms-in-byteball-wallet #3]
|-
| [https://steemit.com/@malos10 @malos10] || [https://explorer.byteball.org/#Z9odHgkCr/FZBteKt/PGE6LOMY5zTY3T2BTiTU9/UfQ= OFPKEGARWOZ6VPTB4GV5QGCNBC4DLDCN] || [https://steemit.com/byteball/@malos10/byteball-use-a-thon-byteball-a-new-method-of-paymet-to-improve-the-quality-of-life-for-venezuelans blog post #1], [https://steemit.com/byteball/@malos10/byteball-use-a-thon-byteball-bytes-as-a-new-method-of-payment-in-venezuela-report-1 #2], [https://steemit.com/byteball/@malos10/byteball-use-a-thon-byteball-bytes-as-a-new-method-of-payment-in-venezuela-report-2 #3],[https://steemit.com/byteball/@malos10/byteball-use-a-thon-byteball-bytes-as-a-new-method-of-payment-in-venezuela-report-3 #4], [https://explorer.byteball.org/#H6FUufTcSgN6gmxPDqt3l8hEl76fJJQYZogjQ9Cnsc4= 16 Sept 1 GB award]
|-
| [https://steemit.com/@jrswab @jrswab] || [https://explorer.byteball.org/#W++uaDE9VcoUmLtJcyEUawfuUGcYWBL8sS6TDzNzw2w= COXXXCJ7Q74ZHKXNLMCPRZE3GO6563NY] ||  
|-
| [https://steemit.com/@alvaro017 @alvaro017] || [https://explorer.byteball.org/#+K1aiDK+p3qXxghj9oM2uIG7vDMxzlOcAvD1MYyrOMc= O725SR6OAQEKYAMBV526EAO4IDLCSMHT] ||  
|-
| [https://steemit.com/@mcassani @mcassani] || [https://explorer.byteball.org/#NzVeAvCu0Blq6VLV2FnfXoTe4U9212glN4WJVX/scKw= ZRDH5XEPHEXYEX7MJOKCCVACF6GSJNHI] ||  
|-
| [https://steemit.com/@meq @meq] || [https://explorer.byteball.org/#79NyHw/+k4bGxukNeC3PsXFtB2hpvsXKdeUBVDf54Co= IRGWXTHW5JZGVW4LOFBJ4E2ZUARKE2N2] ||  
|-
| [https://steemit.com/@onlinegamer @onlinegamer] || [https://explorer.byteball.org/#85/tOkInb/QE0DZcwdX85wp91DF1QoMBUmQNucKzD3I= O6DXROJ6AP5BLOVUBN3F3CBSYFXYBJKF] || [https://steemit.com/byteball/@onlinegamer/byteball-use-a-thon-low-transfer-fee-byteball blog post #1]
|-
| [https://steemit.com/@drumstix @drumstix] || [https://explorer.byteball.org/#hvXvLqdHUa9aNyhZdS9bBZCom9G0bDe6ciGpaAL8FvA= ZSFOMMYZHWT4EYWZJGBICGR2CJWRTKC7] || [https://steemit.com/byteball/@drumstix/byteball-use-a-thon-ending-the-flaws-of-traditional-banking-system-with-little-cost blog post #1]
|-
| [https://steemit.com/@dialsamai @dialsamai] || [https://explorer.byteball.org/#F4OHDbITzj4HLF2T9hXqHTRCB6y5vdkZT5HPNMc3zXo= LFUORYRT7YQY4SVLW476JVNXFUXAZXIX] || [https://steemit.com/byteball/@dialsamai/byteball-use-a-thon-trials-of-israel-web-based-crypto-paying-ad-supported-video-game blog post #1]
|}

===Improper entries===
These appear to be attempted entries, but aren't (yet) valid:

*GJY5BHZXWNGRS2E4UVPJKY3D4ATKHF4O (only 25 KB paid)
*LW3RB3A6BYD646TA3NWCTCRF7N7HDZ2J (only 25 KB paid)
*MSC2MVQBSWOV7XN3UNCARHZKCGXR36E5 (only 24 MB paid)
*MFKTFQ5K3FXEF3BF5H6WGIHRH6ILCN3U (only 25 bytes paid)
*URP3QER4DDV5PO22D6ROIWHKGUMKZP7J (25 MB paid but from private attestation)
*T5JGZZ5PE7J52TUJLPXT4C3T5EHS65SH (only 25 KB paid)
*N23PUSBENG3WDLL76VUI6J3C5G426I5L (25 MB paid but no Steem attestation from that address)
*OCWMLEK4SMBWH7ITABRXOIZDUCPKPNON (only 25 KB paid)

==Weekly Updates on Byteball.org's blog on Steem==
*[https://steemit.com/byteball/@byteball.org/steem-use-a-thon-by-byteball-launch-week First Update]
*[https://steemit.com/byteball/@byteball.org/steem-use-a-thon-by-byteball-weekly-update-1 Weekly Update - Full Week 1]
*[https://steemit.com/byteball/@byteball.org/steem-use-a-thon-by-byteball-weekly-update-2 Weekly Update - Full Week 2]
*[https://steemit.com/byteball/@byteball.org/steem-use-a-thon-by-byteball-weekly-update-3 Weekly Update - Full Week 3]
*[https://steemit.com/byteball/@byteball.org/steem-use-a-thon-by-byteball-weekly-update-4 Weekly Update - Full Week 4]

==Final winners==
*1st Prize: [https://steemit.com/@genievot @genievot]: [https://explorer.byteball.org/#A81h/ujbE58yOPXKQNNZxlo6Ly5M9/ud5ZixaK2IPL4= 10,279,529,411 Bytes] for Byteball Discord bot, plus [https://explorer.byteball.org/#Dsy4XHVDqsmVkzBH8gvc82NP9GWu5pi9yGDINEXo7mY= 1 Prizewinner token]
*2nd Prize: [https://steemit.com/@drsensor @drsensor]: [https://explorer.byteball.org/#omO9uVUk87CkN+ElT/MDtiaCVeim/vsWzg3Fbkv6NB4= 5,139,764,706 Bytes] for rewarding contributors to GitHub, plus [https://explorer.byteball.org/#uK9uvHCM8vmjKl9DhP/Nq6J8Kw15WiC58XWsKTXASrQ= 1 Prizewinner token]
*3rd Prize: [https://steemit.com/@altcoinb @altcoinb]: [https://explorer.byteball.org/#FWa9/okd5Jld12VgB7r6WH5fCihWeHKbohspcHUHCcE= 2,055,905.882 Bytes] for SMS bot, plus [https://explorer.byteball.org/#FKANM0rXUiI2JbwjqVGf9gGT4pa1W5v0+EpiqWR0JEc= 1 Prizewinner token]
*Honourable Mention(s): ...

==Links==
*[https://busy.org/@dakeshi/use-a-thon Korean announcement]
*[https://steemit.com/byteball/@santiagolaw/anuncio-del-steem-use-a-thon-de-byteball Spanish announcement]
*[https://steemit.com/byteball/@byteball.org/announcing-the-steem-use-a-thon-by-byteball English Steemit announcement]
*[https://twitter.com/slackjore/status/1032875390623264768 English Twitter announcement]

==References==
<references />

[[Category: Browse]]

Use-a-thon/botwar

2019-01-19T22:20:21Z

Punqtured: 39 revisions imported

[[File:botwar.png|thumb]]

== The Great Byteball Bot War ==
We invite developers to create [[chatbot|Chat Bots]] for the Byteball platform in a contest to build the most awesome, useful, innovative and creative chat bot. The best ideas will be rewarded generously.

==Contest format==
Over a 4 week period, developers battle in the fine art of coding chat bots. There will be weekly reviews of each contestant’s progress (if the contestant share it) and a weekly award will be granted to the bot creator that provides the best, funniest or most engaging article, blog-post or video.

==Prizes==
===Main prizes===
*1st place: USD 1000 in Bytes (approx 25-35 GB)
*2nd place: USD 500 in Bytes
*3rd place: USD 250 in Bytes

===Weekly prizes===
Each Sunday, the jury will pick the best, most interesting, most informative, funniest or most engaging article, blog post or YouTube video showing the past week’s progress. The best will be awarded $50 worth of Bytes, sent to the dev's registered address. Developers must provide a link to a publicly visible blog, article or other medium by Friday 20:00 UTC. Participants and links to progress reports will be kept updated on this Byteball Wiki page.

===Referral rewards===
Know an awesome developer that would surely win this contest? Then ask him to join and get a reward of 10% of the developer’s prize! Just make sure the developer adds your wallet address on the entry form. So $1000 prize has $100 referral reward, etc. It is OK to invite/refer oneself if there has been no genuine referral (we understand this will occur anyway).

==Schedule==
Wednesday December 12: Announcement of contest and official start

*Friday December 21, 20.00 UTC: Deadline first weekly progress reports
*Sunday December 23: Announcement of weekly winner of 2 GB award
*Friday December 28, 20.00 UTC: Deadline second weekly progress reports
*Sunday December 30: Announcement of weekly winner of 2 GB award
*Friday January 4, 20.00 UTC: Deadline third weekly progress reports
*Sunday January 6: Announcement of weekly winner of 2 GB award

Friday January 11, 23:59:59 UTC: Deadline for all contest entries

==Rules and requirements==
#Each contestant must fill out [https://docs.google.com/forms/d/e/1FAIpQLSfqDp80aN0F296m3C20GpFANWbLnNV4YudD0rZWlSHi2VU9cQ/viewform this form] to enter the contest.
#All code must be published under MIT license on GitHub.
#The bot must apply at least one DAG feature (e.g. payments, storage, attestation etc.)

Weekly progress reports must be submitted to the jury by Friday to be eligible to win the weekly progress award announced on Sunday. Progress reports can be articles, blog posts, videos or similar must be publicly accessible. Submit your report using [https://docs.google.com/forms/d/e/1FAIpQLSeVwr7VZXmeBg7e9coiyyq0Fwo9wYTHTcu8LPPUD11TKucczw/viewform this form].

All chat bots are welcome in the competition. Whether it’s a revenue-generating use case, an interface to an external resource or whatever you can think of - it’s fair game.

==Evaluation and jury==
The jury will consist of:
*Byteball User Acquisition Manager Casper Niebe (@Punqtured)
*Byteball Core Developer Evgenii Stulnikov (@xjenek)
*Byteball Veteran @Slackjore.
The mix of core staff, developers and users helps us evaluate each entry from different perspectives. This means that a brilliant technically-excellent bot with flawless code but no actual real world use would not necessarily have an advantage against a clumsily coded, semi-buggy bot that aims to solve an actual problem or make something easier for Byteball users. Bots should always aim to:
*Solve a real world problem
*Reduce friction in a process
*Have a clear and easily-understood purpose
*Add something new and interesting to the Byteball ecosystem
*Be able to run sustainably without huge costs for the operator.

==Useful help and resources==
Byteball is easy to develop for. The main scripting language is [https://en.wikipedia.org/wiki/Node.js Node.js], which can be run on both backend and frontend. Any other language works as well by connecting through the easy RPC API.

Don’t have any experience with the Byteball platform or developing Chat Bots for it? Don’t panic - there’s plenty of help and inspiration to get! An excellent place to get started is our [https://developer.byteball.org new developer website].

Some sections you may find useful are [https://developer.byteball.org/writing-chatbots-for-byteball Writing chatbots], [https://developer.byteball.org/issuing-assets-on-byteball Issuing assets] and [https://developer.byteball.org/smart-contracts Smart contract definitions].

The developer site documents multiple APIs that you may want to explore, has guides and tutorials showcasing Byteball’s most interesting features. [https://github.com/byteball Our GitHub] has loads of source code of existing bots working in production that you may also want to use in your apps.

If you have coding skills but lack ideas, drop by the Byteball Telegram, Slack or Subreddit to see if other users have an interesting idea. You might also be able to find inspiration from one of the previous Use-a-Thons that Byteball hosted. The most recent was for [https://steemit.com/byteball/@byteball.org/steem-use-a-thon-by-byteball-winners-announcement the Steem community].

On Telegram, we have a [https://t.me/devbyteball dedicated developer’s group] as well. You are also encouraged to join the [https://slack.byteball.org/ Byteball Slack] where you can exchange experience with other developers and the core team. Please state in your request, that you’re a participant in the contest. Finally, the Byteball Subreddit is also an excellent place for inspiration, pitching ideas, getting feedback or simply sharing your thoughts.

==Get your bot listed in the Byteball Bot Store==
Byteball has a fully featured official wallet which contains a Bot Store where you can list your apps. The Bot Store is a prominent part of the wallet, meaning users can easily find your app.

With e.g. Ethereum, marketing your app is difficult and expensive. If users don’t find your app, its chance of success is remote. One reason Android and Apple apps have become so popular is because the Apple App Store and the Google Play Store connect users to developers’ apps. This is the way Byteball has chosen, too.

==Known participants==
*[https://docs.google.com/forms/d/e/1FAIpQLSeVwr7VZXmeBg7e9coiyyq0Fwo9wYTHTcu8LPPUD11TKucczw/viewform Form] for weekly reports
*'''Notes''' includes links to blog botwar posts, and also winners of the weekly prizes
*'''Link''' may be to blog or to Github repo

{| class="wikitable sortable"
|-
! User/Link !! Entrant address !! Referral address !! Notes
|-
| [https://github.com/kaiurin Andrii] || [https://explorer.byteball.org/#XFYE362P4WGQ4IP6WBBMR5XUQPLEUDI6 XFYE3...] || [https://explorer.byteball.org/#R5YQ7N5N5EDI3CZ24HVKKG6CEUXTDWMT R5YQ7...] || SocialBoost [https://steemit.com/byteball/@opposition/bot-wars-socialboost Blog post #1], [https://explorer.byteball.org/#f/vEYvUGQWxaB1B548SB3Bb9aMizX3yQeJYiwSiL+D8= 2GB Week 1], [https://steemit.com/byteball/@opposition/bot-wars-third-report-socialboost post #2 (week 3)], [https://steemit.com/utopian-io/@opposition/bot-wars-final-report-socialboost-launched-on-byteball-testnet post #3 (final)]
|-
| [https://steemit.com/@genievot Genievot] || [https://explorer.byteball.org/#D6Z5A3AC4O7IMFBKUNUDMFL33SGE5J2Z D6Z5A...] || [https://explorer.byteball.org/#D6Z5A3AC4O7IMFBKUNUDMFL33SGE5J2Z D6Z5A...] || DonateBytes [https://steemit.com/byteball/@genievot/progress-report-1st-for-byteball-bot-war-1545379943788 Blog post #1]
|-
| [https://github.com/whoisterencelee/know-it-all-bot whoisterencelee] || [https://explorer.byteball.org/#AAHRPI6UTISGNAEJROXPZZDSXJ4YUD52 AAHRP...] || [https://explorer.byteball.org/#AAHRPI6UTISGNAEJROXPZZDSXJ4YUD52 AAHRP...] || Know-it-all [https://steemit.com/byteball/@whoisterencelee/byteball-know-it-all-bot Blog post #1], [https://steemit.com/byteball/@whoisterencelee/byteball-know-it-all-bot-weekly-update-2 post #2], [https://steemit.com/byteball/@whoisterencelee/byteball-know-it-all-bot-weekly-update-3 post #3], [https://steemit.com/byteball/@whoisterencelee/byteball-know-it-all-bot-weekly-update-4 post #4]
|-
| [https://github.com/pmiklos/byteball-carpool Peter Miklos] || [https://explorer.byteball.org/#ETSFNK5RROAIZBPPZTUAI4K6KUV4WUTI ETSFN...] || [https://explorer.byteball.org/#ETSFNK5RROAIZBPPZTUAI4K6KUV4WUTI ETSFN...] || Carpooling for Byteballers [https://steemit.com/byteball/@byteball.market/carpooling-for-byteballers-the-great-byteball-bot-war Blog post #1], [https://steemit.com/byteball/@byteball.market/carpooling-for-byteballers-the-great-byteball-bot-war-week-2 post #2], [https://explorer.byteball.org/#3XsltvYbQMXCjZ16WLDXOA1Oic+9KgbWyIH5JQMFswM= 2GB Week 2], [https://steemit.com/byteball/@byteball.market/carpooling-for-byteballers-the-great-byteball-bot-war-week-3 post #3], [https://steemit.com/byteball/@byteball.market/carpooling-for-byteballers-the-great-byteball-bot-war-week-4 post #4]
|-
| [https://github.com/AnGrYxx/efa-bot AnGr] || [https://explorer.byteball.org/#BMKMY7VXXLKNPAFIGDVMMHUSTC7MJOU3 BMKMY...] || [https://explorer.byteball.org/#UPFWFMSAJDIRHUPJOCKUD6DXMOE5XFKL UPFWF...] || Error Fare Alerts Bot [https://steemit.com/utopian-io/@angr/byteball-bot-wars-progress-report-1-monetizing-content-with-byteball-error-fare-alerts-bot Blog post #1 (week 3)], [https://explorer.byteball.org/#fojVziXt4OpHs8uCpYUYkXBgcWRtj+6qvUo5rUIkDuI= 2GB Week 3], [https://steemit.com/utopian-io/@angr/byteball-bot-wars-progress-report-2-monetizing-content-and-apis-with-byteball-error-fare-alerts-bot post #2]
|-
| [https://github.com/git-ball/github-attestation DrSensor] || [https://explorer.byteball.org/#ZO3JNGYEKG7AH4YKV43EHEK5YEAVJ4IF ZO3JN...] || [https://explorer.byteball.org/#ZO3JNGYEKG7AH4YKV43EHEK5YEAVJ4IF ZO3JN...] || Github Attestation Bot [https://steemit.com/byteball/@drsensor/byteball-bot-wars-progress-report-github-attestation-bot Blog post (final)]
|}

==Weekly Updates on Byteball.org's blog==
* [https://steemit.com/byteball/@byteball.org/byteball-bot-war-week-1 Week 1]
* [https://steemit.com/byteball/@byteball.org/byteball-bot-war-week-2 Week 2]
* [https://steemit.com/byteball/@byteball.org/byteball-bot-war-week-3 Week 3]

==Final winners==
*1st Prize: ...
*2nd Prize: ...
*3rd Prize: ...
*Honourable Mention(s): ...

==Links==
...

==References==
<references />

[[Category: Browse]]

Use-a-thon

2019-01-19T22:20:19Z

Punqtured: 96 revisions imported

Use-a-Thon #1: See https://wiki.byteball.org/Use-a-thon/usb 
Use-a-Thon #2: See https://wiki.byteball.org/Use-a-thon/steem

'''Use-a-Thon: A contest for innovative uses for off-the-shelf Byteball'''

==Overview==
The general idea is to come up with beneficial '''uses''' for the Byteball platform in a local community. There is a competition format, with individuals or small teams competing for a monetary prize. Entries will be submitted in English, and judged by Byteball veterans. Ongoing help will be available to any team, in writing, but such answers will also be visible to all the other teams too.

===Setting===
*A university: University people are the local co-ordinators, whether faculty or student council members or as appropriate. At least one of them must speak good English, and will be the main person in touch with "Byteball Competition Central", and will be expected to help the teams register. A local faculty member will have final approval of the teams. Local promotion may get done by the local Student Council, or as possible.
*An online community, such as Steem.

===Contestants===
Prior familiarity with Byteball is not essential, but obviously the individual/team must rapidly discover what is possible and not possible to do with [[token]]s on the platform.

Team make-up will vary depending on the circumstances.

==Use-a-Thon Tokens==
[[File:useathon-toks.jpg|thumb]]
There are two tokens created specially for Byteball Use-a-Thons:
*'''Prizewinner:'''<ref>https://explorer.byteball.org/#5fQqISLRM1SIXIoZpqMaOug1YCJapnrCNoH07B8U2IU=</ref> For the main prize winners
*'''Honourable Mention:'''<ref>https://explorer.byteball.org/#D3INZ6ORL3DN2YZaCe5/8PWFYWPqxORHAyOgI3g71iU=</ref> Awarded at the organizers' discretion for an outstanding contribution
{{clear}}

==Help==
*See the presentation linked just below, including three videos showing Byteball features
*Download the platform/wallet from https://byteball.org, get millions of free tokens from the fun-coins faucet in the wallet, and enough Bytes (Byteball currency) for transaction fees from @Punqtured or @Slackjore or some other local person, and try out things
*Contestants may ask questions directly on the Byteball Slack^ at http://slack.byteball.org (Channel #byteball_use-a-thon). Note that anyone can see these messages (there is no private help available). The four main people answering your Use-a-Thon questions are Punqtured, Tarmo888, Suirelav and Slackjore. They are all in the UK/EU time zones (UTC +1/+2), although others may be able to answer general Byteball questions when these four are not available
*The rest of [[Main_Page|this wiki]] is very informative too.

^ To get on Slack, contestants can either:
*Go through slack.byteball.org and click one of the social media buttons Twitter, Facebook, Reddit or Linkedin. Depending on several factors (account age, number of followers etc.) you can get an immediate invite; otherwise you will receive an email from @cryptkeeper in which he will ask for other means of authentication. OR
*Email Punqtured at <code>use-a-thon@byteball.org</code> from your registered account giving your name etc. Ask for the invitation. He will forward your info to @cryptkeeper.

===Presentation===
[See individual Use-a-Thon pages for respective links]

==References==
<references />

[[Category:Browse]]

Trading prediction markets

2019-01-19T22:20:17Z

Punqtured: 4 revisions imported

Prediction markets are exchange-traded markets created for the purpose of trading the outcome of events. This article concerns using the Byteball platform to do this.

==Definition of "prediction market"==
Prediction markets (also known as predictive markets, information markets, decision markets, idea futures, event derivatives, or virtual markets) are [usually] exchange-traded markets created for the purpose of trading the outcome of events. The market prices can indicate what the crowd thinks the probability of the event is. A prediction market contract trades between 0 and 100%. It is a binary option that will expire at the price of 0 or 100%.

Research has suggested that prediction markets are at least as accurate as other institutions predicting the same events with a similar pool of participants.

Source: Wikipedia<ref>https://en.wikipedia.org/wiki/Prediction_market</ref>

==Current available markets==

===Sports-betting on upcoming soccer matches===
See the wiki [[Sports betting]] article for details

===Betting on random numbers===
See the wiki [[Oracle#Random_numbers]] article/section for details, including a video

===Betting on crypto exchange rates===
Crypto exchange rates oracle: '''JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC'''

See wiki [[Oracle]] article for a step-by-step write-up

Reference<ref>[https://medium.com/byteball/making-p2p-great-again-episode-iii-prediction-markets-f40d49c0abab Making P2P Great Again, Episode III: Prediction Markets]</ref>

<hr />Price oracle was extended (29 August 2017) and now also posts total market cap of all crypto coins and BTC dominance percentage (as reported by coinmarketcap).

The new data feed names for smart contracts are:
*TOTAL_CAP - total market cap in billions
*BTC_PERCENTAGE - BTC percentage of total market cap

<hr />

===BinaryBalls===
A commercial site, BinaryBalls<ref>https://binaryballs.com</ref>, from November 2017 was doing binary options trading with Byteball bytes, using this oracle as a trustless referee. On May 10, 2018, it switched to a new data feed directly provided by Bittrex as its new assets-price Oracle.

====Update====
17 September 2018: Due to new EU regulation (DECISION 2018/795) binary options are now illegal and banned from all European Union countries. Therefore Binary Balls has ceased its activities.

===Betting on flight delays===

Flight delay tracker for flight delays insurance 
GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN 
Reference<ref>[https://medium.com/byteball/making-p2p-great-again-episode-iv-p2p-insurance-cbbd1e59d527 Making P2P Great Again, Episode IV: P2P Insurance]</ref>

There is a video of betting on a flight delay on the [[Oracle]] page.

==External links==
*[https://byteball.slack.com Byteball Slack]

==References==
<references />

[[Category:Features]]
[[Category:Trading]]

Textcoin

2019-01-19T22:20:16Z

Punqtured: 5 revisions imported

{{#ev:vimeo|https://vimeo.com/254898717|thumb|right}}

==Sending coins by text==
Source<ref>https://medium.com/byteball/sending-cryptocurrency-to-email-5c9bce22b8a9</ref>

With the release of wallet version 2.0, Byteball users can send Bytes by email. Even if the recipient is not in Byteball yet. 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 prefilled text for the recipient. The sender can edit it before sending.

The recipient receives an email with a link. For example:

<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>

He clicks the link and the money is added to his balance. If he doesn’t have a wallet yet, he is prompted to install one in order to receive the money.

There are more options. When the sender is on a mobile phone and switches to the wallet "Share via message" tab, he is able to use all the options available through the phone’s standard "Share" menu: text message, Telegram, WhatsApp, WeChat, Signal, Viber, Slack, Facebook Messenger, Skype, etc. The recipient receives the same link, but through a chat app.

===Refill===
You can "refill" a textcoin address you have created/emptied. Simply find the interim address in your wallet history, top it up, and when the new transaction is confirmed the original link will work again.

===All public assets===
With version 2.1, you can send any public [[asset]] by textcoin, not only Bytes.

===All private assets===
With version 2.3, you can send any private [[asset]] by textcoin, not only Blackbytes. To maintain privacy, Blackbytes are sent peer-to-peer and contain the entire history of the coin. That is why they carry a lot more information than public textcoins and have to be delivered as digital files.

So, unlike regular textcoins sent as Bytes, Blackbyte textcoins must be transferred via a medium which permits the sending of digital files, such as email or WhatsApp.<ref>https://medium.com/byteball/private-textcoins-6a2288d80757</ref>

===Android===
Another small but important update: when a textcoin link is clicked on Android which doesn't have Byteball app installed yet, the user will be automatically redirected to our app on Google Play and the textcoin will be passed on to Google Play, then to the newly installed app, and claimed immediately after the wallet is created. Which is a very smooth process for new users. <ref>https://bitcointalk.org/index.php?topic=1608859.msg27855312#msg27855312</ref>

==Technical==
On the technical part, the link which is delivered contains a BIP39 mnemonic (we use dashes instead of spaces to avoid confusion with a wallet seed). Only one address, with path m/44'/0'/0'/0/0, is generated from the mnemonic, and the coins are actually sent to this address. When the recipient claims the funds his wallet restores the private key from the mnemonic (everything happens in the background and looks instantaneous), and sweeps the entire balance from this address to one of his own addresses.

Two fees have to be paid, first to fill the temporary address where the money is stored in transit, then to sweep its balance. The sender adds a small amount to cover the fees spent when sweeping. So the amount displayed in the email or text message is the exact net amount. This is to make it clearer for the recipient, especially when he is new to crypto.

==Security==
The textcoins might be delivered through insecure media, such as emails or unencrypted chats. That’s why it is recommended to use them only for small amounts or through end-to-end encrypted chats, such as Signal, WhatsApp, and iMessage.

==Human-friendly==
If the sender makes a mistake in the email address or chooses a wrong recipient, the money is not lost. The sender can claim the money back using the same mnemonic. It is saved in the wallet for such occasions, and a "claim back" link is available on the transaction details page.

==No third party==
This is like PayPal but with one important difference: the money is not kept in the custody of PayPal or any other third party. The money is sent directly from sender to recipient, peer-to-peer, in the spirit of crypto.

==Server-side==
Now textcoins are enabled in server-side (headless) wallets and are available to developers.<ref>https://bitcointalk.org/index.php?topic=1608859.msg26332250#msg26332250</ref>

See the doc about sending them.<ref>https://github.com/byteball/byteballcore/wiki/Sending-textcoins</ref>

Now, any service that has email addresses of its users (that is, almost any service) can easily mass-pay them using just email addresses.

===Chatbots===
Textcoins are also easy to integrate with [[chatbot]]s. For example, a Telegram bot could reward its users for certain actions, e.g. for taking surveys or writing reviews.
===Email lists===
You can automatically send a different textcoin to everyone on an email list you have. Then claim back the ones unclaimed after 7 days, or whatever time you choose.

See the Medium article: Using MailChimp to mass send payments as textcoins<ref>https://medium.com/byteball-help/using-mailchimp-to-mass-send-payments-as-textcoins-5c1db06342e3</ref>

==Cashback==
The [[cashback]] program supports textcoins: merchants don't have to update their order forms to ask users about their Byteball address; instead they can give us the user's email address and we send a textcoin.

==Sending funds directly to email addresses==
You can attest an email address using the [[Chatbot#Email_attestation_bot|Email attestation bot]]. After this, anyone can send funds to your attested email address, and this will automatically be converted to the related single-address.<ref>https://medium.com/byteball/distribution-to-verified-emails-and-sending-cryptocurrency-to-email-episode-ii-cb955fe19d7e</ref>

==Batch creation of textcoins==
See https://github.com/byteball/headless-byteball/blob/master/play/create_textcoins_list.js.

==External links==
*[https://github.com/byteball/byteball/wiki/Cashback-API Updated API description]

==References==
<references />

[[Category:Features]]

Timestamp

2019-01-19T22:20:16Z

Punqtured: 1 revision imported

Different smart-contract uses for the timestamp oracle

==Oracle==
The [[oracle]] address is I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT and timestamps are in milliseconds since Jan 1, 1970 UTC.

==Notes==

===Tied-up funds===
The "offer a contract" options tie up the contract-writer's payment amount until the specified future time without possibility of recovery.

The bound-payment options allow either commitment as above, or the writer's voiding the contract and recovering his funds at any time before the payee collects them.

===Times===
There are three times that may be independently set by the contract-writer:

# The time after which, if the peer doesn't agree to and fund the contract, the writer can reclaim his funds ("offer a contract" option only)
# The time after which the writer/peer can unlock the contract
# The time after which the peer/writer can unlock the contract.

Note that after both (2) and (3) have taken place, either party will be able to spend the funds.

===Who peer pays ("offer a contract" option ONLY)===
Be careful in selecting who the peer pays, either to "me" or "the contract":

* With a bet, where the winner takes all, one would usually write "the contract"
* For a simple future payment, where the recipient must contribute a token amount, it doesn't matter
* But where the contract requires significant funds from both parties if it is executed, its proper non-execution must allow each party to get his funds back.

'''Note that the peer MUST pay, even the token amount, for the contract to be valid.'''

===Smart contract===
Both the "offer a contract" and the bound-payment option create a new smart contract. The writer can see this contract immediately, but the payee only after the oracle posts the specified time. Then the payee can unlock the contract; the writer can unlock the contract after the take-back time. Note that it will be possible for both parties to unlock the contract after the later of those two times.

Using the timestamp oracle like this must be done in paired wallet chat. It cannot be done using some random address pasted into a send-payment screen.

===Conversion===
Use a website like https://www.epochconverter.com to convert between Unix Epoch Time (e.g. 1498989599806) and human-readable date (e.g. GMT: Sunday, July 2, 2017 9:59:59.806 AM).

====Milliseconds====
Note timestamp is in milliseconds, with 13 digits. So if you are converting from date to epoch time remember to add “000” to the end if needed or the contract will fail. For example, six months from July 2, 2017 10:00 AM GMT is January 2, 2018, 10:00 AM GMT. A converter gives 1514887200, so to use the oracle you would change this to 1514887200000.

==A. Simple future payment using "offer a contract"==
This is a birthday present for a friend, 1.7 GBB that can be collected about 4 months from today (July 2) on Nov 5, 2017.

'''Left-click address (PQR...) sent by peer in wallet chat. Select "Offer a contract".'''

===1. PAYMENT TO THE CONTRACT===

'''I PAY:''' 1.7 GBB (can use any asset with sufficient funds) 
'''PEER PAYS:''' .01 MB (peer must pay something; here it is a token amount) 
'''PEER PAYS TO:''' this contract (peer gets payment back anyway) 
'''IF THE PEER DOESN'T PAY, I CAN TAKE MY MONEY BACK AFTER:''' 4 hours (leave as default, not important here as long as peer pays in time)

===2. WHO CAN UNLOCK THE CONTRACT?===
*the peer ''if an event is posted by an oracle:'' 
'''ORACLE ADDRESS:''' I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT 
'''DATA FEED NAME:''' timestamp (copy this name exactly) 
'''POSTED VALUE:''' >1509840000000 (MUST be 13 digits; this epoch time is Nov 5, 2017 00:00:00.000, about 125 days from today)

*me ''after contract expires in'' 
155 days (this particular time allows the peer 30 days to unlock the contract before the writer can reclaim the funds)

==B. Simple future bound payment==
This is a birthday present for a friend, 3 zwibs that can be collected about 4 months from today (July 2) on Nov 5, 2017.

'''Left-click address (PQR...) sent by peer in wallet chat. Select "Pay to this address".'''

===Choose main wallet / sub-wallet===
'''AVAILABLE BALANCE:''' 7 of ZW1b... (select asset to send) 
'''TO:''' PQR... (address is not user-changeable) 
Click link "Bind the payment to a condition" 
'''AMOUNT:''' 3 of ZW1b

===THE PEER RECEIVES THIS PAYMENT IF===
An event is posted by an oracle (select from drop-down menu) 
'''ORACLE ADDRESS:''' I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT 
'''DATA FEED NAME:''' timestamp (copy this name exactly) 
'''EXPECTED VALUE:''' >1509840000000 (MUST be 13 digits; don't forget the ">" (means "greater than"); this epoch time is Nov 5, 2017 00:00:00.000, about 125 days from today)

'''THE EXPECTED VALUE WILL BE POSTED:''' either way 
'''IF THE CONDITION IS NOT MET, I CAN TAKE THIS MONEY BACK AFTER:''' 3720 hours (= 155 days converted to hours. This particular time allows the peer 30 days to unlock the contract before the writer can reclaim the funds)

Click Send.

==Differences between A and B above==
*Both A and B require the recipient to provide a receive address. However, with A the recipient must ratify this particular contract by paying a token amount; while with B the writer does not need the peer's explicit permission this time.

*By setting the time close to now in the "if the condition is not met" field, B allows the writer to void the contract and recover his funds at any time before the expected payment date. This may or may not be desirable.

<hr />

==Request to benefactor using "offer a contract"==
This is a request to a rich aunt for 2 GB as a wedding present, that can be collected about 4 months from today (July 2) on Nov 5, 2017. It is useful because once funded it commits her to the payment, but prevents me from accessing the funds ahead of time.

'''Left-click address (PQR...) sent by peer in wallet chat. Select "Offer a contract".'''

===1. PAYMENT TO THE CONTRACT===
'''I PAY:''' .01 MB (I must pay something; here it is a token amount) 
'''PEER PAYS:''' 2 GB (peer must pay the exact amount; it is not user-changeable in the contract she will receive) 
'''PEER PAYS TO:''' this contract (just in case something happens to me in the meantime) 
'''IF THE PEER DOESN'T PAY, I CAN TAKE MY MONEY BACK AFTER:''' 4 hours (leave as default, not important here as long as peer pays in time)

===2. WHO CAN UNLOCK THE CONTRACT?===
*me ''if an event is posted by an oracle:'' 
'''ORACLE ADDRESS:''' I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT 
'''DATA FEED NAME:''' timestamp (copy this name exactly) 
'''POSTED VALUE:''' >1509840000000 (MUST be 13 digits; this epoch time is Nov 5, 2017 00:00:00.000, about 125 days from today)

*the peer ''after contract expires in'' 
150 days (this particular time allows me 25 days to unlock the contract before the benefactor can reclaim the funds)

==Exercising an option using "offer a contract"==
Normally one buys an option to buy/sell something at a particular price at a particular future time. One pays for the option, but neither party commits the funds now for the possible future transaction. However, with this smart contract the funds from the contract-writer are tied up in the contract until the peer exercises the option or the contract expires, although the contract-writer can void (and violate) the contract at any time before the peer funds the contract.

In the following contract, in exchange for a pre-contract payment to me of 1 MB, I grant the peer the option to buy 15 zwibs from me for 10 MB, starting in 24 hours from now and valid for 29 days only. Any wallet asset could have been used, and asset volatility may be significant.

===Details of figures used in this contract===
*Current date/time is 2017-07-02 1:40pm UTC
*"30 days" from now is, say, 2017-08-01 23:59:59.999 UTC
*017-08-01 23:59:59.999 UTC is from now 30 days 10 hrs 20 mins = 30 + 620/1440 days = 30.43 days = 730.3 hours (the take-back-if-no-peer-payment figure can only be set to the nearest .1 hours, or 6 minutes)
*Epoch time for 2017-07-03 1:40pm UTC is 1499089200000
*2017-08-01 23:59:59.999 UTC is from now 30 days 10 hrs 20 mins = 30 + 620/1440 days = 30.43 days (the contract expiry figure can only be set to the nearest .01 days, about 15 minutes)

'''Left-click address (PQR...) sent by peer in wallet chat. Select "Offer a contract".'''

===1. PAYMENT TO THE CONTRACT===
'''I PAY:''' 15 zwibs (can use any asset with sufficient funds) 
'''PEER PAYS:''' 10 MB (can use any asset with sufficient funds) 
'''PEER PAYS TO:''' me (NOT the contract) 
'''IF THE PEER DOESN'T PAY, I CAN TAKE MY MONEY BACK AFTER:''' 730.3 hours

===2. WHO CAN UNLOCK THE CONTRACT?===
*the peer, ''if an event is posted by an oracle:'' 
'''ORACLE ADDRESS:''' I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT 
'''DATA FEED NAME:''' timestamp (copy this name exactly) 
'''POSTED VALUE:''' >1499089200000 (MUST be 13 digits)

*me ''after contract expires in'' 
30.43 days

==Dead-man contract using a bound payment==
This is a simple contract that will execute unless terminated by the drawer. The idea is that one transfers an asset by default if unable to stop the transaction (maybe because one is dead).

Here I wish to allow the payee to unlock 50 GB any time after 3 months from now. The 3 months is a trade-off between one week -- meaning I would have to remember to reissue this contract every week -- and 6 months or more -- meaning if I died next week the payee would have to wait six months or more to access the funds.

Note that I can revoke/reissue this contract at any time.

===Details of figures used in this contract===
*Current date/time is 2017-07-02 5:00pm UTC
*"3 months" from now is, say, 2017-10-01 00:00:00.000 UTC
*Epoch time for 2017-10-01 00:00:00.000 UTC is 1506816000000

'''Left-click address (PQR...) sent at some prior time by peer in wallet chat. Select "Pay to this address".'''

===Choose main wallet / sub-wallet===
'''AVAILABLE BALANCE:''' XXX GB (select asset to send) 
'''TO:''' PQR... (address is not user-changeable) 
Click link "Bind the payment to a condition" 
'''AMOUNT:''' 50 GB

===THE PEER RECEIVES THIS PAYMENT IF===
An event is posted by an oracle (select from drop-down menu) 
'''ORACLE ADDRESS:''' I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT 
'''DATA FEED NAME:''' timestamp (copy this name exactly) 
'''EXPECTED VALUE:''' >1506816000000 (MUST be 13 digits; don't forget the ">" (means "greater than"); this epoch time is 2017-10-01 00:00:00.000 UTC, about 90 days from today)

'''THE EXPECTED VALUE WILL BE POSTED:''' either way

'''IF THE CONDITION IS NOT MET, I CAN TAKE THIS MONEY BACK AFTER:''' .1 hours (allows the writer to revoke/reissue the contract any time after 6 minutes from when the payment confirms)

Click Send.

==External links==

==References==

[[Category:Features]]
[[Category:Oracles]]

Tingos

2019-01-19T22:20:16Z

Punqtured: 3 revisions imported

[[File:Tingos-9000000.jpg|thumb|upright=0.65]] Tingos are a new [[asset|asset/token]] on the Byteball platform, designed to be easily spread around. Practise receiving them, sending them to others, making [[textcoin]]s with them, exchanging them with other assets in smart contracts, etc. It doesn't matter if you mess up somehow as they are worthless.

==It takes two to Tingo==
So spread them around! They have no monetary value, since there are enough for 9 billion people to have 1,000,000 each. You can always get more. They are like [[Zangos]] without decimal points.

There isn't much you can do with a wallet on a single device. But if you have separate (not multisig) wallets on two or more devices, maybe a laptop and a cellphone, you can pair them and execute smart contracts between them, which is excellent practice.

Each transaction will cost a regular transaction fee of 500-1000 bytes. If 1 GB = $1000, 1 MB = $1, 1 KB (1000 bytes) = 1/10 cent.

=== Change addresses ===
Be aware of [[change address]]es and how they work. The usual time you would first notice this is when you send some of your nice new Tingos to a friend and then cannot send any more anywhere for 5-10 minutes.

==Smart contract==
Here's how to use Tingos in a smart contract. Let's say you are exchanging 10,000 Tingos for 75 X's (KB, Tangos, whatever) with a peer. First, pair your devices.

===Pairing===
*One party gives the other a pairing code, either written out in full or via QR code. Generate this in Byteball wallet chat by clicking on "+ Add a new device" then "Invite the other device". It will look something like <code>A0dDO/XuMzELLq4r7F3/QMB3JOJQpbq40lAeCFdAX7yU@byteball.org/bb#0000</code>. The other party in Byteball wallet chat clicks on "+ Add a new device" then "Accept invitation from the other device" and pastes the pairing code into the almost-invisible line above the "pair" button.

===After pairing===
# In chat, peer sends you a receive address.
# You left-click the address, and click "Pay to this address".
# From the drop-down menu, select Tingos. Click "bind this payment to a condition". Use "I receive another payment" as the condition. Adjust the "take-back" time if you wish. Fill in the amount of 75 X's. Click "Bind payment".
# Fill in your payment amount of 10,000 Tingos and click Send. Or click Cancel if you were just trying it out.
# Peer reads the contract and if it's what was agreed, clicks Pay/Send. Done deal, both payments occur at once.

===Notes===
*See the new smart wallet by selecting it right at the top of the screen to the right of the main wallet's name.
*If you just received Tingos, then the smart wallet won’t have any (white)bytes in it yet to cover the sending fee. Click the Receive tab, copy the address, then paste it into the Send screen of your regular bytes wallet. Send maybe 5000 bytes to cover any possible transaction fee, then after you've moved the Tingos you can send the remaining bytes back to your main wallet.
*You can see the details of the smart (wallet) contract by clicking the little eyeball to the right of the smart contract home screen.
*Be careful to make payments from the correct wallet -- maybe you were looking in a smart wallet and forgot to get back into your main wallet.
*You may get an error message if the funds you are trying to send haven't confirmed yet.
*It is best not to send other payments in the 5-20 minutes while funding and waiting for execution of a smart contract. Additional payment notifications in the chat, and pending confirmations in the wallet home screen, can be confusing.

==New tokens in your wallet==
(Copied from [[Asset]])

You started off with 0 bytes in your wallet. Later, you probably got some bytes, and maybe some blackbytes. At present, maybe some Tingos and/or something else. If you click the Send tab, you'll see you a drop-down menu, and you can spend from any of your asset types.

Note that these listed asset/token types remain, even if the balance of one particular asset/token is zero. So every time someone receives some Bongos, the Bongo asset/token type gets added to their wallet asset/token list, indelibly so for now. After a few of these, if you don't really want them, they act as spam.

So, please don't send your new assets/tokens to someone without asking them first if they want them.

==Differences between Tingos and Tangos==
* There are 10^15 Tangos and 9 x 10^15 Tingos
* Ummm...

==Definition==
Source<ref>https://explorer.byteball.org/#O1DbJWbZJfKhjZQYH5RrdRQ2ojMuo2WiaKbjIWSWd4E=</ref> 
cap: 9,000,000,000,000,000 
is_private: false 
is_transferrable: true 
auto_destroy: true 
fixed_denominations: false 
issued_by_definer_only: true 
cosigned_by_definer: false 
spender_attested: false

==Registry publication==
Source<ref>https://explorer.byteball.org/#ZWKx0ghzXxKkaSLH3jAAaqogCmmLIq7B7YXnocxjW7U=</ref> 
asset: O1DbJWbZJfKhjZQYH5RrdRQ2ojMuo2WiaKbjIWSWd4E= 
decimals: 0 
name: Tingos by Jore Bohne 
shortName: Tingos 
issuer: Jore Bohne 
ticker: TINGO 
description: Like Tangos, they have zero monetary value, and are for zero-risk practice with textcoin, smart contracts, and other Byteball features.

==External links==
[https://byteball.market Byteball Asset Manager (to order your own tokens/assets)]

==References==
<references />

[[Category:fun-coins]]
[[Category:tokens]]

Token

2019-01-19T22:20:16Z

Punqtured: 11 revisions imported

'''"Asset" in financial community = "token" in non-financial community.''' The words '''asset, coin, currency''' and '''token''' are all synonymous here to some extent, in that each refers to funds on the Byteball platform.

There is much covered in the [[Asset]] article that also applies to tokens, such as creating and naming them. This article's emphasis is on tokens with zero or tiny monetary value, rather than those used more financially.
[[File:Alan-unclejoe-1.jpg|thumb]]

==Why use tokens?==
What advantages do Byteball tokens have over existing systems, like paper notes, plastic tokens, "indelible" ink on a user's skin (think a rock concert pass)?

*'''Ease of creation:''' Anyone can [[Asset#Byteball_Asset_Manager|create]] as many identical tokens as needed, at low cost, without a long learning curve, with no third-party permission needed.
*'''Ease of use:''' At least, in a community where people normally carry and use smartphones. This includes '''remote''' use, not simply face-to-face. All "payees" can be kept in the wallet's "address book" for one-click availability.
*'''Transparent use:''' The token creation, and all token movements/transactions can be seen by anyone in Explorer.
*'''Documented use:''' Your wallet's [[Tab#History|history]] records the exact times and amounts of all your token transactions.
*'''Certainty of transaction:''' Like any cryptocurrency, sending any token(s) to an address is irrevocable.
*'''Verifiability:''' There's no way one can counterfeit a real platform token. Similarly, the correct token is easy to recognize in the community using it.
*'''Programmable use:''' At a minimum, one's token can be used with Byteball's default [[Chatbot|bots]], smart contracts and [[Oracle#Personal_oracles|personal oracles]], not merely sent and received.
*'''High-tech:''' For optics, if that is important to you. It all looks cutting-edge, rather than 20th Century or even earlier.

==Token types==
There are five main token types in Byteball. Each is created and named/registered in the same way, but they have different uses. There are also tokens made with no purpose in mind deeper than simply making them.

===Fun-coins===
[[Fun-coins]] deliberately have zero monetary value because they exist in vast quantity. They are intended mainly for practice with smart contracts, [[textcoin]]s, or other Byteball features, where it doesn't matter if you mess up and lose them somehow.

===Family tokens===
[[Family tokens]] use a single token. The family can obtain 1000 generic tokens, "Credits by Jore Bohne", immediately and free of charge from the [[Fun-coins#faucet|fun-coins faucet]] in their wallet's Bot Store. Or they can create a personalised one, say "Joys by Jill Smart", with a bit more effort. They are used in a family token/reward system, designed to improve kids' behaviour.

===Social tokens===
[[Social tokens]] use either a single token or a very small number. The Social Tokens system is basically Family Tokens for grown-ups.
As with Family Tokens, the general idea is to improve the group by rewarding good behaviour, both individually and in groups.

===Personal tokens===
[[File:Social-tokens-1.jpg|thumb]] [[Personal tokens]] are intended for use in a local community, maybe a high school or club, where the people involved tend to know each other. These are tokens backed by real-world goods and services that the issuer will provide on demand. The issuer should honour his or her token, whoever presents it for payment.

===Commercial tokens===
[[Commercial tokens]] on the Byteball platform would be used by businesses in a local community. They function in the same way as discount or rebate coupons, usually distributed in print either separately or on a newspaper page; online to be printed out at home by the consumer; or sent directly to a consumer's mobile phone.

==Rapid distribution==
This needs some preparation. Let's look at a family scene. Mom and Dad and the two kids Jane and Bobby are sitting around the kitchen table. The kids are all excited, holding their new smartphones. Mom has new "Fam" tokens and enough bytes for transaction fees. Jane taps her Receive tab to display the QR code, Mom sends her 10 Fams. After a second it shows up on her phone. Woohoo! Bobby displays his QR code, Mom sets up the 10-Fam transaction, taps Send, and gets an error message. Bobby reacts adversely.

What happened? Normal [[Change_address|change-address]] behaviour. After 5 or 10 minutes, Mom will be able to make the transaction. The same would happen with giving the kids Bytes. Overall, not ideal. How to fix?

===Preparation===
Before the family meeting, Mom goes into another wallet, and sends to her family-tokens wallet two transactions:
*A [[Send#Switch_to_multi-address|multi-address]] transaction of 3x 100 Fams (the 100 is arbitrary)
*A multi-address transaction of 6x 55,000 Bytes (the 55,000 is arbitrary)

After those two transactions have confirmed, they have the family meeting. Mom will be able to rapidly send three transactions of 100 Fams each (plus the transaction fees), and three transactions of 50,000 Bytes each. Result? Everyone gets their tokens and Bytes promptly.

===Other cases===
The principle is the same for any gathering. At a meet-up, maybe the Byteball guy expects to distribute 999 Tangos and 100,000 Bytes to each of 15 people, 30 transactions in all. So he will need to send to his funding wallet:
*A multi-address transaction of 15x 999 Tangos
*A multi-address transaction of 30x 101,000 Bytes to cover 30 transaction fees and 15 100,000-Byte payloads

The 30x 101,000 Bytes is for safety. It should be possible to have 15x 100,000 Bytes for the Byte payloads and 30x 1000 Bytes for the transaction fees, but if the wallet gathers together all 30 1000-Byte inputs to make up part of one 100,000 Byte transaction then one's plan will fail.

==Grass roots==
Byteball adoption will always be helped by one Byteball fan '''using''' the platform tokens (Fun-coins, Family Tokens, Social Tokens, Commercial Tokens) etc with their friends and family, and not just sitting on their GBytes wishing the price would go up more.

==See also==

==References==

[[Category:Browse]]
[[Category:Tokens]]

Trading

2019-01-19T22:20:16Z

Punqtured: 5 revisions imported

Buying GBytes on exchanges; exchanging GB and GBB or bytes and blackbytes; betting on external events using oracles; and more.

==Betting on external events==

===Prediction markets===
The Byteball platform currently supports:

*[[Sports betting]] on upcoming soccer matches
*Gambling on random numbers
*Betting on crypto exchange rates
*Betting on flight delays.

See the wiki [[Trading prediction markets]] article for details.

==Buying GB on exchanges==

===External exchanges===
You can buy GBytes on various external exchanges. Some allow fiat but others are BTC/altcoins only.

'''Bittrex:'''<ref>https://bittrex.com</ref> Crypto only; recently changed (lower) withdrawal limits; KYC/AML all users. It's a good idea to check wallet status for particular cryptos here<ref>https://bittrex.com/Status</ref>.

'''Upbit:'''<ref>https://upbit.com</ref> [Korean]

'''Cryptochangex:'''<ref>https://cryptochangex.com</ref> New, announced 2017-11-05, UK company. Owned by s1lverbox, well-known trader on bitcointalk and Byteball Slack.

'''Cryptox:'''<ref>https://cryptox.pl</ref> Crypto only. Rather small, but generally OK

'''Cryptopia:'''<ref>https://cryptopia.co.nz</ref> Crypto only; site is more than a simple exchange

'''Changelly:'''<ref>https://changelly.com/exchange/btc/gbyte</ref> Accepts Visa/MC and cryptos. The exchange used by the Byteball-Altcoin Exchange Bot (see the wiki article [[Chatbot]])

'''Bitsquare:'''<ref>https://bitsquare.io</ref> Decentralized! National currencies and cryptos

<hr />'''YDX:'''<ref>http://www.iotaexchange.com/#details</ref> It allows you to trade certain coins in a semi-automated way via Slack, and supports GB and even GBB.

====Exchange volume====
*Bittrex 80-98%
*Cryptox 20-2%
*Cryptopia 0-2%

Use Coinmarketcap<ref>https://coinmarketcap.com/currencies/byteball/#markets</ref> for latest figures.

====Exchange fees====
{| class="wikitable"
|-
! Exchange/Fee !! Maker !! Taker !! Withdraw
|-
| Bittrex.com || 0.25% || 0.25% || 2 MB
|-
| Cryptox.pl || (-0.1%) || 0.20% || 2 KB
|}

===''Byte-BTC Exchange''===
There is an '''in-wallet chatbot''' that provides a book for users, but currently [2018-01-07] there seems to be a problem with underpaid btc transaction fees.

===Peer-to-peer Byte-BTC exchange===
'''This one is complex. It is hard for the buyer to verify from reading it that the contract will perform as the buyer expects: maybe the seller is dishonest and made a subtle change in the details.'''

Let's say you want to sell Gbytes to a peer who's paying in BTC. You've agreed the amounts, say .121 BTC for 1 GByte. Let's say your bitcoin receive address is 1MJ7xew1X13okNYKRu7qA3uN4hpRH1Tfpq. You and the buyer pair wallets. The buyer sends you in wallet chat his Byteball receive address, say "5GU...".

You left-click that address, choose "Pay to this address", and in the next screen enter the amount (here 1 GB), the address "5GU...", then just below this address click "Bind the payment to a condition". This opens the next screen.

Under THE PEER RECEIVES THIS PAYMENT IF click the little down arrow, and click "An event is posted by an oracle". This opens the next screen.

Under ORACLE ADDRESS paste
<code>FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH</code>

Under DATA FEED NAME paste
<code>bitcoin_merkle</code>

Under EXPECTED VALUE paste your bitcoin address and the exact amount you are expecting, in the form "address:amount":
<code>1MJ7xew1X13okNYKRu7qA3uN4hpRH1Tfpq:0.121</code> (in this example)

Under THE EXPECTED VALUE WILL BE POSTED click the little down arrow, and click "in merkle tree".

Change the "4" hours to some other figure if you wish. Click SEND PAYMENT. This will return you to the first payment screen and allow you to double-check the amount. Finally click SEND.

The wallet chat will show that your payment (for 1GB here) has been sent. Once this payment has confirmed, after maybe 5-10 minutes, the buyer will automatically get a copy of the smart contract/wallet. The buyer can see it by exiting the wallet chat, going to the home screen, clicking on "smart wallet", and then in the smart wallet home screen clicking on the little eyeball on the right.

The buyer must read the contract carefully, to ensure that it specifies the correct bitcoin address and the correct amount. Otherwise a dishonest seller would be able to receive both the bitcoin payment (sent to a different address that had been passed over) and reclaim the bytes after 4 hours as the expected bitcoin_merkle would not get generated. Also the correct oracle address and data feed name.

After two confirmations, the buyer needs to get the "merkle proof" (just a long string of data) of this transaction. A merkle proof can be obtained (after two or more confirmations) from the BTC oracle at byteball:A7C96Bhg4Gpb2Upw/Ky/YfGG8BKe5DjTiBuJFGAX50N1@byteball.org/bb#0000.

The buyer then copies and pastes in this proof to unlock the bytes payment from the smart contract.

==Slack trading GB and GBB==
You can't buy blackbytes at an exchange like Bittrex, but you can find sellers and buyers in the Slack Byteball #trading_blackbyte channel. How to do the trade is covered in the wiki article [[Trading blackbytes]].

==Merchant chatbots==
There are no known mainnet ones yet.

==External links==

==References==
<references />

[[Category:Browse]]
[[Category:Trading]]

Trading blackbytes

2019-01-19T22:20:16Z

Punqtured: 1 revision imported

How to buy or sell blackbytes in the wallet using conditional payments

==Definitions==
See the [[glossary]] if needed for definitions of "blackbytes" etc.

==Bots==
See [[Blackbytes#Bots]] for info on three blackbytes trading bots.

==Peer-to-peer actions to do==

===The Slack #trading_blackbyte channel===
Post "otc". This will automatically show the available bot commands. Post "asks" and "bids" to show the available offers and bids. Let's say you want to buy 40 GBB for 1GB. Post "bid 1 40". Assuming you used the correct format, the bookbot will respond "OK". Then post "bids" to check that your bid is actually what you wanted to post. When you want to remove your bid, post "remove bid" and if you did that correctly the bot will comply and post "OK". Similarly for asks.

You need to find someone willing to sell/buy at your price. You might need to come down a bit. You might need to haggle. You can try DMing possible traders listed in the book. Some of the entries are outdated.

First, buyer and seller agree on amounts using some messaging channel such as Slack, email, even face to face.

===After agreeing the terms===
#One party gives the other a pairing code, either written out in full or via QR code. Generate this in Byteball wallet chat by clicking on "+ Add a new device" then "Invite the other device". It will look something like <code>AhHPXCpCSTzD1CF53ELGTAsZ6MCA8Ogvk+koyibfPt/2v@byteball.org/bb#GxVBizZ2DSEf</code>. The other party in Byteball wallet chat clicks on "+ Add a new device" then "Accept invitation from the other device" and pastes the pairing code into the almost-invisible line above the "pair" button.
#Say hi etc to establish communication with the other party in the Byteball chat window. If needed, change the units in Settings to be close to your trade quantities. In other words, if you're going to send 40 MB, don't input it as .04 GB or 40000 KB. In the heat of the moment it's easy to miscount the number of zeros.
#'''WARNING: DO THE NEXT STEPS EXACTLY! DON'T SEND AN ADDRESS TO BE CLICKED ON! DON'T DEVIATE FROM STEPS 4, 5, 6 IN SEQUENCE OR YOU'LL SCREW IT UP! THIS WARNING IS IN BOLD CAPS -- HEED IT!'''
#'''Buyer of GBB sends payment request''' (click on ". . ." to the left of the message text field) to seller, say for 40 GBB. -->Chat shows '''payment request''' from buyer for 40 GBB
#Seller clicks on the payment request for 40 GBB and sends 40 GBB to smart wallet, binding it to the condition of receiving a payment of 1.0 GB (for example). '''Make sure you bind it to the condition''', not simply send it without binding. -->Chat shows '''payment request''' from seller for 1.0 GB -->Chat shows '''payment''' from seller of 40 GBB
#Buyer clicks on the payment request for 1.0 GB and sends payment for 1.0 GB. -->Chat shows '''payment''' from buyer of 1 GB
#Done deal. Wait for confirms, and if both parties happy end off the chat. Now go to the smart wallet, and send the funds to your main wallet.

==Notes==
*The new smart wallet won't show up until the payments confirm after 5 minutes or so.
*If you just bought blackbytes then the smart wallet won’t have any (white)bytes in it yet to cover the sending fee. Click the Receive tab, copy the address, then paste it into the Send screen of your regular bytes wallet.
*You can see the details of the smart (wallet) contract by clicking the little eyeball to the right of the smart contract home screen.
*Be careful to make payments from the correct wallet -- maybe you were looking in a smart wallet and forgot to get back into your main wallet.
*You may get an error message if the funds you are trying to send haven't confirmed yet.

[[Category:Features]]
[[Category:Trading]]

Sports betting

2019-01-19T22:20:15Z

Punqtured: 20 revisions imported

Make sports bets peer-to-peer or through the [[Chatbot#Betting_bot_.28Semi-trustless.29|betting bot]].

==Sports betting on Byteball==
Byteball allows you to safely bet on sporting events by making a conditional payment that depends on a match result posted into the DAG by a third party (called the ''sports oracle''). It’s one of easiest ways to bet using a cryptocurrency.

In March 2018 these professional leagues and championships were available for betting:

*Basketball: NBA (US National Basketball Association)
*Baseball: MLB (US Major League Baseball)
*Ice hockey: NHL (US National Hockey League)
*American football: NFL (US National Football League)
*MMA: UFC (Mixed Martial Arts: Ultimate Fighting Championship)
*Soccer: Champions League (EU), Ligue 1 and 2 (France), Premier League (UK), Primera División (Spain), Bundesliga 1 and 2 (Germany), Brasil Série A (Brazil), Primeira Liga (Portugal), Italian Serie A and B (Italy), League One and Two (UK), Eredivisie (Netherlands), World Cup, European Cup.

The sports oracle is operated by the Byteball lead developer. You can check the source code on Github.<ref>https://github.com/byteball/sports-oracle</ref>

There are two ways to bet on sport with Byteball:
*(Harder) Completely P2P with someone that paired his wallet with yours. See [[#P2P_betting]]
*(Easier) Using the sports betting bot that acts as a betting marketplace and facilitates making the [[smart contract]]s. See [[#Betting_bot]]

==P2P betting==
To make a bet P2P you need to be in contact with someone that is willing to bet with you. You will both send to a smart-address an amount of bytes corresponding to the odds you have negotiated. Depending on the result, one of you will collect the total amount staked.

===Get the feedname===
[[File:zzbetbot-1.jpg|thumb|upright=0.55]]
First you need to obtain the feedname of the desired fixture. This feedname will then be used in the contract you draw up. To get this feedname from the sports-oracle bot, follow these steps:

# Click on: <code>Chat > Bot Store > Sports oracle > open chat</code>
# Click on the championship corresponding to the desired fixture
# Click on: <code>coming</code> fixture
# Click on the desired fixture
# The bot will give you a feedname similar to <code>BROOKLYNNETS_CHARLOTTEHORNETS_2018-03-21</code>. Copy and paste it somewhere (in your Notepad, for example) to keep it to hand.

===Pair with your peer===
In order to execute a [[smart contract]] (called ''conditional payment'' in this case), you have to be paired with your peer/counterparty.

# Click on: <code>Chat > Contacts > + Add a new device > Invite the other device</code>
# Copy the pairing code and send it to your peer
# Your peer has to click on: <code>Chat > Contacts > + Add a new device > Accept invitation from the other device</code>, and paste the received code.

You’re now in an encrypted chat with your peer and will be able to propose to him a conditional payment,

===Propose the conditional payment===
# Ask your peer to insert his address: he clicks on the 3 dots (…) at the bottom left, clicks on <code>Insert my address</code>, then sends it
# You then left-click on his address and choose <code>Offer a contract</code>.

[[File:zzbetbot-2.jpg|thumb|upright=0.70]]
The contract is self-explanatory and describes the precise conditions under which you or your peer can take the funds staked.

You have to:
# Select <code>Sports betting</code> as oracle
# Paste the feedname obtained previously from the Sports oracle, for example: <code>BROOKLYNNETS_CHARLOTTEHORNETS_2018-03-21</code>

To bet on one team winning, for example Charlotte Hornets:
# Select <code>=</code> as the logic operator
# Use that exact team name as the <code>expected value</code>, namely <code>CHARLOTTEHORNETS</code>.

To bet on one team not winning (i.e., lose or draw), for example Charlotte Hornets:
# Select <code>|=</code> as the logic operator
# Use that exact team name as the <code>expected value</code>, namely <code>CHARLOTTEHORNETS</code>.

====Notes====
* On the third field, <code>take my money back after ___ hours</code>, the time-out should be set before the beginning of the fixture otherwise your peer would have an unfair advantage in deciding to fund or not fund the contract.

* On the last field, <code>after it expires in ___ days</code>, set a time at least 3 days after the fixture in case the oracle delays in posting the result.

* If the fixture is canceled or moved to a different day, the oracle will never post the feedname and the contract condition won’t happen. You have to consider the bet as a "show and win/not win" and the negotiated odds should consider that. If you want both parties to get a refund as they would with a casual bookmaker, then better use the betting bot as it offers a more elaborate contract.

====Send the contract====
When your contract is set up as you wish, send it. Your peer will get a payment request that shows him all the terms of the contract. The bet will be active after he has paid his share to it. If he won’t pay, you can get your stake back after the time in the <code>take my money back after ___ hours</code> field.

===Getting the payout===
The sports oracle usually posts the result six hours after the fixture. It will send you a notification when the result is posted in the DAG and the payout is available.

If the posted result matches the condition set, you can get the payout immediately. If not, the peer has to wait until the end of the expiry time-out to get paid.

Getting the pay-out is done by moving the stakes from the smart address to one of your main addresses. To do it, go to your wallet [[Tab#Home|Home]] and select the sub-wallet corresponding to the bet (click on wallet middle-top). Then click on [[Send]] and make a transaction that sends all the stakes to your main wallet. If the stakes are other than bytes, you will need to send bytes to the sub-wallet to cover the transaction fee. After the confirmation time, your funds will be available in your main wallet and ready to be spent.

==Betting bot==
This [[Chatbot#Betting_bot_.28Semi-trustless.29|chatbot]] is a marketplace where gamblers and bookmakers can meet. It is divided into two modes:

* '''Taker mode:''' This is the default mode which allows a gambler to place a bet with only a few clicks. A human-readable smart-contract is proposed so the gambler doesn’t have to trust the bot. The result is given by a third-party (the Sports oracle) and it is possible to get the payout even if the bot goes down.

* '''Maker mode:''' This is a more advanced mode for people wanting to earn bytes by acting as bookmakers. The bookmaker sets odds to be proposed for the fixtures of his choice. Then the bot proposes a smart-contract for gamblers willing to take the offered odds.

===Pairing with the chatbot===
In order to use the betting bot, you need to pair with it. To do so, click on: <code>Chat > Bot Store > Betting bot (Semi-trustless) > Open chat</code>. Once paired you can access it at any time from <code>Chat > Contacts</code>.

===Selecting a bet===
[[File:zzbetbot-3.jpg|thumb|left|upright=0.57]]
In the welcome text, the chatbot shows the best odds available for the upcoming fixtures. They are classified by time and you can browse them by clicking on <code> next >></code> or <code><< previous</code>.

It’s possible to filter by sport by clicking on one of the sport icons: Apply filter: 🏀 - ⚾ - ⚽ - ❄ - 🏈 - 👊.

If you don’t find the fixture you want, you may look again a few hours before it starts since most bookmakers tend to propose their odds then in order to not tie up their funds for a long time.

For every sport but soccer, two odds are shown. The first is the decimal odds for the home team winning, the second is the decimal odds for the away team winning.

For soccer three odds are shown, the middle one being the decimal odds for a draw.

If n/a appears instead of odds, it means that no odds have been set for this outcome and so it’s not possible to bet. You might consider coming back later since most bookies propose their odds only a few hours before the fixture.

[[File:zzbetbot-4.jpg|thumb|left|upright=0.57]] Once you have clicked on the desired odds, the bot indicates what the payout would be based on the amount of your stake. Since the bot selects the best offers from the different bookmakers, the resulting odds can decrease as long as the stake increases. You can click directly on a suggested amount, or you can type the precise amount you want to stake. After you’ve inserted your address into the chat as requested, you will immediately see a payment to a smart-address corresponding to your potential gain and you will be asked to pay your share to the bet.

===Paying the bet===
Click on the payment request. A human-readable smart-contract will be shown. Scroll down, then click on <code>Send payment</code>. The bot will notify you that your payment is pending, and again some minutes later when it is confirmed.

===Getting the payout===
[[File:zzbetbot-5.jpg|thumb]]Usually six hours after the fixture, the result will be posted into the DAG by the oracle and the contract will be unlockable by one of the parties. The bot will register when the result is posted. It will notify you of the result: if you have won you will be invited to collect your winnings from the shared address.

As before, getting the pay-out is done by moving the stakes from the smart address to one of your main addresses. To do it, go to your wallet [[Tab#Home|Home]] and select the sub-wallet corresponding to the bet (click on wallet middle-top). Then click on [[Send]] and make a transaction that sends all the stakes to your main wallet. After the confirmation time, your funds will be available in your main wallet and ready to be spent.

If you lost the bet, you don't need to do anything. The bot will collect all the bytes and the shared-address is not shown anymore in your wallet.

If the fixture is canceled or postponed, the oracle won’t post the feedname used by the contract. In such a case the contract allows the bot to collect the bytes five days after the fixture, and it will refund both parties.

===Odds displayed on a website===
There is a website, which shows [https://bb-odds.herokuapp.com/ all the Betting bot odds]. It also has a odds converting tool, so you can see the odds in fractional (British) and moneyline (American) format, additionally to original decimal (European) format.

==External links==
* https://github.com/Papabyte/betting-bot-API

==References==

[[Category:Chatbots]]

Statistics

2019-01-19T22:20:15Z

Punqtured: 3 revisions imported

Global Byteball statistics

==Byteball price==
See Coinmarketcap<ref>https://coinmarketcap.com</ref> for current price, price graphs, [[market capitalization]], and other useful info.

==Transaction volume==
See https://byteball.fr/heartbeat.php for 12-hour snapshot, updated hourly, and historical graphs. Example:

<pre>
Current 12 hours snapshot:
Total active Witnesses 15
Total units posted 3402
Total stables units 3390
Total users units (Witnesses posts excluded) 544
Multisigned addresses units 1
Smart Contracts units 54
Total users payload (in bytes) 128,020
All time Verified Users (at jumio.com) 439
All time Non US Verified Users 290
</pre>

==External links==
https://byteball.fr/heartbeat.php

==References==
<references />

[[Category:Browse]]

Tab

2019-01-19T22:20:15Z

Punqtured: 3 revisions imported

There are five main tabs in the group: Home, Receive, [[Send]], History differ for each individual wallet; and Chat is common across all your wallets.

==Home==
The different features for '''this''' wallet, '''this''' currency. Note that the main menu (top left) shows:
* The version number
* Each separate main wallet in the wallet group
* ADD WALLET Create a new wallet
* PAIRED DEVICES Co-signers for multisig
* SETTINGS Global preferences

{| class="wikitable" style="text-align: center;"
|-
! Left !! Center !! Right
|-
| Main/"Hamburger" menu || Name of Main wallet, with a drop-down menu for sub-wallets (smart wallets) || Button for camera to scan QR codes
|-
| colspan="3" style="background-color: #e1f5fe"|Wallet balance, for example 71.305 MB
|-
| colspan="3" style="background-color: #e1f5fe"|Value in USD if bytes/blackbytes
|-
| colspan="3" style="background-color: #e1f5fe"|Also [balance] in smart wallets {link}
|-
| colspan="3" style="background-color: #e1f5fe"|ooooo (radio buttons, one for each currency you have)
|-
|style="background-color: #e1f5fe"|First letter of name || Wallet name If Smart Wallet, address <code>7CWV4...</code> || Cogwheel menu
|-
| colspan="3"| 
|-
| colspan="3"| 
|-
| colspan="3"| 
|-
| colspan="3"| 
|-
|colspan="3"|Tabs for Home | Receive | Send | History | Chat
|}

==Receive==
Shows the QR code for your current Receive address. Click the "Generate new address" button to get a new one. These addresses don't expire: you can still receive payments to a previous address if you have generated new ones. Note that the same Receive address can be used for more than one currency: Bytes, [[Fun-coins|Tangos]], [[Asset|TitanCoins]], [[Social_tokens|"Kisses by Sarah Sweetbrush"]], whatever.

===Request a specific amount===
This will generate a special QR code that will automatically fill in the amount field in the payer's Send screen with the amount you specify. Note it only works with bytes (and MB etc), and no other currency.

===Claim funds using textcoin===
Fill in the 12 seed words separated by dashes to import the funds from a textcoin.

==Send==
See [[Send]] article.

==History==
Shows each transaction, sent or received, latest on top. Note this history is only for the currency selected in your Send screen. So if you have five currencies there will be five different histories.

Click on a transaction for more details.

===Detailed view===
*+/- [Amount]
* (If sent by you) To Address
* (If received by you) From Address, To (your) Address
* To email (if sent to an attested email)
* Date/time
* (If sent by you) Fee [for example, 588 bytes (=$0.00013)]
* Unit number (this links to the transaction on Explorer)
* Finality (Confirmed or Unconfirmed)

==Chat==
Divided into Contacts and Bot Store.

===Contacts===
Shows, in alphabetical order along with their device number, all the devices your wallet is paired with, with which you can:
* have end-to-end-encrypted chat
* create and execute smart contracts.

At the bottom of the list are links for:
* Add a new device
* Remove a device.

===Bot Store===
See [[Chatbot]] article for a list and description of the available bots.

[[Category: Browse]]

Tangos

2019-01-19T22:20:15Z

Punqtured: 4 revisions imported

[[File:Tanger-3456789.jpg|thumb|upright=0.66]] Tangos are a new [[asset|asset/token]] on the Byteball platform, designed to be easily spread around. Practise receiving them, sending them to others, making [[textcoin]]s with them, exchanging them with other assets in smart contracts, etc. It doesn't matter if you mess up somehow as they are worthless.

==It takes two to Tango==
So spread them around! They have no monetary value, since there are enough for 8 billion people to have 125,000 each. You can always get more. They are like [[Zingos]] without decimal points.

There isn't much you can do with a wallet on a single device. But if you have separate (not multisig) wallets on two or more devices, maybe a laptop and a cellphone, you can pair them and execute smart contracts between them, which is excellent practice.

Each transaction will cost a regular transaction fee of 500-1000 bytes. If 1 GB = $1000, 1 MB = $1, 1 KB (1000 bytes) = 1/10 cent.

=== Change addresses ===
Be aware of [[change address]]es and how they work. The usual time you would first notice this is when you send some of your nice new Tangos to a friend and then cannot send any more anywhere for 5-10 minutes.

==Smart contract==
Here's how to use Tangos in a smart contract. Let's say you are exchanging 10,000 Tangos for 75 X's (KB, Zingos, whatever) with a peer. First, pair your devices.

===Pairing===
*One party gives the other a pairing code, either written out in full or via QR code. Generate this in Byteball wallet chat by clicking on "+ Add a new device" then "Invite the other device". It will look something like <code>AhHPXCpCSTzD1CF53ELGTAsZ6MCA8Ogvk+koyibfPt/2v@byteball.org/bb#GxVBizZ2DSEf</code>. The other party in Byteball wallet chat clicks on "+ Add a new device" then "Accept invitation from the other device" and pastes the pairing code into the almost-invisible line above the "pair" button.

===After pairing===
# In chat, peer sends you a receive address.
# You left-click the address, and click "Pay to this address".
# From the drop-down menu, select Tangos. Click "bind this payment to a condition". Use "I receive another payment" as the condition. Adjust the "take-back" time if you wish. Fill in the amount of 75 X's. Click "Bind payment".
# Fill in your payment amount of 10,000 Tangos and click Send. Or click Cancel if you were just trying it out.
# Peer reads the contract and if it's what was agreed, clicks Pay/Send. Done deal, both payments occur at once.

===Notes===
*See the new smart wallet by selecting it right at the top of the screen to the right of the main wallet's name.
*If you just received Tangos, then the smart wallet won’t have any (white)bytes in it yet to cover the sending fee. Click the Receive tab, copy the address, then paste it into the Send screen of your regular bytes wallet. Send maybe 5000 bytes to cover any possible transaction fee, then after you've moved the Tangos you can send the remaining bytes back to your main wallet.
*You can see the details of the smart (wallet) contract by clicking the little eyeball to the right of the smart contract home screen.
*Be careful to make payments from the correct wallet -- maybe you were looking in a smart wallet and forgot to get back into your main wallet.
*You may get an error message if the funds you are trying to send haven't confirmed yet.
*It is best not to send other payments in the 5-20 minutes while funding and waiting for execution of a smart contract. Additional payment notifications in the chat, and pending confirmations in the wallet home screen, can be confusing.

==New tokens in your wallet==
(Copied from [[Asset]])

You started off with 0 bytes in your wallet. Later, you probably got some bytes, and maybe some blackbytes. At present, maybe some Tangos and/or something else. If you click the Send tab, you'll see you a drop-down menu, and you can spend from any of your asset types.

Note that these listed asset/token types remain, even if the balance of one particular asset/token is zero. So every time someone receives some Bongos, the Bongo asset/token type gets added to their wallet asset/token list, indelibly so for now. After a few of these, if you don't really want them, they act as spam.

So, please don't send your new assets/tokens to someone without asking them first if they want them.

==Differences between Tingos and Tangos==
* There are 10^15 Tangos and 9 x 10^15 Tingos
* Ummm...

==Definition==
Source<ref>https://explorer.byteball.org/#0Qki2BWSJ80dMN58Dq1rrJugaYyFndxkZloLJby+olU=</ref> 
cap: 1,000,000,000,000,000 
is_private: false 
is_transferrable: true 
auto_destroy: true 
fixed_denominations: false 
issued_by_definer_only: true 
cosigned_by_definer: false 
spender_attested: false

==Registry publication==
Source<ref>https://explorer.byteball.org/#ammQoP5B+hpm5wX2EVjro6WGLVDePxUoxXAMhIKq5yE=</ref> 
asset: 0Qki2BWSJ80dMN58Dq1rrJugaYyFndxkZloLJby+olU= 
decimals: 0 
name: Tangos by Jore Bohne 
shortName: Tangos 
issuer: Jore Bohne 
ticker: TANGO 
description: A token of no monetary value to practise with, to be spread around, not worth hoarding because there are so many of them.

==External links==
[https://byteball.market Byteball Asset Manager (to order your own tokens/assets)]

==References==
<references />
[[Category:Fun-coins]]
[[Category:Tokens]]

Smart contract

2019-01-19T22:20:13Z

Punqtured: 5 revisions imported

[[File:smart-address-1.jpg|thumb|upright=0.65]][[File:smart-address-2.jpg|thumb|upright=0.65]]About smart contracts, the basis of conditional payments ("smart payments"), Byteball's killer feature. And "the competition". Not too technical

==Contracts. Ethereum, right?==

'''Byteball''' does '''simple''', human-readable contracts to perform simple actions.

'''Ethereum''' does '''complex''', programmer-readable contracts to perform complex actions.

No overlap.

===But Rootstock?===
Rootstock is a centralized smart-contract platform planned to be layered on top of Bitcoin. RSK is just released on Bitcoin testnet.<ref>https://www.reddit.com/r/Bitcoin/comments/6e7mdz/rsk_testnet_is_open/?st=j3bxt1g7&sh=63cbb552 Reddit thread 2017-05-30</ref>

One post: RSK is EVM on BTC (that is, Ethereum Virtual Machine infrastructure, but linked to and secured by bitcoin's blockchain instead, using sidechains.)

RSK is now supported on Trezor.<ref>http://gk2.sk/how-to-use-trezor-with-rootstock-rsk-using-myetherwallet Online article 2017-05-30</ref>

==Offering smart contracts==
When you want to create a new smart contract with a user, your sequence is usually as follows:<ref>https://github.com/byteball/byteballcore/wiki/Writing-chatbots-for-Byteball Github: Writing chatbots for Byteball</ref>
# You ask the user to send his payment address (it will be included in the contract)
# You define a new contract using the user's address and your address as parties of the contract
# You pay your share to the contract
# At the same time, you send a specially formatted payment request (different from the payment request above) to the user to request his share. You start waiting for the user's payment
# The user views the contract definition in his wallet and agrees to pay
# You receive the payment notification and wait for it to get confirmed
# After the payment is confirmed, the contract is fully funded.

See wiki [[Oracle]] article for examples and [[videos]].
{{clear}}
==Recovering smart contracts==
The contract is hidden once it is emptied but it still exists. To unhide it, you can send any coins, even 1 byte, to the contract address.

==External links==

==References==
<references />
[[Category:Features]]

Social tokens

2019-01-19T22:20:13Z

Punqtured: 11 revisions imported

==Overview==
The Social Tokens system is basically [[Family_tokens|Family Tokens]] for grown-ups.

As with Family Tokens, the general idea is to improve the group by rewarding good behaviour, both individually and in groups.
Our system uses Byteball wallets on the group members' personal cellphones.

==Set-up==
===Create the tokens===
The group leader uses some tokens from the [[fun-coins]] faucet, or preferably creates 1000 personalised "Credits by Group Leader" (or whatever), stores them in the "Treasury" wallet, and is mostly in charge of distributing them.

===Everyone has a wallet===
It is assumed each of the group members has a smartphone already. If not, they can be bought very cheaply. In ASDA (big UK supermarket), one running Android 7.0 goes for £35, or one running Android 5.1 for £20. Both work perfectly for Byteball, including cameras for scanning QR codes.

===Wallet details===
Use single-address wallets to reduce confusion.

*'''Group Leader:''' Personal Group Leader plain wallet; Treasury 1of2 multisig wallet
*'''Deputy:''' Personal Deputy Group Leader plain wallet; Treasury 1of2 multisig wallet
*'''Member A:''' Personal "Member A" plain wallet
*'''Member B:''' Personal "Member B" plain wallet
*'''Member''' . . .
*'''Team K:''' No special wallet, team members just use their regular wallets, etc

===Address list===
Group Leader and any Deputies need the addresses of everyone concerned, in their wallets if not too many. If too many, in a convenient form to make all needed payments promptly.

Each member has the following named addresses in their wallet address lists: Treasury, Group Leader and any Deputies.

===Pairing===
It is not essential, but there are benefits to pairing devices with others. Apart from the encrypted chat, one can then use smart contracts if desired.

One party gives the other a pairing code, either written out in full or via QR code. Generate this in Byteball wallet chat by clicking on "+ Add a new device" then "Invite the other device". It will look something like <code>AhHPXCpCSTzD1CF53ELGTAsZ6MCA8Ogvk+koyibfPt/2v@byteball.org/bb#GxVBizZ2DSEf</code>. The other party in Byteball wallet chat clicks on "+ Add a new device" then "Accept invitation from the other device" and pastes the pairing code into the almost-invisible line above the "pair" button.

===Transaction fees===
Every transaction that moves "Credits" from one wallet to another will cost maybe 1000 bytes. Make sure everyone has enough. One can buy more bytes with regular money. But note that "Credits" cannot be bought for regular money.

==How it works==
The exact system of what behaviours earn how many tokens and what rewards these tokens can be exchanged for (group trips to the movies etc) will need to be worked out by the group concerned.

===Credits and Rewards===
To avoid confusion, it might be best to refer to the tokens handed out to the members as '''credits''' (whether the actual name is ''Credits'' or ''Smarts'' or ''Woos'' or whatever), and what they can be "cashed in" for as '''rewards'''.

===Individual and group credits===
*Member A arrives on time for a week, and Member B does his assigned task for that week (maybe they have a rota for cleaning up the lunch trays), each receiving credits per the agreed list.

*Team K get credits for completing their after-hours project on time. Each member of Team K gets the same number to each wallet, except the team leader gets 20% more.

The group credits encourage peer pressure: "If we turn this in late we don't get the 20 credits, so let’s put in a bit of extra time and get it done, all right?"

===Individual and group rewards===
The members spend their credits on individual rewards:
*Member A wants to choose the TV channel in the lunchroom tomorrow, and Member C wants to skip his week doing communal sweep-up.
*Team L cash them in to go for a free meal together.

====Funding====
Some of the rewards will probably cost money, so funding for this needs to be worked out. Maybe from membership fees, maybe from "management" as a budget line item.

===Credits from Treasury===
When credits are earned, per the social token system, the group leader or a deputy sends them from Treasury to the member’s wallet. This can include use of a personal oracle, if you wish.

===Credits to Treasury===
When credits are exchanged for rewards, the member/s send/s the appropriate number to the Treasury wallet.

===Explorer===
Since all the relevant wallets are single-address, and these addresses are known, everyone can see all the relevant token transactions.

==But grown-ups are not kids!==
Does this really work for grown-ups? Well, try it and see. It has to be done with the agreement of the people involved.

==See also==
*[https://www.verywellfamily.com/create-a-token-economy-system-to-improve-child-behavior-1094888 Very well family website]
*[https://byteball.market To create your own social token in 5 minutes]

==References==
<references />

[[Category:Tokens]]

Send

2019-01-19T22:20:12Z

Punqtured: 18 revisions imported

[[File:Send.jpg|thumb]] Explaining the different options in your [[wallet]]'s Send screen.

==WHAT TO SEND==
Select the item, either a currency of some sort, or data or some sort. The default screen is the currency one.

===Currency items, from the top in order===
The currencies show as Name (or hash if no registered name) followed by the amount available, i.e. cleared/confirmed. This amount updates in real time as confirmations occur. So, for example: 

Bytes (221,088 MB available) Hi/WFGThLixhyaPALYgKnONBgjid0+mAPXQB8hRWp+E= (1 available) 
Zwib by Jore Bohne (77 Zwib by Jore Bohne available)

====Native currencies====
*Bytes
*Blackbytes

====Platform tokens/assets====
These are all the non-native currencies carried on the platform. They are listed in the alphanumeric order of the unit defining them, so Tangos<ref> https://explorer.byteball.org/#0Qki2BWSJ80dMN58Dq1rrJugaYyFndxkZloLJby+olU=</ref> (0Qki2BWSJ80dMN58Dq1rrJugaYyFndxkZloLJby+olU=) comes before SilentNotary<ref>https://explorer.byteball.org/#1OLPCz72F1rJ7IGtmEMuV1LvfLawT9WGOFuHugW2b7c=</ref> (1OLPCz72F1rJ7IGtmEMuV1LvfLawT9WGOFuHugW2b7c=) as 0 comes before 1.

===Data items, from the top in order===
If you select a data option, the amount/address sections will disappear. There is only one possible "payee" destination with a single-address wallet, and there is a note telling you to change to a single-address wallet if you are not already in one. All data sent will be accessible in the Explorer under that address. The "amount" section is replaced by Datafield name/value items.

====Data into datafeed====
Used for [[Oracle#Personal_oracles|personal oracles]]. This option sends arbitrary data into the DAG. The data is of the form [Datafeed name] then [Datafeed value], for example: 

<pre>Charlie_Dutton 74%
Elize_Swanson 69%
Gerald_Youngman 54%
...</pre>

====Attestation====
This relates to [[Identity verification]] using the [[Chatbot#Real_name_attestation_bot|Real name attestation bot]] in the wallet Bot Store. You enter the address given by the entity (ICO issuer etc) requiring the information, then whatever selection of [profile field] and [profile field value] is needed.

For example, age (date of birth) and Non-US country.

====Profile====
Post your profile data, anything you want to say about yourself. The data is of the form [Profile field] then [Profile field data] as before, for more than one field.

====Data====
Post arbitrary key-value pairs of data, not related to your profile. The data is of the form [Field] then [Value] as before, for more than one field.

==AMOUNT (Currency screen)==

Double-check that the currency, and the units if bytes or blackbytes, are correct. You don't want to send 4 GB if intending to send 4 Zwibs, or 0.1 GB if intending 0.1 MB.

===Conversion===
There is a stand-alone currency conversion tool for Byteball wallet https://tarmo888.github.io/bb-convert/, which supports converting 24 different currencies (including USD, EUR, BTC & ETH) into GByte, MByte, KByte and Byte amounts and if Byteball wallet is already installed then it opens the wallet where user can simply click Send to initiate the payment (nothing will be sent if user doesn't click SEND in the wallet app). This tool solves the problem that Byteball wallet doesn't have a built-in currency conversion tool for sending amount values other than native currency.

It is possible to prefill form fields and request somebody to send, for example, 1 million Venezuelan Bolívar (VEF) by sending a link like this (obviously with your own address). Just type in new values and it generates a new link on your browser address bar.
https://tarmo888.github.io/bb-convert/#amount=1000000&currency=VEF&address=NTYO4ZKPRBPXW6WY2QUMJBPNDLOGX5OJ

There is also a QR code generator on this tool that could be useful for seller, who can enter the number in their local currency and show the QR code to buyer. Just fill all fields correctly and "QR code for mobile wallet" link will appear under the calculated amounts.

Byteball wallet supports sending to multiple addresses, which can be entered as 2 column (comma separated address and amount) list. This tool has a multi-address mode (https://tarmo888.github.io/bb-convert/multi.html), but instead lets users enter the total amount they want to send and all the addresses they want to send to. By default, it will split the total amount equally (un-equally if some addresses appear multiple times) between the addresses and will generate the address list with amounts, which are compatible to be pasted into Byteball wallet. It also accepts any other 2 column (comma separated address and amount) lists in case user wants to add weight to some addresses, so these would get proportionally bigger amount. When clicking on Copy button (GByte, MByte, KByte or Byte - depending what unit you have selected in your wallet app), it will generate a new list into your clipboard that can be pasted to wallet app.

==PAYEE: TO BYTEBALL ADDRESS OR EMAIL OR USERNAME==
===Byteball address===
Enter in an address like <code>CARJFJ6SKDC2XGLX2XSNMIITAVRDEW2R</code>. A green check-mark will appear to the right if this is a valid address. If it is invalid, you'll see a red cross and "Not valid". Note it will still say "Not valid" if you pasted in a correct address with a space (character) at the start or end, so check this if the address appears valid to your eye. If you are typing in a correct address character by character, it will say "Not valid" right up to the point you type the final character, when the mark will turn green.

===Email===
The green check-mark only indicates it is of the form "___@___.___", not that it is an attested email address or even a valid email address. For example, you'll get a green check mark with <code>hfhfhd@hdhd.hdhdhdhd</code>

If you send a payment to an email address that hasn't been attested, it goes through as a [[textcoin]] -- which you can claim back as soon as the transaction is confirmed and you will lose only about 1500 bytes (2 transaction fees). If the email address is "in the system", it goes through to their attested single-wallet address, as you can immediately see in your wallet history.

===Username===
If the recipient has registered the username "@robin" using the [[Chatbot#Username_registration_bot|Username registration bot]], simply enter <code>@robin</code>

===Steem username===
If the person's Steem username is "alice", enter <code>steem/alice</code>

===Bind this payment to a condition===
This sets up a [[smart contract]]. You'll need to click the payee's address in [[Chatbot#Introduction|Chat]] first.

===Switch to multi-address===
From wallet version 2.2 on, you also have the option to send funds to multiple (up to 120) addresses in one transaction. This also works if you repeat an address, so with the units set to MB listing <code>CARJFJ6SKDC2XGLX2XSNMIITAVRDEW2R, 1.5</code> and <code>CARJFJ6SKDC2XGLX2XSNMIITAVRDEW2R, 1.5</code> results in two UTXOs (unspent transaction outputs) of 1.5 MB being received, not one UTXO of 3.0 MB. This can be very useful if you need to make several separate transactions rapidly without having to wait for confirmations. See the wiki [[Token#Rapid_distribution|Token]] article.

'''* NOTE:''' Be very careful with this, or it will seem like "it doesn't work". Your multi-address payment should look like:

<code>
WM6MOD5MOUCNMBQODXDUSA6F5T5FV4CC, 0.01↵ 
WM6MOD5MOUCNMBQODXDUSA6F5T5FV4CC, .0124↵ 
CARJFJ6SKDC2XGLX2XSNMIITAVRDEW2R, 2.00 
</code>

where the "↵" represents "Enter" on your keyboard. The addresses can be any valid addresses, up to 120 in all. The amounts must be valid amounts, and the total less than the available balance in that wallet.

If the wallet says it's invalid, or the Send button is greyed out, look for extra spaces before or after the address or amount. They will be visible if you select the addresses/amounts. If not obvious, look for one extra space after the amount.

====Multi-address with tokens====
In version 2.2.0, there is a bug when sending tokens with multi-address. There is a maximum of three digits, no decimals allowed. So you can send 999 Tangos but not 1000, and you can send 51 Zangos but not 5.1 etc. This bug is fixed in version 2.3.0.

==PAYEE: SHARE VIA MESSAGE==
This sends a textcoin.

==See also==

==References==
<references />
[[Category:Browse]]
[[Category:Features]]

Slack

2019-01-19T22:20:12Z

Punqtured: 3 revisions imported

Some of the Byteball channels at Slack.com

==Archive==
Slack channels only keep a few weeks of posts, depending on volume. But older messages in a few channels are available from https://byteball.slackarchive.io.

==Our Slack channels==

===#byteball_wiki===
*for matters concerning this wiki. The wiki editors/admins mostly hang out on Slack, and can be pinged easily

===#general===
*for general matters

*on changing the name/logo:

<blockquote>'''tonych [2018-01-02 9:45 PM]'''<ref>https://byteball.slack.com/archives/C30NVUJAD/p1514929559000560</ref>
''So @tonych if you want to help us out here: do you have any intention of ever changing the name or logo?''

I'm ok with the name and the logo. Maybe the logo could still be improved but the concept should stay the same: a circle. Simplicity, minimalism, no embellishments. I saw suggestions to change the name to Bytes. Bytes is already the name of the first coin. And Byteball - the platform.

</blockquote>

===#helpdesk===
*tends to be for newbies with simple questions, most of which should be able to be answered by giving a reference to a page in this wiki

===#ideas===
*for brainstorming new stuff. "Sticky" ideas might rate their own section or page here. . .

====change====

====Change the unit from GB to MB====
*You can choose the unit in your wallet as KB, MB or GB. Plus . . .

<blockquote>'''tonych [2017-05-24 10:48 PM]'''
I don't think it would be a good move now. We are still traded mostly against bitcoin and the price of MB (0.00013 BTC) with its many zeros wouldn't be easier to read than the price of GB 0.13 BTC</blockquote>

<blockquote>'''tonych [2018-01-05 See thread started 23:39 UTC by @neo]'''
Guys don't waste your energy on the units issue. @blokchain I saw your excellent post on reddit, and you had far more important points to care about than this one. We are not trying to appeal to stupid "investors" who don't understand that the choice of unit is arbitrary. They are easy to be fooled but we don't exploit them. Everybody is free to use the unit of his choice, it's easy to change in the wallet, and the default is bytes, which already shows amounts as integers (to your point @Phyzy that you prefer integers).</blockquote>

====slogan====
*Lots of "ooh, I thought of a nice slogan, it's ... . " posts. Rationale for current [[slogan]].

===#marketing===
*for questions, announcements, ideas, co-ordination on marketing matters

===#tech===
*where the developers hang out

===#trading===
*for Byteball trading generally, discussion about troubles with external exchanges dealing with GBytes, etc

===#trading_blackbyte===
*limited to trading blackbytes and related discussions. There's a bookbot that lists asks and bids, with commands that are available displayed by posting "otc"

===#zwib===
*for all things zwib, including getting some and trading them for other new assets

==External links==
* [https://docs.google.com/document/d/1zmJZ198N8KLClY9zAAKrYJyG8ftIpFNhsqse2jWxMVM/edit Byteball Slack Community Guidelines]

==References==
<references />

[[Category:Browse]]

Slogan

2019-01-19T22:20:12Z

Punqtured: 2 revisions imported

Edited mostly from Slack posts by Slackjore

==Smart payments made simple==
What's a slogan? It's not just some cute phrase someone thought of one day, like "Byte me!"

A slogan is a memorable motto or phrase used in a clan, political, commercial, religious, and other context as a repetitive expression of an idea or purpose, with the goal of persuading members of the public or a more defined target group. The Oxford Dictionary of English defines a slogan as "a short and striking or memorable phrase used in advertising." A slogan usually has the attributes of being memorable, very concise and appealing to the audience. These attributes are necessary in a slogan, as it is only a short phrase. Therefore, it is necessary for slogans to be memorable, as well as concise in what the organisation or brand is trying to say and appealing to who the organisation or brand is trying to reach.<ref>https://en.wikipedia.org/wiki/Slogan</ref>

Note the final sentence. Exactly WHO are we trying to reach?

===Byteball's primary public/audience===
Our primary target right now must be cryptofans, people who are interested in cryptocurrencies, who probably already have one or more crypto wallets, who have received/sent crypto transactions, and who are aware of the world of altcoins beyond Bitcoin.

Why? Because we speak a language that is different to what "the general public" uses, even if both are nominally English. The penetration into normal society of King Crypto -- Bitcoin -- is just about negligible. How many bricks-and-mortar stores in your neighborhood even accept Bitcoin, let alone any other crypto? Yes, this will change in the future, but wishing it were happening now is not the same as the actuality of it happening now.

So our marketing time and efforts must go in the direction of who we can reach with our message, and that is limited to people already in the crypto space.

Our primary public/audience are existing cryptofans.

===What message?===
Right now, Byteball is just another altcoin (among 1000+) to many. How to distinguish it from the others?

Positioning refers to the place that a brand occupies in the mind of the customer and how it is distinguished from products from competitors. In order to position products or brands, companies may emphasize the distinguishing features of their brand (what it is, what it does and how, etc.) or they may try to create a suitable image (inexpensive or premium, utilitarian or luxurious, entry-level or high-end, etc.) through [marketing]. Once a brand has achieved a strong position, it can become difficult to reposition it. Positioning is one of the most powerful marketing concepts.<ref>https://en.wikipedia.org/wiki/Positioning_(marketing</ref>

In the cryptocurrency field, Byteball functions as a brand name, as do Bitcoin, Ripple, Ethereum, Dash and all the 1000+ others. The space is becoming increasingly commoditized, and as Bitcoin loses its dominance a crypto brand needs a unique selling point in order to stand out from the crowd. The Byteball USP at this point in time is its conditional-payments feature.
<ref>https://en.wikipedia.org/wiki/Unique_selling_proposition</ref>

===Killer feature===
Byteball's killer feature right now is the Smart/Conditional Payment. What's the first bit of copy on Tony's site under the headings?

<blockquote>
Why use Byteball?

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.
</blockquote>

Factually, Byteball is the first cryptocurrency with conditional payments. But you can't use the words "conditional payments" in a slogan as no-one knows what they are. Hence we use "smart payments" instead. It's true that "smart payments" can mean almost anything, but that doesn't matter at all. Why? Because no other cryptocurrency has taken the "smart payments" branding position, so we get to explain what smart payments are.

==="But Byteball has so much more!"===
The opening words of the white paper are

<blockquote>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 [cryptographically].</blockquote>

One could say those benefits are only tenuously described as "smart payments", which is true. But those attributes are not yet available to consumers. No single crypto brand is going to be all things to all people, for buying a coffee, buying a house, immigrant workers sending money back home weekly, a store of value just in case, a simple contract, a complex contract, validating real estate ownership, and lots more. A crypto must select its best niche market and concentrate its marketing on that. All the other development and roll-out can continue, but the marketing emphasis is limited to one single theme: conditional payments.

Our best message target is the conditional-payments niche in the cryptofans market.

===What words for the message?===
We have to position Byteball against (i.e., in relation to, not in opposition to) the leader in this conditional-payments category. Let's see how some copycat cryptos with savvy marketing people might do it:

<blockquote>

*'''Byteclub''', the powerful smart-payments crypto
*'''Chicbyte''', the smart-payments solution for the smart woman
*'''Firstbyte''', smart-payments for your 5-year-old
*'''Bytenip''', the smart-payments app for cats

For men, women, young kids not yet old enough to download an app themselves, and pets. Well, OK, maybe not the last one.
</blockquote>

But what about Byteball? Oh! Oh! There are zero competitors (at present) in the conditional-payments category. We are the leader, the first by default. So we can say whatever we want.

After considerable discussion in the Slack #marketing channel on 20 June 2017 (look it up in the archives if you wish), we settled on Cryptkeeper's '''Smart Payments Made Simple'''.

===The future===
"Smart payments made simple" looks good for a long time. It uses no crypto-specific words -- although explaining how smart payments equals conditional payments still needs to occur -- so will transfer seamlessly from a public very familiar with cryptocurrencies to one not so.

===Marketing===
[[Grassroots]] marketing by Byteball volunteers should not stray too far from this direction.

==See also==
Some references on Branding:
*[https://www.amazon.com/Positioning-Battle-Your-Al-Ries/dp/0071373586 Positioning: The Battle for Your Mind] (Ries and Trout, 1981)
*[https://www.amazon.com/22-Immutable-Laws-Marketing-Violate/dp/0887306667 22 Immutable Laws of Marketing] (Ries and Trout, 1994)
*[https://www.amazon.com/22-Immutable-Laws-Branding/dp/0060007737 22 Immutable Laws of Branding] (Ries and Ries, 2002)

== References==
<references />

[[Category:Browse]]

Smart Voucher

2019-01-19T22:20:12Z

Punqtured: 4 revisions imported

Smart Vouchers for [[Identity_verification|Real Name Attestation]] were introduced in a Medium Article<ref>https://medium.com/byteball/introducing-smart-vouchers-a-new-way-to-earn-referral-rewards-by-sending-bytes-to-new-users-38972ec645a7</ref> on October 15, 2018.

==The steps==
0. To become a Sponsor, you need to be already attested yourself. After completing your own attestation, you are offered an option to create and fund a Smart Voucher. If you are already attested, type “help” in chat with the [[Chatbot#Real_name_attestation_bot|Real Name Attestation Bot]] to see the voucher related commands.

1. You as a Sponsor fund a Smart Voucher with at least $8 of Bytes. Let’s say you deposited $40 to the Smart Voucher to be able to fund five attestations at the same time.

[[File:Smart-voucher.png|thumb|upright=0.70]]2. The Smart Voucher code is automatically created: it’s just a sequence of letters and digits that looks like <code>VMJKYJGE3RUMT</code>. You can now share it with whoever you feel like: a friend, colleague, family member, readers of your blog, viewers of your YouTube channel etc.

3. Let’s say you share it with your brother Ben (referred user). He can then use that code instead of paying the $8 fee for a Real Name Attestation. For Ben, the Smart Voucher acts like a discount code, or a coupon, that entitles him to a 100% discount on real name attestation.

4. The Real Name Attestation Bot accepts the Smart Voucher, and withdraws the $8 fee (in Bytes) from the Smart Voucher to pay for the attestation.

5. If Ben’s attestation is successful, his $20 [[Referral#Real-name_attestation_reward|attestation reward]] is split in two: $12 (in Bytes) is sent to a time-locked smart contract on Ben’s wallet. He can withdraw that amount 1 year later.

6. The other part of the attestation reward is a $8 reward. This part gets returned to your Voucher to reimburse you for the price of the successful attestation. You also receive a $20 referral reward. This gets sent to the same Smart Voucher and its entire balance ($60 in this example) can now be used to fund new attestation fees.

7. You (the Sponsor) can withdraw the amount you initially deposited directly to your wallet (but not exceeding the Smart Voucher balance). The Smart Voucher balance exceeding what you deposited to it (that is, your net earnings) can be withdrawn to a time-locked Smart Contract from which it can be withdrawn after 1 year. The smart contract is automatically created by the bot when it is first withdrawn to.

== Notes==
*The Sponsor himself must be verified prior to creating a Smart Voucher.

*Recovering a wallet from seed will not bring back access to the contract. So make sure to do a full [[backup]] '''every time''' a new smart contract is created on your wallet.

*The Smart Voucher balance is tracked in Bytes, not USD, and is therefore subject to cryptocurrency rate fluctuations. For the best user experience, deposit to the Voucher more than $8 for each attestation attempt you wish to fund.

*Byteball rewards new users that join the network. Therefore, referral rewards don’t get paid if an attestation is performed from a device that was previously used to attest another person, as this isn’t considered a new Byteball user. A referral means the Sponsor gets a second person to install the Byteball wallet on his own device (smartphone or computer) and doing an attestation from that device/wallet, using the Smart Voucher received from the Sponsor.

==References==
<references />

[[Category: Browse]]

Polls

2019-01-19T22:20:11Z

Punqtured: 2 revisions imported

This is to record Byteball poll results from Twitter etc.
==Twitter 2018-01-25==
'''Poll for #Byteball wallet holders, have you made a simple payment to another wallet? (91 votes)'''<ref>https://twitter.com/slackjore/status/956134649973149696</ref>
*(53 votes) 58% Yes, I've sent Bytes
*(14 votes) 16% Yes, I've sent others too
*(11 votes) 12% No, I've 0 Bytes for fees
*(13 votes) 14% No, another problem

===Notes===
'''Purpose of poll:''' To get some idea of what fraction of wallet-owners had done the simplest task 
'''Follow up:''' (1) Send #3 people maybe 20KB so they can make 20+ tx; (2) Ask #4 people for details.<ref>https://twitter.com/slackjore/status/956504398095704065</ref> '''Results:''' Sent about twice the number of #3 people 20 KB; ZERO #4 people answered the question! 
'''Conclusions:'''

==Twitter 2018-02-16==
'''Poll for #Byteball people on fun-coin experience, per http://wiki.byteball.org/fun-coins. Have you received fun-coins, either from a friend or the free wallet faucet? Have you sent them? Simple payment? Textcoin? Smart contract? (18 votes)'''
* (9 votes) 50% No, not at all
* (3 votes) 17% Yes, received only
* (4 votes) 22% Yes, simple or textcoin
* (2 votes) 11% Yes, in a smart contract
===Notes===
'''Purpose of poll:''' To get some idea of fun-coins [[statistics]] 
'''Follow up:''' ...

==Twitter 2018-02-24==
'''The #Byteball-Altcoin Exchange Bot in the wallet Bot Store exchanges over 60 altcoins to Bytes, Bytes to altcoins, or altcoins to altcoins. Have you ever used it? (165 votes)'''<ref>https://twitter.com/slackjore/status/967383258743918593</ref>
*(26 votes) 16% Yes, it worked great
*(7 votes) 4% Yes, but had a problem
*(39 votes) 24% No, but used another bot
*(93 votes) 56% No, not used any bot

===Notes===
'''Comment:''' Should have specified for Byteball holders. Should have included "$GBYTE". It's not clear if "not used any bot" includes responses from non-Byteball holders. 
'''Purpose of poll:''' To get some idea of what fraction of wallet-owners have used the altcoin exchange bot, or any bot. Also to promote both ideas. 
'''Follow up:'''

==Twitter 2018-02-26==
'''An unofficial poll for $GBYTE users. Of these four options, choose #Byteball's Unique Selling Proposition: Smart contracts, oracles? Easy token creation, with private KYC, ICO functionality? Textcoins, made from any platform asset? Chatbots in the Bot Store? (70 votes)'''<ref>https://twitter.com/slackjore/status/968175539214258176</ref>
*(30 votes) 43% Smart/conditional payment
*(8 votes) 11% Platform for own tokens
*(17 votes) 24% Textcoin, using own token
*(15 votes) 22% 20 chatbots, more to come

===Notes===
'''Comment:''' It is assumed most people answering this poll aren't particularly familiar with '''any''' of the options, so don't read too much into the responses. 
'''Purpose of poll:''' To possibly get some idea of what Byteball's USP should be. 
'''Follow up:'''... Reported on Slack.

==See also==

==References==
<references />
[[Category:Browse]]

Quiz

2019-01-19T22:20:11Z

Punqtured: 8 revisions imported

==Introduction==
This is just for fun, no prizes, to test your general knowledge of the platform. Nothing really technical. The answers are in the referenced/footnoted articles.

==Questions==
Only one answer is correct in each the following questions:

1.<ref>[[Token]]</ref> Which of these can you not create and send in the regular wallet?
<ol style="list-style-type:lower-alpha">
<li>Family tokens</li>
<li>Social tokens</li>
<li>Commercial tokens</li>
<li>Plastic tokens</li>
<li>Fun-coins</li>
</ol>

2.<ref>[[Social_tokens]]</ref> Which of these could not be personal tokens in your wallet?
<ol style="list-style-type:lower-alpha">
<li>5 Kisses by Sarah Sweetbrush</li>
<li>2 Lambo rides by Elon Tassle</li>
<li>6 Guitar Lessons by TedTheShred</li>
<li>45 Listening Minutes from Charity Wilson</li>
<li>10 Fierce Microbrews by Al Schlitz</li>
</ol>

3.<ref>[[Wallet]]</ref> Which of these could you have in your platform on one device?
<ol style="list-style-type:lower-alpha">
<li>Small Expenses Wallet, Savings Wallet, no others possible</li>
<li>As many as you want, all with custom names</li>
<li>Up to 5, choose from 24 fixed names</li>
</ol>

4.<ref>[[Textcoin]]</ref> Which of these could you not send as a textcoin?
<ol style="list-style-type:lower-alpha">
<li>Blackbytes</li>
<li>Tangos</li>
<li>TitanCoins</li>
</ol>

5.<ref>[[Blackbytes]]</ref> Where are you not able to buy/sell blackbytes?
<ol style="list-style-type:lower-alpha">
<li>Bittrex</li>
<li>BEEB chatbot in your wallet [now discontinued]</li>
<li>Freebe chatbot in your wallet</li>
<li>Byteball Slack channel #trading_blackbyte</li>
</ol>

6.<ref>[[News]]</ref> The Byteball live network was launched on:
<ol style="list-style-type:lower-alpha">
<li>January 3, 2009</li>
<li>December 25, 2016</li>
<li>April 1, 2017</li>
</ol>

7.<ref>[[Slogan]]</ref> The current Byteball slogan is:
<ol style="list-style-type:lower-alpha">
<li>Byte me!</li>
<li>Smart payments made simple</li>
<li>The crypto that works right out of the box</li>
<li>They talk. We deliver</li>
</ol>

8.<ref>[[Send]]</ref> Which of these can't you put into the DAG with your regular wallet?
<ol style="list-style-type:lower-alpha">
<li>A transaction for 375.44 Zangos</li>
<li>“I feel good today”</li>
<li>A low-quality picture of your cat</li>
</ol>

9.<ref>[[Chatbot]]</ref> Which of these is not possible with the regular platform?
<ol style="list-style-type:lower-alpha">
<li>End-to-end encrypted text chat with any paired device</li>
<li>Sports betting on next week's major fixtures</li>
<li>Getting nine million Tingos in five minutes free from a faucet bot</li>
<li>Exchanging Ethereum for Dash via a bot with no ID needed</li>
<li>Getting a regional weather forecast</li>
</ol>

==References==
<references />

[[Category:Browse]]

Recover

2019-01-19T22:20:11Z

Punqtured: 3 revisions imported

== Recreating wallet overview ==
Byteball has two options for recreating your lost funds, both requiring preparatory actions '''before''' you lose the wallet.

===Recover from the seed===
If you write down the 12 wallet seed words (put them in a safe place!), then, anyone will be able to use those words to recreate the '''public''' assets in your wallet. By "public assets" is meant Bytes and all assets detailed in the DAG. "Private assets" are those few like Blackbytes, which are detailed in your wallet but not in the DAG.

'''Backup wallet seed:''' The seed alone will back up your bytes but not your blackbytes. This is important! (It means "backup platform seed")

'''Recovery from seed:''' Recovery is available in single-sig (i.e., not multi-sig) light wallets from version 1.10.1.

Please note that multisig wallets and smart contracts cannot be recreated from the 12 seed words: they can be recreated only from a full backup.

===Restore from a full backup===
A full backup will allow you to recreate your full wallet, including Blackbytes, any other private assets and also smart contracts, up to the date of the last private transaction before the backup. You should do a full backup every time you do a Blackbytes transaction.

See the [[Backup]] page for backing up your wallet using the Main Menu "Full Backup" option.

==See also==
Check this linked article about both options:
http://dailybyteball.blogspot.com/2017/05/how-to-make-backup-your-byteball-wallet.html

[[Category:Browse]]

Referral

2019-01-19T22:20:11Z

Punqtured: 6 revisions imported

== Real-name attestation reward ==
Every new user who successfully [[identity verification|verifies]] himself for the first time will receive $12 in Bytes from the distribution fund. With $8 they have to spend for verification, it is net $4. The amount seems large enough to care about but not too large to bother about instadumping.

Real-name attestation is available only for single-address wallets, and to avoid confusion, starting with version 2.1, the default ("Small expenses") wallet of new users is created as single-address (nothing changes for old users). Users can still easily add another wallet and make it multi-address for better privacy. The second wallet is not linked to the user’s verified identity and can be used anonymously.<ref>https://medium.com/byteball/distribution-to-verified-users-and-referrals-ed00b9b2a30e</ref>

The real-name attestation reward is held in a [[smart contract]] and paid after a year.<ref>https://medium.com/byteball/distribution-to-verified-users-and-referrals-episode-ii-29b6f1cd4ecc</ref>

===Real-name attestation referral reward===
By referring '''a new user''', the referrer also receives $20 after the referred verifies himself. The main purpose of this referral reward is to encourage new Byteball users. The referrer must be also verified at this moment. Just like the attestation reward, the referral reward of $20 will be deposited to a smart contract with a 12 months vesting period and a two year expiration time. Restoring a wallet from seed will not bring back access to the contract. So remember to regularly make full backups.

Referral rewards don't get paid if the second person is performing attestation in the same wallet. It isn't a referral. A referral is getting a second person to install the Byteball wallet on his own device (smartphone or computer) and doing an attestation from that device/wallet, using Bytes received from the first person.

===Transparency===
This address is used to pay real-name attestation and real-name referral rewards: https://explorer.byteball.org/#RJIUGYIVHM5TAZHU3ZPNTNZL5JF4JUTN<ref>https://bitcointalk.org/index.php?topic=1608859.msg30605651#msg30605651</ref>

==Email attestation reward==
See [[attestation]] article.

When email attestation is done for a whitelisted domain, there is an attestation reward of $10 in Bytes, paid only for the first attestation of each Byteball or email address.

===Email attestation referral reward===
If you attest your email address (not necessarily on a whitelisted domain) and then send Bytes to someone else who later uses these Bytes to pay for attestation of a whitelisted email, then the referred user receives the attestation reward and you receive a referral reward, which is also $10 in Bytes.<ref>https://medium.com/byteball/distribution-to-verified-emails-and-sending-cryptocurrency-to-email-episode-ii-cb955fe19d7e</ref>

===Transparency===
This address is used to pay email attestation and email referral rewards: https://explorer.byteball.org/#UOYYSPEE7UUW3KJAB5F4Y4AWMYMDDB4Y

You can watch email attestations taking place in real time at https://byteball.co.

==Multiple referrers==
It can sometimes be difficult to tell who will get the reward if more people have sent bytes to the user performing the attestation. Therefore, if you want to be absolutely sure you get the referral reward, ask the user to create a new (single-address) wallet that has no bytes in it. Send your bytes to that wallet and ask the user to perform the attestation from that wallet.

==External links==

==References==
<references />

[[Category:Features]]

Overview

2019-01-19T22:20:10Z

Punqtured: 23 revisions imported

<languages/>
<translate>
'''Byteball''' features in-wallet: sports betting bots, payments to emails, encrypted text chat, altcoin exchange, your own custom tokens, your smart contracts.


Listed on CoinMarketCap as ''Byteball Bytes'', it is a [[Directed_acyclic_graph|DAG]]-based cryptocurrency developed by Anton Churyumov.

==Features== 

===Smart/conditional payments=== 


[[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.


This [[Special:MyLanguage/Smart_contract|smart-contract]] feature has many real-world peer-to-peer applications, including:


* no-fee crypto exchanges
* [[Sports_betting|sports betting]]
* selling or buying insurance concerning negative events like a flight delay.

===Textcoin=== 


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:


<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=== 


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.


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>

===Sending payments directly to email addresses=== 


When you have attested an email address using the [[Chatbot#Email_attestation_bot|Email attestation bot]], anyone can make payments to you from their [[wallet]] using only that email address. The platform will automatically replace it with the attested Byteball address.<ref>https://medium.com/byteball/distribution-to-verified-emails-and-sending-cryptocurrency-to-email-episode-ii-cb955fe19d7e</ref>


Note that if you have several email addresses you can link each one to separate single-address wallets you create in your main wallet. This is all independent of the identity verification procedure above.

===Blackbytes=== 


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=== 


[[File:Betting-bot.jpg|thumb|left]][[Special:MyLanguage/Chatbot|Chatbot]]s are fun and facilitate real-world transactions. There are over 20 bots, including oracles, betting bots, exchange bots for blackbytes and other cryptos, games and ICOs (both for facilitating ICOs and actual ICOs).</translate>

Current chatbots are: Real name attestation bot, Email attestation bot, Flight delay insurance, Byte-BTC exchange, Flight delays [[Special:MyLanguage/oracle|oracle]], Sports oracle, BTC oracle, Rosie bot, Byteball Asset Manager, Zork | game, Poll bot, 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, Worldopoly ICO.


^Ideally, crypto transactions are trustless, i.e., neither the sender nor the receiver need trust the other. The more trustful the situation is, the less ideal.

<translate>

==Platform== 


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>


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.
*'''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.
*'''Worldopoly 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.<ref>https://bitcointalk.org/index.php?topic=1608859.msg16156239#msg16156239</ref>
*Platform went live on 25 December 2016.

===DAG=== 


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.


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.

==Zurich presentation== 


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== 


<youtube>https://www.youtube.com/watch?v=2ZuYZOitKfQ</youtube>


<youtube>https://www.youtube.com/watch?v=zOayZ2_6cN4</youtube>


<youtube>https://www.youtube.com/watch?v=RT-pA_KHz4U</youtube>


<youtube>https://www.youtube.com/watch?v=SnXuylxUKqo</youtube>

==External links== 


* [https://byteball.org Main website]
* [https://byteball.org/Byteball.pdf White paper]
* [https://explorer.byteball.org Transactions explorer]
* [https://medium.com/@Byteball Medium articles]
* [https://bitcointalk.org/index.php?topic=1608859.0 Bitcointalk thread]
* [https://byteball.market/#!/asset/order Byteball Asset Manager (for you to create your own coin on the Byteball platform)]
* [https://wiki.byteball.org Byteball Wiki]
* [https://www.reddit.com/r/ByteBall Community Subreddit]
* [https://byteball.slack.com Community Slack]

==References== 


<references />


[[Category:Browse]]
[[Category:Features]]
</translate>

Personal tokens

2019-01-19T22:20:10Z

Punqtured: 2 revisions imported

Personal tokens are one of the five kinds of [[token]] on the Byteball platform. In a local community, most people have regular money in varying amounts, and it works fine apart from one generally not having enough of it. But there are other resources, personal to the individual, that can be "monetised", with these tokens then being passed around like cash.

[[File:Deb-alan-1.jpg|thumb]]
==Backing==
To be more than a [[fun-coins|fun-coin]], useful for practising [[textcoin]]s or [[smart contract]]s but with zero monetary value, a token must be backed by something. That means the bearer can exchange the token with reasonable ease for something in the real world that the bearer considers valuable.

===Historical===
In the distant past, "I promise to pay the bearer on demand the sum of 1 pound" on a one-pound English note meant on presentation at the bank the bearer could receive in exchange one pound weight of sterling silver. With fiat money -- where it's still valuable -- the backing is only the confidence that other people will accept it in exchange for usual goods and services.

===Present day===
How does this apply today, in 2018, and especially with Byteball? It's not generally practical to create a token exchangeable one-for-one with the national fiat currency, although [[local currency|local currencies]] complementary to the national currency do exist. They are accepted at participating merchants to encourage residents to shop locally.<ref>https://en.wikipedia.org/wiki/Local_currency</ref>

However, [[Glossary|ICOs]] that collect money in exchange for tokens -- especially on the Ethereum platform -- are very popular, despite threats of government regulatory action.

==Counterfeiting==

The [[File:Bobby-10credits.jpg|thumb|upright=0.67]] thing about non-crypto tokens is many ideas seem great until you get to the practicalities and realise that any physical tokens one will make (hand-made or computer-printed or even hammered rounds of metal) can easily be counterfeited. It's why national banknotes and passports are so incredibly intricate and beyond creation at home. And creating a crypto token on the Ethereum platform, say, is relatively difficult and costly.

But Byteball tokens change all that because:
* the cost and effort of creation is negligible, and
* despite this ease one's token is instantly recognisable and can't be forged.
This is a '''big''' deal!
{{clear}}

==The Personal Tokens system==
[[File:Social-tokens-1.jpg|thumb|left]]
===Personal tokens===
One creates a "personal token". This is not an empty token but one backed with some real-world good or service that enough people in one's group would value. The default resource, that most anyone can monetise to some extent, is their spare time. So Bobby Smart creates a token called "Minutes by Bobby Smart" that he issues very carefully. Because the promise is that '''anyone''' holding his tokens can "cash them in" with Bobby on demand in exchange for that many minutes of his time and attention. Obviously one is not expected to drop whatever they are doing to honour the new demand, but a reasonable accommodation, satisfactory to both parties, should be made.

===Good faith===
This is a good faith system, where "I promise to pay the bearer on demand ..." for once means what it says. Both token issuers and token redeemers are expected to act reasonably and if they don't the value of their "money" will drop accordingly along with their social reputation.

===Skills===
The time of a professional, whether a plumber or a tax accountant, will have to be specified as social or professional, i.e. whether an hour with the plumber is just chat or includes unblocking your sink.

"Minutes by Gary Watson", a local plumber, would be a confusing token. Does this time include plumbing labour, or only chat time? "Plumbing Minutes by Gary Watson" or "Casual Minutes by Gary Watson" would be clearer. But "Professional Landscape Gardening Minutes by Sotiris Papadopoulos" isn't going to fit in the space available.

===Exchange rates===
Just as 1 Zimbabwean Dollar is not worth the same as 1 US Dollar, "Kisses by Sally Snodgrass" might not be as prized -- or as rare -- as "Kisses by Sarah Sweetbrush". The relative values of various similar tokens in a community will become clearer as time goes by.

===Fiat or token?===
Some items can readily be exchanged for fiat cash, but others could be exchanged for social tokens that don't feel right to sell for cash. For example, spending an hour fixing a good friend's computer would probably be done for free; doing it for a complete stranger might involve a normal cash payment; but how about the awkward area in the middle where neither seems appropriate?

===Examples===
These are things friends with skills might do for each other, not full-blown commercial offerings.
* Lambo rides (from a rich family)
* DJ sessions
* Haircuts
* Microbrews (from a home-brewing fan)
* Backrubs
* Horserides (family farm)
* Makeovers (make-up expert)
* Portraits (from someone who draws well)
* Guitar lessons
* Language lessons (bilingual person)
* Listening minutes (sympathetic person)
* Babysitting hours

==Textcoins==
Deb is perfect to illustrate all this as she both likes Byteball and loves to give away her kisses with wild abandon. If an intended target does not have a Byteball wallet yet, no problem. She sends some “Kisses by Deb” as a [[textcoin]] in a text message on WhatsApp or whatever is in vogue at the time.

===Creating and registering tokens===
How tokens are '''created''' is covered in the [[asset]] article. To have a token '''display''' in English, "Tingos by Jore Bohne" instead of "O1DbJWbZJfKhjZQYH5RrdRQ2ojMuo2WiaKbjIWSWd4E=", requires registration<ref>https://docs.google.com/document/d/e/2PACX-1vQnpiwTipnBgrhSJcELOYYAOa3mTLZbmLmOebbtHFJFrfgHtlsNNZ9MPEGafvtuTnVAyfWukwu_hYSB/pub</ref> too.

Note your created token name will always display in the form: '''<goods/service'''> by <'''your identity as verified by the token name registry'''>. See [[asset#Byteball_Asset_Manager|asset]] article for details.

==See also==

==References==
<references />
[[Category:Tokens]]
[[Category:Features]]

Platform

2019-01-19T22:20:10Z

Punqtured: 4 revisions imported

This article is mainly about coins/assets/tokens on the Byteball platform in addition to its native currencies of bytes and blackbytes.

==Stress-tests==
Any platform must be continually stress-tested, with defects repaired in a timely manner. See the wiki article [[Antifragility]].

==Classification==
The distinction of "asset in the financial world = token in the non-financial world" is not always easy to make. For example, with personal tokens, "Kisses by Deb" are clearly not likely to be sold for much money, but how about "Plumbing Minutes by Joe Silverman", a qualified plumber, who normally charges $1 a minute for his labour?

==Existing==
To date, we have descriptions and articles about:
* [[Fun-coins]]
* [[Family tokens]]
* [[Personal tokens]]
* [[Social tokens]]
* [[Commercial tokens]]
* TitanCoin
* ICO bot

==Future==
* [[Local currency|Local currencies]]<ref>https://en.wikipedia.org/wiki/Local_currency</ref>
* Accounting and tax implications of non-trivial personal/social tokens

==See also==

==References==
<references />
[[Category:Browse]]
[[Category:Tokens]]

Oracle

2019-01-19T22:20:09Z

Punqtured: 7 revisions imported

An ORACLE is a trusted third party that monitors specific external events and imports them into the Byteball database as a data feed. An example is a list of cryptocurrency exchange rates updated every ten minutes.

==Known oracles==
'''P2P exchange of Bytes vs. Bitcoin'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-ii-bitcoin-exchange-d98adfbde2a5</ref> | FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH

'''P2P random numbers gambling''' | FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH (same oracle as above)

'''Crypto exchange rates'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-iii-prediction-markets-f40d49c0abab</ref> | JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC

'''Flight delay tracker for flight delays insurance'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-iv-p2p-insurance-cbbd1e59d527</ref> | GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN

'''Sports betting on soccer match results'''<ref>[[Sports betting]]</ref> | TKT4UESIKTTRALRRLWS4SENSTJX6ODCW

'''Timestamp in Unix Epoch Time'''<ref>[[Timestamp]]</ref> | I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT

==Contract times==
There are two times in a non-timestamp smart contract which are set by the contract writer. The default time for peer non-payment is not as important as the contract expiry time, which may or may not play an important role in the bet.

===Peer non-payment===
This is the minimum time period after which the contract-writer can recover his stake if the peer doesn't pay his stake. The default is set to 4 hours, but it can be set as low as .1 hours (6 minutes).

===Contract expiry===
This is the time period after which the contract does not operate. The default setting is 7 days, but it can be set as low as .01 days (14 1/2 minutes). If you are betting on a discrete event, like a particular sporting event or single flight arrival it doesn't matter. But if you are betting on a system in continual flux like whether the price of a particular cryptocurrency pair will exceed a certain amount, it makes a big difference. In such a case this time must be discussed as one of the terms of the bet.

==Personal oracles==
{{#ev:vimeo|https://vimeo.com/254485316|thumb|right|'''Personal oracles'''}}Use a single-address wallet. Use the <code>Data into datafeed</code> option in your [[Send]] menu.

Here is an example. A father, away from home, gives his child money conditional on doing some chores. When the mother signals online they are done, the money automatically becomes spendable.

This sort of thing could be used as part of a [[family tokens]] set-up in a household.

{{clear}}

==Example of trading using an oracle==
[[File:Oracle-1.png|thumb|left|upright=0.66]][[File:Oracle-2.png|thumb|none|upright=0.66]]

{{clear}}

From the Slack Byteball #prediction_markets forum, tonych:

<blockquote>This is a trading floor, shout out your offers like in the old times. For example:
"I bet on BTC going below 1150 within 1 day, I pay 0.3GB out of 1GB"</blockquote>

Use the crypto exchange rates oracle for this.

<div style="clear: both;"></div>
==Using the crypto-exchange-rates oracle in a smart contract==
# Practise thoroughly with small amounts of money first. The finished contract is human-readable but it is not obvious to a novice who gets to pay what under what conditions.
# Pair up with a peer in wallet chat. Agree on the terms for the contract with your peer as needed throughout. After you have started writing the contract you will not be able to use the wallet chat until you finish (or abort) it. So either carefully agree all the details first, or have a separate chat channel open.
# Peer sends you a receive address. Left-click the address. Click “offer a contract.” Go down filling in the easy bits, with the details as agreed on.
# When you get to ORACLE ADDRESS, copy/paste in the crypto exchange rates one: '''JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC'''
# See an [https://explorer.byteball.org/#qjh31Ng5gSDDF5Vq+MizhVife3zw8eNFwBwSOcmnw3w= example of the feed] from this oracle, and pick a currency pair, maybe BTC_USD. Then under DATA FEED NAME paste: '''BTC_USD'''
# Fill in the remaining easy bits with the agreed details, then click/press PAY AND OFFER. This will send your stake to the smart contract, and send a payment request to your peer for their stake.
# '''Caution: The peer should read the contract VERY carefully. Maybe neither party knows the other, and a costly mistake could have been made in the details, like a "<" (less than) sign instead of a ">" (greater than) sign. Or an incorrect currency pair. Also check that the payment request is for the correct amount, both the figures and the units (GB/MB).'''
# Your peer clicks Send on the payment request. The new contract will be visible as a smart wallet.
# Now you both wait. You can view an up-to-date feed from that oracle by entering its full JPQ… address in the [byteball explorer search box](http://explorer.byteball.org). As soon as one party fulfills the terms of the contract its funds can be spent.

==Random numbers==
{{#ev:vimeo|https://vimeo.com/221655112|thumb|right|'''Betting on Random Numbers'''}} Video in Hi-Def and with English subtitles.
# Practise thoroughly with small amounts of money first. The finished contract is human-readable but it is not obvious to a novice who gets to pay what under what conditions.
# Pair up with a peer in wallet chat. Agree on the terms for the contract with your peer as needed throughout. After you have started writing the contract you will not be able to use the wallet chat until you finish (or abort) it. So either carefully agree all the details first, or have a separate chat channel open.
# Peer sends you a receive address. Left-click the address. Click “offer a contract.” Go down filling in the easy bits, with the details as agreed on.
# When you get to ORACLE ADDRESS, copy/paste in the random-numbers-gambling one: '''FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH'''
# Here is an example of the data feed from this oracle:<ref>
https://explorer.byteball.org/#Ns//o52EKR32ykuHfUfcm3ailHtta6TvM5kB07vbpVA= 
bitcoin_hash: 0000000000000000019dd457cf8e233701dab44ac855492d575a4366556213e0 
bitcoin_height: 460852 
bitcoin_merkle: GW9cQW5m0KLIi2suUlkzRP2yurg8jLEax3uHiun7kik= 
random460852: 34789
</ref> You will need to know the current bitcoin height, and pick a future one to bet on. [https://blockchain.info Blockchain.info] is an easy source for current block height. Let's say you're doing this before the one above. So under DATA FEED NAME paste: '''random460852'''
# Fill in the remaining easy bits with the agreed details. Let's say you're doing an evens bet, above or below 50,000, then put "50000" in the POSTED VALUE box. Then click/press PAY AND OFFER. This will send your stake to the smart contract, and send a payment request to your peer for their stake.
# '''Caution: The peer should read the contract VERY carefully. Maybe neither party knows the other, and a costly mistake could have been made in the details, like a "<" (less than) sign instead of a ">" (greater than) sign. Or an incorrect bitcoin height. Also check that the payment request is for the correct amount, both the figures and the units (GB/MB).'''
# Your peer clicks Send on the payment request. The new contract will be visible as a smart wallet.
# Now you both wait. You can view an up-to-date feed from that oracle by entering its full FOP… address in the [http://explorer.byteball.org Byteball Explorer search box]. Find the right one by the timing, compared to when "your" block was mined. As soon as one party fulfills the terms of the contract its funds can be spent.

==Flight delays tracker==
{{#ev:vimeo|https://vimeo.com/222006250|thumb|right|'''Betting on Flight Delays'''}} Video in Hi-Def and with English subtitles.

Better to use Flight Delay Insurance chatbot in the wallet bot store. You can get flight numbers and schedules from flightstats.com. You can choose any flight 1 day to 3 months in advance, with maximum compensation 1 GB. Example premiums for 1 GB compensation are:

*30 minutes delay: 0.082258065 GB
*1 hour delay: 0.079996985 GB
*2 hour delay: 0.070952668 GB
*4 hour delay: 0.066129032 GB

<div style="clear: both;"></div>

==External links==

==References==
<references />

[[Category:Features]]
[[Category:Trading]]
[[Category:Oracles]]

News

2019-01-19T22:20:08Z

Punqtured: 37 revisions imported

Very brief '''headline''' items only, with links to each announcement, usually on Bitcointalk as a permanent record.

==2019==
*Jan 17: Byteball rebranded to Obyte<ref>https://medium.com/byteball/byteball-rebrand-the-next-step-to-real-world-adoption-6a0a924390de</ref>

==2018==
*Dec 12: Announced third Byteball Use-a-thon, a Bot War<ref>https://steemit.com/byteball/@byteball.org/introducing-the-great-byteball-bot-war</ref>
*Dec 1: Byteball developer resources site launched at https://developer.byteball.org<ref>https://twitter.com/slackjore/status/1069216217691508736</ref>
*Oct 15: Smart Vouchers for Real Name Attestation introduced<ref>https://bitcointalk.org/index.php?topic=1608859.msg46911901#msg46911901</ref>
*Oct 14: Filter added to Explorer<ref>https://twitter.com/slackjore/status/1051452800696238080</ref>
*Sep 23: Dice bot added to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg46089759#msg46089759</ref>
*Sep 23: Version 2.6.0 released. Includes ability to hide unused and junk assets<ref>https://bitcointalk.org/index.php?topic=1608859.msg46046016#msg46046016</ref>
*Aug 28: Nousplatform ICO added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg44795934#msg44795934</ref>
*Aug 23: Release of grant-funded Byteball.js, the JavaScript library for Byteball<ref>https://steemit.com/utopian-io/@fabien/byteball-js-the-javascript-library-for-byteball-is-out</ref>
*Aug 20: Version 2.5.0 released, includes sending to @username<ref>https://medium.com/byteball/crypto-does-not-have-to-be-cryptic-e68737b19ba7</ref>
*Jul 27: Version 2.4.2 released, includes full backup and restore for iOS<ref>https://bitcointalk.org/index.php?topic=1608859.msg42998142#msg42998142</ref>
*Jul 16: Version 2.4.1 released, a bugfix to handle the causes of the network crash July 13-15<ref>https://bitcointalk.org/index.php?topic=1608859.msg42296035#msg42296035</ref>
*Jul 12: Wallet version 2.4 released. Includes sending money to Steem username and spending unconfirmed funds<ref>https://bitcointalk.org/index.php?topic=1608859.msg42049495#msg42049495</ref>
*Jul 10: General Roadmap published, including funding for 18 months using one third of undistributed funds<ref>https://medium.com/byteball/the-future-of-byteball-the-byteball-foundation-cca9d495bf46</ref>
*Jul 2: Apple finally approved Byteball wallet for their iOS App Store<ref>https://medium.com/byteball/long-awaited-news-the-byteball-wallet-is-now-available-for-download-from-the-apple-app-store-ca762e817b7c</ref>
*Jun 23: Wallet version 2.3 released. Includes sending blackbytes as textcoins<ref>https://bitcointalk.org/index.php?topic=1608859.msg40698998#msg40698998</ref>
*Jun 7: Added team member Valerius Coppens (@Suirelav) as Head of Marketing and Strategy Development<ref>https://medium.com/byteball/setting-the-course-for-real-world-adoption-head-of-marketing-and-strategy-development-joins-the-e7e653a07c4</ref>
*May 29: Added Private Chat Room bot to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg38902178#msg38902178</ref>
*May 28: Added Exchange Bot for Dual-Chain Tokens to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg38743714#msg38743714</ref>
*May 26: Added Milan Horvarth to the team as Community Manager<ref>https://medium.com/@byteballjesus/byteball-speaking-at-blockshow-europe-berlin-may-28-29-7018f4cec8b5</ref>
*May 11: Added team members Elena Tairova (Communications/PR) and Luke Angell (Partnerships/Events)<ref>https://bitcointalk.org/index.php?topic=1608859.msg36952353#msg36952353</ref>
*May 8: Added @usb.ve (Simón Bolívar University, Venezuela) as white-listed email domain for attestation<ref>https://bitcointalk.org/index.php?topic=1608859.msg36719898#msg36719898</ref>
*May 8: Announced first Byteball Use-a-Thon, at Simón Bolívar University in Caracas, Venezuela<ref>https://bitcointalk.org/index.php?topic=1608859.msg36719898#msg36719898</ref>
*Apr 26: Added World Community Grid linking bot to the Bot Store<ref>https://medium.com/byteball/computing-for-good-again-3795336bdaed</ref>
*Apr 20: Added Accredited investor attestation bot to the Bot Store<ref>https://medium.com/byteball/attestation-of-accredited-investors-d4a8dabf683b</ref>
*Apr 12: Added "Buy Bytes with Visa or Mastercard" bot to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg34561216#msg34561216</ref>
*Apr 4: Paul Murray (@byteballjesus) added to team as Head of Digital Content<ref>https://medium.com/@Suirelav/byteball-whats-happening-april-2018-ddf5018bac23</ref>
*Mar 26: Launching a Telegram [[quiz]] bot that rewards a pass with $5 in Bytes<ref>https://medium.com/byteball/money-for-knowledge-distribution-via-telegram-quiz-bot-2dd400e22997</ref>
*Mar 23: Exchange bot for ICOs added to the Bot Store<ref>https://medium.com/byteball/byteball-exchange-bot-78c8154f4e6a</ref>
*Mar 20: Wallet version 2.2 released. Includes sending funds to multi-addresses and [[Overview#Sending_payments_directly_to_email_addresses|directly to attested emails]]<ref>https://bitcointalk.org/index.php?topic=1608859.msg32784549#msg32784549</ref>
*Feb 18: March 2 and future [[airdrop]]s terminated<ref>https://bitcointalk.org/index.php?topic=1608859.msg30564528#msg30564528</ref>
*Feb 15: SilentNotary ICO added to Bot Store<ref>https://twitter.com/ByteballOrg/status/964267908879781888</ref>
*Jan 26: Free [[fun-coins]] faucet added to Bot Store<ref>https://twitter.com/slackjore/status/957355056235499520</ref>
*Jan 18: Byteball partners with Jumio to offer secure identity verification, which can be linked to a Byteball address and used on demand<ref>https://medium.com/byteball/bringing-identity-to-crypto-b35964feee8e</ref>
*Jan 13: 1000 x $10 in textcoin to go to World Crypto Economic Forum attendees<ref>https://bitcointalk.org/index.php?topic=1608859.msg28047149#msg28047149</ref>
*Jan 13: Eli Taranto now onboard as PR and Marketing director.<ref>https://bitcointalk.org/index.php?topic=1608859.msg28047149#msg28047149</ref>
*Jan 8: How to mass send textcoins using MailChimp.<ref>https://medium.com/byteball-help/using-mailchimp-to-mass-send-payments-as-textcoins-5c1db06342e3</ref>
*Jan 7: First name-registry recognized by the main hub. Reg policy.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27668314#msg27668314</ref>
*Jan 7: Our ICO bot now supports BTC and ETH.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27619698#msg27619698</ref>
*Jan 3: CFD Trading (Trustful) bot added to bot store.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27431192#msg27431192</ref>
*Jan 3: Wallet version 2.1 released.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27376650#msg27376650</ref>

==2017==
*Dec 14: Textcoins enabled in server-side wallets for bulk emails.<ref>https://bitcointalk.org/index.php?topic=1608859.msg26332250#msg26332250</ref>
*Dec 9: Wallet version 2.0 released.<ref>https://bitcointalk.org/index.php?topic=1608859.msg26003939#msg26003939</ref>
*Nov 21: Sports Oracle now supports UFC.<ref>https://bitcointalk.org/index.php?topic=1608859.msg24962770#msg24962770</ref>
*Nov 14: Byteball-Altcoin Exchange Bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg24594142#msg24594142</ref>
*Nov 11: Wallet version 1.11.3 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg24377569#msg24377569</ref>
*Nov 3: First real-world project with ICO on platform: TitanCoin<ref>https://bitcointalk.org/index.php?topic=1608859.msg24004338#msg24004338</ref>
*Oct 18: Wallet version 1.11.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg23182135#msg23182135</ref>
*Oct 2: LuckyBytes lottery bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg22484391#msg22484391</ref>
*Sep 29: Sports Betting bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg22371562#msg22371562</ref>
*Sep 7: Slice&Dice MUD game bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg21607962#msg21607962</ref>
*Sep 5: First Cashback merchants added<ref>https://bitcointalk.org/index.php?topic=1608859.msg21533378#msg21533378</ref>
*Aug 27: Buy Blackbytes bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg21250868#msg21250868</ref>
*Aug 25: Sports Oracle now supports MLB, NBA, NFL, NHL and soccer<ref>https://bitcointalk.org/index.php?topic=1608859.msg21199623#msg21199623</ref>
*Aug 23: Wallet version 1.10.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg21138107#msg21138107</ref>
*Aug 23: Cashback API for merchants is ready<ref>https://bitcointalk.org/index.php?topic=1608859.msg21130417#msg21130417</ref>
*Aug 7: Cashback program launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg20686283#msg20686283</ref>
*Aug 1: Wallet version 1.10.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg20534934#msg20534934</ref>
*Jul 29: Flight Delay Insurance bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg20474959#msg20474959</ref>
*Jun 30: Wallet version 1.9.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg19864486#msg19864486</ref>
*Jun 22: Grants program launched<ref>https://medium.com/byteball/byteball-grants-program-906a71b93d3c</ref>
*Jun 5: Rosie chatbot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg19378793#msg19378793</ref>
*Jun 1: Bot Store launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg19315253#msg19315253</ref>
*Jun 1: Wallet version 1.9.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg19315253#msg19315253</ref>
*May 28: Crowdin now used for wallet translations<ref>https://bitcointalk.org/index.php?topic=1608859.msg19244480#msg19244480</ref>
*May 19: Sports oracle P2P betting on soccer launched in Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg19101028#msg19101028</ref>
*Apr 26: P2P insurance on smart contracts launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18759349#msg18759349</ref>
*Apr 18: Wallet version 1.8 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18646968#msg18646968</ref>
*Apr 7: P2P gambling using smart contracts launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18499180#msg18499180</ref>
*Apr 5: Wallet version 1.7 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18466533#msg18466533</ref>
*Mar 18: Binding payments to oracle-posted events launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18240736#msg18240736</ref>
*Mar 18: Wallet version 1.6 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18240736#msg18240736</ref>
*Mar 6: Wallet version 1.5 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18080683#msg18080683</ref>
*Feb 22: Wallet version 1.4 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17942383#msg17942383</ref>
*Feb 11: Wallet version 1.3 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17808504#msg17808504</ref>
*Feb 10: Chinese WeChat group "Byteball 中国" launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg17803910#msg17803910</ref>
*Feb 3: Transaction Explorer now shows all blackbyte details as only "Hidden Payments"<ref>https://bitcointalk.org/index.php?topic=1608859.msg17720913#msg17720913</ref>
*Feb 3: Wallet version 1.2 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17718842#msg17718842</ref>
*Jan 19: Wallet version 1.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17559287#msg17559287</ref>
*Jan 17: Byte-BTC Exchange bot now live<ref>https://bitcointalk.org/index.php?topic=1608859.msg17527112#msg17527112</ref>

==2016==
*Dec 25: Live network launched. Wallet version 1.0<ref>https://bitcointalk.org/index.php?topic=1608859.msg17303311#msg17303311</ref>
==External links==

==References==
<references />
[[Category:Browse]]

Node

2019-01-19T22:20:08Z

Punqtured: 1 revision imported

==Roles of different types of nodes==

{| class="wikitable"
|-
! Capability !! Hub !! Relay !! Full W !! Light W
|-
| Performs full validation || y || y || y || x
|-
| Relays units || y || y || y || x
|-
| Stores and forwards e2ee messages || y || x || x || x
|-
| Owns funds, owns private keys || x || x || y || y
|-
| Creates transactions || x || x || y || y
|-
| Accepts incoming connections || y || y || y/n || x
|-
| Serves light clients || y || x || x || x
|}

Abbreviations are used so the table is viewable on most mobile screens:

*e2ee = end-to-end encrypted
*W = wallet

===Hub===
See wiki article [[Hub]]

==External links==
*Source: https://docs.google.com/spreadsheets/d/11sZXCJEebtIrcOeMWTvjqbEua-WURsIxCl5EYxscctI/edit#gid=0 Google docs spreadsheet

==References==

[[Category:Nodes]]

Money

2019-01-19T22:20:04Z

Punqtured: 7 revisions imported

This article gives the simplified basics of money with regard to its use in cryptocurrencies.
[[File:zim-money-1.jpg|thumb]]
==What is money?==
Simply stated, money is any item or verifiable record that is generally accepted as payment for goods and services and repayment of debts in a particular country or context. The main functions of money are distinguished as:

===A medium of exchange===
An intermediary used in trade to avoid the inconveniences of a pure barter system.

===A unit of account===
"I'll give you US $50 for that" makes sense because the value of the US dollar is relatively stable. However, when the price of lunch in a restaurant is twice as much at the end of the meal than at the start, that currency is next to worthless as money. All fiat currencies issued by national governments become worthless over time, because they cannot resist the lure of free money made possible by inflating the supply, which results in the devaluation of the currency. $100 was worth a lot more in 1917 than 2017.

===A store of value===
Gold and silver have been used as money for literally thousands of years. Gold bullion in a bank vault or an Indian woman's gold jewelry is a familiar store of value, although it makes lousy money for buying a cup of coffee.

Main source:<ref>https://en.wikipedia.org/wiki/Money </ref>

==Counterparties==
Properly speaking, real money has some intrinsic worth, like gold and silver. All national currencies (Dollar, Euro, Yen etc) are fiat currencies based on debt. All usual paper "assets" -- bonds, shares, pension funds, bank accounts etc -- have counterparties, a debtor on one side and a creditor on the other. If push comes to shove, and the debtor is unable to pay, one's "asset" becomes painfully worthless.

Nowadays, such paper assets often exist in digital/electronic form, but this does not change the counterparty component. Globally, the amount of national currency in digital form (not coins and banknotes) is about 95%. There is a big difference between centralized, top-down, government digital money (even if a cryptocurrency) and decentralized, grassroots cryptocurrencies.

Does a cryptocurrency have any intrinsic value? One could argue both yes and no, but what a cryptocurrency platform does not have is the risk of a counterparty going belly-up reducing the value of the cryptotokens in your wallet to zero.

==What is a cryptocurrency?==
A cryptocurrency (or crypto currency) is a digital asset designed to work as a medium of exchange using cryptography to secure the transactions and to control the creation of additional units of the currency.

Bitcoin became the first decentralized cryptocurrency in 2009. Since then, numerous cryptocurrencies have been created. These are frequently called ''altcoins'', as a blend of ''bitcoin alternative''. Bitcoin and its derivatives use decentralized control as opposed to centralized electronic money/centralized banking systems. The decentralized control is related to the use of Bitcoin's blockchain transaction database in the role of a distributed ledger.<ref>https://en.wikipedia.org/wiki/Cryptocurrency</ref>

Crypto payments generally:
*are sent peer-to-peer, with no intermediary like a bank or credit-card company
*require no permission from a central authority
*are irrevocable: once the payment is sent it's sent and that's it.

==How well do cryptos satisfy the three main functions of money?==

===A medium of exchange===
Very few merchants, and very few customers, have adopted '''any''' cryptocurrency. We are barely into the early-adoption phase.

===A unit of account===
Generally a crypto's price is very volatile on a day-to-day -- even minute-to-minute -- basis. It is not uncommon for one to go up 100% in a week, then down 20% in an hour. Crypto veterans grow accustomed to this behavior and shrug it off, but it can be unnerving to the new user.

===A store of value===
Bitcoin and many altcoins have appreciated hundreds or thousands of times in a few years. Some have gone to zero. But it is an asymmetric investment. If you invest, say, $1000 in a crypto that looks promising, and there is a distinct chance you may make $100,000; while (usually) the most you can lose is the $1000.

So overall, cryptos currently make lousy money for everyday use but have HUGE potential as speculative asymmetric investments.

==Additional properties of a good currency==
===Fungibility===
The units of the currency are interchangeable. Generally speaking, one $20 bill is as valuable as any other $20 bill; one ounce of gold is as valuable as any other ounce of gold.

===Divisibility===
The currency exists in sufficient denominations to be useful in everyday trade. This applies to almost all national currencies that aren't hyperinflating. You can buy a pack of chewing gum or a cheap used car in US $ cash. Gold is useless for buying gum, unless the gum-seller will accept a tiny pinch of gold dust. Well-known US gold coins like the 1-ounce Eagle and 1/10-ounce Eagle have (approximate) values of $1200 and $120 each, so unless the car price is some multiple of those, it won't work. And even if the car's asking price is $1200, the seller probably wouldn't accept an Eagle in exchange.

===Portability===
You can easily move it around. This varies depending on the amounts involved. It is easy to carry US $100 in your wallet. It is harder to quickly wire $10 million abroad, and very hard to both get hold of and safely transport $10 million in cash. Anytime you cross the Canadian border, you must declare any currency or monetary instruments you have valued at Can $10,000 or more. Carrying $12,000-worth of gold coins in your pocket is easy, as they would weigh about 10 ounces. But $12,000-worth of silver coins would weigh about 500 ounces.

===Resistance to attack===
Nation states attack other national currencies all the time. If you devalue your own currency your exports become cheaper, giving you an advantage in international trade. A competitor may be forced to follow suit. But more expensive imports accompany the cheaper exports, driving up the costs of producers and citizens generally. Many countries do it. It’s a race to the bottom.

A [[local currency]] is a currency that can be spent in a particular geographical locality at participating organisations. A local currency acts as a complementary currency to a national currency, rather than replacing it, and aims to encourage spending within a local community, especially with locally-owned businesses. These are basically no threat to a national currency, so get largely ignored by the State.<ref>https://en.wikipedia.org/wiki/Local_currency</ref>.

===Easy to recognise===
Is what you are being offered for your service or good the real thing? Is it a counterfeit that won't be accepted when you try to buy something with it later on? National currencies do pretty well at this, especially ones that have been in use for some time. There may well be counterfeit notes or coins in circulation, but if the fake was good enough to fool you it will probably also fool whoever you pass it on to. Gold and silver coins are much harder to use, because they are very unfamiliar generally and hardly anyone can validate one except for a professional coin dealer.

==How well do cryptos satisfy these additional properties?==
===Fungibility===
Generally, not well. The entire history of the coins making up a bitcoin address is readily available online, at least in terms of earlier associated addresses. What if, unknown to you, the bitcoins you just sent to your grandmother for her birthday were stolen from an orphanage's main (crypto) savings fund last month? This is known as "taint", and it means some coins may be considered less desirable than other coins.

It's all very well to declare that a coin's history doesn't matter -- and in practice, it's impossible to trace the entire history of an address's coins unless close to their creation -- but what if you run an exchange and you discover someone trying to offload $10 million of cryptocoins you '''know''' were stolen last week?

What if some government decides to mandate that a merchant may only accept a crypto payment from a registered (i.e., linked to a known identity) address?

Very few cryptos are free of this problem. Byteball's blackbytes are, its (white)bytes aren't.

===Divisibility===
Bingo! Cryptos tend to excel at this, better than any non-crypto currency. It is as easy to send a crypto payment equivalent of $10 million as one of $0.001.

===Portability===
Cryptos excel at this too. A paper wallet or Byteball [[textcoin]] could hold your entire life savings.

===Resistance to attack===
A decentralised cryptocurrency is hard for a State to destroy, especially since it is usually global. Look what happened when the centralised file-sharing innovator Napster got stomped out of existence: peer-to-peer file-sharing software got developed, and now how successful are governments or big media corporations at stamping out the use of bittorrent? Perhaps in the future some country will make it illegal for a merchant to accept crypto payments, and the value of the currency will plummet. Perhaps. It is hard to say what the future will bring. In the meantime, enjoy the ride.

===Easy to recognise===
Cryptos suffer from the same problem as gold and silver coins: general lack of familiarity. You couldn't pass off a fake bitcoin to someone familiar with how it all works, but you could show a noob one of those Chinese novelty metal "bitcoins" that cost $2 each and he wouldn't know the difference from the real thing.

==Any other advantages to a cryptocurrency?==
*Crypto markets seem to be free of State manipulation.

*Its issuance rate is generally known from the beginning.

*It is not subject to whims of the State such as making worthless 86% of the cash in use (India, 2016) or stealing maybe 20% of bank deposits (Cyprus, 2013). So if you are concerned about your government confiscating your pension fund or bank account savings, or your stock-market investments tanking, cryptos '''may''' provide a way out.

*Cryptos are programmable money, some more so than others.

*Fractional payments become possible. For example, a taxi-driver could receive a small payment at the completion of every kilometer (or even every meter). Most importantly, the partial payments would immediately become hers, and she could, in theory, be spending that money elsewhere even before the trip is complete.<ref>https://www.coininsider.com/lightning-network/</ref>

==Is a cryptocurrency actually a currency?==

===Currency vs commodity===
The traditional definition of a currency is that it is a medium of exchange and a store of value. The traditional definition of a commodity is that it is a nearly-perfectly fungible good. A commodity could be used as a currency if it is convenient to do so. Likewise, a currency can become a commodity under certain conditions.

===Because taxes===
Should cryptos be treated in law as currencies or commodities, each with their own established rules and regulations? Unfortunately it is generally impossible to neatly pigeonhole them as one or the other.

Currently different States are struggling with how to treat cryptocurrencies, with no consensus among them. The IRS treats cryptos as regular commodities subject to capital gains taxes, meaning that you should somehow keep minute track of every satoshi acquired and spent, with the $-equivalent noted at the times of acquisition and disposal.

<blockquote>For Bitcoins, however, if there is a path to full currency status it is likely in future generations of the technology that address version 1.0’s weaknesses, including anticipating how the government will surely intervene to block it. Until you can whip out your phone and pay in bitcoins without issuing a 1099 [IRS tax form] and calculating the capital gains tax on the transaction (or maybe there will be an app that will do both?) the potential is limited to largely the specific forms of commerce currently open to them (more so black market or darknet).<ref>http://www.zerohedge.com/news/2017-05-26/bitcoin-rebounds-2600-greshams-law-looms</ref></blockquote>

While this is clearly unreal except in broad strokes and will make the average crypto-user guilty of tax evasion even if they are '''trying''' to do it right, Governments tend to want their pound of flesh wherever they can get it and aren't too likely to merely roll over and give cryptos a free pass.

==General adoption of cryptocurrencies by society==
A study on Americans and cryptocurrencies, commissioned by Finder.com in February 2018, shows that 8 percent, or around 26 million, of Americans have purchased cryptocurrency.<ref>https://cointelegraph.com/news/new-survey-shows-around-26-mln-americans-own-and-8-percent-plan-to-buy-cryptocurrencies</ref> They also found:
[[File:crypto-adoption-2018.jpg|reasons why people don't invest in cryptos]]
{{clear}}

==Comparison of market sizes==
Figures are approximate, and given in US$ millions (equivalent value)

{| class="wikitable"
|-
! Market !! Daily global trading volume
|-
| Bonds || 100,000,000
|-
| Forex || 5,000,000
|-
| Equities || 200,000
|-
| Gold || 30,000
|-
| Cryptos || 5,000
|-
| Silver || 2,000
|-
| '''Byteball''' || 0.2
|}

==Finally, food for thought==
[[File:zim-money-2.jpg|thumb|left]]
<blockquote>Paper money eventually returns to its intrisic value: zero. -- Voltaire</blockquote>

According to an interesting study of the 775 fiat currencies that have existed 599 are no longer in circulation. The median life expectancy for the defunct currencies? Fifteen years. Perhaps the author was being unfair by focusing solely on the failures. '''Sadly no, the average life expectancy of all fiat currency is running at a truly underwhelming 27 years.''' Only a select few have managed anything approaching old age. The British pound sterling is one such example at over 300 years and counting. Before we get too excited by this apparent example of longevity, at inception the pound was defined as 12 ounces of silver. The pound is now worth less than 0.5% of this original value and of course there is no silver involved anywhere. In other words, '''the most successful currency in existence in terms of life-span has lost more than 99% of its value.'''<ref>http://historysquared.com/2012/06/26/fiat-currencies-trend-towards-their-intrinsic-value-often-rather-quickly Stephen Johnson</ref>

==Also see==
* https://www.zerohedge.com/news/2018-03-16/bitcoin-bubble-or-hyperdeflation Useful article, especially long-term chart of fiat currencies vs gold
* https://medium.com/@vijayboyapati/the-bullish-case-for-bitcoin-6ecc8bdecc1 See especioally section on evolution of money, first as a collectible, then store of value, then medium of exchange, and lastly as unit of account

==References==
<references />

[[Category:Browse]]

Market capitalization

2019-01-19T22:20:03Z

Punqtured: 4 revisions imported

What the term normally means and how it is applied to cryptocurrencies.

==What is market capitalization?==
The well-known site CoinMarketCap<ref>https://coinmarketcap.com</ref> lists hundreds of altcoins next to their "Market Cap", along with a large amount of timely data on each. But what exactly is a cryptocurrency’s "Market Cap"?

==Normal usage==
Market capitalization is the aggregate valuation of the company based on its current share price and the total number of outstanding stocks. It is calculated by multiplying the current market price of the company's share with the total outstanding shares of the company.<ref>https://economictimes.indiatimes.com/definition/market-capitalization</ref>

"Outstanding" here means not inside the company's own Treasury. Some, even all, of these outstanding shares may have legal restrictions preventing the owners dumping them on the market at any time.

===But unicorns!===
Decades ago the term was taken to mean something. It started to look wild in 2000 when TimeWarner, a long-established company with huge real-world holdings of studios, magazines and newspapers, a vast movie back-catalog, and much more <strike>got taken over by</strike> merged with AOL (America OnLine), an internet upstart with lots of people in offices, billions of distributed CDs to get people onto this new-fangled Internet thingy -- most now in landfills or hanging up in gardens to scare away birds -- and little else.

Today, Uber, the ride-share <strike>company</strike> app, again has lots of people in offices and owns little else, and somehow is considered -- by virtue of its insane market cap -- to be worth more than Exxon-Mobil with all its heavy-duty oil drilling platforms, pipelines, refineries, 70,000 employees getting their hands dirty out in the real world, and so on.

===Conclusion===
A company's market cap does give some indication of the company's size, but don't read too much into it.

==Crypto usage==
It is generally taken to be the aggregate valuation of a cryptocurrency based on its current unit price multiplied by the number of units in circulation. So if you look it up at CoinMarketCap, the market cap for Bitcoin is the current price multiplied by the number of coins created so far (about 17 million out of the total of 21 million that will have been created by 2140). And the market cap for [[Main_Page|Byteball]] is the current market price multiplied by the number of units so far distributed (about 645,000) out of the total 1,000,000 already created and due for full distribution maybe in 2018.

==No problem, right?==
Well, not exactly. It's fine if you don't look too closely. But look at these examples:

'''A new scamcoin:''' Some lazy scammer instamines 50% (21 million) of the intended final total volume (42 million) of his new coins, ''buttclones''. He sells one ''buttclone'' to a friend for $5. So the market cap of the ''Buttclones'' platform is $105 million?

'''(More examples from real coins should be added)'''

==Conclusion==
Like a commercial company, a crypto's market cap does give some indication of its size, but don't read too much into it.

==References==
<references />

[[Category:Browse]]

Invest

2019-01-19T22:20:02Z

Punqtured: 3 revisions imported

The text below was posted in reddit.com/r/dashpay by forgoodnessshakes 2017-06-13 and is copied here with permission. It applies to [[Main_Page|Byteball]] too.

== Crypto investment questions ==

All crypto-currencies are high-risk investments that can produce a high rate of return or large losses. Is this the type of investment you are looking for?

The best thing is to get to know what you are buying by asking the questions (these are mine, add your own):
* Is it useful?
* Do other tokens fulfill the same need?
* Is it a natural monopoly (likely to be only one token in this market or many)?
* Is it scarce/limited supply?
* Is it actively under development?
* Do you admire the 'cleverness' of the project?
* Is the development reliant on volunteers?
* Does it have a large community?
* Does it have a network of users?
* Does it have first-mover advantage?
* Is it liquid enough to get out in small amounts or in total?
* Is there a large market?
* Can it scale?
* Is demand likely to exceed supply?
* Can you hold it long enough to iron out any bumps in growth?
Review the competitor's criticisms of it - are they at all valid?

Lastly, does the thought of buying it get your Spidey-senses tingling? Do you 'sense' it is undervalued? Then swoop.

[[Category:Browse]]

License

2019-01-19T22:20:02Z

Punqtured: 3 revisions imported

Creative Commons Attribution-ShareAlike 3.0 Unported License
==License and copyright==
All the content of this [[Main_Page|wiki]] is copyrighted by the wiki editors and contributors and is formally licensed to the public under the Creative Commons Attribution-ShareAlike 3.0 Unported License<ref>https://creativecommons.org/licenses/by-sa/3.0</ref>.

==Human-readable summary of the full license==
[[File:Cc-deed.png|thumb|center]]

==See also==
*[https://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License Text of license]
*[https://en.wikipedia.org/wiki/Wikipedia:Copyrights Wikipedia Copyrights]

==References==
<references />

[[Category:Browse]]

Local currency

2019-01-19T22:20:02Z

Punqtured: 1 revision imported

In economics, a '''local currency''' is a currency that can be spent in a particular geographical locality at participating organisations. A '''regional currency''' is a form of local currency encompassing a larger geographical area. A local currency acts as a complementary currency to a national currency, rather than replacing it, and aims to encourage spending within a local community, especially with locally owned businesses.[2] The currency may not be backed by a national government or be legal tender.<ref>https://en.wikipedia.org/wiki/Local_currency</ref>

==Examples==
===Bristol, UK===
The Bristol Pound (£B) is a form of local complementary currency, or community currency launched in Bristol, UK on 19 September 2012. Its objective is to encourage people to spend their money with local, independent businesses in Bristol. As of September 2012 it is the largest alternative in the UK to official sterling currency, though it is backed by Sterling.<ref>https://en.wikipedia.org/wiki/Bristol_Pound</ref>

It is the first local currency that can be used to pay local taxes, and the council has offered its 17,000 staff the option of receiving part of their pay in the currency. The scheme is run as a not-for-profit social enterprise partnership between the Bristol Pound Community Interest Company and Bristol Credit Union. Bristol Pounds can be spent as hard currency, by SMS text message or online through electronic accounts managed by Bristol Credit Union. Business accounts are available to traders that are independently owned and based in or around Bristol. While Bristol pounds are in free circulation, they are not legal tender, and accepting the currency is voluntary for organisations. Money can only be taken out of the system by registered account holders.<ref>https://www.designweek.co.uk/issues/may-2012/bristol-launches-local-currency/ 2012009-19 article</ref>

===Totnes, UK===
{{#ev:youtube|https://www.youtube.com/watch?v=WQtlkgAPuto|thumb}}

Pounds are available in electronic or paper form. You can get paper ones by exchanging regular British sterling pounds one-for-one at some local businesses. Online, you can register an account, then transfer British pounds into it from your regular bank account. The amount you transferred will appear in your Totnes Pound account within 3 working days ready for spending with Pay-by-Text (SMS on any mobile phone, no smartphone needed) or online.<ref>https://www.totnespound.org/</ref>

====Fees====
*'''Changing e-t£s back to sterling:''' If you need to change e-t£s back into sterling you will be charged a 2% fee.
* '''Pay-by-Text charges:''' If you pay another individual (not a business) by Pay-by-Text you will be charged 2% (minimum 10p, maximum £1.99).
It is not clear if these fees are current.

====Taxes====
For tax purposes all Totnes Pound transactions are treated as if they were made in sterling. So this will not affect how a business declares revenues, expenses and any taxable profits to HMRC [UK IRS equivalent). Likewise VAT should be charged based on the price of goods as normal. On completing VAT returns, payments to HMRC must be made in sterling.

====Financing====
Financing for this is provided by a national governmental body, the UK Technology Strategy Board<ref>https://en.wikipedia.org/wiki/Innovate_UK</ref>

==Byteball factors==
* '''If a feasible idea:''' Would add to [[token]] types.
* '''Technology leap:''' a crypto wallet is an unfamiliar interface, whereas using web sites, doing online bank transfers and sending texts are more familiar.
* '''Financing:''' Would the whole scheme still get subsidised by a government body, or would it be "You're on your own"?
* '''Backing:''' A regular trusted (ahem) financial institution would have to issue the Byteball Local Currency Tokens (LCTs) into the community, and hold the regular fiat currency backing these. This would need to be severely audited.
* '''How does an individual get LCTs?''' In person, individual hands over fiat cash and gets equivalent amount in LCTs (two decimals!) transferred from trader's wallet to individual's wallet. Online individual provides single-address wallet address, with bank account data, and makes regular online bank transfer.
* '''How does an individual get bytes for transaction fees?''' Provided at the same time as the LCTs.
* '''How does an individual pay a trader?''' From the individual's view, they just send a regular Byteball transaction, manually inputting the amount and using a QR code for the receive address. This works in the shop or online.
* '''How does the trader handle it?''' The figures are easy enough to input into his accounting admin. The accrued LCTs he can, (1) give back to customers as change after they paid in fiat, (2) pay his suppliers if they accept LCTs, or (3) exchange for regular fiat with the financial institution.
* '''Who shows customers how to use the wallet?''' Traders, if they've got time. More likely the paid Byteball Guys.
* '''Who shows traders how to use the wallet?''' It would have to be the paid Byteball Guys.
* '''Who recruits traders?''' The paid Byteball Guys.
* '''Who recruits individuals?''' The paid Byteball Guys.
* '''Who mainly keeps it all running?''' The paid Byteball Guys.
* '''Who recruits/trains the Byteball Guys' Team Leader?''' To be determined
* '''Who funds all this?''' :)

== See also ==

== References ==
<references />

[[Category:Browse]]
[[Category:Tokens]]