http://wiki.obyte.org/mediawiki/api.php?action=feedcontributions&user=Slackjore&feedformat=atomObyte Wiki - User contributions [en]2024-03-28T16:01:20ZUser contributionsMediaWiki 1.32.0http://wiki.obyte.org/mediawiki/index.php?title=Oracle&diff=1557Oracle2020-03-08T12:18:29Z<p>Slackjore: /* Precious metals exchange rates */ added note re moving averages addition</p>
<hr />
<div>An ORACLE is a trusted third party that monitors specific external events and imports them into the Obyte database as a data feed. An example is a list of cryptocurrency exchange rates updated every ten minutes.<br />
<br />
==Known oracles==<br />
'''P2P exchange of Bytes vs. Bitcoin'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-ii-bitcoin-exchange-d98adfbde2a5</ref> | FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH<br />
<br />
'''P2P random numbers gambling''' | FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH (same oracle as above) <br />
<br />
'''Crypto exchange rates'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-iii-prediction-markets-f40d49c0abab</ref> | JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC<br />
<br />
'''Flight delay tracker for flight delays insurance'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-iv-p2p-insurance-cbbd1e59d527</ref> | GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN <br />
<br />
'''Sports betting on soccer match results'''<ref>[[Sports betting]]</ref> | TKT4UESIKTTRALRRLWS4SENSTJX6ODCW <br />
<br />
'''Timestamp in Unix Epoch Time'''<ref>[[Timestamp]]</ref> | I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT <br />
<br />
'''Precious metals exchange rates oracle''' | DXYWHSZ72ZDNDZ7WYZXKWBBH425C6WZN<br />
<br />
==Contract times==<br />
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.<br />
<br />
===Peer non-payment===<br />
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).<br />
<br />
===Contract expiry===<br />
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.<br />
<br />
==Personal oracles==<br />
{{#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.<br />
<br />
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.<br />
<br />
This sort of thing could be used as part of a [[family tokens]] set-up in a household.<br />
<br />
{{clear}}<br />
<br />
==Example of trading using an oracle==<br />
[[File:Oracle-1.png|thumb|left|upright=0.66]][[File:Oracle-2.png|thumb|none|upright=0.66]]<br />
<br />
{{clear}}<br />
<br />
From the Slack Obyte #prediction_markets forum, tonych:<br />
<br />
<blockquote>This is a trading floor, shout out your offers like in the old times. For example: <br />
"I bet on BTC going below 1150 within 1 day, I pay 0.3GB out of 1GB"</blockquote><br />
<br />
Use the crypto exchange rates oracle for this.<br />
<br />
<div style="clear: both;"></div><br />
==Using the crypto-exchange-rates oracle in a smart contract==<br />
{{#ev:youtube|https://www.youtube.com/watch?v=tjWHxlHBGAg|200|right}}<br />
<br />
# 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.<br />
# 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.<br />
# 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.<br />
# When you get to ORACLE ADDRESS, copy/paste in the crypto exchange rates one: '''JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC'''<br />
# 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'''<br />
# 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.<br />
# '''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).'''<br />
# Your peer clicks Send on the payment request. The new contract will be visible as a smart wallet.<br />
# Now you both wait. You can view an up-to-date feed from that oracle by entering its full JPQ… address in the [Obyte explorer search box](http://explorer.obyte.org). As soon as one party fulfills the terms of the contract its funds can be spent.<br />
{{clear}}<br />
<br />
==Random numbers==<br />
{{#ev:vimeo|https://vimeo.com/221655112|thumb|right|'''Betting on Random Numbers'''}} Video in Hi-Def and with English subtitles.<br />
# 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.<br />
# 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.<br />
# 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.<br />
# When you get to ORACLE ADDRESS, copy/paste in the random-numbers-gambling one: '''FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH'''<br />
# Here is an example of the data feed from this oracle:<ref><br />
https://explorer.byteball.org/#Ns//o52EKR32ykuHfUfcm3ailHtta6TvM5kB07vbpVA=<br /> <br />
bitcoin_hash: 0000000000000000019dd457cf8e233701dab44ac855492d575a4366556213e0<br /> <br />
bitcoin_height: 460852<br /> <br />
bitcoin_merkle: GW9cQW5m0KLIi2suUlkzRP2yurg8jLEax3uHiun7kik=<br /> <br />
random460852: 34789<br />
</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'''<br />
# 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.<br />
# '''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).'''<br />
# Your peer clicks Send on the payment request. The new contract will be visible as a smart wallet.<br />
# 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.<br />
<br />
==Flight delays tracker==<br />
{{#ev:vimeo|https://vimeo.com/222006250|thumb|right|'''Betting on Flight Delays'''}} Video in Hi-Def and with English subtitles.<br />
<br />
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: <br />
<br />
*30 minutes delay: 0.082258065 GB <br />
*1 hour delay: 0.079996985 GB <br />
*2 hour delay: 0.070952668 GB <br />
*4 hour delay: 0.066129032 GB<br />
<br />
<div style="clear: both;"></div><br />
<br />
== Precious metals exchange rates ==<br />
This oracle [https://obyte.io/@DXYWHSZ72ZDNDZ7WYZXKWBBH425C6WZN posts units] every 10 minutes. The data feed shows 20 pairs, such as XAG_BTC, XAG_EUR, XAU_USD, XAG_GBYTE and XAU_GBLACKBYTE, sourced from https://1forge.com/forex-data-api/currency-pair-list. Global precious metals markets are closed over the weekend, Friday 21:00 - Sunday 21:00 UTC, so the oracle will not post during these times.<br />
<br />
This oracle can be used in the same way as the crypto exchange rates oracle, the only difference being the oracle address and ticker of the pair. Each oracle also shows moving averages over the previous ten units, GBYTE_USD_MA and GBYTE_BTC_MA for the exchange rates and GBYTE_XAU_MA and GBYTE_XAG_MA for the precious metals.<br />
<br />
==External links==<br />
<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Features]]<br />
[[Category:Trading]]<br />
[[Category:Oracles]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Main_Page&diff=1556Main Page2020-03-07T13:23:02Z<p>Slackjore: added Mar 5 news item</p>
<hr />
<div>__NOTOC__<br />
[[File:Obyte-logo.jpg|thumb|250px]] <br />
'''Welcome to the Obyte Wiki. See first a one-page [[overview|OVERVIEW]], the [[glossary|GLOSSARY]], and the [[wallet|WALLET]] page. See [[Special:AllPages|ALL PAGES here]].'''<br />
<br />
==Introduction==<br />
Obyte, formerly Byteball, now listed on CoinMarketCap<ref>https://coinmarketcap.com</ref> as simply ''Obyte'', is a DAG-based cryptocurrency developed by Anton (Tony) Churyumov.<br />
<br />
This wiki is aimed at general cryptocurrency users, as well as Obyte users, who want to become better informed about Obyte. <br />
<br />
The wiki content is currently generated by invited contributors, and not randomly.<br />
<br />
==License==<br />
All content of this wiki is available under a Creative Commons Attribution-ShareAlike 3.0 Unported [[License]].<br />
<br />
== External links ==<br />
*[https://obyte.org Main official site]<br />
*[https://explorer.obyte.org Transactions explorer]<br />
*[https://obyte.org/Byteball.pdf White paper]<br />
*[https://medium.com/Obyte ''Medium'' articles]<br />
*[https://www.youtube.com/channel/UCYAjbxT5zHfeTtXe_hr9Gxg Obyte Channel on YouTube]<br />
*[https://asset.obyte.app Obyte Asset Registry for you to create a new asset]<br />
*[https://github.com/byteball/byteball Repository]<br />
*[https://obyte.io An Obyte data explorer]<br />
<br />
===Forums===<br />
*[https://discord.obyte.org Discord channel invitation] <br />
*[https://bitcointalk.org/index.php?topic=1608859.0) Bitcointalk thread]<br />
*[https://bitcointalk.org/index.php?action=profile;u=412662;sa=showPosts;start=0) Tony's posts on bitcointalk]<br />
*[https://reddit.com/r/obyte Subreddit]<br />
*[https://telegram.me/obyte Telegram]<br />
*[https://twitter.com/ObyteOrg Twitter]<br />
<br />
==Latest [[News]]==<br />
*Mar 5: Version 3.0.2 released (mandatory, bug fix)<ref>https://github.com/byteball/obyte-gui-wallet/releases/tag/v3.0.2</ref><br />
*Feb 25: Version 3.0.1 released (mandatory, bug fix)<ref>https://github.com/byteball/obyte-gui-wallet/releases/tag/v3.0.1</ref><br />
*Feb 19: Version 3.0.0 released, preparatory to activating AAs on mainnet on 29 Feb<ref>https://medium.com/obyte/autonomous-agents-on-mainnet-ready-for-takeoff-d89b50e6d921</ref><br />
*Feb 6: [[PolloPollo]] 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><br />
*Dec 27: Bosch Connectory announced as the 3rd default witness (order provider)<ref>https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03</ref><br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=News&diff=1555News2020-03-07T13:19:43Z<p>Slackjore: added Mar 5 item</p>
<hr />
<div>Very brief '''headline''' items only, with links to each announcement, usually on Bitcointalk as a permanent record.<br />
<br />
== 2020 ==<br />
*Mar 5: Version 3.0.2 released (mandatory, bug fix)<ref>https://github.com/byteball/obyte-gui-wallet/releases/tag/v3.0.2</ref><br />
*Feb 25: Version 3.0.1 released (mandatory, bug fix)<ref>https://github.com/byteball/obyte-gui-wallet/releases/tag/v3.0.1</ref><br />
*Feb 19: Version 3.0.0 released, preparatory to activating AAs on mainnet in approx 2 weeks<ref>https://medium.com/obyte/autonomous-agents-on-mainnet-ready-for-takeoff-d89b50e6d921</ref><br />
*Feb 6: [[PolloPollo]] announced as the 4th default witness (order provider)<ref>https://medium.com/obyte/pollopollo-approved-to-become-a-default-witness-on-the-obyte-public-network-9ee32238142f</ref><br />
<br />
==2019==<br />
*Dec 27: Bosch Connectory announced as the 3rd default witness (order provider)<ref>https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03</ref><br />
*Sep 25: Version 2.8.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg52555921#msg52555921</ref><br />
*Aug 7: The first Ocademy (Obyte Academy) student graduates<ref>https://medium.com/obyte/meet-the-first-ocademy-workshop-graduate-133617202c</ref><br />
*Aug 5: Sports oracle updated to work with [[Autonomous Agent]]s<ref>https://medium.com/obyte/sports-oracle-for-autonomous-agents-96b56369168a</ref><br />
*Aug 1: "What's [[next]] for Obyte" blog launched<ref>https://medium.com/obyte/whats-next-for-obyte-b495cfbb698</ref><br />
*Jul 18: Autonomous Agents protocol upgrade released on Testnet<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
*Jun 11: Version 2.7.2 released<ref>https://github.com/byteball/obyte-gui-wallet/releases</ref><br />
*Apr 30: Obyte Foundation Establishment announced<ref>https://medium.com/obyte/obyte-foundation-is-established-c92a28d2d20e</ref><br />
*Apr 20: Version 2.7.0 released. Includes prosaic contracts.<ref>https://github.com/byteball/obyte-gui-wallet/releases</ref><br />
*Apr 16: 2nd independent witness candidate announced<ref>https://medium.com/obyte/second-independent-witness-candidate-fabien-marino-d4e8dccadee</ref><br />
*Apr 10: New method of identity verification launched for residents of Estonia, Latvia, Lithuania, and e-residents of Estonia.<ref>https://medium.com/obyte/new-methods-for-identity-verification-3d5045287533</ref><br />
*Jan 17: Byteball rebranded to Obyte<ref>https://medium.com/byteball/byteball-rebrand-the-next-step-to-real-world-adoption-6a0a924390de</ref><br />
<br />
==2018==<br />
*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><br />
*Dec 1: Byteball developer resources site launched at https://developer.byteball.org<ref>https://twitter.com/slackjore/status/1069216217691508736</ref><br />
*Oct 15: Smart Vouchers for Real Name Attestation introduced<ref>https://bitcointalk.org/index.php?topic=1608859.msg46911901#msg46911901</ref><br />
*Oct 14: Filter added to Explorer<ref>https://twitter.com/slackjore/status/1051452800696238080</ref><br />
*Sep 23: Dice bot added to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg46089759#msg46089759</ref><br />
*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><br />
*Aug 28: Nousplatform ICO added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg44795934#msg44795934</ref><br />
*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><br />
*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><br />
*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><br />
*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><br />
*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><br />
*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><br />
*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><br />
*Jun 23: Wallet version 2.3 released. Includes sending blackbytes as textcoins<ref>https://bitcointalk.org/index.php?topic=1608859.msg40698998#msg40698998</ref><br />
*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><br />
*May 29: Added Private Chat Room bot to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg38902178#msg38902178</ref><br />
*May 28: Added Exchange Bot for Dual-Chain Tokens to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg38743714#msg38743714</ref><br />
*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><br />
*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><br />
*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><br />
*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><br />
*Apr 26: Added World Community Grid linking bot to the Bot Store<ref>https://medium.com/byteball/computing-for-good-again-3795336bdaed</ref><br />
*Apr 20: Added Accredited investor attestation bot to the Bot Store<ref>https://medium.com/byteball/attestation-of-accredited-investors-d4a8dabf683b</ref><br />
*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><br />
*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><br />
*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> <br />
*Mar 23: Exchange bot for ICOs added to the Bot Store<ref>https://medium.com/byteball/byteball-exchange-bot-78c8154f4e6a</ref><br />
*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><br />
*Feb 18: March 2 and future [[airdrop]]s terminated<ref>https://bitcointalk.org/index.php?topic=1608859.msg30564528#msg30564528</ref><br />
*Feb 15: SilentNotary ICO added to Bot Store<ref>https://twitter.com/ByteballOrg/status/964267908879781888</ref><br />
*Jan 26: Free [[fun-coins]] faucet added to Bot Store<ref>https://twitter.com/slackjore/status/957355056235499520</ref><br />
*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><br />
*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><br />
*Jan 13: Eli Taranto now onboard as PR and Marketing director.<ref>https://bitcointalk.org/index.php?topic=1608859.msg28047149#msg28047149</ref><br />
*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><br />
*Jan 7: First name-registry recognized by the main hub. Reg policy.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27668314#msg27668314</ref><br />
*Jan 7: Our ICO bot now supports BTC and ETH.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27619698#msg27619698</ref><br />
*Jan 3: CFD Trading (Trustful) bot added to bot store.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27431192#msg27431192</ref><br />
*Jan 3: Wallet version 2.1 released.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27376650#msg27376650</ref><br />
<br />
==2017==<br />
*Dec 14: Textcoins enabled in server-side wallets for bulk emails.<ref>https://bitcointalk.org/index.php?topic=1608859.msg26332250#msg26332250</ref><br />
*Dec 9: Wallet version 2.0 released.<ref>https://bitcointalk.org/index.php?topic=1608859.msg26003939#msg26003939</ref><br />
*Nov 21: Sports Oracle now supports UFC.<ref>https://bitcointalk.org/index.php?topic=1608859.msg24962770#msg24962770</ref><br />
*Nov 14: Byteball-Altcoin Exchange Bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg24594142#msg24594142</ref><br />
*Nov 11: Wallet version 1.11.3 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg24377569#msg24377569</ref><br />
*Nov 3: First real-world project with ICO on platform: TitanCoin<ref>https://bitcointalk.org/index.php?topic=1608859.msg24004338#msg24004338</ref><br />
*Oct 18: Wallet version 1.11.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg23182135#msg23182135</ref><br />
*Oct 2: LuckyBytes lottery bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg22484391#msg22484391</ref><br />
*Sep 29: Sports Betting bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg22371562#msg22371562</ref><br />
*Sep 7: Slice&Dice MUD game bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg21607962#msg21607962</ref><br />
*Sep 5: First Cashback merchants added<ref>https://bitcointalk.org/index.php?topic=1608859.msg21533378#msg21533378</ref><br />
*Aug 27: Buy Blackbytes bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg21250868#msg21250868</ref><br />
*Aug 25: Sports Oracle now supports MLB, NBA, NFL, NHL and soccer<ref>https://bitcointalk.org/index.php?topic=1608859.msg21199623#msg21199623</ref><br />
*Aug 23: Wallet version 1.10.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg21138107#msg21138107</ref><br />
*Aug 23: Cashback API for merchants is ready<ref>https://bitcointalk.org/index.php?topic=1608859.msg21130417#msg21130417</ref><br />
*Aug 7: Cashback program launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg20686283#msg20686283</ref><br />
*Aug 1: Wallet version 1.10.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg20534934#msg20534934</ref><br />
*Jul 29: Flight Delay Insurance bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg20474959#msg20474959</ref><br />
*Jun 30: Wallet version 1.9.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg19864486#msg19864486</ref><br />
*Jun 22: Grants program launched<ref>https://medium.com/byteball/byteball-grants-program-906a71b93d3c</ref><br />
*Jun 5: Rosie chatbot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg19378793#msg19378793</ref><br />
*Jun 1: Bot Store launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg19315253#msg19315253</ref><br />
*Jun 1: Wallet version 1.9.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg19315253#msg19315253</ref><br />
*May 28: Crowdin now used for wallet translations<ref>https://bitcointalk.org/index.php?topic=1608859.msg19244480#msg19244480</ref><br />
*May 19: Sports oracle P2P betting on soccer launched in Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg19101028#msg19101028</ref><br />
*Apr 26: P2P insurance on smart contracts launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18759349#msg18759349</ref><br />
*Apr 18: Wallet version 1.8 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18646968#msg18646968</ref><br />
*Apr 7: P2P gambling using smart contracts launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18499180#msg18499180</ref><br />
*Apr 5: Wallet version 1.7 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18466533#msg18466533</ref><br />
*Mar 18: Binding payments to oracle-posted events launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18240736#msg18240736</ref><br />
*Mar 18: Wallet version 1.6 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18240736#msg18240736</ref><br />
*Mar 6: Wallet version 1.5 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18080683#msg18080683</ref><br />
*Feb 22: Wallet version 1.4 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17942383#msg17942383</ref><br />
*Feb 11: Wallet version 1.3 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17808504#msg17808504</ref><br />
*Feb 10: Chinese WeChat group "Byteball 中国" launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg17803910#msg17803910</ref><br />
*Feb 3: Transaction Explorer now shows all blackbyte details as only "Hidden Payments"<ref>https://bitcointalk.org/index.php?topic=1608859.msg17720913#msg17720913</ref><br />
*Feb 3: Wallet version 1.2 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17718842#msg17718842</ref><br />
*Jan 19: Wallet version 1.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17559287#msg17559287</ref><br />
*Jan 17: Byte-BTC Exchange bot now live<ref>https://bitcointalk.org/index.php?topic=1608859.msg17527112#msg17527112</ref><br />
<br />
==2016==<br />
*Dec 25: Live network launched. Wallet version 1.0<ref>https://bitcointalk.org/index.php?topic=1608859.msg17303311#msg17303311</ref><br />
==External links==<br />
<br />
<br />
==References==<br />
<references /><br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Hub&diff=1554Hub2020-03-01T20:20:51Z<p>Slackjore: /* List of hubs */ updated Connectory hub</p>
<hr />
<div>==Hub for Obyte network==<br />
This is a [[node]] for the Obyte network that serves as a relay, plus it facilitates the exchange of messages among devices connected to the Obyte network. Since all messages are encrypted with the recipient's key, the hub cannot read them. The hub does not hold any private keys and cannot send payments itself. <br />
<br />
The messages are used for the following purposes:<ref>https://github.com/byteball/byteball-hub</ref><br />
<br />
===Private-payment information===<br />
Conveying private-payment (such as blackbytes) information from payer to payee.<br />
<br />
===Multisig address===<br />
Exchanging partially-signed transactions when sending from a multisig address. One of the devices initiates a transaction and signs it with its private key, then it sends the partially-signed transaction to the other devices that participate on the multisig address. The user(s) confirm the transaction on the other devices, they sign and return the signatures to the initiator.<br />
<br />
===Multilateral signing===<br />
Multilateral signing, when several addresses sign the same unit, e.g. when exchanging one asset for another, or when signing a contract. The exchange of messages is similar to the multisig scenario above.<br />
<br />
===Chat between users===<br />
Plain text chat between users; in particular, users can send each other the newly generated addresses to receive payments to.<br />
<br />
===Chat with bots===<br />
Plain text chat with bots that offer a service and can receive or send payments. ''Faucet'' is an example of such a bot. The hub helps deliver such messages when the recipient is temporarily offline or is behind NAT. If the recipient is connected, the message is delivered immediately, otherwise it is stored and delivered as soon as the recipient connects to the hub. As soon as delivered, the message is deleted from the hub.<br />
<br />
==Hub address==<br />
Users set their hub address in their wallet settings. The default hub is wss://obyte.org/bb but users can change it.<br />
<br />
===List of hubs===<br />
Wallet user: to use one of these hubs in the wallet, change it in main menu > settings > hub.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Hub !! Notes<br />
|-<br />
| '''obyte.org/bb''' || '''default hub, operated by @tonych'''<br />
|-<br />
| hub.obyte.connectory.io/bb || operated by Bosch Connectory Stuttgart<br />
|-<br />
| obyte-hub.com/bb || operated by Tsonko Mirchev<br />
|-<br />
| hub.obytechina.org/bb || set up by @punqtured<br />
|}<br />
<br />
==Incentives==<br />
From Slack #tech channel:<br />
<br />
'''tonych [2018-08-24 12:26 AM]'''<br /><br />
regarding incentives to run a hub, there is one that is based on internal economy: a hub is usually combined with a light vendor, and light vendor is first to see new transactions submitted by light clients connected to it, and has the best chance to snatch the header commissions paid by them. This works only when the network is big of course.<br />
<br />
'''tonych [2018-08-24 12:33 AM]'''<br /><br />
another incentive, and i think it is more powerful, is that hub has access to large number of users and users is the most valuable asset in the modern internet economy. There are various ways to monetize large userbases, for example the hub controls the bot store, most bots are for-profit apps and won't mind paying a fee for access to large number of potential customers (for example, a "promoted" app).<br />
<br />
==External links==<br />
*https://stats.obyte.org/byteballworldmap.php World map showing hubs<br />
<br />
==References==<br />
<br />
[[Category:Nodes]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Autonomous_Agent&diff=1553Autonomous Agent2020-03-01T09:25:24Z<p>Slackjore: reworded first AA release</p>
<hr />
<div>== Overview ==<br />
[[Smart contract]]s embody voluntary relationships between two free equals.<br />
<br />
However, there is another class of applications that are not covered by smart contracts: applications where an autonomous central counterparty interacts with multiple users and does so strictly according to the rules that are public, known in advance, and can never be changed. That’s what '''Autonomous Agents''' are.<br />
<br />
An Autonomous Agent (AA) is a special address (account) on the ledger that acts according to a program associated with it. Its behavior is similar to that of a vending machine that receives coins and data entered on a keypad and in response, releases a cup of coffee, plays a song, or does whatever it was programmed to do.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
This is the first major upgrade to the Obyte protocol. It has been under development for 9 months. It was released to Testnet 18 June 2019, where testing and development was expected to take 2-4 months. The release had been expected in January/February 2020, after AA-based [[ODEX]]'s addition to livenet too.<ref>https://medium.com/obyte/whats-next-for-obyte-a-decentralized-exchange-fd7164569a9d</ref><br />
<br />
=== Mainnet release ===<br />
Wallet version 3.0.0 was released Feb 19, 2020.<ref>https://medium.com/obyte/autonomous-agents-on-mainnet-ready-for-takeoff-d89b50e6d921</ref> AAs became activated on mainnet on 29 February. The first mainnet AA can be seen on Explorer.<ref>https://explorer.obyte.org/#FJjUeexpyRSckvcqbT2jtVKRDgE5xos/h9yF/yZiB68=</ref><br />
<br />
== Developer contest ==<br />
To celebrate this massive milestone, we invited developers to join a running contest to build the most innovative, impressive, useful, exciting and spectacular Autonomous Agents.<br />
<br />
Total Prize Pool worth $38,000 at current rate.<br />
<br />
The contest kicked off July 18, 2019 and ran until mid-October. Every two weeks, a jury of Obyte team members led by the platform’s founder, Tony, announced the best entries. Autonomous Agents were live on Testnet, and the easy-to-use online editor is available for developers to explore. It even has a few nice templates to help get everyone off to an easy start.<ref>https://medium.com/obyte/obyte-autonomous-agents-developer-contest-6a67ae3dacd2</ref><br />
<br />
=== Results ===<br />
Round 1, announced 4 August<ref>https://medium.com/obyte/winners-of-the-first-round-of-the-autonomous-agents-developer-contest-bc8cbbe0d8b4</ref><br />
*1st place (140 GB / 422 GBB): Fabien — “A Simple DAO”<br />
*2nd place (70 GB / 147.7 GBB): Barborico — “Bank With Secrets"<br />
*3rd place (35 GB / 73.85 GBB): Pmiklos — “Lottery With Community Governance” <br />
*Best guide/tutorial (55 GB and 116.05 GBB): Pmiklos — “Getting Started With Obyte Autonomous Agents” <br />
<br />
Round 2, announced 19 August<ref>https://medium.com/obyte/winners-of-the-second-round-of-the-obyte-autonomous-agents-developer-contest-c69e37dbf55</ref><br />
*1st place (140 GB / 422 GBB): Pmiklos — “Autonomous Subscription Service”<br />
*2nd place (70 GB / 147.7 GBB): Alvarlaigna — “EOS-like Crowdsale”<br />
*3rd place (35 GB / 73.85 GBB): Hey_monkey — “The Attested Reputations Autonomous Agent”<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Pmiklos — “Stateful Autonomous Agents”<br />
<br />
Round 3, announced 3 September<ref>https://medium.com/obyte/third-round-of-obyte-autonomous-agents-developer-contest-4a7df3d70b29</ref><br />
*Postponed because of testnet crashes (good for [[antifragility]])<br />
*Special testnet crash-testing bonus of 10 GB and 21.111 GBB each: Whoisterencelee, hey_monkey and barborico<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Hey_monkey — "Understanding Obyte AA Bounce Fee" <br />
<br />
Round 4, announced 16 September<ref>https://medium.com/obyte/fourth-round-of-obyte-atonomous-agents-developer-contest-430891f9cf4b</ref><br />
*1st place (140 GB / 422 GBB): Hey_monkey — “Offer reward to get triggered in the future (THAANKS)”<br />
*2nd place (70 GB / 147.7 GBB): Barborico — “Ownerless AA Registry”<br />
*3rd place (35 GB / 73.85 GBB): Whoisterencelee — “Red vs Blue”<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Hey_monkey — “Understanding AA Structures” <br />
<br />
Round 5, announced 2 October<ref>https://medium.com/obyte/fifth-round-of-obyte-autonomous-agents-developer-contest-c554f7756d04</ref><br />
*1st place (140 GB / 422 GBB): Hey_monkey — “Joint Account Autonomous Agent (JAAA)”<br />
*2nd place (70 GB / 147.7 GBB): Vik — “ByteKeeper”<br />
*3rd place (35 GB / 73.85 GBB): Whoisterencelee — “Time For Birthday Fiddle”<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Pmiklos — “How to set up devnet for rapid development” <br />
<br />
Round 6, announced 15 October<ref>https://medium.com/obyte/sixth-round-of-obyte-autonomous-agents-developer-contest-6aa89bedd712</ref><br />
*1st place (140 GB / 422 GBB): Crypto Girl — “ObyStack”<br />
*2nd place (70 GB / 147.7 GBB): Hey_monkey — “WEAALTH Use An AA To Establish Your GBytes Testament”<br />
*3rd place (35 GB / 73.85 GBB): Sharjar — “Simple Public Asset Storage”<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Crypto Girl — “ObyStack AA Stack Game” <br />
<br />
Round 7 (Final round), announced 1 November<ref>https://medium.com/obyte/final-round-of-obyte-autonomous-agents-developer-contest-704306b64d79</ref><br />
*1st place (140 GB / 422 GBB): Frank Bee — “Autonomous Auctioneer”<br />
*2nd place (70 GB / 147.7 GBB): Lion’s Heart — “Certificate of Deposit”<br />
*3rd place (35 GB / 73.85 GBB): Hey_monkey — “A Renting Guarantee Autonomous Agent (ARGAA)”<br />
*Honorable mention (10 GB / 21.111 GBB): Whoisterencelee — "Obotic"<br />
*Honorable mention (10 GB / 21.111 GBB): Vik — "EmailBank"<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Hey_monkey — “Use a web page to interact with Obyte powered AA” <br />
<br />
== Oscript editor ==<br />
Autonomous Agents are written in Oscript — a new programming language developed specifically for this purpose.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref> The editor offers everything you would expect from a modern editor. Syntax highlighting with tooltips and help, auto completion and the editor even has built-in code validation. In other words, a full fledged code editor ready for real world adoption.<ref>https://medium.com/obyte/oscript-improvements-and-competiton-inspiration-57051449b139</ref><br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category: Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Autonomous_Agent&diff=1552Autonomous Agent2020-03-01T09:17:39Z<p>Slackjore: added first AA on mainnet</p>
<hr />
<div>== Overview ==<br />
[[Smart contract]]s embody voluntary relationships between two free equals.<br />
<br />
However, there is another class of applications that are not covered by smart contracts: applications where an autonomous central counterparty interacts with multiple users and does so strictly according to the rules that are public, known in advance, and can never be changed. That’s what '''Autonomous Agents''' are.<br />
<br />
An Autonomous Agent (AA) is a special address (account) on the ledger that acts according to a program associated with it. Its behavior is similar to that of a vending machine that receives coins and data entered on a keypad and in response, releases a cup of coffee, plays a song, or does whatever it was programmed to do.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
This is the first major upgrade to the Obyte protocol. It has been under development for 9 months. It was released to Testnet 18 June 2019, where testing and development was expected to take 2-4 months. The release had been expected in January/February 2020, after AA-based [[ODEX]]'s addition to livenet too.<ref>https://medium.com/obyte/whats-next-for-obyte-a-decentralized-exchange-fd7164569a9d</ref><br />
<br />
=== Mainnet release ===<br />
Wallet version 3.0.0 was released Feb 19, 2020. AAs will become activated on mainnet at approximately the end of February.<ref>https://medium.com/obyte/autonomous-agents-on-mainnet-ready-for-takeoff-d89b50e6d921</ref><br />
<br />
==== First AA ====<br />
29 February sees the first AA on mainnet: https://explorer.obyte.org/#FJjUeexpyRSckvcqbT2jtVKRDgE5xos/h9yF/yZiB68=<br />
<br />
== Developer contest ==<br />
To celebrate this massive milestone, we invited developers to join a running contest to build the most innovative, impressive, useful, exciting and spectacular Autonomous Agents.<br />
<br />
Total Prize Pool worth $38,000 at current rate.<br />
<br />
The contest kicked off July 18, 2019 and ran until mid-October. Every two weeks, a jury of Obyte team members led by the platform’s founder, Tony, announced the best entries. Autonomous Agents were live on Testnet, and the easy-to-use online editor is available for developers to explore. It even has a few nice templates to help get everyone off to an easy start.<ref>https://medium.com/obyte/obyte-autonomous-agents-developer-contest-6a67ae3dacd2</ref><br />
<br />
=== Results ===<br />
Round 1, announced 4 August<ref>https://medium.com/obyte/winners-of-the-first-round-of-the-autonomous-agents-developer-contest-bc8cbbe0d8b4</ref><br />
*1st place (140 GB / 422 GBB): Fabien — “A Simple DAO”<br />
*2nd place (70 GB / 147.7 GBB): Barborico — “Bank With Secrets"<br />
*3rd place (35 GB / 73.85 GBB): Pmiklos — “Lottery With Community Governance” <br />
*Best guide/tutorial (55 GB and 116.05 GBB): Pmiklos — “Getting Started With Obyte Autonomous Agents” <br />
<br />
Round 2, announced 19 August<ref>https://medium.com/obyte/winners-of-the-second-round-of-the-obyte-autonomous-agents-developer-contest-c69e37dbf55</ref><br />
*1st place (140 GB / 422 GBB): Pmiklos — “Autonomous Subscription Service”<br />
*2nd place (70 GB / 147.7 GBB): Alvarlaigna — “EOS-like Crowdsale”<br />
*3rd place (35 GB / 73.85 GBB): Hey_monkey — “The Attested Reputations Autonomous Agent”<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Pmiklos — “Stateful Autonomous Agents”<br />
<br />
Round 3, announced 3 September<ref>https://medium.com/obyte/third-round-of-obyte-autonomous-agents-developer-contest-4a7df3d70b29</ref><br />
*Postponed because of testnet crashes (good for [[antifragility]])<br />
*Special testnet crash-testing bonus of 10 GB and 21.111 GBB each: Whoisterencelee, hey_monkey and barborico<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Hey_monkey — "Understanding Obyte AA Bounce Fee" <br />
<br />
Round 4, announced 16 September<ref>https://medium.com/obyte/fourth-round-of-obyte-atonomous-agents-developer-contest-430891f9cf4b</ref><br />
*1st place (140 GB / 422 GBB): Hey_monkey — “Offer reward to get triggered in the future (THAANKS)”<br />
*2nd place (70 GB / 147.7 GBB): Barborico — “Ownerless AA Registry”<br />
*3rd place (35 GB / 73.85 GBB): Whoisterencelee — “Red vs Blue”<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Hey_monkey — “Understanding AA Structures” <br />
<br />
Round 5, announced 2 October<ref>https://medium.com/obyte/fifth-round-of-obyte-autonomous-agents-developer-contest-c554f7756d04</ref><br />
*1st place (140 GB / 422 GBB): Hey_monkey — “Joint Account Autonomous Agent (JAAA)”<br />
*2nd place (70 GB / 147.7 GBB): Vik — “ByteKeeper”<br />
*3rd place (35 GB / 73.85 GBB): Whoisterencelee — “Time For Birthday Fiddle”<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Pmiklos — “How to set up devnet for rapid development” <br />
<br />
Round 6, announced 15 October<ref>https://medium.com/obyte/sixth-round-of-obyte-autonomous-agents-developer-contest-6aa89bedd712</ref><br />
*1st place (140 GB / 422 GBB): Crypto Girl — “ObyStack”<br />
*2nd place (70 GB / 147.7 GBB): Hey_monkey — “WEAALTH Use An AA To Establish Your GBytes Testament”<br />
*3rd place (35 GB / 73.85 GBB): Sharjar — “Simple Public Asset Storage”<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Crypto Girl — “ObyStack AA Stack Game” <br />
<br />
Round 7 (Final round), announced 1 November<ref>https://medium.com/obyte/final-round-of-obyte-autonomous-agents-developer-contest-704306b64d79</ref><br />
*1st place (140 GB / 422 GBB): Frank Bee — “Autonomous Auctioneer”<br />
*2nd place (70 GB / 147.7 GBB): Lion’s Heart — “Certificate of Deposit”<br />
*3rd place (35 GB / 73.85 GBB): Hey_monkey — “A Renting Guarantee Autonomous Agent (ARGAA)”<br />
*Honorable mention (10 GB / 21.111 GBB): Whoisterencelee — "Obotic"<br />
*Honorable mention (10 GB / 21.111 GBB): Vik — "EmailBank"<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Hey_monkey — “Use a web page to interact with Obyte powered AA” <br />
<br />
== Oscript editor ==<br />
Autonomous Agents are written in Oscript — a new programming language developed specifically for this purpose.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref> The editor offers everything you would expect from a modern editor. Syntax highlighting with tooltips and help, auto completion and the editor even has built-in code validation. In other words, a full fledged code editor ready for real world adoption.<ref>https://medium.com/obyte/oscript-improvements-and-competiton-inspiration-57051449b139</ref><br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category: Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Glossary&diff=1551Glossary2020-02-27T22:53:39Z<p>Slackjore: added MOO</p>
<hr />
<div>Obyte terms, not too technical, but assuming some familiarity with cryptocurrencies <br />
<br />
==Entries==<br />
'''ADDRESS:''' (Disambiguation) <br />
<br />
* A device address is all upper case, starts with 0, looks like 0VCPO8MYDRN2E6N5JDRHRLTVEVZSZYARM<br />
<br />
* A payment address in a wallet is all upper case, looks like K7RMH5EFPZW67JTS5B5GA6PDZA4MYX4LY<br />
<br />
* A wallet ID looks like lNeHNjLs3u38SJ9dPb+SUZ+aZX3a7RWI1osYJH9QHRw=<br />
<br />
* A unit address, like a transaction you sent, looks like Ip241kkFRkZnaVF61Z6+/JW3YELOaHn9C6PAjeMp8fs= <br />
<br />
* A bitcoin address looks like 13AM4VW2dhxYgXeQepoHkHSQuy6NgaEb94, may also start with "3" or "bc1".<br />
<br />
'''AIR-DROP:''' The final snapshot for distribution of new bytes to payment addresses linked to proven BTC balances occurred on 4 November 2017 at 05:23 UTC. <br />
<br />
* For each 1 BTC linked --> 6.25MB (0.00625GB) <br />
<br />
* For each 1 BTC linked --> 2.1111 x 6.25 million blackbytes (money supply of blackbytes is 2.1111 times as much as that of bytes)<br />
<br />
* For every 10 (white)bytes on any address --> 1 new (white)byte<br />
<br />
* For every 10 (white)bytes on a '''linked''' address --> 2.1111 new blackbytes.<br />
<br />
See wiki [[Airdrop]] article.<br />
<br />
'''ASSET:''' Users can issue new assets and define rules that govern their transferability. For example: ICOs, shares, bonds, fiat-pegged coins, loyalty points, minutes of airtime, assets in online games, whatever you can imagine. You can do this in Obyte right now. See wiki article [[Asset]] for instructions<br />
<br />
'''ATOMIC EXCHANGE:''' When two parties sign a single unit that executes both legs of the exchange, the two transactions either happen simultaneously or don't happen at all. It is no longer necessary to trust any centralized exchanges. Note this uses a definition of "atomic" related to databases, and has nothing to do with the usual "extremely small" senses.<ref>https://obyte.org Front page, other features</ref><br />
<br />
'''ATTESTOR:''' The attestor who attests the email addresses through the [[Chatbot#Email_attestation_bot|Email attestation bot]] is <code>H5EZTQE7ABFH27AUDTQFMZIALANK6RBG</code>, and it is also a WITNESS. The attestor is trusted to post only true Obyte-address-to-email-address links to the DAG.<ref>https://medium.com/byteball/distribution-to-verified-emails-and-sending-cryptocurrency-to-email-episode-ii-cb955fe19d7e</ref><br />
<br />
'''AUTHOR:''' (In explorer) Authors are payment addresses that signed the transaction, similar to bitcoin sending address.<br />
<br />
'''AUTONOMOUS AGENT:''' An [[Autonomous Agent]] (AA) is a special address (account) on the ledger that acts according to a program associated with it. Its behavior is similar to that of a vending machine that receives coins and data entered on a keypad and in response, releases a cup of coffee, plays a song, or does whatever it was programmed to do.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
'''BBIP:''' Byteball Improvement Proposal. Replaced by OIP.<br />
<br />
'''BIND:''' See CONDITIONAL PAYMENTS<br />
<br />
'''BLACKBYTE:''' One of the two native Obyte currencies (also see BYTE). When you want complete privacy pay in blackbytes, a cash-like untraceable currency whose transactions are not visible on the public database. They are sent peer-to-peer instead.<ref>https://obyte.org Front page</ref>. With wallet version 2.3 they can be sent by digital file to someone not in Obyte yet.<ref>https://medium.com/byteball/private-textcoins-6a2288d80757</ref><br />
<br />
'''BOT:''' See CHATBOT<br />
<br />
'''BOT STORE:''' The section in the Obyte platform, available from the CHAT tab, that contains about 20 bots you can add to your contacts.<br />
<br />
'''BYTE:''' One of the two native currencies of the Obyte network (also see BLACKBYTE). It is also a basic general computing term: *A sequence of adjacent bits, usually eight, operated on as a unit, e.g. 0 1 0 1 1 1 0 1. One byte can store one character, e.g. 'A' or 'x' or '$'.* There are 10^15 total Bytes in the system. The unit traded on exchanges is the "GByte", 10^9 Bytes.<br />
<br />
'''BYTEBALL (NAME):''' (1) Once a unit is broadcast into the network, and other users start building their units on top of it (referencing it as parent), the number of secondary revisions required to edit this unit hence grows like a snowball. That’s why we call this design '''Byteball''' (our snowflakes are bytes of data).<ref>https://obyte.org/Byteball.pdf p.5</ref> [Rebranded to ''Obyte'' on 17 Jan 2019]<br />
<br />
(2) ''Byteball'' (upper-case "B") was the name of the platform, the protocol; ''byteball'' (lower-case "b") was sometimes (mis)used very loosely to represent the currency, as in "Hey, I see a byteball [1 GB] is now worth $250!" or "Use blackbytes for private transactions and byteballs for the open ones".<br />
<br />
'''BYTEROLL:''' The original Byteball wiki was hosted at byteroll.com on @portabella's private server. The Byteball wiki subdomain forwarded to Byteroll.<br />
<br />
'''CASHBACK:''' We want to get this coin into the hands of as many people as possible. In addition to the regular monthly airdrop, we are going to partner with several categories of companies, like merchants, payment processors, and "Bitcoin debit card" companies. We will offer 10% [[cashback]], paid in Bytes, for all qualifying purchases (no matter how the purchases are paid). <br />
<br />
'''CHAT:''' The platform incorporates a chat function, allowing the user to exchange end-to-end-encrypted messages using AES with a peer or bot when their devices are paired. It's end-to-end encrypted using AES. The hubs only forward the encrypted messages; they can't see anything. To deliver your message, your platform connects to the recipient's hub (if it's different from your home hub).<ref>https://bitcointalk.org/index.php?topic=1608859.msg21798347#msg21798347</ref><br />
<br />
'''CHATBOT:''' You can pair your platform with a bot, which emulates the experience of chatting with a live person. The bot will have very limited responses, but enough to get the job done. A merchant bot could allow you to select from a range of pizzas, for example, then pay for your order with two clicks while still in that chat session. See the wiki [[Chatbot]] article for a list.<br />
<br />
'''CHILDREN:''' (In explorer) Children and parents are pointers to later and earlier units in the DAG (see the arrows between units).<br />
<br />
'''CONDITIONAL PAYMENTS:''' This is the '''killer feature''' of Obyte, and the "smart payments" in the [[slogan]]. You can choose to bind a payment to a condition. If/when that condition is satisfied the payment is unlocked and only the recipient can collect it. If the condition fails the payment can only be collected by the issuer. See the wiki [[Trading blackbytes]] article for an example.<br />
<br />
'''CONFIRMED:''' An Obyte payment is confirmed/stable once it has become sufficiently buried by later transactions to be unalterable, similar to confirmations on a blockchain. It usually takes about five minutes.<br />
<br />
'''DAG:''' [[Directed_acyclic_graph]], the radically-different immutable data structure used in the Obyte platform instead of the usual cryptocurrency blockchain. No mining, no proof-of-work, no proof-of-stake.<ref>https://obyte.org/Byteball.pdf White paper</ref><br />
<br />
'''DATAFEED:''' A line item posted into the DAG by an oracle. The data is of the form [Datafeed name] then [Datafeed value], for example <code>BTC_USD: 6788.0</code>.<br />
<br />
'''DISTRIBUTION:''' See AIRDROP. For current campaigns to give away undistributed bytes, see https://obyte.org/#dist.<br />
<br />
'''DOUBLE-SPEND:''' In case of doublespend, the version that comes earlier on the main chain wins. Therefore, if your node is well-connected and you see a few other transactions piling up on top of the new unconfirmed transaction, and the time since its arrival is significantly larger than the typical network latency, then you can be reasonably sure that even if a doublespend appears later it will be sorted later, hence voided.<br />
<br />
'''DRAW:''' A weekly random airdrop to existing bytes holders, started Dec 8, 2018.<ref>https://medium.com/obyte/weekly-draw-for-the-byteball-community-f464ae731c88</ref> As a distribution method it was superseded July 18, 2019 by the Autonomous Agent developer contest.<ref>https://medium.com/obyte/distribution-outlook-bb28ff0b91aa</ref><br />
<br />
'''FREE UNIT:''' A unit that has no children.<br />
<br />
'''FULLY FUNDED:''' The state of a SMART CONTRACT when the agreed payments from both parties have been locked in the contract until certain conditions are satisfied. See the wiki [[Smart contract]] article.<br />
<br />
'''FUN-COIN:''' A freely-available token on the Obyte platform having zero monetary value, intended for practice with various features like textcoin and smart contracts. See the wiki [[fun-coins]] article.<br />
<br />
'''GENESIS UNIT:''' The Obyte analog to Bitcoin's genesis block, including the creation of the entire global supply of its native currencies: 1,000,000 GBytes and 2,111,100 GBBytes. <br />
<br />
'''GRANTS:''' Obyte Grants Program. We’ll pay for work that improves the ecosystem. We want the contributors to both come up with new ideas and realize them.<ref>https://medium.com/byteball/byteball-grants-program-906a71b93d3c)</ref><br />
<br />
'''HUB:''' This is a node for the Obyte network that serves as a relay, plus it facilitates the exchange of end-to-end encrypted messages among devices connected to the Obyte network. The hub does not hold any private keys and cannot send payments itself, nor can it read the messages. Users set their hub address in their wallet settings. The default hub is wss://obyte.org/bb but users can change it.<ref>https://github.com/byteball/byteball-hub) Github readme.md</ref> See wiki [[Hub]] article.<br />
<br />
'''ICO:''' An '''initial coin offering''' is a controversial means of crowdfunding centered around cryptocurrency, which can be a source of capital for startup companies. In an ICO, a quantity of the crowdfunded cryptocurrency is preallocated to investors in the form of "tokens", in exchange for legal tender or other cryptocurrencies such as bitcoin or ethereum. These tokens supposedly become functional units of currency if or when the ICO's funding goal is met and the project launches.<ref>https://en.wikipedia.org/wiki/Initial_coin_offering</ref> Obyte has an ICO bot, and anyone can issue tokens on the platform.<br />
<br />
'''IDENTITY VERIFICATION:''' Proving one's real-world identity with government-issued documentation using the [[Chatbot#Real_name_attestation_bot|REAL NAME ATTESTATION bot]], but after this one can verify age or country of origin without disclosing further identifying information. Same as REAL NAME ATTESTATION<br />
<br />
'''LINKED:''' Concerning airdrops, it refers to (white)bytes at one of your wallet addresses linked to bitcoins, where the link has been verified by the transition bot. All such pairs were visible on the transition pages<ref>https://transition.byteball.org</ref>.<br />
<br />
'''MOO:''' [https://madeonobyte.org MadeOnObyte.org], a website that makes it easier to find out what is happening at Obyte and who is working on what.<ref>https://medium.com/obyte/finding-out-what-is-being-built-using-obyte-and-the-obbies-involved-just-became-easier-d7cedbbcfaa6</ref><br />
<br />
'''MOVED:''' In a wallet history, shows funds moving from one address in your wallet to a different address in the same wallet. Either you deliberately sent them there, or they moved as change. See wiki article [[Change address]].<br />
<br />
'''MULTI SIGNATURE:''' For security, you can require that your funds be spendable only when several signatures are provided, e.g. from your laptop and from your phone. For shared control of funds, signatures from different people may be required.<ref>https://obyte.org front page, other features</ref><br />
<br />
'''NODE:''' Imagine a fishing net: the nodes would be the knots holding the lines of rope together. Every device in the Obyte network is technically a node, whether a light client/platform, a full platform, a relay or a hub. Informally, node is used to mean full platform. See wiki article [[Node]] for different roles.<br />
<br />
'''O:''' [Tony:] O in Obyte stands for Open. When we renamed, many people wondered what O stands for. While it is true that it replaces the former "ball", I also want to make it clear that O stands for Open. It speaks about the core values of the platform: open access to the ledger, not encumbered by miners or other intermediaries, which simply do not exist here in a DAG. We are going to have more O-names for the products built on top of the platform.<ref>https://www.reddit.com/r/obyte/comments/aioub3/o_in_obyte_stands_for_open</ref><br />
<br />
'''OBBY CHAT:''' Instant mobile-only messaging app for Obyte. Offering secure end-to-end encryption, cryptocurrency payments, and smart contracts.<ref>https://obby.chat/</ref> Being built by BindCreative from a grant application<ref>https://drive.google.com/file/d/1KWlwbFO1QU-IER_kgRjOf4UDLwEp0a0n/view</ref> approved July 2019.<br />
<br />
'''OBYTE COMMUNITY FUND:''' The [[Obyte_community_fund|Obyte Community Fund]]'s goal is to support and encourage the Obyte crypto platform. Fundraising is done by voluntary donations from investors, stakeholders and enthusiasts. <br />
<br />
'''ODEX:''' DEX is a Decentralized Exchanged. [[ODEX]] is Obyte's DEX.<br />
<br />
'''OIP:''' Obyte Improvement Proposal. Based on the Bitcoin BIP system. See [[OIP]] wiki article.<br />
<br />
'''ORACLE:''' A trusted third party that monitors specific external events and registers selected data-feed items to the Obyte database. An example is a list of cryptocurrency exchange rates updated every ten minutes. When dealing with untrusted counterparties, you can lock the funds on a payment address that is spendable either by you or by the counterparty, depending on the oracle's data collection and registration.<ref>https://obyte.org front page, other features</ref> See wiki article [[Oracle]].<br />
<br />
'''OSCRIPT:''' AUTONOMOUS AGENTS are written in Oscript — a new programming language developed specifically for this purpose.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
'''OSWAP:''' [Chinese] One-click exchange platform for hundreds of crypto assets.<ref>https://www.oswap.cc/#/</ref> OSwap is funded by the Obyte Foundation to facilitate purchase of bytes by the Chinese community. Telegram channel.<ref>https://t.me/oswapcc</ref><br />
<br />
'''P2P INSURANCE:''' Insurance against a negative event provided by another peer instead of a faceless company. An example is flight delays insurance.<ref>https://medium.com/byteball/making-p2p-great-again-episode-iv-p2p-insurance-cbbd1e59d527</ref><br />
<br />
'''PAIR:''' To link with another Obyte device, either remote or face-to-face, use a pairing code generated by either device. In your wallet, '''Chat > add a new device > invite the other device''' OR '''Chat > add a new device > accept invitation'''. The code can then be sent by pasting it into a non-platform messaging app, or by QR code.<br />
<br />
'''PARENTS:''' (In explorer) Children and parents are pointers to later and earlier units in the DAG (see the arrows between units).<br />
<br />
'''PLATFORM:''' (1) Generally, refers to the entire Obyte protocol, as in "You can easily create new custom assets that will run on the platform." (2) An instance of the Obyte platform software installed on one of your devices, sometimes called a ''wallet''. But that name is confusing as this platform instance can contain many wallets, for example a Single-Address Wallet, a Small Expenses Wallet, a Savings Wallet, etc. A full platform/wallet downloads the whole Obyte database, a light platform/wallet doesn't. See wiki article [[Node]] for different roles, and [[Wallet]] for many more details.<br />
<br />
'''POLL:''' See VOTE. Also marketing [[polls]] via Twitter etc, in usual meaning of the word.<br />
<br />
'''PREDICTION MARKETS:''' Prediction markets are (usually) exchange-traded markets created for the purpose of trading the outcome of events. The purpose of the Slack<ref>https://obyte.slack.com</ref> #prediction_markets channel was "Finding a counterpart for bets on future events". See wiki article [[Trading prediction markets]].<br />
<br />
'''PROSAIC CONTRACT:''' See the wiki [[Prosaic contract]] article. Compare SMART CONTRACT<br />
<br />
'''REAL NAME ATTESTATION:''' See IDENTITY VERIFICATION<br />
<br />
'''RECOVER:''' Recovery is available in single-sig (i.e., not multi-sig) light platforms from version 1.10.1, and full platforms too. Note that blackbytes are not included. Also see RESTORE<br />
<br />
'''REFERRAL:''' A [[referral]] is getting a second person to install the Obyte wallet on his own device (smartphone or computer) and doing an attestation from that device/wallet, using Bytes received from the first person.<br />
<br />
'''REGULATED ASSETS:''' Regulated institutions can issue assets that are compatible with KYC/AML requirements. Every transfer of such asset is to be cosigned by the issuer, and if there is anything that contradicts the regulations, the issuer won't cosign.<ref>https://obyte.org front page, other features</ref><br />
<br />
'''RELAY:''' This is a node for the Obyte network that stores the entire database and forwards new storage units to peers. The relay does not hold any private keys and cannot send payments itself.<ref>https://github.com/byteball/byteball-relay readme.md</ref> See wiki article [[Node]] for different roles.<br />
<br />
'''RESTORE:''' To restore from a full backup. This also includes private assets. Works with any wallet type. Also see RECOVER<br />
<br />
'''SINGLE-ADDRESS WALLET:''' These wallets have only one payment address and the change always returns to the same address, supporting applications that require a stable identity. For example, you can run a manual oracle right from your wallet without having to run a node on a server. This allows you to run a PREDICTION MARKET for a future event, enabling users to make contracts (bets) referencing your payment address as an oracle, and when the outcome of the event is known you post its result from your wallet. See the wiki [[Wallet]] article.<br />
<br />
'''SMART CONTRACT/WALLET:''' See the wiki [[Smart contract]] article. See CONDITIONAL PAYMENTS. Compare PROSAIC CONTRACT <br />
<br />
'''SMART VOUCHER:''' A coupon to fund IDENTITY VERIFICATION / REAL NAME ATTESTATION for new users. See the wiki [Smart Voucher]] article.<br />
<br />
'''STABLE:''' See CONFIRMED<br />
<br />
'''STORAGE UNIT:''' Obyte 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]. <ref>https://obyte.org/Byteball.pdf</ref><br />
<br />
'''TANGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Tangos]] article.<br />
<br />
'''TEXTCOIN:''' Sending Obyte funds from one's wallet through a text app, such as an email, Telegram, WhatsApp etc. See the wiki [[Textcoin]] article. <br />
<br />
'''TINGOS:''' A Obyte fun-coin created in January 2018. See the wiki [[Tingos]] article.<br />
<br />
'''TRANSACTION FEE:''' The fee you pay is identical to the size of the data you want stored. So a storage unit that takes up 18,000 bytes in the distributed Obyte database will cost 18,000 (white)Bytes to send there. Currently a usual transaction fee is maybe 500 Bytes, with a blackbytes fee being maybe 1000 Bytes or so. If 1GB = $750, then 1MB = $0.75, and 1KB (1000 bytes) = $0.00075. So that's less than 1/10 cent US.<br />
<br />
'''TRANSITION BOT:''' After installing the wallet, one chatted with the Transition Bot to participate in the next distribution round. See the wiki article [[Airdrop]].<br />
<br />
'''UNIT:''' (In explorer) Unit is hash of data unit, similar to bitcoin transaction ID, but a unit can have more than just a transaction.<br />
<br />
'''VOTE:''' (In platform [[chatbot|Poll bot]]) A vote is a small transaction that pays to yourself and is signed by your most funded addresses; the weight of the vote is the combined balance of the signing addresses. Note that there is a privacy concern because by making a vote you associate a number of your addresses. <br />
<br />
'''WALLET:''' The Obyte PLATFORM software a regular user downloads/installs comes with a default SINGLE-ADDRESS WALLET, but you can create as many more wallets as you wish. See wiki article [[wallet]] for many more wallet details, and other wiki articles for what you can do with the platform and wallets you create.<br />
<br />
'''WITNESS:''' A witness is a highly reputable user with a real-world identity, who stamps 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. This list varies very little from transaction to transaction. If 11 witnesses say no to a bad transaction and 1 says yes, that witness gets deemed unreliable and effectively fired. It would be unthinkable for all 12 to collude and allow a fraudulent transaction through. In this way the network is safeguarded.<ref>https://obyte.org/Byteball.pdf</ref><br />
<br />
'''ZANGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Zangos]] article.<br />
<br />
'''ZINGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Zingos]] article.<br />
<br />
'''ZWIB:''' The first Obyte new asset/token traded on Slack. The name comes from the unit address, *ZW1b...* <br />
<br />
==External links==<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Main_Page&diff=1550Main Page2020-02-25T18:41:18Z<p>Slackjore: added Feb 25 news item</p>
<hr />
<div>__NOTOC__<br />
[[File:Obyte-logo.jpg|thumb|250px]] <br />
'''Welcome to the Obyte Wiki. See first a one-page [[overview|OVERVIEW]], the [[glossary|GLOSSARY]], and the [[wallet|WALLET]] page. See [[Special:AllPages|ALL PAGES here]].'''<br />
<br />
==Introduction==<br />
Obyte, formerly Byteball, now listed on CoinMarketCap<ref>https://coinmarketcap.com</ref> as simply ''Obyte'', is a DAG-based cryptocurrency developed by Anton (Tony) Churyumov.<br />
<br />
This wiki is aimed at general cryptocurrency users, as well as Obyte users, who want to become better informed about Obyte. <br />
<br />
The wiki content is currently generated by invited contributors, and not randomly.<br />
<br />
==License==<br />
All content of this wiki is available under a Creative Commons Attribution-ShareAlike 3.0 Unported [[License]].<br />
<br />
== External links ==<br />
*[https://obyte.org Main official site]<br />
*[https://explorer.obyte.org Transactions explorer]<br />
*[https://obyte.org/Byteball.pdf White paper]<br />
*[https://medium.com/Obyte ''Medium'' articles]<br />
*[https://www.youtube.com/channel/UCYAjbxT5zHfeTtXe_hr9Gxg Obyte Channel on YouTube]<br />
*[https://asset.obyte.app Obyte Asset Registry for you to create a new asset]<br />
*[https://github.com/byteball/byteball Repository]<br />
*[https://obyte.io An Obyte data explorer]<br />
<br />
===Forums===<br />
*[https://discord.obyte.org Discord channel invitation] <br />
*[https://bitcointalk.org/index.php?topic=1608859.0) Bitcointalk thread]<br />
*[https://bitcointalk.org/index.php?action=profile;u=412662;sa=showPosts;start=0) Tony's posts on bitcointalk]<br />
*[https://reddit.com/r/obyte Subreddit]<br />
*[https://telegram.me/obyte Telegram]<br />
*[https://twitter.com/ObyteOrg Twitter]<br />
<br />
==Latest [[News]]==<br />
*Feb 25: Version 3.0.1 released (bug fix)<ref>https://github.com/byteball/obyte-gui-wallet/releases/tag/v3.0.1</ref><br />
*Feb 19: Version 3.0.0 released, preparatory to activating AAs on mainnet in approx 2 weeks<ref>https://medium.com/obyte/autonomous-agents-on-mainnet-ready-for-takeoff-d89b50e6d921</ref><br />
*Feb 6: [[PolloPollo]] 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><br />
*Dec 27: Bosch Connectory announced as the 3rd default witness (order provider)<ref>https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03</ref><br />
*Sep 25: Version 2.8.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg52555921#msg52555921</ref><br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=News&diff=1549News2020-02-25T18:40:28Z<p>Slackjore: added Feb 25 item</p>
<hr />
<div>Very brief '''headline''' items only, with links to each announcement, usually on Bitcointalk as a permanent record.<br />
<br />
== 2020 ==<br />
*Feb 25: Version 3.0.1 released (bug fix)<ref>https://github.com/byteball/obyte-gui-wallet/releases/tag/v3.0.1</ref><br />
*Feb 19: Version 3.0.0 released, preparatory to activating AAs on mainnet in approx 2 weeks<ref>https://medium.com/obyte/autonomous-agents-on-mainnet-ready-for-takeoff-d89b50e6d921</ref><br />
*Feb 6: [[PolloPollo]] announced as the 4th default witness (order provider)<ref>https://medium.com/obyte/pollopollo-approved-to-become-a-default-witness-on-the-obyte-public-network-9ee32238142f</ref><br />
<br />
==2019==<br />
*Dec 27: Bosch Connectory announced as the 3rd default witness (order provider)<ref>https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03</ref><br />
*Sep 25: Version 2.8.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg52555921#msg52555921</ref><br />
*Aug 7: The first Ocademy (Obyte Academy) student graduates<ref>https://medium.com/obyte/meet-the-first-ocademy-workshop-graduate-133617202c</ref><br />
*Aug 5: Sports oracle updated to work with [[Autonomous Agent]]s<ref>https://medium.com/obyte/sports-oracle-for-autonomous-agents-96b56369168a</ref><br />
*Aug 1: "What's [[next]] for Obyte" blog launched<ref>https://medium.com/obyte/whats-next-for-obyte-b495cfbb698</ref><br />
*Jul 18: Autonomous Agents protocol upgrade released on Testnet<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
*Jun 11: Version 2.7.2 released<ref>https://github.com/byteball/obyte-gui-wallet/releases</ref><br />
*Apr 30: Obyte Foundation Establishment announced<ref>https://medium.com/obyte/obyte-foundation-is-established-c92a28d2d20e</ref><br />
*Apr 20: Version 2.7.0 released. Includes prosaic contracts.<ref>https://github.com/byteball/obyte-gui-wallet/releases</ref><br />
*Apr 16: 2nd independent witness candidate announced<ref>https://medium.com/obyte/second-independent-witness-candidate-fabien-marino-d4e8dccadee</ref><br />
*Apr 10: New method of identity verification launched for residents of Estonia, Latvia, Lithuania, and e-residents of Estonia.<ref>https://medium.com/obyte/new-methods-for-identity-verification-3d5045287533</ref><br />
*Jan 17: Byteball rebranded to Obyte<ref>https://medium.com/byteball/byteball-rebrand-the-next-step-to-real-world-adoption-6a0a924390de</ref><br />
<br />
==2018==<br />
*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><br />
*Dec 1: Byteball developer resources site launched at https://developer.byteball.org<ref>https://twitter.com/slackjore/status/1069216217691508736</ref><br />
*Oct 15: Smart Vouchers for Real Name Attestation introduced<ref>https://bitcointalk.org/index.php?topic=1608859.msg46911901#msg46911901</ref><br />
*Oct 14: Filter added to Explorer<ref>https://twitter.com/slackjore/status/1051452800696238080</ref><br />
*Sep 23: Dice bot added to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg46089759#msg46089759</ref><br />
*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><br />
*Aug 28: Nousplatform ICO added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg44795934#msg44795934</ref><br />
*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><br />
*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><br />
*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><br />
*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><br />
*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><br />
*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><br />
*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><br />
*Jun 23: Wallet version 2.3 released. Includes sending blackbytes as textcoins<ref>https://bitcointalk.org/index.php?topic=1608859.msg40698998#msg40698998</ref><br />
*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><br />
*May 29: Added Private Chat Room bot to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg38902178#msg38902178</ref><br />
*May 28: Added Exchange Bot for Dual-Chain Tokens to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg38743714#msg38743714</ref><br />
*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><br />
*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><br />
*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><br />
*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><br />
*Apr 26: Added World Community Grid linking bot to the Bot Store<ref>https://medium.com/byteball/computing-for-good-again-3795336bdaed</ref><br />
*Apr 20: Added Accredited investor attestation bot to the Bot Store<ref>https://medium.com/byteball/attestation-of-accredited-investors-d4a8dabf683b</ref><br />
*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><br />
*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><br />
*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> <br />
*Mar 23: Exchange bot for ICOs added to the Bot Store<ref>https://medium.com/byteball/byteball-exchange-bot-78c8154f4e6a</ref><br />
*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><br />
*Feb 18: March 2 and future [[airdrop]]s terminated<ref>https://bitcointalk.org/index.php?topic=1608859.msg30564528#msg30564528</ref><br />
*Feb 15: SilentNotary ICO added to Bot Store<ref>https://twitter.com/ByteballOrg/status/964267908879781888</ref><br />
*Jan 26: Free [[fun-coins]] faucet added to Bot Store<ref>https://twitter.com/slackjore/status/957355056235499520</ref><br />
*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><br />
*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><br />
*Jan 13: Eli Taranto now onboard as PR and Marketing director.<ref>https://bitcointalk.org/index.php?topic=1608859.msg28047149#msg28047149</ref><br />
*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><br />
*Jan 7: First name-registry recognized by the main hub. Reg policy.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27668314#msg27668314</ref><br />
*Jan 7: Our ICO bot now supports BTC and ETH.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27619698#msg27619698</ref><br />
*Jan 3: CFD Trading (Trustful) bot added to bot store.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27431192#msg27431192</ref><br />
*Jan 3: Wallet version 2.1 released.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27376650#msg27376650</ref><br />
<br />
==2017==<br />
*Dec 14: Textcoins enabled in server-side wallets for bulk emails.<ref>https://bitcointalk.org/index.php?topic=1608859.msg26332250#msg26332250</ref><br />
*Dec 9: Wallet version 2.0 released.<ref>https://bitcointalk.org/index.php?topic=1608859.msg26003939#msg26003939</ref><br />
*Nov 21: Sports Oracle now supports UFC.<ref>https://bitcointalk.org/index.php?topic=1608859.msg24962770#msg24962770</ref><br />
*Nov 14: Byteball-Altcoin Exchange Bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg24594142#msg24594142</ref><br />
*Nov 11: Wallet version 1.11.3 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg24377569#msg24377569</ref><br />
*Nov 3: First real-world project with ICO on platform: TitanCoin<ref>https://bitcointalk.org/index.php?topic=1608859.msg24004338#msg24004338</ref><br />
*Oct 18: Wallet version 1.11.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg23182135#msg23182135</ref><br />
*Oct 2: LuckyBytes lottery bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg22484391#msg22484391</ref><br />
*Sep 29: Sports Betting bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg22371562#msg22371562</ref><br />
*Sep 7: Slice&Dice MUD game bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg21607962#msg21607962</ref><br />
*Sep 5: First Cashback merchants added<ref>https://bitcointalk.org/index.php?topic=1608859.msg21533378#msg21533378</ref><br />
*Aug 27: Buy Blackbytes bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg21250868#msg21250868</ref><br />
*Aug 25: Sports Oracle now supports MLB, NBA, NFL, NHL and soccer<ref>https://bitcointalk.org/index.php?topic=1608859.msg21199623#msg21199623</ref><br />
*Aug 23: Wallet version 1.10.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg21138107#msg21138107</ref><br />
*Aug 23: Cashback API for merchants is ready<ref>https://bitcointalk.org/index.php?topic=1608859.msg21130417#msg21130417</ref><br />
*Aug 7: Cashback program launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg20686283#msg20686283</ref><br />
*Aug 1: Wallet version 1.10.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg20534934#msg20534934</ref><br />
*Jul 29: Flight Delay Insurance bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg20474959#msg20474959</ref><br />
*Jun 30: Wallet version 1.9.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg19864486#msg19864486</ref><br />
*Jun 22: Grants program launched<ref>https://medium.com/byteball/byteball-grants-program-906a71b93d3c</ref><br />
*Jun 5: Rosie chatbot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg19378793#msg19378793</ref><br />
*Jun 1: Bot Store launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg19315253#msg19315253</ref><br />
*Jun 1: Wallet version 1.9.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg19315253#msg19315253</ref><br />
*May 28: Crowdin now used for wallet translations<ref>https://bitcointalk.org/index.php?topic=1608859.msg19244480#msg19244480</ref><br />
*May 19: Sports oracle P2P betting on soccer launched in Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg19101028#msg19101028</ref><br />
*Apr 26: P2P insurance on smart contracts launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18759349#msg18759349</ref><br />
*Apr 18: Wallet version 1.8 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18646968#msg18646968</ref><br />
*Apr 7: P2P gambling using smart contracts launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18499180#msg18499180</ref><br />
*Apr 5: Wallet version 1.7 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18466533#msg18466533</ref><br />
*Mar 18: Binding payments to oracle-posted events launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18240736#msg18240736</ref><br />
*Mar 18: Wallet version 1.6 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18240736#msg18240736</ref><br />
*Mar 6: Wallet version 1.5 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18080683#msg18080683</ref><br />
*Feb 22: Wallet version 1.4 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17942383#msg17942383</ref><br />
*Feb 11: Wallet version 1.3 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17808504#msg17808504</ref><br />
*Feb 10: Chinese WeChat group "Byteball 中国" launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg17803910#msg17803910</ref><br />
*Feb 3: Transaction Explorer now shows all blackbyte details as only "Hidden Payments"<ref>https://bitcointalk.org/index.php?topic=1608859.msg17720913#msg17720913</ref><br />
*Feb 3: Wallet version 1.2 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17718842#msg17718842</ref><br />
*Jan 19: Wallet version 1.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17559287#msg17559287</ref><br />
*Jan 17: Byte-BTC Exchange bot now live<ref>https://bitcointalk.org/index.php?topic=1608859.msg17527112#msg17527112</ref><br />
<br />
==2016==<br />
*Dec 25: Live network launched. Wallet version 1.0<ref>https://bitcointalk.org/index.php?topic=1608859.msg17303311#msg17303311</ref><br />
==External links==<br />
<br />
<br />
==References==<br />
<references /><br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1548PolloPollo2020-02-24T11:45:38Z<p>Slackjore: added link</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
=== Basic principles ===<br />
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><br />
<br />
== Website ==<br />
The project website at www.pollopollo.org is online, but not yet fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
<br />
=== Grant ===<br />
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:<br />
<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.<br />
<br />
<p>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.</p></blockquote><br />
<br />
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.<br />
<br />
== Independent witness ==<br />
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><br />
<br />
== The future for PolloPollo ==<br />
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.<br />
<br />
These are some of the key goals for the platform in the current year:<br />
* Establish our legal position with the Danish Board of Charitable Organizations “ISOBRO”<br />
* Establish our legal position for current functionality with Danish FSA<br />
* Acquire knowledge of the regulations if donations are done using a stablecoin<br />
* Acquire knowledge of the requirements for KYC of donors and producers<br />
* Determine who, how, where and when to store KYC information<br />
* 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><br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.ambcrypto.com/bitcoin-btc-proyecto-humanitario-en-blockchain-lleva-comida-a-venezuela/ AMBCrypto article (in Spanish) Nov 19 2019 about PolloPollo]<br />
*[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]<br />
*[https://www.criptonoticias.com/comunidad/beneficencia/travesia-bitcoiner-venezolano-premio-labitconf/ Criptonoticias article (Spanish) 26 Jan 2020 about B4H award for PolloPollo]<br />
*[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]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1547PolloPollo2020-02-24T11:28:25Z<p>Slackjore: added section on the future for PolloPollo</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
=== Basic principles ===<br />
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><br />
<br />
== Website ==<br />
The project website at www.pollopollo.org is online, but not yet fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
<br />
=== Grant ===<br />
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:<br />
<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.<br />
<br />
<p>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.</p></blockquote><br />
<br />
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.<br />
<br />
== Independent witness ==<br />
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><br />
<br />
== The future for PolloPollo ==<br />
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.<br />
<br />
These are some of the key goals for the platform in the current year:<br />
* Establish our legal position with the Danish Board of Charitable Organizations “ISOBRO”<br />
* Establish our legal position for current functionality with Danish FSA<br />
* Acquire knowledge of the regulations if donations are done using a stablecoin<br />
* Acquire knowledge of the requirements for KYC of donors and producers<br />
* Determine who, how, where and when to store KYC information<br />
* Establish the requirements to enable direct fiat-crypto-fiat donation facilities.<br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.ambcrypto.com/bitcoin-btc-proyecto-humanitario-en-blockchain-lleva-comida-a-venezuela/ AMBCrypto article (in Spanish) Nov 19 2019 about PolloPollo]<br />
*[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]<br />
*[https://www.criptonoticias.com/comunidad/beneficencia/travesia-bitcoiner-venezolano-premio-labitconf/ Criptonoticias article (Spanish) 26 Jan 2020 about B4H award for PolloPollo]<br />
*[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]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1546PolloPollo2020-02-24T08:55:24Z<p>Slackjore: added section re Danish FSA doc</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
=== Basic principles ===<br />
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><br />
<br />
== Website ==<br />
The project website at www.pollopollo.org is online, but not yet fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
<br />
=== Grant ===<br />
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:<br />
<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.<br />
<br />
<p>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.</p></blockquote><br />
<br />
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.<br />
<br />
== Independent witness ==<br />
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><br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.ambcrypto.com/bitcoin-btc-proyecto-humanitario-en-blockchain-lleva-comida-a-venezuela/ AMBCrypto article (in Spanish) Nov 19 2019 about PolloPollo]<br />
*[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]<br />
*[https://www.criptonoticias.com/comunidad/beneficencia/travesia-bitcoiner-venezolano-premio-labitconf/ Criptonoticias article (Spanish) 26 Jan 2020 about B4H award for PolloPollo]<br />
*[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]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Overview&diff=1545Overview2020-02-19T15:30:55Z<p>Slackjore: updated name</p>
<hr />
<div>'''Obyte''' features in-wallet: sports betting bots, payments to emails, encrypted text chat, altcoin exchange, your own custom tokens, your smart contracts.<br />
<br />
Formerly ''Byteball'', Obyte is a [[Directed_acyclic_graph|DAG]]-based cryptocurrency developed by Anton Churyumov.<br />
<br />
==Features==<br />
<br />
===Smart/conditional payments===<br />
<br />
[[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.<br />
<br />
This [[Smart_contract|smart-contract]] feature has many real-world peer-to-peer applications, including:<br />
<br />
* no-fee crypto exchanges<br />
* [[Sports_betting|sports betting]]<br />
* selling or buying insurance concerning negative events like a flight delay.<br />
<br />
===Textcoin===<br />
<br />
One can [[send]] Bytes (Obyte funds) by email or WhatsApp etc, even if the recipient is not in Obyte yet. For email, the sender just writes an email address where he would normally write a Obyte address. When he hits "Send", his email app is opened with pre-filled text for the recipient. The sender can edit the [[textcoin]] text before sending. The recipient receives an email with a link. Example:<br />
<br />
<blockquote>Here is your link to receive 0.001 GB: https://obyte.org/openapp.html#textcoin?pact-volume-lazy-midnight-mix-cool-fiction-symbol-tag-fiction-coral-sibling</blockquote><br />
<br />
===Identity verification for cryptos===<br />
<br />
Starting 18 January 2018, every Obyte user can link his Obyte 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 Obyte [[wallet]]. At the same time, a hash of the personal data is stored on the public DAG and signed by a trusted attestor. The attestor also serves as a [[witness]], so it is already trusted.<br />
<br />
This attestation allows the user to prove to anybody that his Obyte 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><br />
<br />
===Sending payments directly to email addresses===<br />
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 [Obyte] address.<ref>https://medium.com/byteball/distribution-to-verified-emails-and-sending-cryptocurrency-to-email-episode-ii-cb955fe19d7e</ref><br />
<br />
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.<br />
<br />
===Blackbytes===<br />
Private payments can be made using [[blackbytes]], a cash-like untraceable currency. Its transactions are not visible on the public database that shows all payments made with (white)bytes. Blackbytes are sent peer-to-peer instead in an encrypted chat session.<br />
<br />
===Chatbots===<br />
[[File:Betting-bot.jpg|thumb|left]][[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).<br />
<br />
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, [[Fun-coins]] faucet, SilentNotary ICO, Worldopoly ICO.<br />
<br />
^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.<br />
<br />
==Platform== <br />
Obyte has its native currencies, Bytes and Blackbytes. It is also a [[platform]] for new assets (coins or [[token]]s) you can create yourself at minimal cost in five minutes. You can simply send your [[asset]] to anyone with a Obyte wallet, or you can use your asset in many smart contracts.<ref>https://wiki.obyte.org/asset</ref><br />
<br />
Some examples:<br />
*'''Fun-coins:''' You can get millions of [[Tingos]], [[Tangos]], [[Zingos]] and [[Zangos]] from the free faucet in the Bot Store. The idea is use them to practise with textcoins, smart contracts etc without worrying if you lose them somehow.<br />
*'''TitanCoin ICO:''' Independent ICO, where coins can be bought via the bot paying with GB, BTC, or Ethereum.<br />
*'''SilentNotary ICO:''' Independent ICO, where coins can be bought via the bot paying with GB, BTC, or Ethereum.<br />
*'''Worldopoly ICO:''' Independent ICO, where coins can be bought via the bot paying with GB, BTC, or Ethereum.<br />
<br />
==Basic info==<br />
<br />
===Native currencies=== <br />
*'''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.<br />
*'''Blackbytes:''' Total supply = 2.1111 x 10^15. 1 GBB = 1,000 MBB = 1,000,000 KBB = 1,000,000,000 Blackbytes.<br />
<br />
All Bytes and Blackbytes were created at the genesis and 2nd unit. So far approx 69% have been issued for use.<br />
<br />
===Date introduced===<br />
*First announced 5 September 2016.<ref>https://bitcointalk.org/index.php?topic=1608859.msg16156239#msg16156239</ref><br />
*Platform went live on 25 December 2016.<br />
<br />
===DAG===<br />
Obyte data is stored and ordered using a [[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.<br />
<br />
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.<br />
<br />
The Obyte DAG is about 35 GB in March 2019.<br />
<br />
==Zurich presentation==<br />
A presentation given by Tony on 2 February 2018, that gives an excellent overview of Obyte.<ref>https://docs.google.com/presentation/d/1dpbE1l4Aj8Te2_i9wjVsW48igZMhdyjKJVcWY-45qd8/edit#slide=id.p5</ref><br />
<br />
==Videos==<br />
<youtube>https://www.youtube.com/watch?v=2ZuYZOitKfQ</youtube><br />
<br />
<youtube>https://www.youtube.com/watch?v=zOayZ2_6cN4</youtube><br />
<br />
<youtube>https://www.youtube.com/watch?v=RT-pA_KHz4U</youtube><br />
<br />
<youtube>https://www.youtube.com/watch?v=SnXuylxUKqo</youtube><br />
<br />
==External links==<br />
* [https://obyte.org Main website]<br />
* [https://obyte.org/Byteball.pdf White paper]<br />
* [https://explorer.obyte.org Transactions explorer]<br />
* [https://medium.com/@Byteball Medium articles]<br />
* [https://bitcointalk.org/index.php?topic=1608859.0 Bitcointalk thread]<br />
* [https://byteball.market/#!/asset/order Byteball Asset Manager (for you to create your own coin on the Obyte platform)]<br />
* [https://wiki.obyte.org Byteball Wiki]<br />
* [https://www.reddit.com/r/Obyte Community Subreddit]<br />
* [https://obyte.slack.com Community Slack]<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Browse]]<br />
[[Category:Features]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Autonomous_Agent&diff=1544Autonomous Agent2020-02-19T15:24:18Z<p>Slackjore: added mainnet release info</p>
<hr />
<div>== Overview ==<br />
[[Smart contract]]s embody voluntary relationships between two free equals.<br />
<br />
However, there is another class of applications that are not covered by smart contracts: applications where an autonomous central counterparty interacts with multiple users and does so strictly according to the rules that are public, known in advance, and can never be changed. That’s what '''Autonomous Agents''' are.<br />
<br />
An Autonomous Agent (AA) is a special address (account) on the ledger that acts according to a program associated with it. Its behavior is similar to that of a vending machine that receives coins and data entered on a keypad and in response, releases a cup of coffee, plays a song, or does whatever it was programmed to do.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
This is the first major upgrade to the Obyte protocol. It has been under development for 9 months. It was released to Testnet 18 June 2019, where testing and development was expected to take 2-4 months. The release had been expected in January/February 2020, after AA-based [[ODEX]]'s addition to livenet too.<ref>https://medium.com/obyte/whats-next-for-obyte-a-decentralized-exchange-fd7164569a9d</ref><br />
<br />
=== Mainnet release ===<br />
Wallet version 3.0.0 was released Feb 19, 2020. AAs will become activated on mainnet at approximately the end of February.<ref>https://medium.com/obyte/autonomous-agents-on-mainnet-ready-for-takeoff-d89b50e6d921</ref><br />
<br />
== Developer contest ==<br />
To celebrate this massive milestone, we invited developers to join a running contest to build the most innovative, impressive, useful, exciting and spectacular Autonomous Agents.<br />
<br />
Total Prize Pool worth $38,000 at current rate.<br />
<br />
The contest kicked off July 18, 2019 and ran until mid-October. Every two weeks, a jury of Obyte team members led by the platform’s founder, Tony, announced the best entries. Autonomous Agents were live on Testnet, and the easy-to-use online editor is available for developers to explore. It even has a few nice templates to help get everyone off to an easy start.<ref>https://medium.com/obyte/obyte-autonomous-agents-developer-contest-6a67ae3dacd2</ref><br />
<br />
=== Results ===<br />
Round 1, announced 4 August<ref>https://medium.com/obyte/winners-of-the-first-round-of-the-autonomous-agents-developer-contest-bc8cbbe0d8b4</ref><br />
*1st place (140 GB / 422 GBB): Fabien — “A Simple DAO”<br />
*2nd place (70 GB / 147.7 GBB): Barborico — “Bank With Secrets"<br />
*3rd place (35 GB / 73.85 GBB): Pmiklos — “Lottery With Community Governance” <br />
*Best guide/tutorial (55 GB and 116.05 GBB): Pmiklos — “Getting Started With Obyte Autonomous Agents” <br />
<br />
Round 2, announced 19 August<ref>https://medium.com/obyte/winners-of-the-second-round-of-the-obyte-autonomous-agents-developer-contest-c69e37dbf55</ref><br />
*1st place (140 GB / 422 GBB): Pmiklos — “Autonomous Subscription Service”<br />
*2nd place (70 GB / 147.7 GBB): Alvarlaigna — “EOS-like Crowdsale”<br />
*3rd place (35 GB / 73.85 GBB): Hey_monkey — “The Attested Reputations Autonomous Agent”<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Pmiklos — “Stateful Autonomous Agents”<br />
<br />
Round 3, announced 3 September<ref>https://medium.com/obyte/third-round-of-obyte-autonomous-agents-developer-contest-4a7df3d70b29</ref><br />
*Postponed because of testnet crashes (good for [[antifragility]])<br />
*Special testnet crash-testing bonus of 10 GB and 21.111 GBB each: Whoisterencelee, hey_monkey and barborico<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Hey_monkey — "Understanding Obyte AA Bounce Fee" <br />
<br />
Round 4, announced 16 September<ref>https://medium.com/obyte/fourth-round-of-obyte-atonomous-agents-developer-contest-430891f9cf4b</ref><br />
*1st place (140 GB / 422 GBB): Hey_monkey — “Offer reward to get triggered in the future (THAANKS)”<br />
*2nd place (70 GB / 147.7 GBB): Barborico — “Ownerless AA Registry”<br />
*3rd place (35 GB / 73.85 GBB): Whoisterencelee — “Red vs Blue”<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Hey_monkey — “Understanding AA Structures” <br />
<br />
Round 5, announced 2 October<ref>https://medium.com/obyte/fifth-round-of-obyte-autonomous-agents-developer-contest-c554f7756d04</ref><br />
*1st place (140 GB / 422 GBB): Hey_monkey — “Joint Account Autonomous Agent (JAAA)”<br />
*2nd place (70 GB / 147.7 GBB): Vik — “ByteKeeper”<br />
*3rd place (35 GB / 73.85 GBB): Whoisterencelee — “Time For Birthday Fiddle”<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Pmiklos — “How to set up devnet for rapid development” <br />
<br />
Round 6, announced 15 October<ref>https://medium.com/obyte/sixth-round-of-obyte-autonomous-agents-developer-contest-6aa89bedd712</ref><br />
*1st place (140 GB / 422 GBB): Crypto Girl — “ObyStack”<br />
*2nd place (70 GB / 147.7 GBB): Hey_monkey — “WEAALTH Use An AA To Establish Your GBytes Testament”<br />
*3rd place (35 GB / 73.85 GBB): Sharjar — “Simple Public Asset Storage”<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Crypto Girl — “ObyStack AA Stack Game” <br />
<br />
Round 7 (Final round), announced 1 November<ref>https://medium.com/obyte/final-round-of-obyte-autonomous-agents-developer-contest-704306b64d79</ref><br />
*1st place (140 GB / 422 GBB): Frank Bee — “Autonomous Auctioneer”<br />
*2nd place (70 GB / 147.7 GBB): Lion’s Heart — “Certificate of Deposit”<br />
*3rd place (35 GB / 73.85 GBB): Hey_monkey — “A Renting Guarantee Autonomous Agent (ARGAA)”<br />
*Honorable mention (10 GB / 21.111 GBB): Whoisterencelee — "Obotic"<br />
*Honorable mention (10 GB / 21.111 GBB): Vik — "EmailBank"<br />
*Best guide/tutorial (55 GB and 116.05 GBB): Hey_monkey — “Use a web page to interact with Obyte powered AA” <br />
<br />
== Oscript editor ==<br />
Autonomous Agents are written in Oscript — a new programming language developed specifically for this purpose.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref> The editor offers everything you would expect from a modern editor. Syntax highlighting with tooltips and help, auto completion and the editor even has built-in code validation. In other words, a full fledged code editor ready for real world adoption.<ref>https://medium.com/obyte/oscript-improvements-and-competiton-inspiration-57051449b139</ref><br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category: Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Main_Page&diff=1543Main Page2020-02-19T15:16:28Z<p>Slackjore: added Feb 19 news item</p>
<hr />
<div>__NOTOC__<br />
[[File:Obyte-logo.jpg|thumb|250px]] <br />
'''Welcome to the Obyte Wiki. See first a one-page [[overview|OVERVIEW]], the [[glossary|GLOSSARY]], and the [[wallet|WALLET]] page. See [[Special:AllPages|ALL PAGES here]].'''<br />
<br />
==Introduction==<br />
Obyte, formerly Byteball, now listed on CoinMarketCap<ref>https://coinmarketcap.com</ref> as simply ''Obyte'', is a DAG-based cryptocurrency developed by Anton (Tony) Churyumov.<br />
<br />
This wiki is aimed at general cryptocurrency users, as well as Obyte users, who want to become better informed about Obyte. <br />
<br />
The wiki content is currently generated by invited contributors, and not randomly.<br />
<br />
==License==<br />
All content of this wiki is available under a Creative Commons Attribution-ShareAlike 3.0 Unported [[License]].<br />
<br />
== External links ==<br />
*[https://obyte.org Main official site]<br />
*[https://explorer.obyte.org Transactions explorer]<br />
*[https://obyte.org/Byteball.pdf White paper]<br />
*[https://medium.com/Obyte ''Medium'' articles]<br />
*[https://www.youtube.com/channel/UCYAjbxT5zHfeTtXe_hr9Gxg Obyte Channel on YouTube]<br />
*[https://asset.obyte.app Obyte Asset Registry for you to create a new asset]<br />
*[https://github.com/byteball/byteball Repository]<br />
*[https://obyte.io An Obyte data explorer]<br />
<br />
===Forums===<br />
*[https://discord.obyte.org Discord channel invitation] <br />
*[https://bitcointalk.org/index.php?topic=1608859.0) Bitcointalk thread]<br />
*[https://bitcointalk.org/index.php?action=profile;u=412662;sa=showPosts;start=0) Tony's posts on bitcointalk]<br />
*[https://reddit.com/r/obyte Subreddit]<br />
*[https://telegram.me/obyte Telegram]<br />
*[https://twitter.com/ObyteOrg Twitter]<br />
<br />
==Latest [[News]]==<br />
*Feb 19: Version 3.0.0 released, preparatory to activating AAs on mainnet in approx 2 weeks<ref>https://medium.com/obyte/autonomous-agents-on-mainnet-ready-for-takeoff-d89b50e6d921</ref><br />
*Feb 6: [[PolloPollo]] 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><br />
*Dec 27: Bosch Connectory announced as the 3rd default witness (order provider)<ref>https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03</ref><br />
*Sep 25: Version 2.8.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg52555921#msg52555921</ref><br />
*Aug 7: The first Ocademy (Obyte Academy) student graduates<ref>https://medium.com/obyte/meet-the-first-ocademy-workshop-graduate-133617202c</ref><br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=News&diff=1542News2020-02-19T15:15:02Z<p>Slackjore: added 19 Feb item</p>
<hr />
<div>Very brief '''headline''' items only, with links to each announcement, usually on Bitcointalk as a permanent record.<br />
<br />
== 2020 ==<br />
*Feb 19: Version 3.0.0 released, preparatory to activating AAs on mainnet in approx 2 weeks<ref>https://medium.com/obyte/autonomous-agents-on-mainnet-ready-for-takeoff-d89b50e6d921</ref><br />
*Feb 6: [[PolloPollo]] announced as the 4th default witness (order provider)<ref>https://medium.com/obyte/pollopollo-approved-to-become-a-default-witness-on-the-obyte-public-network-9ee32238142f</ref><br />
<br />
==2019==<br />
*Dec 27: Bosch Connectory announced as the 3rd default witness (order provider)<ref>https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03</ref><br />
*Sep 25: Version 2.8.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg52555921#msg52555921</ref><br />
*Aug 7: The first Ocademy (Obyte Academy) student graduates<ref>https://medium.com/obyte/meet-the-first-ocademy-workshop-graduate-133617202c</ref><br />
*Aug 5: Sports oracle updated to work with [[Autonomous Agent]]s<ref>https://medium.com/obyte/sports-oracle-for-autonomous-agents-96b56369168a</ref><br />
*Aug 1: "What's [[next]] for Obyte" blog launched<ref>https://medium.com/obyte/whats-next-for-obyte-b495cfbb698</ref><br />
*Jul 18: Autonomous Agents protocol upgrade released on Testnet<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
*Jun 11: Version 2.7.2 released<ref>https://github.com/byteball/obyte-gui-wallet/releases</ref><br />
*Apr 30: Obyte Foundation Establishment announced<ref>https://medium.com/obyte/obyte-foundation-is-established-c92a28d2d20e</ref><br />
*Apr 20: Version 2.7.0 released. Includes prosaic contracts.<ref>https://github.com/byteball/obyte-gui-wallet/releases</ref><br />
*Apr 16: 2nd independent witness candidate announced<ref>https://medium.com/obyte/second-independent-witness-candidate-fabien-marino-d4e8dccadee</ref><br />
*Apr 10: New method of identity verification launched for residents of Estonia, Latvia, Lithuania, and e-residents of Estonia.<ref>https://medium.com/obyte/new-methods-for-identity-verification-3d5045287533</ref><br />
*Jan 17: Byteball rebranded to Obyte<ref>https://medium.com/byteball/byteball-rebrand-the-next-step-to-real-world-adoption-6a0a924390de</ref><br />
<br />
==2018==<br />
*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><br />
*Dec 1: Byteball developer resources site launched at https://developer.byteball.org<ref>https://twitter.com/slackjore/status/1069216217691508736</ref><br />
*Oct 15: Smart Vouchers for Real Name Attestation introduced<ref>https://bitcointalk.org/index.php?topic=1608859.msg46911901#msg46911901</ref><br />
*Oct 14: Filter added to Explorer<ref>https://twitter.com/slackjore/status/1051452800696238080</ref><br />
*Sep 23: Dice bot added to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg46089759#msg46089759</ref><br />
*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><br />
*Aug 28: Nousplatform ICO added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg44795934#msg44795934</ref><br />
*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><br />
*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><br />
*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><br />
*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><br />
*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><br />
*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><br />
*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><br />
*Jun 23: Wallet version 2.3 released. Includes sending blackbytes as textcoins<ref>https://bitcointalk.org/index.php?topic=1608859.msg40698998#msg40698998</ref><br />
*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><br />
*May 29: Added Private Chat Room bot to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg38902178#msg38902178</ref><br />
*May 28: Added Exchange Bot for Dual-Chain Tokens to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg38743714#msg38743714</ref><br />
*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><br />
*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><br />
*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><br />
*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><br />
*Apr 26: Added World Community Grid linking bot to the Bot Store<ref>https://medium.com/byteball/computing-for-good-again-3795336bdaed</ref><br />
*Apr 20: Added Accredited investor attestation bot to the Bot Store<ref>https://medium.com/byteball/attestation-of-accredited-investors-d4a8dabf683b</ref><br />
*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><br />
*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><br />
*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> <br />
*Mar 23: Exchange bot for ICOs added to the Bot Store<ref>https://medium.com/byteball/byteball-exchange-bot-78c8154f4e6a</ref><br />
*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><br />
*Feb 18: March 2 and future [[airdrop]]s terminated<ref>https://bitcointalk.org/index.php?topic=1608859.msg30564528#msg30564528</ref><br />
*Feb 15: SilentNotary ICO added to Bot Store<ref>https://twitter.com/ByteballOrg/status/964267908879781888</ref><br />
*Jan 26: Free [[fun-coins]] faucet added to Bot Store<ref>https://twitter.com/slackjore/status/957355056235499520</ref><br />
*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><br />
*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><br />
*Jan 13: Eli Taranto now onboard as PR and Marketing director.<ref>https://bitcointalk.org/index.php?topic=1608859.msg28047149#msg28047149</ref><br />
*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><br />
*Jan 7: First name-registry recognized by the main hub. Reg policy.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27668314#msg27668314</ref><br />
*Jan 7: Our ICO bot now supports BTC and ETH.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27619698#msg27619698</ref><br />
*Jan 3: CFD Trading (Trustful) bot added to bot store.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27431192#msg27431192</ref><br />
*Jan 3: Wallet version 2.1 released.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27376650#msg27376650</ref><br />
<br />
==2017==<br />
*Dec 14: Textcoins enabled in server-side wallets for bulk emails.<ref>https://bitcointalk.org/index.php?topic=1608859.msg26332250#msg26332250</ref><br />
*Dec 9: Wallet version 2.0 released.<ref>https://bitcointalk.org/index.php?topic=1608859.msg26003939#msg26003939</ref><br />
*Nov 21: Sports Oracle now supports UFC.<ref>https://bitcointalk.org/index.php?topic=1608859.msg24962770#msg24962770</ref><br />
*Nov 14: Byteball-Altcoin Exchange Bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg24594142#msg24594142</ref><br />
*Nov 11: Wallet version 1.11.3 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg24377569#msg24377569</ref><br />
*Nov 3: First real-world project with ICO on platform: TitanCoin<ref>https://bitcointalk.org/index.php?topic=1608859.msg24004338#msg24004338</ref><br />
*Oct 18: Wallet version 1.11.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg23182135#msg23182135</ref><br />
*Oct 2: LuckyBytes lottery bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg22484391#msg22484391</ref><br />
*Sep 29: Sports Betting bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg22371562#msg22371562</ref><br />
*Sep 7: Slice&Dice MUD game bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg21607962#msg21607962</ref><br />
*Sep 5: First Cashback merchants added<ref>https://bitcointalk.org/index.php?topic=1608859.msg21533378#msg21533378</ref><br />
*Aug 27: Buy Blackbytes bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg21250868#msg21250868</ref><br />
*Aug 25: Sports Oracle now supports MLB, NBA, NFL, NHL and soccer<ref>https://bitcointalk.org/index.php?topic=1608859.msg21199623#msg21199623</ref><br />
*Aug 23: Wallet version 1.10.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg21138107#msg21138107</ref><br />
*Aug 23: Cashback API for merchants is ready<ref>https://bitcointalk.org/index.php?topic=1608859.msg21130417#msg21130417</ref><br />
*Aug 7: Cashback program launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg20686283#msg20686283</ref><br />
*Aug 1: Wallet version 1.10.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg20534934#msg20534934</ref><br />
*Jul 29: Flight Delay Insurance bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg20474959#msg20474959</ref><br />
*Jun 30: Wallet version 1.9.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg19864486#msg19864486</ref><br />
*Jun 22: Grants program launched<ref>https://medium.com/byteball/byteball-grants-program-906a71b93d3c</ref><br />
*Jun 5: Rosie chatbot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg19378793#msg19378793</ref><br />
*Jun 1: Bot Store launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg19315253#msg19315253</ref><br />
*Jun 1: Wallet version 1.9.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg19315253#msg19315253</ref><br />
*May 28: Crowdin now used for wallet translations<ref>https://bitcointalk.org/index.php?topic=1608859.msg19244480#msg19244480</ref><br />
*May 19: Sports oracle P2P betting on soccer launched in Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg19101028#msg19101028</ref><br />
*Apr 26: P2P insurance on smart contracts launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18759349#msg18759349</ref><br />
*Apr 18: Wallet version 1.8 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18646968#msg18646968</ref><br />
*Apr 7: P2P gambling using smart contracts launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18499180#msg18499180</ref><br />
*Apr 5: Wallet version 1.7 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18466533#msg18466533</ref><br />
*Mar 18: Binding payments to oracle-posted events launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18240736#msg18240736</ref><br />
*Mar 18: Wallet version 1.6 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18240736#msg18240736</ref><br />
*Mar 6: Wallet version 1.5 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18080683#msg18080683</ref><br />
*Feb 22: Wallet version 1.4 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17942383#msg17942383</ref><br />
*Feb 11: Wallet version 1.3 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17808504#msg17808504</ref><br />
*Feb 10: Chinese WeChat group "Byteball 中国" launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg17803910#msg17803910</ref><br />
*Feb 3: Transaction Explorer now shows all blackbyte details as only "Hidden Payments"<ref>https://bitcointalk.org/index.php?topic=1608859.msg17720913#msg17720913</ref><br />
*Feb 3: Wallet version 1.2 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17718842#msg17718842</ref><br />
*Jan 19: Wallet version 1.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17559287#msg17559287</ref><br />
*Jan 17: Byte-BTC Exchange bot now live<ref>https://bitcointalk.org/index.php?topic=1608859.msg17527112#msg17527112</ref><br />
<br />
==2016==<br />
*Dec 25: Live network launched. Wallet version 1.0<ref>https://bitcointalk.org/index.php?topic=1608859.msg17303311#msg17303311</ref><br />
==External links==<br />
<br />
<br />
==References==<br />
<references /><br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Glossary&diff=1541Glossary2020-02-17T16:48:54Z<p>Slackjore: typo</p>
<hr />
<div>Obyte terms, not too technical, but assuming some familiarity with cryptocurrencies <br />
<br />
==Entries==<br />
'''ADDRESS:''' (Disambiguation) <br />
<br />
* A device address is all upper case, starts with 0, looks like 0VCPO8MYDRN2E6N5JDRHRLTVEVZSZYARM<br />
<br />
* A payment address in a wallet is all upper case, looks like K7RMH5EFPZW67JTS5B5GA6PDZA4MYX4LY<br />
<br />
* A wallet ID looks like lNeHNjLs3u38SJ9dPb+SUZ+aZX3a7RWI1osYJH9QHRw=<br />
<br />
* A unit address, like a transaction you sent, looks like Ip241kkFRkZnaVF61Z6+/JW3YELOaHn9C6PAjeMp8fs= <br />
<br />
* A bitcoin address looks like 13AM4VW2dhxYgXeQepoHkHSQuy6NgaEb94, may also start with "3" or "bc1".<br />
<br />
'''AIR-DROP:''' The final snapshot for distribution of new bytes to payment addresses linked to proven BTC balances occurred on 4 November 2017 at 05:23 UTC. <br />
<br />
* For each 1 BTC linked --> 6.25MB (0.00625GB) <br />
<br />
* For each 1 BTC linked --> 2.1111 x 6.25 million blackbytes (money supply of blackbytes is 2.1111 times as much as that of bytes)<br />
<br />
* For every 10 (white)bytes on any address --> 1 new (white)byte<br />
<br />
* For every 10 (white)bytes on a '''linked''' address --> 2.1111 new blackbytes.<br />
<br />
See wiki [[Airdrop]] article.<br />
<br />
'''ASSET:''' Users can issue new assets and define rules that govern their transferability. For example: ICOs, shares, bonds, fiat-pegged coins, loyalty points, minutes of airtime, assets in online games, whatever you can imagine. You can do this in Obyte right now. See wiki article [[Asset]] for instructions<br />
<br />
'''ATOMIC EXCHANGE:''' When two parties sign a single unit that executes both legs of the exchange, the two transactions either happen simultaneously or don't happen at all. It is no longer necessary to trust any centralized exchanges. Note this uses a definition of "atomic" related to databases, and has nothing to do with the usual "extremely small" senses.<ref>https://obyte.org Front page, other features</ref><br />
<br />
'''ATTESTOR:''' The attestor who attests the email addresses through the [[Chatbot#Email_attestation_bot|Email attestation bot]] is <code>H5EZTQE7ABFH27AUDTQFMZIALANK6RBG</code>, and it is also a WITNESS. The attestor is trusted to post only true Obyte-address-to-email-address links to the DAG.<ref>https://medium.com/byteball/distribution-to-verified-emails-and-sending-cryptocurrency-to-email-episode-ii-cb955fe19d7e</ref><br />
<br />
'''AUTHOR:''' (In explorer) Authors are payment addresses that signed the transaction, similar to bitcoin sending address.<br />
<br />
'''AUTONOMOUS AGENT:''' An [[Autonomous Agent]] (AA) is a special address (account) on the ledger that acts according to a program associated with it. Its behavior is similar to that of a vending machine that receives coins and data entered on a keypad and in response, releases a cup of coffee, plays a song, or does whatever it was programmed to do.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
'''BBIP:''' Byteball Improvement Proposal. Replaced by OIP.<br />
<br />
'''BIND:''' See CONDITIONAL PAYMENTS<br />
<br />
'''BLACKBYTE:''' One of the two native Obyte currencies (also see BYTE). When you want complete privacy pay in blackbytes, a cash-like untraceable currency whose transactions are not visible on the public database. They are sent peer-to-peer instead.<ref>https://obyte.org Front page</ref>. With wallet version 2.3 they can be sent by digital file to someone not in Obyte yet.<ref>https://medium.com/byteball/private-textcoins-6a2288d80757</ref><br />
<br />
'''BOT:''' See CHATBOT<br />
<br />
'''BOT STORE:''' The section in the Obyte platform, available from the CHAT tab, that contains about 20 bots you can add to your contacts.<br />
<br />
'''BYTE:''' One of the two native currencies of the Obyte network (also see BLACKBYTE). It is also a basic general computing term: *A sequence of adjacent bits, usually eight, operated on as a unit, e.g. 0 1 0 1 1 1 0 1. One byte can store one character, e.g. 'A' or 'x' or '$'.* There are 10^15 total Bytes in the system. The unit traded on exchanges is the "GByte", 10^9 Bytes.<br />
<br />
'''BYTEBALL (NAME):''' (1) Once a unit is broadcast into the network, and other users start building their units on top of it (referencing it as parent), the number of secondary revisions required to edit this unit hence grows like a snowball. That’s why we call this design '''Byteball''' (our snowflakes are bytes of data).<ref>https://obyte.org/Byteball.pdf p.5</ref> [Rebranded to ''Obyte'' on 17 Jan 2019]<br />
<br />
(2) ''Byteball'' (upper-case "B") was the name of the platform, the protocol; ''byteball'' (lower-case "b") was sometimes (mis)used very loosely to represent the currency, as in "Hey, I see a byteball [1 GB] is now worth $250!" or "Use blackbytes for private transactions and byteballs for the open ones".<br />
<br />
'''BYTEROLL:''' The original Byteball wiki was hosted at byteroll.com on @portabella's private server. The Byteball wiki subdomain forwarded to Byteroll.<br />
<br />
'''CASHBACK:''' We want to get this coin into the hands of as many people as possible. In addition to the regular monthly airdrop, we are going to partner with several categories of companies, like merchants, payment processors, and "Bitcoin debit card" companies. We will offer 10% [[cashback]], paid in Bytes, for all qualifying purchases (no matter how the purchases are paid). <br />
<br />
'''CHAT:''' The platform incorporates a chat function, allowing the user to exchange end-to-end-encrypted messages using AES with a peer or bot when their devices are paired. It's end-to-end encrypted using AES. The hubs only forward the encrypted messages; they can't see anything. To deliver your message, your platform connects to the recipient's hub (if it's different from your home hub).<ref>https://bitcointalk.org/index.php?topic=1608859.msg21798347#msg21798347</ref><br />
<br />
'''CHATBOT:''' You can pair your platform with a bot, which emulates the experience of chatting with a live person. The bot will have very limited responses, but enough to get the job done. A merchant bot could allow you to select from a range of pizzas, for example, then pay for your order with two clicks while still in that chat session. See the wiki [[Chatbot]] article for a list.<br />
<br />
'''CHILDREN:''' (In explorer) Children and parents are pointers to later and earlier units in the DAG (see the arrows between units).<br />
<br />
'''CONDITIONAL PAYMENTS:''' This is the '''killer feature''' of Obyte, and the "smart payments" in the [[slogan]]. You can choose to bind a payment to a condition. If/when that condition is satisfied the payment is unlocked and only the recipient can collect it. If the condition fails the payment can only be collected by the issuer. See the wiki [[Trading blackbytes]] article for an example.<br />
<br />
'''CONFIRMED:''' An Obyte payment is confirmed/stable once it has become sufficiently buried by later transactions to be unalterable, similar to confirmations on a blockchain. It usually takes about five minutes.<br />
<br />
'''DAG:''' [[Directed_acyclic_graph]], the radically-different immutable data structure used in the Obyte platform instead of the usual cryptocurrency blockchain. No mining, no proof-of-work, no proof-of-stake.<ref>https://obyte.org/Byteball.pdf White paper</ref><br />
<br />
'''DATAFEED:''' A line item posted into the DAG by an oracle. The data is of the form [Datafeed name] then [Datafeed value], for example <code>BTC_USD: 6788.0</code>.<br />
<br />
'''DISTRIBUTION:''' See AIRDROP. For current campaigns to give away undistributed bytes, see https://obyte.org/#dist.<br />
<br />
'''DOUBLE-SPEND:''' In case of doublespend, the version that comes earlier on the main chain wins. Therefore, if your node is well-connected and you see a few other transactions piling up on top of the new unconfirmed transaction, and the time since its arrival is significantly larger than the typical network latency, then you can be reasonably sure that even if a doublespend appears later it will be sorted later, hence voided.<br />
<br />
'''DRAW:''' A weekly random airdrop to existing bytes holders, started Dec 8, 2018.<ref>https://medium.com/obyte/weekly-draw-for-the-byteball-community-f464ae731c88</ref> As a distribution method it was superseded July 18, 2019 by the Autonomous Agent developer contest.<ref>https://medium.com/obyte/distribution-outlook-bb28ff0b91aa</ref><br />
<br />
'''FREE UNIT:''' A unit that has no children.<br />
<br />
'''FULLY FUNDED:''' The state of a SMART CONTRACT when the agreed payments from both parties have been locked in the contract until certain conditions are satisfied. See the wiki [[Smart contract]] article.<br />
<br />
'''FUN-COIN:''' A freely-available token on the Obyte platform having zero monetary value, intended for practice with various features like textcoin and smart contracts. See the wiki [[fun-coins]] article.<br />
<br />
'''GENESIS UNIT:''' The Obyte analog to Bitcoin's genesis block, including the creation of the entire global supply of its native currencies: 1,000,000 GBytes and 2,111,100 GBBytes. <br />
<br />
'''GRANTS:''' Obyte Grants Program. We’ll pay for work that improves the ecosystem. We want the contributors to both come up with new ideas and realize them.<ref>https://medium.com/byteball/byteball-grants-program-906a71b93d3c)</ref><br />
<br />
'''HUB:''' This is a node for the Obyte network that serves as a relay, plus it facilitates the exchange of end-to-end encrypted messages among devices connected to the Obyte network. The hub does not hold any private keys and cannot send payments itself, nor can it read the messages. Users set their hub address in their wallet settings. The default hub is wss://obyte.org/bb but users can change it.<ref>https://github.com/byteball/byteball-hub) Github readme.md</ref> See wiki [[Hub]] article.<br />
<br />
'''ICO:''' An '''initial coin offering''' is a controversial means of crowdfunding centered around cryptocurrency, which can be a source of capital for startup companies. In an ICO, a quantity of the crowdfunded cryptocurrency is preallocated to investors in the form of "tokens", in exchange for legal tender or other cryptocurrencies such as bitcoin or ethereum. These tokens supposedly become functional units of currency if or when the ICO's funding goal is met and the project launches.<ref>https://en.wikipedia.org/wiki/Initial_coin_offering</ref> Obyte has an ICO bot, and anyone can issue tokens on the platform.<br />
<br />
'''IDENTITY VERIFICATION:''' Proving one's real-world identity with government-issued documentation using the [[Chatbot#Real_name_attestation_bot|REAL NAME ATTESTATION bot]], but after this one can verify age or country of origin without disclosing further identifying information. Same as REAL NAME ATTESTATION<br />
<br />
'''LINKED:''' Concerning airdrops, it refers to (white)bytes at one of your wallet addresses linked to bitcoins, where the link has been verified by the transition bot. All such pairs were visible on the transition pages<ref>https://transition.byteball.org</ref>.<br />
<br />
'''MOVED:''' In a wallet history, shows funds moving from one address in your wallet to a different address in the same wallet. Either you deliberately sent them there, or they moved as change. See wiki article [[Change address]].<br />
<br />
'''MULTI SIGNATURE:''' For security, you can require that your funds be spendable only when several signatures are provided, e.g. from your laptop and from your phone. For shared control of funds, signatures from different people may be required.<ref>https://obyte.org front page, other features</ref><br />
<br />
'''NODE:''' Imagine a fishing net: the nodes would be the knots holding the lines of rope together. Every device in the Obyte network is technically a node, whether a light client/platform, a full platform, a relay or a hub. Informally, node is used to mean full platform. See wiki article [[Node]] for different roles.<br />
<br />
'''O:''' [Tony:] O in Obyte stands for Open. When we renamed, many people wondered what O stands for. While it is true that it replaces the former "ball", I also want to make it clear that O stands for Open. It speaks about the core values of the platform: open access to the ledger, not encumbered by miners or other intermediaries, which simply do not exist here in a DAG. We are going to have more O-names for the products built on top of the platform.<ref>https://www.reddit.com/r/obyte/comments/aioub3/o_in_obyte_stands_for_open</ref><br />
<br />
'''OBBY CHAT:''' Instant mobile-only messaging app for Obyte. Offering secure end-to-end encryption, cryptocurrency payments, and smart contracts.<ref>https://obby.chat/</ref> Being built by BindCreative from a grant application<ref>https://drive.google.com/file/d/1KWlwbFO1QU-IER_kgRjOf4UDLwEp0a0n/view</ref> approved July 2019.<br />
<br />
'''OBYTE COMMUNITY FUND:''' The [[Obyte_community_fund|Obyte Community Fund]]'s goal is to support and encourage the Obyte crypto platform. Fundraising is done by voluntary donations from investors, stakeholders and enthusiasts. <br />
<br />
'''ODEX:''' DEX is a Decentralized Exchanged. [[ODEX]] is Obyte's DEX.<br />
<br />
'''OIP:''' Obyte Improvement Proposal. Based on the Bitcoin BIP system. See [[OIP]] wiki article.<br />
<br />
'''ORACLE:''' A trusted third party that monitors specific external events and registers selected data-feed items to the Obyte database. An example is a list of cryptocurrency exchange rates updated every ten minutes. When dealing with untrusted counterparties, you can lock the funds on a payment address that is spendable either by you or by the counterparty, depending on the oracle's data collection and registration.<ref>https://obyte.org front page, other features</ref> See wiki article [[Oracle]].<br />
<br />
'''OSCRIPT:''' AUTONOMOUS AGENTS are written in Oscript — a new programming language developed specifically for this purpose.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
'''OSWAP:''' [Chinese] One-click exchange platform for hundreds of crypto assets.<ref>https://www.oswap.cc/#/</ref> OSwap is funded by the Obyte Foundation to facilitate purchase of bytes by the Chinese community. Telegram channel.<ref>https://t.me/oswapcc</ref><br />
<br />
'''P2P INSURANCE:''' Insurance against a negative event provided by another peer instead of a faceless company. An example is flight delays insurance.<ref>https://medium.com/byteball/making-p2p-great-again-episode-iv-p2p-insurance-cbbd1e59d527</ref><br />
<br />
'''PAIR:''' To link with another Obyte device, either remote or face-to-face, use a pairing code generated by either device. In your wallet, '''Chat > add a new device > invite the other device''' OR '''Chat > add a new device > accept invitation'''. The code can then be sent by pasting it into a non-platform messaging app, or by QR code.<br />
<br />
'''PARENTS:''' (In explorer) Children and parents are pointers to later and earlier units in the DAG (see the arrows between units).<br />
<br />
'''PLATFORM:''' (1) Generally, refers to the entire Obyte protocol, as in "You can easily create new custom assets that will run on the platform." (2) An instance of the Obyte platform software installed on one of your devices, sometimes called a ''wallet''. But that name is confusing as this platform instance can contain many wallets, for example a Single-Address Wallet, a Small Expenses Wallet, a Savings Wallet, etc. A full platform/wallet downloads the whole Obyte database, a light platform/wallet doesn't. See wiki article [[Node]] for different roles, and [[Wallet]] for many more details.<br />
<br />
'''POLL:''' See VOTE. Also marketing [[polls]] via Twitter etc, in usual meaning of the word.<br />
<br />
'''PREDICTION MARKETS:''' Prediction markets are (usually) exchange-traded markets created for the purpose of trading the outcome of events. The purpose of the Slack<ref>https://obyte.slack.com</ref> #prediction_markets channel was "Finding a counterpart for bets on future events". See wiki article [[Trading prediction markets]].<br />
<br />
'''PROSAIC CONTRACT:''' See the wiki [[Prosaic contract]] article. Compare SMART CONTRACT<br />
<br />
'''REAL NAME ATTESTATION:''' See IDENTITY VERIFICATION<br />
<br />
'''RECOVER:''' Recovery is available in single-sig (i.e., not multi-sig) light platforms from version 1.10.1, and full platforms too. Note that blackbytes are not included. Also see RESTORE<br />
<br />
'''REFERRAL:''' A [[referral]] is getting a second person to install the Obyte wallet on his own device (smartphone or computer) and doing an attestation from that device/wallet, using Bytes received from the first person.<br />
<br />
'''REGULATED ASSETS:''' Regulated institutions can issue assets that are compatible with KYC/AML requirements. Every transfer of such asset is to be cosigned by the issuer, and if there is anything that contradicts the regulations, the issuer won't cosign.<ref>https://obyte.org front page, other features</ref><br />
<br />
'''RELAY:''' This is a node for the Obyte network that stores the entire database and forwards new storage units to peers. The relay does not hold any private keys and cannot send payments itself.<ref>https://github.com/byteball/byteball-relay readme.md</ref> See wiki article [[Node]] for different roles.<br />
<br />
'''RESTORE:''' To restore from a full backup. This also includes private assets. Works with any wallet type. Also see RECOVER<br />
<br />
'''SINGLE-ADDRESS WALLET:''' These wallets have only one payment address and the change always returns to the same address, supporting applications that require a stable identity. For example, you can run a manual oracle right from your wallet without having to run a node on a server. This allows you to run a PREDICTION MARKET for a future event, enabling users to make contracts (bets) referencing your payment address as an oracle, and when the outcome of the event is known you post its result from your wallet. See the wiki [[Wallet]] article.<br />
<br />
'''SMART CONTRACT/WALLET:''' See the wiki [[Smart contract]] article. See CONDITIONAL PAYMENTS. Compare PROSAIC CONTRACT <br />
<br />
'''SMART VOUCHER:''' A coupon to fund IDENTITY VERIFICATION / REAL NAME ATTESTATION for new users. See the wiki [Smart Voucher]] article.<br />
<br />
'''STABLE:''' See CONFIRMED<br />
<br />
'''STORAGE UNIT:''' Obyte 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]. <ref>https://obyte.org/Byteball.pdf</ref><br />
<br />
'''TANGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Tangos]] article.<br />
<br />
'''TEXTCOIN:''' Sending Obyte funds from one's wallet through a text app, such as an email, Telegram, WhatsApp etc. See the wiki [[Textcoin]] article. <br />
<br />
'''TINGOS:''' A Obyte fun-coin created in January 2018. See the wiki [[Tingos]] article.<br />
<br />
'''TRANSACTION FEE:''' The fee you pay is identical to the size of the data you want stored. So a storage unit that takes up 18,000 bytes in the distributed Obyte database will cost 18,000 (white)Bytes to send there. Currently a usual transaction fee is maybe 500 Bytes, with a blackbytes fee being maybe 1000 Bytes or so. If 1GB = $750, then 1MB = $0.75, and 1KB (1000 bytes) = $0.00075. So that's less than 1/10 cent US.<br />
<br />
'''TRANSITION BOT:''' After installing the wallet, one chatted with the Transition Bot to participate in the next distribution round. See the wiki article [[Airdrop]].<br />
<br />
'''UNIT:''' (In explorer) Unit is hash of data unit, similar to bitcoin transaction ID, but a unit can have more than just a transaction.<br />
<br />
'''VOTE:''' (In platform [[chatbot|Poll bot]]) A vote is a small transaction that pays to yourself and is signed by your most funded addresses; the weight of the vote is the combined balance of the signing addresses. Note that there is a privacy concern because by making a vote you associate a number of your addresses. <br />
<br />
'''WALLET:''' The Obyte PLATFORM software a regular user downloads/installs comes with a default SINGLE-ADDRESS WALLET, but you can create as many more wallets as you wish. See wiki article [[wallet]] for many more wallet details, and other wiki articles for what you can do with the platform and wallets you create.<br />
<br />
'''WITNESS:''' A witness is a highly reputable user with a real-world identity, who stamps 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. This list varies very little from transaction to transaction. If 11 witnesses say no to a bad transaction and 1 says yes, that witness gets deemed unreliable and effectively fired. It would be unthinkable for all 12 to collude and allow a fraudulent transaction through. In this way the network is safeguarded.<ref>https://obyte.org/Byteball.pdf</ref><br />
<br />
'''ZANGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Zangos]] article.<br />
<br />
'''ZINGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Zingos]] article.<br />
<br />
'''ZWIB:''' The first Obyte new asset/token traded on Slack. The name comes from the unit address, *ZW1b...* <br />
<br />
==External links==<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Glossary&diff=1540Glossary2020-02-17T16:45:20Z<p>Slackjore: added OSwap (Chinese one)</p>
<hr />
<div>Obyte terms, not too technical, but assuming some familiarity with cryptocurrencies <br />
<br />
==Entries==<br />
'''ADDRESS:''' (Disambiguation) <br />
<br />
* A device address is all upper case, starts with 0, looks like 0VCPO8MYDRN2E6N5JDRHRLTVEVZSZYARM<br />
<br />
* A payment address in a wallet is all upper case, looks like K7RMH5EFPZW67JTS5B5GA6PDZA4MYX4LY<br />
<br />
* A wallet ID looks like lNeHNjLs3u38SJ9dPb+SUZ+aZX3a7RWI1osYJH9QHRw=<br />
<br />
* A unit address, like a transaction you sent, looks like Ip241kkFRkZnaVF61Z6+/JW3YELOaHn9C6PAjeMp8fs= <br />
<br />
* A bitcoin address looks like 13AM4VW2dhxYgXeQepoHkHSQuy6NgaEb94, may also start with "3" or "bc1".<br />
<br />
'''AIR-DROP:''' The final snapshot for distribution of new bytes to payment addresses linked to proven BTC balances occurred on 4 November 2017 at 05:23 UTC. <br />
<br />
* For each 1 BTC linked --> 6.25MB (0.00625GB) <br />
<br />
* For each 1 BTC linked --> 2.1111 x 6.25 million blackbytes (money supply of blackbytes is 2.1111 times as much as that of bytes)<br />
<br />
* For every 10 (white)bytes on any address --> 1 new (white)byte<br />
<br />
* For every 10 (white)bytes on a '''linked''' address --> 2.1111 new blackbytes.<br />
<br />
See wiki [[Airdrop]] article.<br />
<br />
'''ASSET:''' Users can issue new assets and define rules that govern their transferability. For example: ICOs, shares, bonds, fiat-pegged coins, loyalty points, minutes of airtime, assets in online games, whatever you can imagine. You can do this in Obyte right now. See wiki article [[Asset]] for instructions<br />
<br />
'''ATOMIC EXCHANGE:''' When two parties sign a single unit that executes both legs of the exchange, the two transactions either happen simultaneously or don't happen at all. It is no longer necessary to trust any centralized exchanges. Note this uses a definition of "atomic" related to databases, and has nothing to do with the usual "extremely small" senses.<ref>https://obyte.org Front page, other features</ref><br />
<br />
'''ATTESTOR:''' The attestor who attests the email addresses through the [[Chatbot#Email_attestation_bot|Email attestation bot]] is <code>H5EZTQE7ABFH27AUDTQFMZIALANK6RBG</code>, and it is also a WITNESS. The attestor is trusted to post only true Obyte-address-to-email-address links to the DAG.<ref>https://medium.com/byteball/distribution-to-verified-emails-and-sending-cryptocurrency-to-email-episode-ii-cb955fe19d7e</ref><br />
<br />
'''AUTHOR:''' (In explorer) Authors are payment addresses that signed the transaction, similar to bitcoin sending address.<br />
<br />
'''AUTONOMOUS AGENT:''' An [[Autonomous Agent]] (AA) is a special address (account) on the ledger that acts according to a program associated with it. Its behavior is similar to that of a vending machine that receives coins and data entered on a keypad and in response, releases a cup of coffee, plays a song, or does whatever it was programmed to do.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
'''BBIP:''' Byteball Improvement Proposal. Replaced by OIP.<br />
<br />
'''BIND:''' See CONDITIONAL PAYMENTS<br />
<br />
'''BLACKBYTE:''' One of the two native Obyte currencies (also see BYTE). When you want complete privacy pay in blackbytes, a cash-like untraceable currency whose transactions are not visible on the public database. They are sent peer-to-peer instead.<ref>https://obyte.org Front page</ref>. With wallet version 2.3 they can be sent by digital file to someone not in Obyte yet.<ref>https://medium.com/byteball/private-textcoins-6a2288d80757</ref><br />
<br />
'''BOT:''' See CHATBOT<br />
<br />
'''BOT STORE:''' The section in the Obyte platform, available from the CHAT tab, that contains about 20 bots you can add to your contacts.<br />
<br />
'''BYTE:''' One of the two native currencies of the Obyte network (also see BLACKBYTE). It is also a basic general computing term: *A sequence of adjacent bits, usually eight, operated on as a unit, e.g. 0 1 0 1 1 1 0 1. One byte can store one character, e.g. 'A' or 'x' or '$'.* There are 10^15 total Bytes in the system. The unit traded on exchanges is the "GByte", 10^9 Bytes.<br />
<br />
'''BYTEBALL (NAME):''' (1) Once a unit is broadcast into the network, and other users start building their units on top of it (referencing it as parent), the number of secondary revisions required to edit this unit hence grows like a snowball. That’s why we call this design '''Byteball''' (our snowflakes are bytes of data).<ref>https://obyte.org/Byteball.pdf p.5</ref> [Rebranded to ''Obyte'' on 17 Jan 2019]<br />
<br />
(2) ''Byteball'' (upper-case "B") was the name of the platform, the protocol; ''byteball'' (lower-case "b") was sometimes (mis)used very loosely to represent the currency, as in "Hey, I see a byteball [1 GB] is now worth $250!" or "Use blackbytes for private transactions and byteballs for the open ones".<br />
<br />
'''BYTEROLL:''' The original Byteball wiki was hosted at byteroll.com on @portabella's private server. The Byteball wiki subdomain forwarded to Byteroll.<br />
<br />
'''CASHBACK:''' We want to get this coin into the hands of as many people as possible. In addition to the regular monthly airdrop, we are going to partner with several categories of companies, like merchants, payment processors, and "Bitcoin debit card" companies. We will offer 10% [[cashback]], paid in Bytes, for all qualifying purchases (no matter how the purchases are paid). <br />
<br />
'''CHAT:''' The platform incorporates a chat function, allowing the user to exchange end-to-end-encrypted messages using AES with a peer or bot when their devices are paired. It's end-to-end encrypted using AES. The hubs only forward the encrypted messages; they can't see anything. To deliver your message, your platform connects to the recipient's hub (if it's different from your home hub).<ref>https://bitcointalk.org/index.php?topic=1608859.msg21798347#msg21798347</ref><br />
<br />
'''CHATBOT:''' You can pair your platform with a bot, which emulates the experience of chatting with a live person. The bot will have very limited responses, but enough to get the job done. A merchant bot could allow you to select from a range of pizzas, for example, then pay for your order with two clicks while still in that chat session. See the wiki [[Chatbot]] article for a list.<br />
<br />
'''CHILDREN:''' (In explorer) Children and parents are pointers to later and earlier units in the DAG (see the arrows between units).<br />
<br />
'''CONDITIONAL PAYMENTS:''' This is the '''killer feature''' of Obyte, and the "smart payments" in the [[slogan]]. You can choose to bind a payment to a condition. If/when that condition is satisfied the payment is unlocked and only the recipient can collect it. If the condition fails the payment can only be collected by the issuer. See the wiki [[Trading blackbytes]] article for an example.<br />
<br />
'''CONFIRMED:''' An Obyte payment is confirmed/stable once it has become sufficiently buried by later transactions to be unalterable, similar to confirmations on a blockchain. It usually takes about five minutes.<br />
<br />
'''DAG:''' [[Directed_acyclic_graph]], the radically-different immutable data structure used in the Obyte platform instead of the usual cryptocurrency blockchain. No mining, no proof-of-work, no proof-of-stake.<ref>https://obyte.org/Byteball.pdf White paper</ref><br />
<br />
'''DATAFEED:''' A line item posted into the DAG by an oracle. The data is of the form [Datafeed name] then [Datafeed value], for example <code>BTC_USD: 6788.0</code>.<br />
<br />
'''DISTRIBUTION:''' See AIRDROP. For current campaigns to give away undistributed bytes, see https://obyte.org/#dist.<br />
<br />
'''DOUBLE-SPEND:''' In case of doublespend, the version that comes earlier on the main chain wins. Therefore, if your node is well-connected and you see a few other transactions piling up on top of the new unconfirmed transaction, and the time since its arrival is significantly larger than the typical network latency, then you can be reasonably sure that even if a doublespend appears later it will be sorted later, hence voided.<br />
<br />
'''DRAW:''' A weekly random airdrop to existing bytes holders, started Dec 8, 2018.<ref>https://medium.com/obyte/weekly-draw-for-the-byteball-community-f464ae731c88</ref> As a distribution method it was superseded July 18, 2019 by the Autonomous Agent developer contest.<ref>https://medium.com/obyte/distribution-outlook-bb28ff0b91aa</ref><br />
<br />
'''FREE UNIT:''' A unit that has no children.<br />
<br />
'''FULLY FUNDED:''' The state of a SMART CONTRACT when the agreed payments from both parties have been locked in the contract until certain conditions are satisfied. See the wiki [[Smart contract]] article.<br />
<br />
'''FUN-COIN:''' A freely-available token on the Obyte platform having zero monetary value, intended for practice with various features like textcoin and smart contracts. See the wiki [[fun-coins]] article.<br />
<br />
'''GENESIS UNIT:''' The Obyte analog to Bitcoin's genesis block, including the creation of the entire global supply of its native currencies: 1,000,000 GBytes and 2,111,100 GBBytes. <br />
<br />
'''GRANTS:''' Obyte Grants Program. We’ll pay for work that improves the ecosystem. We want the contributors to both come up with new ideas and realize them.<ref>https://medium.com/byteball/byteball-grants-program-906a71b93d3c)</ref><br />
<br />
'''HUB:''' This is a node for the Obyte network that serves as a relay, plus it facilitates the exchange of end-to-end encrypted messages among devices connected to the Obyte network. The hub does not hold any private keys and cannot send payments itself, nor can it read the messages. Users set their hub address in their wallet settings. The default hub is wss://obyte.org/bb but users can change it.<ref>https://github.com/byteball/byteball-hub) Github readme.md</ref> See wiki [[Hub]] article.<br />
<br />
'''ICO:''' An '''initial coin offering''' is a controversial means of crowdfunding centered around cryptocurrency, which can be a source of capital for startup companies. In an ICO, a quantity of the crowdfunded cryptocurrency is preallocated to investors in the form of "tokens", in exchange for legal tender or other cryptocurrencies such as bitcoin or ethereum. These tokens supposedly become functional units of currency if or when the ICO's funding goal is met and the project launches.<ref>https://en.wikipedia.org/wiki/Initial_coin_offering</ref> Obyte has an ICO bot, and anyone can issue tokens on the platform.<br />
<br />
'''IDENTITY VERIFICATION:''' Proving one's real-world identity with government-issued documentation using the [[Chatbot#Real_name_attestation_bot|REAL NAME ATTESTATION bot]], but after this one can verify age or country of origin without disclosing further identifying information. Same as REAL NAME ATTESTATION<br />
<br />
'''LINKED:''' Concerning airdrops, it refers to (white)bytes at one of your wallet addresses linked to bitcoins, where the link has been verified by the transition bot. All such pairs were visible on the transition pages<ref>https://transition.byteball.org</ref>.<br />
<br />
'''MOVED:''' In a wallet history, shows funds moving from one address in your wallet to a different address in the same wallet. Either you deliberately sent them there, or they moved as change. See wiki article [[Change address]].<br />
<br />
'''MULTI SIGNATURE:''' For security, you can require that your funds be spendable only when several signatures are provided, e.g. from your laptop and from your phone. For shared control of funds, signatures from different people may be required.<ref>https://obyte.org front page, other features</ref><br />
<br />
'''NODE:''' Imagine a fishing net: the nodes would be the knots holding the lines of rope together. Every device in the Obyte network is technically a node, whether a light client/platform, a full platform, a relay or a hub. Informally, node is used to mean full platform. See wiki article [[Node]] for different roles.<br />
<br />
'''O:''' [Tony:] O in Obyte stands for Open. When we renamed, many people wondered what O stands for. While it is true that it replaces the former "ball", I also want to make it clear that O stands for Open. It speaks about the core values of the platform: open access to the ledger, not encumbered by miners or other intermediaries, which simply do not exist here in a DAG. We are going to have more O-names for the products built on top of the platform.<ref>https://www.reddit.com/r/obyte/comments/aioub3/o_in_obyte_stands_for_open</ref><br />
<br />
'''OBBY CHAT:''' Instant mobile-only messaging app for Obyte. Offering secure end-to-end encryption, cryptocurrency payments, and smart contracts.<ref>https://obby.chat/</ref> Being built by BindCreative from a grant application<ref>https://drive.google.com/file/d/1KWlwbFO1QU-IER_kgRjOf4UDLwEp0a0n/view</ref> approved July 2019.<br />
<br />
'''OBYTE COMMUNITY FUND:''' The [[Obyte_community_fund|Obyte Community Fund]]'s goal is to support and encourage the Obyte crypto platform. Fundraising is done by voluntary donations from investors, stakeholders and enthusiasts. <br />
<br />
'''ODEX:''' DEX is a Decentralized Exchanged. [[ODEX]] is Obyte's DEX.<br />
<br />
'''OIP:''' Obyte Improvement Proposal. Based on the Bitcoin BIP system. See [[OIP]] wiki article.<br />
<br />
'''ORACLE:''' A trusted third party that monitors specific external events and registers selected data-feed items to the Obyte database. An example is a list of cryptocurrency exchange rates updated every ten minutes. When dealing with untrusted counterparties, you can lock the funds on a payment address that is spendable either by you or by the counterparty, depending on the oracle's data collection and registration.<ref>https://obyte.org front page, other features</ref> See wiki article [[Oracle]].<br />
<br />
'''OSCRIPT:''' AUTONOMOUS AGENTS are written in Oscript — a new programming language developed specifically for this purpose.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
'''OSWAP:''' [Chinese] One-click exchange platform for hundreds of crypto assets.<ref>https://www.oswap.cc/#/</ref> OSwap is funded by the Obyte Foundation to facilitate purchase of bytes by the Chinese community.<br />
<br />
'''P2P INSURANCE:''' Insurance against a negative event provided by another peer instead of a faceless company. An example is flight delays insurance.<ref>https://medium.com/byteball/making-p2p-great-again-episode-iv-p2p-insurance-cbbd1e59d527</ref><br />
<br />
'''PAIR:''' To link with another Obyte device, either remote or face-to-face, use a pairing code generated by either device. In your wallet, '''Chat > add a new device > invite the other device''' OR '''Chat > add a new device > accept invitation'''. The code can then be sent by pasting it into a non-platform messaging app, or by QR code.<br />
<br />
'''PARENTS:''' (In explorer) Children and parents are pointers to later and earlier units in the DAG (see the arrows between units).<br />
<br />
'''PLATFORM:''' (1) Generally, refers to the entire Obyte protocol, as in "You can easily create new custom assets that will run on the platform." (2) An instance of the Obyte platform software installed on one of your devices, sometimes called a ''wallet''. But that name is confusing as this platform instance can contain many wallets, for example a Single-Address Wallet, a Small Expenses Wallet, a Savings Wallet, etc. A full platform/wallet downloads the whole Obyte database, a light platform/wallet doesn't. See wiki article [[Node]] for different roles, and [[Wallet]] for many more details.<br />
<br />
'''POLL:''' See VOTE. Also marketing [[polls]] via Twitter etc, in usual meaning of the word.<br />
<br />
'''PREDICTION MARKETS:''' Prediction markets are (usually) exchange-traded markets created for the purpose of trading the outcome of events. The purpose of the Slack<ref>https://obyte.slack.com</ref> #prediction_markets channel was "Finding a counterpart for bets on future events". See wiki article [[Trading prediction markets]].<br />
<br />
'''PROSAIC CONTRACT:''' See the wiki [[Prosaic contract]] article. Compare SMART CONTRACT<br />
<br />
'''REAL NAME ATTESTATION:''' See IDENTITY VERIFICATION<br />
<br />
'''RECOVER:''' Recovery is available in single-sig (i.e., not multi-sig) light platforms from version 1.10.1, and full platforms too. Note that blackbytes are not included. Also see RESTORE<br />
<br />
'''REFERRAL:''' A [[referral]] is getting a second person to install the Obyte wallet on his own device (smartphone or computer) and doing an attestation from that device/wallet, using Bytes received from the first person.<br />
<br />
'''REGULATED ASSETS:''' Regulated institutions can issue assets that are compatible with KYC/AML requirements. Every transfer of such asset is to be cosigned by the issuer, and if there is anything that contradicts the regulations, the issuer won't cosign.<ref>https://obyte.org front page, other features</ref><br />
<br />
'''RELAY:''' This is a node for the Obyte network that stores the entire database and forwards new storage units to peers. The relay does not hold any private keys and cannot send payments itself.<ref>https://github.com/byteball/byteball-relay readme.md</ref> See wiki article [[Node]] for different roles.<br />
<br />
'''RESTORE:''' To restore from a full backup. This also includes private assets. Works with any wallet type. Also see RECOVER<br />
<br />
'''SINGLE-ADDRESS WALLET:''' These wallets have only one payment address and the change always returns to the same address, supporting applications that require a stable identity. For example, you can run a manual oracle right from your wallet without having to run a node on a server. This allows you to run a PREDICTION MARKET for a future event, enabling users to make contracts (bets) referencing your payment address as an oracle, and when the outcome of the event is known you post its result from your wallet. See the wiki [[Wallet]] article.<br />
<br />
'''SMART CONTRACT/WALLET:''' See the wiki [[Smart contract]] article. See CONDITIONAL PAYMENTS. Compare PROSAIC CONTRACT <br />
<br />
'''SMART VOUCHER:''' A coupon to fund IDENTITY VERIFICATION / REAL NAME ATTESTATION for new users. See the wiki [Smart Voucher]] article.<br />
<br />
'''STABLE:''' See CONFIRMED<br />
<br />
'''STORAGE UNIT:''' Obyte 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]. <ref>https://obyte.org/Byteball.pdf</ref><br />
<br />
'''TANGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Tangos]] article.<br />
<br />
'''TEXTCOIN:''' Sending Obyte funds from one's wallet through a text app, such as an email, Telegram, WhatsApp etc. See the wiki [[Textcoin]] article. <br />
<br />
'''TINGOS:''' A Obyte fun-coin created in January 2018. See the wiki [[Tingos]] article.<br />
<br />
'''TRANSACTION FEE:''' The fee you pay is identical to the size of the data you want stored. So a storage unit that takes up 18,000 bytes in the distributed Obyte database will cost 18,000 (white)Bytes to send there. Currently a usual transaction fee is maybe 500 Bytes, with a blackbytes fee being maybe 1000 Bytes or so. If 1GB = $750, then 1MB = $0.75, and 1KB (1000 bytes) = $0.00075. So that's less than 1/10 cent US.<br />
<br />
'''TRANSITION BOT:''' After installing the wallet, one chatted with the Transition Bot to participate in the next distribution round. See the wiki article [[Airdrop]].<br />
<br />
'''UNIT:''' (In explorer) Unit is hash of data unit, similar to bitcoin transaction ID, but a unit can have more than just a transaction.<br />
<br />
'''VOTE:''' (In platform [[chatbot|Poll bot]]) A vote is a small transaction that pays to yourself and is signed by your most funded addresses; the weight of the vote is the combined balance of the signing addresses. Note that there is a privacy concern because by making a vote you associate a number of your addresses. <br />
<br />
'''WALLET:''' The Obyte PLATFORM software a regular user downloads/installs comes with a default SINGLE-ADDRESS WALLET, but you can create as many more wallets as you wish. See wiki article [[wallet]] for many more wallet details, and other wiki articles for what you can do with the platform and wallets you create.<br />
<br />
'''WITNESS:''' A witness is a highly reputable user with a real-world identity, who stamps 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. This list varies very little from transaction to transaction. If 11 witnesses say no to a bad transaction and 1 says yes, that witness gets deemed unreliable and effectively fired. It would be unthinkable for all 12 to collude and allow a fraudulent transaction through. In this way the network is safeguarded.<ref>https://obyte.org/Byteball.pdf</ref><br />
<br />
'''ZANGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Zangos]] article.<br />
<br />
'''ZINGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Zingos]] article.<br />
<br />
'''ZWIB:''' The first Obyte new asset/token traded on Slack. The name comes from the unit address, *ZW1b...* <br />
<br />
==External links==<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Glossary&diff=1539Glossary2020-02-16T10:07:26Z<p>Slackjore: added OBBY CHAT</p>
<hr />
<div>Obyte terms, not too technical, but assuming some familiarity with cryptocurrencies <br />
<br />
==Entries==<br />
'''ADDRESS:''' (Disambiguation) <br />
<br />
* A device address is all upper case, starts with 0, looks like 0VCPO8MYDRN2E6N5JDRHRLTVEVZSZYARM<br />
<br />
* A payment address in a wallet is all upper case, looks like K7RMH5EFPZW67JTS5B5GA6PDZA4MYX4LY<br />
<br />
* A wallet ID looks like lNeHNjLs3u38SJ9dPb+SUZ+aZX3a7RWI1osYJH9QHRw=<br />
<br />
* A unit address, like a transaction you sent, looks like Ip241kkFRkZnaVF61Z6+/JW3YELOaHn9C6PAjeMp8fs= <br />
<br />
* A bitcoin address looks like 13AM4VW2dhxYgXeQepoHkHSQuy6NgaEb94, may also start with "3" or "bc1".<br />
<br />
'''AIR-DROP:''' The final snapshot for distribution of new bytes to payment addresses linked to proven BTC balances occurred on 4 November 2017 at 05:23 UTC. <br />
<br />
* For each 1 BTC linked --> 6.25MB (0.00625GB) <br />
<br />
* For each 1 BTC linked --> 2.1111 x 6.25 million blackbytes (money supply of blackbytes is 2.1111 times as much as that of bytes)<br />
<br />
* For every 10 (white)bytes on any address --> 1 new (white)byte<br />
<br />
* For every 10 (white)bytes on a '''linked''' address --> 2.1111 new blackbytes.<br />
<br />
See wiki [[Airdrop]] article.<br />
<br />
'''ASSET:''' Users can issue new assets and define rules that govern their transferability. For example: ICOs, shares, bonds, fiat-pegged coins, loyalty points, minutes of airtime, assets in online games, whatever you can imagine. You can do this in Obyte right now. See wiki article [[Asset]] for instructions<br />
<br />
'''ATOMIC EXCHANGE:''' When two parties sign a single unit that executes both legs of the exchange, the two transactions either happen simultaneously or don't happen at all. It is no longer necessary to trust any centralized exchanges. Note this uses a definition of "atomic" related to databases, and has nothing to do with the usual "extremely small" senses.<ref>https://obyte.org Front page, other features</ref><br />
<br />
'''ATTESTOR:''' The attestor who attests the email addresses through the [[Chatbot#Email_attestation_bot|Email attestation bot]] is <code>H5EZTQE7ABFH27AUDTQFMZIALANK6RBG</code>, and it is also a WITNESS. The attestor is trusted to post only true Obyte-address-to-email-address links to the DAG.<ref>https://medium.com/byteball/distribution-to-verified-emails-and-sending-cryptocurrency-to-email-episode-ii-cb955fe19d7e</ref><br />
<br />
'''AUTHOR:''' (In explorer) Authors are payment addresses that signed the transaction, similar to bitcoin sending address.<br />
<br />
'''AUTONOMOUS AGENT:''' An [[Autonomous Agent]] (AA) is a special address (account) on the ledger that acts according to a program associated with it. Its behavior is similar to that of a vending machine that receives coins and data entered on a keypad and in response, releases a cup of coffee, plays a song, or does whatever it was programmed to do.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
'''BBIP:''' Byteball Improvement Proposal. Replaced by OIP.<br />
<br />
'''BIND:''' See CONDITIONAL PAYMENTS<br />
<br />
'''BLACKBYTE:''' One of the two native Obyte currencies (also see BYTE). When you want complete privacy pay in blackbytes, a cash-like untraceable currency whose transactions are not visible on the public database. They are sent peer-to-peer instead.<ref>https://obyte.org Front page</ref>. With wallet version 2.3 they can be sent by digital file to someone not in Obyte yet.<ref>https://medium.com/byteball/private-textcoins-6a2288d80757</ref><br />
<br />
'''BOT:''' See CHATBOT<br />
<br />
'''BOT STORE:''' The section in the Obyte platform, available from the CHAT tab, that contains about 20 bots you can add to your contacts.<br />
<br />
'''BYTE:''' One of the two native currencies of the Obyte network (also see BLACKBYTE). It is also a basic general computing term: *A sequence of adjacent bits, usually eight, operated on as a unit, e.g. 0 1 0 1 1 1 0 1. One byte can store one character, e.g. 'A' or 'x' or '$'.* There are 10^15 total Bytes in the system. The unit traded on exchanges is the "GByte", 10^9 Bytes.<br />
<br />
'''BYTEBALL (NAME):''' (1) Once a unit is broadcast into the network, and other users start building their units on top of it (referencing it as parent), the number of secondary revisions required to edit this unit hence grows like a snowball. That’s why we call this design '''Byteball''' (our snowflakes are bytes of data).<ref>https://obyte.org/Byteball.pdf p.5</ref> [Rebranded to ''Obyte'' on 17 Jan 2019]<br />
<br />
(2) ''Byteball'' (upper-case "B") was the name of the platform, the protocol; ''byteball'' (lower-case "b") was sometimes (mis)used very loosely to represent the currency, as in "Hey, I see a byteball [1 GB] is now worth $250!" or "Use blackbytes for private transactions and byteballs for the open ones".<br />
<br />
'''BYTEROLL:''' The original Byteball wiki was hosted at byteroll.com on @portabella's private server. The Byteball wiki subdomain forwarded to Byteroll.<br />
<br />
'''CASHBACK:''' We want to get this coin into the hands of as many people as possible. In addition to the regular monthly airdrop, we are going to partner with several categories of companies, like merchants, payment processors, and "Bitcoin debit card" companies. We will offer 10% [[cashback]], paid in Bytes, for all qualifying purchases (no matter how the purchases are paid). <br />
<br />
'''CHAT:''' The platform incorporates a chat function, allowing the user to exchange end-to-end-encrypted messages using AES with a peer or bot when their devices are paired. It's end-to-end encrypted using AES. The hubs only forward the encrypted messages; they can't see anything. To deliver your message, your platform connects to the recipient's hub (if it's different from your home hub).<ref>https://bitcointalk.org/index.php?topic=1608859.msg21798347#msg21798347</ref><br />
<br />
'''CHATBOT:''' You can pair your platform with a bot, which emulates the experience of chatting with a live person. The bot will have very limited responses, but enough to get the job done. A merchant bot could allow you to select from a range of pizzas, for example, then pay for your order with two clicks while still in that chat session. See the wiki [[Chatbot]] article for a list.<br />
<br />
'''CHILDREN:''' (In explorer) Children and parents are pointers to later and earlier units in the DAG (see the arrows between units).<br />
<br />
'''CONDITIONAL PAYMENTS:''' This is the '''killer feature''' of Obyte, and the "smart payments" in the [[slogan]]. You can choose to bind a payment to a condition. If/when that condition is satisfied the payment is unlocked and only the recipient can collect it. If the condition fails the payment can only be collected by the issuer. See the wiki [[Trading blackbytes]] article for an example.<br />
<br />
'''CONFIRMED:''' An Obyte payment is confirmed/stable once it has become sufficiently buried by later transactions to be unalterable, similar to confirmations on a blockchain. It usually takes about five minutes.<br />
<br />
'''DAG:''' [[Directed_acyclic_graph]], the radically-different immutable data structure used in the Obyte platform instead of the usual cryptocurrency blockchain. No mining, no proof-of-work, no proof-of-stake.<ref>https://obyte.org/Byteball.pdf White paper</ref><br />
<br />
'''DATAFEED:''' A line item posted into the DAG by an oracle. The data is of the form [Datafeed name] then [Datafeed value], for example <code>BTC_USD: 6788.0</code>.<br />
<br />
'''DISTRIBUTION:''' See AIRDROP. For current campaigns to give away undistributed bytes, see https://obyte.org/#dist.<br />
<br />
'''DOUBLE-SPEND:''' In case of doublespend, the version that comes earlier on the main chain wins. Therefore, if your node is well-connected and you see a few other transactions piling up on top of the new unconfirmed transaction, and the time since its arrival is significantly larger than the typical network latency, then you can be reasonably sure that even if a doublespend appears later it will be sorted later, hence voided.<br />
<br />
'''DRAW:''' A weekly random airdrop to existing bytes holders, started Dec 8, 2018.<ref>https://medium.com/obyte/weekly-draw-for-the-byteball-community-f464ae731c88</ref> As a distribution method it was superseded July 18, 2019 by the Autonomous Agent developer contest.<ref>https://medium.com/obyte/distribution-outlook-bb28ff0b91aa</ref><br />
<br />
'''FREE UNIT:''' A unit that has no children.<br />
<br />
'''FULLY FUNDED:''' The state of a SMART CONTRACT when the agreed payments from both parties have been locked in the contract until certain conditions are satisfied. See the wiki [[Smart contract]] article.<br />
<br />
'''FUN-COIN:''' A freely-available token on the Obyte platform having zero monetary value, intended for practice with various features like textcoin and smart contracts. See the wiki [[fun-coins]] article.<br />
<br />
'''GENESIS UNIT:''' The Obyte analog to Bitcoin's genesis block, including the creation of the entire global supply of its native currencies: 1,000,000 GBytes and 2,111,100 GBBytes. <br />
<br />
'''GRANTS:''' Obyte Grants Program. We’ll pay for work that improves the ecosystem. We want the contributors to both come up with new ideas and realize them.<ref>https://medium.com/byteball/byteball-grants-program-906a71b93d3c)</ref><br />
<br />
'''HUB:''' This is a node for the Obyte network that serves as a relay, plus it facilitates the exchange of end-to-end encrypted messages among devices connected to the Obyte network. The hub does not hold any private keys and cannot send payments itself, nor can it read the messages. Users set their hub address in their wallet settings. The default hub is wss://obyte.org/bb but users can change it.<ref>https://github.com/byteball/byteball-hub) Github readme.md</ref> See wiki [[Hub]] article.<br />
<br />
'''ICO:''' An '''initial coin offering''' is a controversial means of crowdfunding centered around cryptocurrency, which can be a source of capital for startup companies. In an ICO, a quantity of the crowdfunded cryptocurrency is preallocated to investors in the form of "tokens", in exchange for legal tender or other cryptocurrencies such as bitcoin or ethereum. These tokens supposedly become functional units of currency if or when the ICO's funding goal is met and the project launches.<ref>https://en.wikipedia.org/wiki/Initial_coin_offering</ref> Obyte has an ICO bot, and anyone can issue tokens on the platform.<br />
<br />
'''IDENTITY VERIFICATION:''' Proving one's real-world identity with government-issued documentation using the [[Chatbot#Real_name_attestation_bot|REAL NAME ATTESTATION bot]], but after this one can verify age or country of origin without disclosing further identifying information. Same as REAL NAME ATTESTATION<br />
<br />
'''LINKED:''' Concerning airdrops, it refers to (white)bytes at one of your wallet addresses linked to bitcoins, where the link has been verified by the transition bot. All such pairs were visible on the transition pages<ref>https://transition.byteball.org</ref>.<br />
<br />
'''MOVED:''' In a wallet history, shows funds moving from one address in your wallet to a different address in the same wallet. Either you deliberately sent them there, or they moved as change. See wiki article [[Change address]].<br />
<br />
'''MULTI SIGNATURE:''' For security, you can require that your funds be spendable only when several signatures are provided, e.g. from your laptop and from your phone. For shared control of funds, signatures from different people may be required.<ref>https://obyte.org front page, other features</ref><br />
<br />
'''NODE:''' Imagine a fishing net: the nodes would be the knots holding the lines of rope together. Every device in the Obyte network is technically a node, whether a light client/platform, a full platform, a relay or a hub. Informally, node is used to mean full platform. See wiki article [[Node]] for different roles.<br />
<br />
'''O:''' [Tony:] O in Obyte stands for Open. When we renamed, many people wondered what O stands for. While it is true that it replaces the former "ball", I also want to make it clear that O stands for Open. It speaks about the core values of the platform: open access to the ledger, not encumbered by miners or other intermediaries, which simply do not exist here in a DAG. We are going to have more O-names for the products built on top of the platform.<ref>https://www.reddit.com/r/obyte/comments/aioub3/o_in_obyte_stands_for_open</ref><br />
<br />
'''OBBY CHAT:''' Instant mobile-only messaging app for Obyte. Offering secure end-to-end encryption, cryptocurrency payments, and smart contracts.<ref>https://obby.chat/</ref> Being built by BindCreative from a grant application<ref>https://drive.google.com/file/d/1KWlwbFO1QU-IER_kgRjOf4UDLwEp0a0n/view</ref> approved July 2019.<br />
<br />
'''OBYTE COMMUNITY FUND:''' The [[Obyte_community_fund|Obyte Community Fund]]'s goal is to support and encourage the Obyte crypto platform. Fundraising is done by voluntary donations from investors, stakeholders and enthusiasts. <br />
<br />
'''ODEX:''' DEX is a Decentralized Exchanged. [[ODEX]] is Obyte's DEX.<br />
<br />
'''OIP:''' Obyte Improvement Proposal. Based on the Bitcoin BIP system. See [[OIP]] wiki article.<br />
<br />
'''ORACLE:''' A trusted third party that monitors specific external events and registers selected data-feed items to the Obyte database. An example is a list of cryptocurrency exchange rates updated every ten minutes. When dealing with untrusted counterparties, you can lock the funds on a payment address that is spendable either by you or by the counterparty, depending on the oracle's data collection and registration.<ref>https://obyte.org front page, other features</ref> See wiki article [[Oracle]].<br />
<br />
'''OSCRIPT:''' AUTONOMOUS AGENTS are written in Oscript — a new programming language developed specifically for this purpose.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
'''P2P INSURANCE:''' Insurance against a negative event provided by another peer instead of a faceless company. An example is flight delays insurance.<ref>https://medium.com/byteball/making-p2p-great-again-episode-iv-p2p-insurance-cbbd1e59d527</ref><br />
<br />
'''PAIR:''' To link with another Obyte device, either remote or face-to-face, use a pairing code generated by either device. In your wallet, '''Chat > add a new device > invite the other device''' OR '''Chat > add a new device > accept invitation'''. The code can then be sent by pasting it into a non-platform messaging app, or by QR code.<br />
<br />
'''PARENTS:''' (In explorer) Children and parents are pointers to later and earlier units in the DAG (see the arrows between units).<br />
<br />
'''PLATFORM:''' (1) Generally, refers to the entire Obyte protocol, as in "You can easily create new custom assets that will run on the platform." (2) An instance of the Obyte platform software installed on one of your devices, sometimes called a ''wallet''. But that name is confusing as this platform instance can contain many wallets, for example a Single-Address Wallet, a Small Expenses Wallet, a Savings Wallet, etc. A full platform/wallet downloads the whole Obyte database, a light platform/wallet doesn't. See wiki article [[Node]] for different roles, and [[Wallet]] for many more details.<br />
<br />
'''POLL:''' See VOTE. Also marketing [[polls]] via Twitter etc, in usual meaning of the word.<br />
<br />
'''PREDICTION MARKETS:''' Prediction markets are (usually) exchange-traded markets created for the purpose of trading the outcome of events. The purpose of the Slack<ref>https://obyte.slack.com</ref> #prediction_markets channel was "Finding a counterpart for bets on future events". See wiki article [[Trading prediction markets]].<br />
<br />
'''PROSAIC CONTRACT:''' See the wiki [[Prosaic contract]] article. Compare SMART CONTRACT<br />
<br />
'''REAL NAME ATTESTATION:''' See IDENTITY VERIFICATION<br />
<br />
'''RECOVER:''' Recovery is available in single-sig (i.e., not multi-sig) light platforms from version 1.10.1, and full platforms too. Note that blackbytes are not included. Also see RESTORE<br />
<br />
'''REFERRAL:''' A [[referral]] is getting a second person to install the Obyte wallet on his own device (smartphone or computer) and doing an attestation from that device/wallet, using Bytes received from the first person.<br />
<br />
'''REGULATED ASSETS:''' Regulated institutions can issue assets that are compatible with KYC/AML requirements. Every transfer of such asset is to be cosigned by the issuer, and if there is anything that contradicts the regulations, the issuer won't cosign.<ref>https://obyte.org front page, other features</ref><br />
<br />
'''RELAY:''' This is a node for the Obyte network that stores the entire database and forwards new storage units to peers. The relay does not hold any private keys and cannot send payments itself.<ref>https://github.com/byteball/byteball-relay readme.md</ref> See wiki article [[Node]] for different roles.<br />
<br />
'''RESTORE:''' To restore from a full backup. This also includes private assets. Works with any wallet type. Also see RECOVER<br />
<br />
'''SINGLE-ADDRESS WALLET:''' These wallets have only one payment address and the change always returns to the same address, supporting applications that require a stable identity. For example, you can run a manual oracle right from your wallet without having to run a node on a server. This allows you to run a PREDICTION MARKET for a future event, enabling users to make contracts (bets) referencing your payment address as an oracle, and when the outcome of the event is known you post its result from your wallet. See the wiki [[Wallet]] article.<br />
<br />
'''SMART CONTRACT/WALLET:''' See the wiki [[Smart contract]] article. See CONDITIONAL PAYMENTS. Compare PROSAIC CONTRACT <br />
<br />
'''SMART VOUCHER:''' A coupon to fund IDENTITY VERIFICATION / REAL NAME ATTESTATION for new users. See the wiki [Smart Voucher]] article.<br />
<br />
'''STABLE:''' See CONFIRMED<br />
<br />
'''STORAGE UNIT:''' Obyte 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]. <ref>https://obyte.org/Byteball.pdf</ref><br />
<br />
'''TANGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Tangos]] article.<br />
<br />
'''TEXTCOIN:''' Sending Obyte funds from one's wallet through a text app, such as an email, Telegram, WhatsApp etc. See the wiki [[Textcoin]] article. <br />
<br />
'''TINGOS:''' A Obyte fun-coin created in January 2018. See the wiki [[Tingos]] article.<br />
<br />
'''TRANSACTION FEE:''' The fee you pay is identical to the size of the data you want stored. So a storage unit that takes up 18,000 bytes in the distributed Obyte database will cost 18,000 (white)Bytes to send there. Currently a usual transaction fee is maybe 500 Bytes, with a blackbytes fee being maybe 1000 Bytes or so. If 1GB = $750, then 1MB = $0.75, and 1KB (1000 bytes) = $0.00075. So that's less than 1/10 cent US.<br />
<br />
'''TRANSITION BOT:''' After installing the wallet, one chatted with the Transition Bot to participate in the next distribution round. See the wiki article [[Airdrop]].<br />
<br />
'''UNIT:''' (In explorer) Unit is hash of data unit, similar to bitcoin transaction ID, but a unit can have more than just a transaction.<br />
<br />
'''VOTE:''' (In platform [[chatbot|Poll bot]]) A vote is a small transaction that pays to yourself and is signed by your most funded addresses; the weight of the vote is the combined balance of the signing addresses. Note that there is a privacy concern because by making a vote you associate a number of your addresses. <br />
<br />
'''WALLET:''' The Obyte PLATFORM software a regular user downloads/installs comes with a default SINGLE-ADDRESS WALLET, but you can create as many more wallets as you wish. See wiki article [[wallet]] for many more wallet details, and other wiki articles for what you can do with the platform and wallets you create.<br />
<br />
'''WITNESS:''' A witness is a highly reputable user with a real-world identity, who stamps 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. This list varies very little from transaction to transaction. If 11 witnesses say no to a bad transaction and 1 says yes, that witness gets deemed unreliable and effectively fired. It would be unthinkable for all 12 to collude and allow a fraudulent transaction through. In this way the network is safeguarded.<ref>https://obyte.org/Byteball.pdf</ref><br />
<br />
'''ZANGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Zangos]] article.<br />
<br />
'''ZINGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Zingos]] article.<br />
<br />
'''ZWIB:''' The first Obyte new asset/token traded on Slack. The name comes from the unit address, *ZW1b...* <br />
<br />
==External links==<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=ODEX&diff=1538ODEX2020-02-15T13:56:56Z<p>Slackjore: added Testnet launch date and link</p>
<hr />
<div>== Overview ==<br />
After the [[Autonomous Agent]]s are released on livenet, we’ll have a lot of tokens. Stablecoins, shares in prediction markets, synthetic assets, portfolio tokens, many others, and certainly something that we can’t even imagine today. We’ll need an easy way to trade them and ensure that access to trading is as open as possible. This is what a decentralized exchange (DEX) would provide.<br />
<br />
Autonomous Agents is an excellent tool for developing decentralized applications and while the DEX will enable trading of mostly AA-issued tokens, the DEX itself will also be AA-based.<ref>https://medium.com/obyte/whats-next-for-obyte-a-decentralized-exchange-fd7164569a9d</ref><br />
<br />
AAs and ODEX are expected to go live in January/February 2020. <br />
<br />
== Testnet launch ==<br />
ODEX launched on Testnet 14 Feb 2020: https://testnet.odex.ooo/trade<br />
<br />
== References ==<br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Textcoin&diff=1537Textcoin2020-02-11T14:59:01Z<p>Slackjore: added link to guide on making physical textcoins as handouts</p>
<hr />
<div>{{#ev:vimeo|https://vimeo.com/254898717|thumb|right}}<br />
<br />
==Sending coins by text==<br />
Source<ref>https://medium.com/byteball/sending-cryptocurrency-to-email-5c9bce22b8a9</ref><br />
<br />
With the release of wallet version 2.0, Obyte users can send Bytes by email. Even if the recipient is not in Obyte yet. The sender just writes an email address where he would normally write a Obyte address. When he hits “Send”, his email app is opened with prefilled text for the recipient. The sender can edit it before sending.<br />
<br />
The recipient receives an email with a link. For example:<br />
<br />
<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><br />
<br />
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.<br />
<br />
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.<br />
<br />
===Refill===<br />
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.<br />
<br />
===All public assets===<br />
With version 2.1, you can send any public [[asset]] by textcoin, not only Bytes.<br />
<br />
===All private assets===<br />
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.<br />
<br />
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><br />
<br />
To claim the funds, click on the file.<br />
<br />
===Android===<br />
Another small but important update: when a textcoin link is clicked on Android which doesn't have Obyte 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><br />
<br />
==Technical==<br />
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.<br />
<br />
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.<br />
<br />
==Security==<br />
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.<br />
<br />
==Human-friendly==<br />
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.<br />
<br />
==No third party==<br />
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.<br />
<br />
==Server-side==<br />
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><br />
<br />
See the doc about sending them.<ref>https://github.com/byteball/byteballcore/wiki/Sending-textcoins</ref><br />
<br />
Now, any service that has email addresses of its users (that is, almost any service) can easily mass-pay them using just email addresses.<br />
<br />
===Chatbots===<br />
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.<br />
===Email lists===<br />
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.<br />
<br />
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><br />
<br />
==Cashback==<br />
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.<br />
<br />
==Sending funds directly to email addresses==<br />
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><br />
<br />
==Batch creation of textcoins==<br />
See https://github.com/byteball/headless-byteball/blob/master/play/create_textcoins_list.js.<br />
<br />
==External links==<br />
*[https://github.com/byteball/byteball/wiki/Cashback-API Updated API description]<br />
*[https://docs.google.com/document/d/1ppphsO0jnuu94r2L61xR5X0UwsenY9CeiBCJ_VBkdA8/view Google Doc guide by @punqtured on how to create physical textcoins to hand out at events etc]<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Features]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1536PolloPollo2020-02-11T14:51:48Z<p>Slackjore: typo</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
== Website ==<br />
The project website at www.pollopollo.org is online, but not yet fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
=== Grant ===<br />
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:<br />
<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.<br />
<br />
<p>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.</p></blockquote><br />
<br />
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.<br />
<br />
== Independent witness ==<br />
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><br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.ambcrypto.com/bitcoin-btc-proyecto-humanitario-en-blockchain-lleva-comida-a-venezuela/ AMBCrypto article (in Spanish) Nov 19 2019 about PolloPollo]<br />
*[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]<br />
*[https://www.criptonoticias.com/comunidad/beneficencia/travesia-bitcoiner-venezolano-premio-labitconf/ Criptonoticias article (Spanish) 26 Jan 2020 about B4H award for PolloPollo]<br />
*[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]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1535PolloPollo2020-02-11T14:46:18Z<p>Slackjore: typo</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
== Website ==<br />
The project website at www.pollopollo.org is online, but not yet fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
<br />
=== Grant ===<br />
On 5 June 2019 a grant proposal<ref>https://docs.google.com/document/d/1OSlqa3hZLdzwByE4BYHrYotJVjvF_6Qa5a8kqikoGO8/edit#</ref> was submitted to improve the website. The intro:<br />
<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.<br />
<br />
<p>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.</p></blockquote><br />
<br />
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.<br />
<br />
== Independent witness ==<br />
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><br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.ambcrypto.com/bitcoin-btc-proyecto-humanitario-en-blockchain-lleva-comida-a-venezuela/ AMBCrypto article (in Spanish) Nov 19 2019 about PolloPollo]<br />
*[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]<br />
*[https://www.criptonoticias.com/comunidad/beneficencia/travesia-bitcoiner-venezolano-premio-labitconf/ Criptonoticias article (Spanish) 26 Jan 2020 about B4H award for PolloPollo]<br />
*[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]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1534PolloPollo2020-02-11T14:42:10Z<p>Slackjore: typo</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
== Website ==<br />
The project website at www.pollopollo.org is online, but not yet fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
<br />
=== Grant ===<br />
On 5 June 2019 a [https://docs.google.com/document/d/1OSlqa3hZLdzwByE4BYHrYotJVjvF_6Qa5a8kqikoGO8/view grant proposal] was submitted to improve the website. The intro:<br />
<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.<br />
<br />
<p>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.</p></blockquote><br />
<br />
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.<br />
<br />
== Independent witness ==<br />
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><br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.ambcrypto.com/bitcoin-btc-proyecto-humanitario-en-blockchain-lleva-comida-a-venezuela/ AMBCrypto article (in Spanish) Nov 19 2019 about PolloPollo]<br />
*[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]<br />
*[https://www.criptonoticias.com/comunidad/beneficencia/travesia-bitcoiner-venezolano-premio-labitconf/ Criptonoticias article (Spanish) 26 Jan 2020 about B4H award for PolloPollo]<br />
*[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]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1533PolloPollo2020-02-11T14:40:31Z<p>Slackjore: added website/grant section</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
== Website ==<br />
The project website at www.pollopollo.org is online, but not yet fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
<br />
=== Grant ===<br />
On 5 June 2019 a [https://docs.google.com/document/d/1OSlqa3hZLdzwByE4BYHrYotJVjvF_6Qa5a8kqikoGO8/view grant] was submitted to improve the website. The intro:<br />
<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.<br />
<br />
<p>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.</p></blockquote><br />
<br />
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.<br />
<br />
== Independent witness ==<br />
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><br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.ambcrypto.com/bitcoin-btc-proyecto-humanitario-en-blockchain-lleva-comida-a-venezuela/ AMBCrypto article (in Spanish) Nov 19 2019 about PolloPollo]<br />
*[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]<br />
*[https://www.criptonoticias.com/comunidad/beneficencia/travesia-bitcoiner-venezolano-premio-labitconf/ Criptonoticias article (Spanish) 26 Jan 2020 about B4H award for PolloPollo]<br />
*[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]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1532PolloPollo2020-02-11T14:07:20Z<p>Slackjore: added date to article link</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
The project website at www.pollopollo.org is online, but not yet (February 2020) fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
<br />
== Independent witness ==<br />
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><br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.ambcrypto.com/bitcoin-btc-proyecto-humanitario-en-blockchain-lleva-comida-a-venezuela/ AMBCrypto article (in Spanish) Nov 19 2019 about PolloPollo]<br />
*[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]<br />
*[https://www.criptonoticias.com/comunidad/beneficencia/travesia-bitcoiner-venezolano-premio-labitconf/ Criptonoticias article (Spanish) 26 Jan 2020 about B4H award for PolloPollo]<br />
*[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]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1531PolloPollo2020-02-11T14:04:01Z<p>Slackjore: added link to 26/1/2020 article</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
The project website at www.pollopollo.org is online, but not yet (February 2020) fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
<br />
== Independent witness ==<br />
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><br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.cointelegraph.com/news/blockchain-solutions-to-help-venezuelans-were-awarded-at-the-b4h-awards-2019 CoinTelegraph article in Spanish about B4H award for PolloPollo]<br />
*[https://es.ambcrypto.com/bitcoin-btc-proyecto-humanitario-en-blockchain-lleva-comida-a-venezuela/ AMBCrypto article (in Spanish) Nov 19 2019 about PolloPollo]<br />
*[https://www.criptonoticias.com/comunidad/beneficencia/travesia-bitcoiner-venezolano-premio-labitconf/ Criptonoticias article (Spanish) 26 Jan 2020 about B4H award for PolloPollo]<br />
*[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]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1530PolloPollo2020-02-10T23:42:43Z<p>Slackjore: added link to AMBCrypto article</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
The project website at www.pollopollo.org is online, but not yet (February 2020) fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
<br />
== Independent witness ==<br />
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><br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.cointelegraph.com/news/blockchain-solutions-to-help-venezuelans-were-awarded-at-the-b4h-awards-2019 CoinTelegraph article in Spanish about B4H award for PolloPollo]<br />
*[https://es.ambcrypto.com/bitcoin-btc-proyecto-humanitario-en-blockchain-lleva-comida-a-venezuela/ AMBCrypto article (in Spanish) Nov 19 2019 about PolloPollo]<br />
*[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]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1529PolloPollo2020-02-10T23:38:20Z<p>Slackjore: added link to CoinTelegraph article</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
The project website at www.pollopollo.org is online, but not yet (February 2020) fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
<br />
== Independent witness ==<br />
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><br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.cointelegraph.com/news/blockchain-solutions-to-help-venezuelans-were-awarded-at-the-b4h-awards-2019 CoinTelegraph article in Spanish about B4H award for PolloPollo]<br />
*[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]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1528PolloPollo2020-02-09T12:22:37Z<p>Slackjore: added section re witness</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
The project website at www.pollopollo.org is online, but not yet (February 2020) fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
<br />
== Independent witness ==<br />
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><br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.cointelegraph.com/news/blockchain-solutions-to-help-venezuelans-were-awarded-at-the-b4h-awards-2019 CoinTelegraph article in Spanish about B4H award for PolloPollo]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Main_Page&diff=1527Main Page2020-02-09T12:17:03Z<p>Slackjore: added Feb 6 news item</p>
<hr />
<div>__NOTOC__<br />
[[File:Obyte-logo.jpg|thumb|250px]] <br />
'''Welcome to the Obyte Wiki. See first a one-page [[overview|OVERVIEW]], the [[glossary|GLOSSARY]], and the [[wallet|WALLET]] page. See [[Special:AllPages|ALL PAGES here]].'''<br />
<br />
==Introduction==<br />
Obyte, formerly Byteball, now listed on CoinMarketCap<ref>https://coinmarketcap.com</ref> as simply ''Obyte'', is a DAG-based cryptocurrency developed by Anton (Tony) Churyumov.<br />
<br />
This wiki is aimed at general cryptocurrency users, as well as Obyte users, who want to become better informed about Obyte. <br />
<br />
The wiki content is currently generated by invited contributors, and not randomly.<br />
<br />
==License==<br />
All content of this wiki is available under a Creative Commons Attribution-ShareAlike 3.0 Unported [[License]].<br />
<br />
== External links ==<br />
*[https://obyte.org Main official site]<br />
*[https://explorer.obyte.org Transactions explorer]<br />
*[https://obyte.org/Byteball.pdf White paper]<br />
*[https://medium.com/Obyte ''Medium'' articles]<br />
*[https://www.youtube.com/channel/UCYAjbxT5zHfeTtXe_hr9Gxg Obyte Channel on YouTube]<br />
*[https://asset.obyte.app Obyte Asset Registry for you to create a new asset]<br />
*[https://github.com/byteball/byteball Repository]<br />
*[https://obyte.io An Obyte data explorer]<br />
<br />
===Forums===<br />
*[https://discord.obyte.org Discord channel invitation] <br />
*[https://bitcointalk.org/index.php?topic=1608859.0) Bitcointalk thread]<br />
*[https://bitcointalk.org/index.php?action=profile;u=412662;sa=showPosts;start=0) Tony's posts on bitcointalk]<br />
*[https://reddit.com/r/obyte Subreddit]<br />
*[https://telegram.me/obyte Telegram]<br />
*[https://twitter.com/ObyteOrg Twitter]<br />
<br />
==Latest [[News]]==<br />
*Feb 6: [[PolloPollo]] 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><br />
*Dec 27: Bosch Connectory announced as the 3rd default witness (order provider)<ref>https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03</ref><br />
*Sep 25: Version 2.8.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg52555921#msg52555921</ref><br />
*Aug 7: The first Ocademy (Obyte Academy) student graduates<ref>https://medium.com/obyte/meet-the-first-ocademy-workshop-graduate-133617202c</ref><br />
*Aug 5: Sports oracle updated to work with [[Autonomous Agent]]s<ref>https://medium.com/obyte/sports-oracle-for-autonomous-agents-96b56369168a</ref><br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=News&diff=1526News2020-02-09T12:15:09Z<p>Slackjore: added Feb 6 item</p>
<hr />
<div>Very brief '''headline''' items only, with links to each announcement, usually on Bitcointalk as a permanent record.<br />
<br />
== 2020 ==<br />
*Feb 6: [[PolloPollo]] announced as the 4th default witness (order provider)<ref>https://medium.com/obyte/pollopollo-approved-to-become-a-default-witness-on-the-obyte-public-network-9ee32238142f</ref><br />
<br />
==2019==<br />
*Dec 27: Bosch Connectory announced as the 3rd default witness (order provider)<ref>https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03</ref><br />
*Sep 25: Version 2.8.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg52555921#msg52555921</ref><br />
*Aug 7: The first Ocademy (Obyte Academy) student graduates<ref>https://medium.com/obyte/meet-the-first-ocademy-workshop-graduate-133617202c</ref><br />
*Aug 5: Sports oracle updated to work with [[Autonomous Agent]]s<ref>https://medium.com/obyte/sports-oracle-for-autonomous-agents-96b56369168a</ref><br />
*Aug 1: "What's [[next]] for Obyte" blog launched<ref>https://medium.com/obyte/whats-next-for-obyte-b495cfbb698</ref><br />
*Jul 18: Autonomous Agents protocol upgrade released on Testnet<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
*Jun 11: Version 2.7.2 released<ref>https://github.com/byteball/obyte-gui-wallet/releases</ref><br />
*Apr 30: Obyte Foundation Establishment announced<ref>https://medium.com/obyte/obyte-foundation-is-established-c92a28d2d20e</ref><br />
*Apr 20: Version 2.7.0 released. Includes prosaic contracts.<ref>https://github.com/byteball/obyte-gui-wallet/releases</ref><br />
*Apr 16: 2nd independent witness candidate announced<ref>https://medium.com/obyte/second-independent-witness-candidate-fabien-marino-d4e8dccadee</ref><br />
*Apr 10: New method of identity verification launched for residents of Estonia, Latvia, Lithuania, and e-residents of Estonia.<ref>https://medium.com/obyte/new-methods-for-identity-verification-3d5045287533</ref><br />
*Jan 17: Byteball rebranded to Obyte<ref>https://medium.com/byteball/byteball-rebrand-the-next-step-to-real-world-adoption-6a0a924390de</ref><br />
<br />
==2018==<br />
*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><br />
*Dec 1: Byteball developer resources site launched at https://developer.byteball.org<ref>https://twitter.com/slackjore/status/1069216217691508736</ref><br />
*Oct 15: Smart Vouchers for Real Name Attestation introduced<ref>https://bitcointalk.org/index.php?topic=1608859.msg46911901#msg46911901</ref><br />
*Oct 14: Filter added to Explorer<ref>https://twitter.com/slackjore/status/1051452800696238080</ref><br />
*Sep 23: Dice bot added to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg46089759#msg46089759</ref><br />
*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><br />
*Aug 28: Nousplatform ICO added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg44795934#msg44795934</ref><br />
*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><br />
*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><br />
*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><br />
*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><br />
*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><br />
*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><br />
*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><br />
*Jun 23: Wallet version 2.3 released. Includes sending blackbytes as textcoins<ref>https://bitcointalk.org/index.php?topic=1608859.msg40698998#msg40698998</ref><br />
*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><br />
*May 29: Added Private Chat Room bot to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg38902178#msg38902178</ref><br />
*May 28: Added Exchange Bot for Dual-Chain Tokens to the Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg38743714#msg38743714</ref><br />
*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><br />
*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><br />
*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><br />
*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><br />
*Apr 26: Added World Community Grid linking bot to the Bot Store<ref>https://medium.com/byteball/computing-for-good-again-3795336bdaed</ref><br />
*Apr 20: Added Accredited investor attestation bot to the Bot Store<ref>https://medium.com/byteball/attestation-of-accredited-investors-d4a8dabf683b</ref><br />
*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><br />
*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><br />
*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> <br />
*Mar 23: Exchange bot for ICOs added to the Bot Store<ref>https://medium.com/byteball/byteball-exchange-bot-78c8154f4e6a</ref><br />
*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><br />
*Feb 18: March 2 and future [[airdrop]]s terminated<ref>https://bitcointalk.org/index.php?topic=1608859.msg30564528#msg30564528</ref><br />
*Feb 15: SilentNotary ICO added to Bot Store<ref>https://twitter.com/ByteballOrg/status/964267908879781888</ref><br />
*Jan 26: Free [[fun-coins]] faucet added to Bot Store<ref>https://twitter.com/slackjore/status/957355056235499520</ref><br />
*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><br />
*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><br />
*Jan 13: Eli Taranto now onboard as PR and Marketing director.<ref>https://bitcointalk.org/index.php?topic=1608859.msg28047149#msg28047149</ref><br />
*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><br />
*Jan 7: First name-registry recognized by the main hub. Reg policy.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27668314#msg27668314</ref><br />
*Jan 7: Our ICO bot now supports BTC and ETH.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27619698#msg27619698</ref><br />
*Jan 3: CFD Trading (Trustful) bot added to bot store.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27431192#msg27431192</ref><br />
*Jan 3: Wallet version 2.1 released.<ref>https://bitcointalk.org/index.php?topic=1608859.msg27376650#msg27376650</ref><br />
<br />
==2017==<br />
*Dec 14: Textcoins enabled in server-side wallets for bulk emails.<ref>https://bitcointalk.org/index.php?topic=1608859.msg26332250#msg26332250</ref><br />
*Dec 9: Wallet version 2.0 released.<ref>https://bitcointalk.org/index.php?topic=1608859.msg26003939#msg26003939</ref><br />
*Nov 21: Sports Oracle now supports UFC.<ref>https://bitcointalk.org/index.php?topic=1608859.msg24962770#msg24962770</ref><br />
*Nov 14: Byteball-Altcoin Exchange Bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg24594142#msg24594142</ref><br />
*Nov 11: Wallet version 1.11.3 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg24377569#msg24377569</ref><br />
*Nov 3: First real-world project with ICO on platform: TitanCoin<ref>https://bitcointalk.org/index.php?topic=1608859.msg24004338#msg24004338</ref><br />
*Oct 18: Wallet version 1.11.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg23182135#msg23182135</ref><br />
*Oct 2: LuckyBytes lottery bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg22484391#msg22484391</ref><br />
*Sep 29: Sports Betting bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg22371562#msg22371562</ref><br />
*Sep 7: Slice&Dice MUD game bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg21607962#msg21607962</ref><br />
*Sep 5: First Cashback merchants added<ref>https://bitcointalk.org/index.php?topic=1608859.msg21533378#msg21533378</ref><br />
*Aug 27: Buy Blackbytes bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg21250868#msg21250868</ref><br />
*Aug 25: Sports Oracle now supports MLB, NBA, NFL, NHL and soccer<ref>https://bitcointalk.org/index.php?topic=1608859.msg21199623#msg21199623</ref><br />
*Aug 23: Wallet version 1.10.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg21138107#msg21138107</ref><br />
*Aug 23: Cashback API for merchants is ready<ref>https://bitcointalk.org/index.php?topic=1608859.msg21130417#msg21130417</ref><br />
*Aug 7: Cashback program launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg20686283#msg20686283</ref><br />
*Aug 1: Wallet version 1.10.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg20534934#msg20534934</ref><br />
*Jul 29: Flight Delay Insurance bot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg20474959#msg20474959</ref><br />
*Jun 30: Wallet version 1.9.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg19864486#msg19864486</ref><br />
*Jun 22: Grants program launched<ref>https://medium.com/byteball/byteball-grants-program-906a71b93d3c</ref><br />
*Jun 5: Rosie chatbot added to Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg19378793#msg19378793</ref><br />
*Jun 1: Bot Store launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg19315253#msg19315253</ref><br />
*Jun 1: Wallet version 1.9.0 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg19315253#msg19315253</ref><br />
*May 28: Crowdin now used for wallet translations<ref>https://bitcointalk.org/index.php?topic=1608859.msg19244480#msg19244480</ref><br />
*May 19: Sports oracle P2P betting on soccer launched in Bot Store<ref>https://bitcointalk.org/index.php?topic=1608859.msg19101028#msg19101028</ref><br />
*Apr 26: P2P insurance on smart contracts launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18759349#msg18759349</ref><br />
*Apr 18: Wallet version 1.8 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18646968#msg18646968</ref><br />
*Apr 7: P2P gambling using smart contracts launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18499180#msg18499180</ref><br />
*Apr 5: Wallet version 1.7 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18466533#msg18466533</ref><br />
*Mar 18: Binding payments to oracle-posted events launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg18240736#msg18240736</ref><br />
*Mar 18: Wallet version 1.6 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18240736#msg18240736</ref><br />
*Mar 6: Wallet version 1.5 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg18080683#msg18080683</ref><br />
*Feb 22: Wallet version 1.4 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17942383#msg17942383</ref><br />
*Feb 11: Wallet version 1.3 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17808504#msg17808504</ref><br />
*Feb 10: Chinese WeChat group "Byteball 中国" launched<ref>https://bitcointalk.org/index.php?topic=1608859.msg17803910#msg17803910</ref><br />
*Feb 3: Transaction Explorer now shows all blackbyte details as only "Hidden Payments"<ref>https://bitcointalk.org/index.php?topic=1608859.msg17720913#msg17720913</ref><br />
*Feb 3: Wallet version 1.2 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17718842#msg17718842</ref><br />
*Jan 19: Wallet version 1.1 released<ref>https://bitcointalk.org/index.php?topic=1608859.msg17559287#msg17559287</ref><br />
*Jan 17: Byte-BTC Exchange bot now live<ref>https://bitcointalk.org/index.php?topic=1608859.msg17527112#msg17527112</ref><br />
<br />
==2016==<br />
*Dec 25: Live network launched. Wallet version 1.0<ref>https://bitcointalk.org/index.php?topic=1608859.msg17303311#msg17303311</ref><br />
==External links==<br />
<br />
<br />
==References==<br />
<references /><br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Witness&diff=1525Witness2020-02-09T12:10:59Z<p>Slackjore: added PolloPollo as 4th default independent witness</p>
<hr />
<div><br />
==What is a witness?==<br />
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://obyte.org/Byteball.pdf</ref><br />
<br />
==How to replace a witness==<br />
Wallet menu > Settings > Witnesses displays the 12 witnesses set in one's wallet.<br />
<br />
*If "Auto-update the witness list from the hub" is turned 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.<br />
<br />
*If Auto-update is turned on, one's witness list will be updated to match the hub's default list automatically.<br />
<br />
=== New default witness ===<br />
After a new default witness has been approved, the next time one's wallet is turned on a screen will suggest replacing a particular Founder's Witness with the new one. So select either "Replace" or "Maybe later."<br />
<br />
==Non-Founder's witnesses==<br />
===Why change?===<br />
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. Obyte 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.<br />
<br />
===portabella, the first independent witness===<br />
No real-world identity posted. Known in the Obyte community as a veteran Byteball developer and contributor, who started this very wiki. Also operated the first independent Byteball hubs (see [[hub]] list) from January 2017. Currently (2019) not active in Obyte.<br />
<br />
===seb486, the cashback witness===<br />
No real-world identity posted. Known in the Obyte community as seb486 on Slack and Bytefan on BitcoinTalk. Not operating as a witness since July 2018.<br />
<br />
=== Rogier Eijkelhof ===<br />
The first default decentralized witness, from the Netherlands.<ref>https://medium.com/obyte/first-decentralized-witness-candidate-rogier-eijkelhof-9e5619166334</ref><br />
<br />
=== Fabien Marino ===<br />
The second default independent witness, co-founder of Busy.org and SteemConnect, involved with Obyte since February 2017.<ref>https://medium.com/obyte/second-independent-witness-candidate-fabien-marino-d4e8dccadee</ref><br />
<br />
=== Bosch Connectory ===<br />
This is the third default independent witness, overwhelmingly approved by vote (178:2 addresses, 31320 GB : 68 MB).<ref>https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03</ref><br />
<br />
=== PolloPollo ===<br />
In a poll closing on 4 Feb 2020, [[PolloPollo]] was convincingly voted in as the fourth default independent witness.<ref>https://medium.com/obyte/pollopollo-approved-to-become-a-default-witness-on-the-obyte-public-network-9ee32238142f</ref><br />
<br />
==Witness monitoring service==<br />
This is a useful page: https://stats.obyte.org/witnesses.php<br />
<br />
==Witness list==<br />
{| class="wikitable"<br />
|-<br />
! Witness ID !! Owner !! Discord ID !! Started<br />
|-<br />
| BVVJ2K7ENPZZ3VYZFWQWK7ISPCATFIW3 || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| DJMMI5JYA5BWQYSXDPRZJVLW3UGL3GJS || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| H5EZTQE7ABFH27AUDTQFMZIALANK6RBG || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| JEDZYC2HMGDBIDQKG3XSTXUSHMCBK725 || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| OYW2XTDKSNKGSEZ27LMGNOPJSYIXHBHC || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| S7N5FE42F6ONPNDQLCF64E2MGFYKQR2I || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| TKT4UESIKTTRALRRLWS4SENSTJX6ODCW || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| UENJPVZ7HVHM6QGVGT6MWOJGGRTUTJXQ || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| MEJGDND55XNON7UU3ZKERJIZMMXJTVCV || anon || @seb486 || 2017-05-25<br />
|-<br />
| 4GDZSXHEFVFMHCUCSHZVXBVF5T2LJHMU || Rogier Eijkelhof || @Rogier || 2018-10-23<br />
|-<br />
| FAB6TH7IRAVHDLK2AAWY5YBE6CEBUACF || Fabien Marino || @fabien || 2019-04-16<br />
|-<br />
| 2TO6NYBGX3NF5QS24MQLFR7KXYAMCIE5 || Bosch Connectory || N/A || 2019-12-27<br />
|-<br />
| APABTE2IBKOIHLS2UNK6SAR4T5WRGH2J || PolloPollo || @punqtured || 2020-02-04<br />
|}<br />
<br />
<hr /><br />
<br />
==FAQ about witnesses, double spending, finality==<br />
<br />
===Witnesses and consensus===<br />
<br />
Q: Those witnesses that wallet has chosen that will try to determine the validity of the transaction/message?<br /><br />
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. <br />
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.<br />
<br />
Q: Are witnesses required to validate all transactions?<br /><br />
A: Witnesses are required to be full nodes, hence validate all transactions<br />
<br />
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?<br /><br />
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)<br />
<br />
Q: Does a full node need to receive and validate all transactions?<br /><br />
A: Yes, that's the definition of a full node<br />
<br />
Q: To illustrate how little a witness has to decide:<br /><br />
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.<br />
<br />
Q: The witnesses together they decide which branch of the transaction tree is the real one?<br /><br />
A: More accurate wording: they don't decide but enable others to decide, by looking at witnesses as markers of reality<br />
<br />
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?<br /><br />
A: Correct.<br />
<br />
Q: Are the “witnessing” units specialised by any means?<br /><br />
A: There are no specialised witnessing units. Any witness-authored unit counts as “witnessing” unit<br />
<br />
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?<br /><br />
A: Correct<br />
<br />
Q: The protocol requires that transactors have an overlap of 11 (out of 12) witnesses, correct?<br /><br />
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<br />
<br />
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?<br /><br />
A: No, witnesses do not determine the chain state<br />
<br />
Q: is there an option of organic replacement of one or more witnesses?<br /><br />
A: Edit the list in the wallet settings<br />
<br />
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?<br /><br />
A: If we define users as those who post transactions to the DAG, No.<br />
<br />
Q: Is it possible to choose 12 completely new witnesses for my wallet? What would happen?<br /><br />
A: Possible but you won’t be able to post any transactions until all active users migrate to roughly the same list<br />
<br />
Q: What does “predominant witnesses” mean?<br /><br />
A: Those that you see on the most recently posted units (they can be slightly different)<br />
<br />
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?<br /><br />
A: Yes, the majority of the current predominant witnesses<br />
<br />
Q: If an individual, company or government seizes a witness (or all), would they be able to censor transactions?<br /><br />
A: If "a" witness, no, they will only censor out themselves. If all witnesses, yes.<br />
<br />
Q: What happens if all witnesses are shut down?<br /><br />
A: There will be no confirmations. The MC will still be there but the “stability point” will stop advancing.<br />
<br />
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?<br /><br />
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.<br />
<br />
===Double spending===<br />
Q: Are full (or light) nodes capable of identifying and solving double spend attempts without the use of witnesses?<br /><br />
A: No, they need the witness-authorized units’ positions on the DAG to build the MC, and they use the MC to resolve doublespends<br />
<br />
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?<br /><br />
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.<br />
<br />
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?<br /><br />
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.<br />
<br />
===Finality in Byteball===<br />
Q: What is “finality” in Byteball?<br /><br />
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”)<br />
<br />
Q:.What is “stability point” in Byteball?<br /><br />
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.<br />
<br />
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).<br /><br />
A: No, it is not allowed.<br />
<br />
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? <br />
A: if the colluding witnesses are a majority, the network will get into undefined state once they publish the shadow chain<br />
<br />
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?<br /><br />
A: Every full node replays the entire history and recalculates the stability point itself<br />
<br />
==Additional comments==<br />
[Slack 11:00 PM 2017-06-22]<br /><br />
<br />
<blockquote>'''markcross:''' And it's those witnesses that wallet has chosen that will try to determine the validity of the transaction/message?</blockquote><br />
<br />
<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. <br />
<br />
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.<br />
</blockquote><br />
<br />
[Bitcointalk 2017-02-06]<br />
<br />
<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><br />
<br />
===Decentralizing witnesses===<br />
[Bitcointalk 2018-03-21]<br />
<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><br />
<br />
<br />
===Witness functions===<br />
[Slack 2018-05-14]<br />
<br />
<blockquote>'''tonych:'''<br />
> · Are witnesses required to validate all transactions?<br /><br />
witnesses are required to be full nodes, hence validate all transactions<br /><br />
> · What happens if all witnesses are shut down?<br /><br />
there will be no confirmations. The MC [main chain] will still be there but the stability point will stop advancing<br /><br />
> · If an individual, company or government seizes a witness (or all), would they be able to censor transactions?<br /><br />
If "a" witness, no, they will only censor out themselves. If all witnesses, yes.<br /><br />
> So in effect, a witness has the same role as any other full node, except when attempts of double spends without partial order occur?<br /><br />
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<br /><br />
> Every full node validates all transactions?<br /><br />
Yes, that's the definition of a full node<br />
> · Are full (or light) nodes capable of identifying and solving double-spend attempts without the use of witnesses?<br /><br />
No, they need witness positions on the DAG to build the MC, and they use the MC to resolve doublespends</blockquote><br />
<br />
<blockquote>'''Tsonko Mirchev:''' Is that mean that full node doesn't need MC to resolve doublespends?</blockquote><br />
<br />
<blockquote>'''tonych:''' no, it needs the MC</blockquote><br />
<br />
<blockquote>'''tonych:''' another thing to illustrate how little a witness has to decide:<br />
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><br />
<br />
<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><br />
<br />
<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. <br />
<br />
Which of these is wrong?</blockquote><br />
<br />
<blockquote>'''tonych:''' no, witnesses do not "stamp", stamping would make them gatekeepers</blockquote><br />
<br />
<blockquote>'''tonych:''' the functions are just to 1) be honest, and 2) be there<br />
<br />
> because together they decide which branch of the transaction tree is the real one<br />
more accurate wording: they don't decide but enable others to decide, by looking at witnesses as markers of reality<br />
> Hm, I added Bittrex as a witness and the explorer considers the tx stable, but my wallet doesn't<br />
<br />
if your wallet is light, it sees stability later</blockquote><br />
<br />
<blockquote>'''slackjore:''' OK. I was using the word "stamp" wrongly, to mean basically "comment upon". How about my other assumptions?</blockquote><br />
<br />
<blockquote>'''tonych:'''(2) correct<br /><br />
(3) correct, the "additional software" is anything responsible for frequent posting of transactions<br /><br />
(4) correct<br /><br />
(5) correct<br /><br />
(6) of course</blockquote><br />
<br />
<blockquote>'''slackjore:''' Thank you. So how can Bittrex act as an unknowing witness, if a witness has to author units?</blockquote><br />
<br />
<blockquote>'''tonych:''' they do withdrawals and other txs from this address</blockquote><br />
<br />
<blockquote>'''slackjore:'''yes, but you said: https://byteball.slack.com/archives/C9GDDLW0N/p1526293317000487<br />
tonych<br />
another thing to illustrate how little a witness has to decide:<br />
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.<br />
Posted in #marketing_discussionToday at 11:21 AM</blockquote><br />
<br />
<blockquote>'''tonych:''' yes, any contradiction?</blockquote><br />
<br />
<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><br />
<br />
<blockquote>'''tonych:''' there are no specialised witnessing units, any witness-authored unit counts</blockquote><br />
<br />
<blockquote>'''slackjore:''' I mean a unit like this: https://explorer.byteball.org/#OaMFZKr+2zQp4Ce0Oxz0tpTaB4Jb2jLDYcrLACxt+jA=<br />
arbitrary, first one I saw</blockquote><br />
<br />
<blockquote>'''tonych:''' nothing special in it</blockquote><br />
<br />
<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.<br />
<br />
Is that correct?</blockquote><br />
<br />
<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><br />
<br />
<blockquote>'''slackjore:''' ok, great, now I understand how Bittrex could be an unknowing witness. Thank you very much indeed.</blockquote><br />
<br />
-----<br />
<br />
<blockquote>'''Person:''' Hi @tonych please help to answer some questions. I would like to understand the WP. <br />
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?<br />
<br />
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”?<br />
<br />
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?<br />
<br />
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?</blockquote><br />
<br />
<blockquote>'''tonych:''' 1. the witnesses of the newly added unit<br />
<br />
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.<br />
<br />
3. correct<br />
<br />
4. correct</blockquote><br />
<br />
<blockquote>'''Person:''' tony: Is it correct to state that the “current MC” is determined by the witnesses of the unit in the current stability point?</blockquote><br />
<br />
<blockquote>'''tonych:''' No, no witness list matters at all at this step. You just define the best parent using witnessed level and level</blockquote><br />
<br />
<blockquote>'''Person:''' [question lost]</blockquote><br />
<br />
<blockquote>'''tonych:'''. 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.</blockquote><br />
<br />
==How to become a witness==<br />
To become a winess, you are expected to:<br />
<br />
*have a publicly known real name, no anonymity<br />
*be well known in the community<br />
*be trusted<br />
*have a lot to lose (material and/or nonmaterial) in case of misbehavior. The loss is your business (outside Byteball) and/or reputation<br />
*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)<br />
*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.<br />
<br />
If you think that you satisfy these criteria, this is your course of action: <snip><ref>https://github.com/byteball/byteball-witness</ref><br />
<br />
==External links==<br />
*[https://www.youtube.com/watch?v=N1aWPAm0SdY&feature=youtu.be Video: Byteball Witnesses - the basics explained]<br />
*[https://medium.com/obyte/first-decentralized-witness-candidate-rogier-eijkelhof-9e5619166334 First decentralized witness candidate]<br />
*[https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03 Bosch Connectory Approved as Obyte Witness]<br />
<br />
==References==<br />
<references /><br />
[[Category:Features]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Oracle&diff=1524Oracle2020-01-16T15:19:59Z<p>Slackjore: added note re PMs exchange rates oracle, and video</p>
<hr />
<div>An ORACLE is a trusted third party that monitors specific external events and imports them into the Obyte database as a data feed. An example is a list of cryptocurrency exchange rates updated every ten minutes.<br />
<br />
==Known oracles==<br />
'''P2P exchange of Bytes vs. Bitcoin'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-ii-bitcoin-exchange-d98adfbde2a5</ref> | FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH<br />
<br />
'''P2P random numbers gambling''' | FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH (same oracle as above) <br />
<br />
'''Crypto exchange rates'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-iii-prediction-markets-f40d49c0abab</ref> | JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC<br />
<br />
'''Flight delay tracker for flight delays insurance'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-iv-p2p-insurance-cbbd1e59d527</ref> | GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN <br />
<br />
'''Sports betting on soccer match results'''<ref>[[Sports betting]]</ref> | TKT4UESIKTTRALRRLWS4SENSTJX6ODCW <br />
<br />
'''Timestamp in Unix Epoch Time'''<ref>[[Timestamp]]</ref> | I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT <br />
<br />
'''Precious metals exchange rates oracle''' | DXYWHSZ72ZDNDZ7WYZXKWBBH425C6WZN<br />
<br />
==Contract times==<br />
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.<br />
<br />
===Peer non-payment===<br />
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).<br />
<br />
===Contract expiry===<br />
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.<br />
<br />
==Personal oracles==<br />
{{#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.<br />
<br />
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.<br />
<br />
This sort of thing could be used as part of a [[family tokens]] set-up in a household.<br />
<br />
{{clear}}<br />
<br />
==Example of trading using an oracle==<br />
[[File:Oracle-1.png|thumb|left|upright=0.66]][[File:Oracle-2.png|thumb|none|upright=0.66]]<br />
<br />
{{clear}}<br />
<br />
From the Slack Obyte #prediction_markets forum, tonych:<br />
<br />
<blockquote>This is a trading floor, shout out your offers like in the old times. For example: <br />
"I bet on BTC going below 1150 within 1 day, I pay 0.3GB out of 1GB"</blockquote><br />
<br />
Use the crypto exchange rates oracle for this.<br />
<br />
<div style="clear: both;"></div><br />
==Using the crypto-exchange-rates oracle in a smart contract==<br />
{{#ev:youtube|https://www.youtube.com/watch?v=tjWHxlHBGAg|200|right}}<br />
<br />
# 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.<br />
# 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.<br />
# 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.<br />
# When you get to ORACLE ADDRESS, copy/paste in the crypto exchange rates one: '''JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC'''<br />
# 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'''<br />
# 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.<br />
# '''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).'''<br />
# Your peer clicks Send on the payment request. The new contract will be visible as a smart wallet.<br />
# Now you both wait. You can view an up-to-date feed from that oracle by entering its full JPQ… address in the [Obyte explorer search box](http://explorer.obyte.org). As soon as one party fulfills the terms of the contract its funds can be spent.<br />
{{clear}}<br />
<br />
==Random numbers==<br />
{{#ev:vimeo|https://vimeo.com/221655112|thumb|right|'''Betting on Random Numbers'''}} Video in Hi-Def and with English subtitles.<br />
# 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.<br />
# 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.<br />
# 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.<br />
# When you get to ORACLE ADDRESS, copy/paste in the random-numbers-gambling one: '''FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH'''<br />
# Here is an example of the data feed from this oracle:<ref><br />
https://explorer.byteball.org/#Ns//o52EKR32ykuHfUfcm3ailHtta6TvM5kB07vbpVA=<br /> <br />
bitcoin_hash: 0000000000000000019dd457cf8e233701dab44ac855492d575a4366556213e0<br /> <br />
bitcoin_height: 460852<br /> <br />
bitcoin_merkle: GW9cQW5m0KLIi2suUlkzRP2yurg8jLEax3uHiun7kik=<br /> <br />
random460852: 34789<br />
</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'''<br />
# 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.<br />
# '''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).'''<br />
# Your peer clicks Send on the payment request. The new contract will be visible as a smart wallet.<br />
# 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.<br />
<br />
==Flight delays tracker==<br />
{{#ev:vimeo|https://vimeo.com/222006250|thumb|right|'''Betting on Flight Delays'''}} Video in Hi-Def and with English subtitles.<br />
<br />
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: <br />
<br />
*30 minutes delay: 0.082258065 GB <br />
*1 hour delay: 0.079996985 GB <br />
*2 hour delay: 0.070952668 GB <br />
*4 hour delay: 0.066129032 GB<br />
<br />
<div style="clear: both;"></div><br />
<br />
== Precious metals exchange rates ==<br />
This oracle [https://obyte.io/@DXYWHSZ72ZDNDZ7WYZXKWBBH425C6WZN posts units] every 20 minutes. The data feed shows 20 pairs, such as XAG_BTC, XAG_EUR, XAU_USD, XAG_GBYTE and XAU_GBLACKBYTE. The data feed is sourced from https://1forge.com/forex-data-api/currency-pair-list. Global precious metals markets are closed over the weekend, Friday 21:00 - Sunday 21:00 UTC, so the oracle will not post during these times.<br />
<br />
This oracle can be used in the same way as the crypto exchange rates oracle, the only difference being the oracle address and ticker of the pair.<br />
<br />
==External links==<br />
<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Features]]<br />
[[Category:Trading]]<br />
[[Category:Oracles]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Oracle&diff=1523Oracle2020-01-14T22:05:13Z<p>Slackjore: added note re PM markets shut over weekends</p>
<hr />
<div>An ORACLE is a trusted third party that monitors specific external events and imports them into the Obyte database as a data feed. An example is a list of cryptocurrency exchange rates updated every ten minutes.<br />
<br />
==Known oracles==<br />
'''P2P exchange of Bytes vs. Bitcoin'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-ii-bitcoin-exchange-d98adfbde2a5</ref> | FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH<br />
<br />
'''P2P random numbers gambling''' | FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH (same oracle as above) <br />
<br />
'''Crypto exchange rates'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-iii-prediction-markets-f40d49c0abab</ref> | JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC<br />
<br />
'''Flight delay tracker for flight delays insurance'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-iv-p2p-insurance-cbbd1e59d527</ref> | GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN <br />
<br />
'''Sports betting on soccer match results'''<ref>[[Sports betting]]</ref> | TKT4UESIKTTRALRRLWS4SENSTJX6ODCW <br />
<br />
'''Timestamp in Unix Epoch Time'''<ref>[[Timestamp]]</ref> | I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT <br />
<br />
'''Precious metals exchange rates oracle''' | DXYWHSZ72ZDNDZ7WYZXKWBBH425C6WZN<br />
<br />
==Contract times==<br />
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.<br />
<br />
===Peer non-payment===<br />
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).<br />
<br />
===Contract expiry===<br />
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.<br />
<br />
==Personal oracles==<br />
{{#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.<br />
<br />
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.<br />
<br />
This sort of thing could be used as part of a [[family tokens]] set-up in a household.<br />
<br />
{{clear}}<br />
<br />
==Example of trading using an oracle==<br />
[[File:Oracle-1.png|thumb|left|upright=0.66]][[File:Oracle-2.png|thumb|none|upright=0.66]]<br />
<br />
{{clear}}<br />
<br />
From the Slack Obyte #prediction_markets forum, tonych:<br />
<br />
<blockquote>This is a trading floor, shout out your offers like in the old times. For example: <br />
"I bet on BTC going below 1150 within 1 day, I pay 0.3GB out of 1GB"</blockquote><br />
<br />
Use the crypto exchange rates oracle for this.<br />
<br />
<div style="clear: both;"></div><br />
==Using the crypto-exchange-rates oracle in a smart contract==<br />
# 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.<br />
# 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.<br />
# 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.<br />
# When you get to ORACLE ADDRESS, copy/paste in the crypto exchange rates one: '''JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC'''<br />
# 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'''<br />
# 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.<br />
# '''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).'''<br />
# Your peer clicks Send on the payment request. The new contract will be visible as a smart wallet.<br />
# Now you both wait. You can view an up-to-date feed from that oracle by entering its full JPQ… address in the [Obyte explorer search box](http://explorer.obyte.org). As soon as one party fulfills the terms of the contract its funds can be spent.<br />
<br />
==Random numbers==<br />
{{#ev:vimeo|https://vimeo.com/221655112|thumb|right|'''Betting on Random Numbers'''}} Video in Hi-Def and with English subtitles.<br />
# 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.<br />
# 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.<br />
# 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.<br />
# When you get to ORACLE ADDRESS, copy/paste in the random-numbers-gambling one: '''FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH'''<br />
# Here is an example of the data feed from this oracle:<ref><br />
https://explorer.byteball.org/#Ns//o52EKR32ykuHfUfcm3ailHtta6TvM5kB07vbpVA=<br /> <br />
bitcoin_hash: 0000000000000000019dd457cf8e233701dab44ac855492d575a4366556213e0<br /> <br />
bitcoin_height: 460852<br /> <br />
bitcoin_merkle: GW9cQW5m0KLIi2suUlkzRP2yurg8jLEax3uHiun7kik=<br /> <br />
random460852: 34789<br />
</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'''<br />
# 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.<br />
# '''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).'''<br />
# Your peer clicks Send on the payment request. The new contract will be visible as a smart wallet.<br />
# 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.<br />
<br />
==Flight delays tracker==<br />
{{#ev:vimeo|https://vimeo.com/222006250|thumb|right|'''Betting on Flight Delays'''}} Video in Hi-Def and with English subtitles.<br />
<br />
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: <br />
<br />
*30 minutes delay: 0.082258065 GB <br />
*1 hour delay: 0.079996985 GB <br />
*2 hour delay: 0.070952668 GB <br />
*4 hour delay: 0.066129032 GB<br />
<br />
<div style="clear: both;"></div><br />
<br />
== Precious metals exchange rates ==<br />
This oracle [https://obyte.io/@DXYWHSZ72ZDNDZ7WYZXKWBBH425C6WZN posts units] every 20 minutes. The data feed shows 20 pairs, such as XAG_BTC, XAG_EUR, XAU_USD, XAG_GBYTE and XAU_GBLACKBYTE. The data feed is sourced from https://1forge.com/forex-data-api/currency-pair-list. Global precious metals markets are closed over the weekend, Friday 21:00 - Sunday 21:00 UTC, so the oracle will not post during these times.<br />
<br />
==External links==<br />
<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Features]]<br />
[[Category:Trading]]<br />
[[Category:Oracles]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Oracle&diff=1522Oracle2020-01-14T22:00:24Z<p>Slackjore: added oracle: precious metals exchange rates</p>
<hr />
<div>An ORACLE is a trusted third party that monitors specific external events and imports them into the Obyte database as a data feed. An example is a list of cryptocurrency exchange rates updated every ten minutes.<br />
<br />
==Known oracles==<br />
'''P2P exchange of Bytes vs. Bitcoin'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-ii-bitcoin-exchange-d98adfbde2a5</ref> | FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH<br />
<br />
'''P2P random numbers gambling''' | FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH (same oracle as above) <br />
<br />
'''Crypto exchange rates'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-iii-prediction-markets-f40d49c0abab</ref> | JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC<br />
<br />
'''Flight delay tracker for flight delays insurance'''<ref>https://medium.com/byteball/making-p2p-great-again-episode-iv-p2p-insurance-cbbd1e59d527</ref> | GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN <br />
<br />
'''Sports betting on soccer match results'''<ref>[[Sports betting]]</ref> | TKT4UESIKTTRALRRLWS4SENSTJX6ODCW <br />
<br />
'''Timestamp in Unix Epoch Time'''<ref>[[Timestamp]]</ref> | I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT <br />
<br />
'''Precious metals exchange rates oracle''' | DXYWHSZ72ZDNDZ7WYZXKWBBH425C6WZN<br />
<br />
==Contract times==<br />
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.<br />
<br />
===Peer non-payment===<br />
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).<br />
<br />
===Contract expiry===<br />
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.<br />
<br />
==Personal oracles==<br />
{{#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.<br />
<br />
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.<br />
<br />
This sort of thing could be used as part of a [[family tokens]] set-up in a household.<br />
<br />
{{clear}}<br />
<br />
==Example of trading using an oracle==<br />
[[File:Oracle-1.png|thumb|left|upright=0.66]][[File:Oracle-2.png|thumb|none|upright=0.66]]<br />
<br />
{{clear}}<br />
<br />
From the Slack Obyte #prediction_markets forum, tonych:<br />
<br />
<blockquote>This is a trading floor, shout out your offers like in the old times. For example: <br />
"I bet on BTC going below 1150 within 1 day, I pay 0.3GB out of 1GB"</blockquote><br />
<br />
Use the crypto exchange rates oracle for this.<br />
<br />
<div style="clear: both;"></div><br />
==Using the crypto-exchange-rates oracle in a smart contract==<br />
# 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.<br />
# 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.<br />
# 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.<br />
# When you get to ORACLE ADDRESS, copy/paste in the crypto exchange rates one: '''JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC'''<br />
# 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'''<br />
# 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.<br />
# '''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).'''<br />
# Your peer clicks Send on the payment request. The new contract will be visible as a smart wallet.<br />
# Now you both wait. You can view an up-to-date feed from that oracle by entering its full JPQ… address in the [Obyte explorer search box](http://explorer.obyte.org). As soon as one party fulfills the terms of the contract its funds can be spent.<br />
<br />
==Random numbers==<br />
{{#ev:vimeo|https://vimeo.com/221655112|thumb|right|'''Betting on Random Numbers'''}} Video in Hi-Def and with English subtitles.<br />
# 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.<br />
# 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.<br />
# 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.<br />
# When you get to ORACLE ADDRESS, copy/paste in the random-numbers-gambling one: '''FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH'''<br />
# Here is an example of the data feed from this oracle:<ref><br />
https://explorer.byteball.org/#Ns//o52EKR32ykuHfUfcm3ailHtta6TvM5kB07vbpVA=<br /> <br />
bitcoin_hash: 0000000000000000019dd457cf8e233701dab44ac855492d575a4366556213e0<br /> <br />
bitcoin_height: 460852<br /> <br />
bitcoin_merkle: GW9cQW5m0KLIi2suUlkzRP2yurg8jLEax3uHiun7kik=<br /> <br />
random460852: 34789<br />
</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'''<br />
# 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.<br />
# '''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).'''<br />
# Your peer clicks Send on the payment request. The new contract will be visible as a smart wallet.<br />
# 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.<br />
<br />
==Flight delays tracker==<br />
{{#ev:vimeo|https://vimeo.com/222006250|thumb|right|'''Betting on Flight Delays'''}} Video in Hi-Def and with English subtitles.<br />
<br />
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: <br />
<br />
*30 minutes delay: 0.082258065 GB <br />
*1 hour delay: 0.079996985 GB <br />
*2 hour delay: 0.070952668 GB <br />
*4 hour delay: 0.066129032 GB<br />
<br />
<div style="clear: both;"></div><br />
<br />
== Precious metals exchange rates ==<br />
This oracle [https://obyte.io/@DXYWHSZ72ZDNDZ7WYZXKWBBH425C6WZN posts units] every 20 minutes. The data feed shows 20 pairs, such as XAG_BTC, XAG_EUR, XAU_USD, XAG_GBYTE and XAU_GBLACKBYTE. The data feed is sourced from https://1forge.com/forex-data-api/currency-pair-list. Global precious metals markets are closed over the weekend, Friday 21:00 - Sunday 21:00 UTC.<br />
<br />
==External links==<br />
<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Features]]<br />
[[Category:Trading]]<br />
[[Category:Oracles]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Trading_prediction_markets&diff=1521Trading prediction markets2020-01-12T17:34:08Z<p>Slackjore: /* External links */ updated Slack to Discord</p>
<hr />
<div>Prediction markets are exchange-traded markets created for the purpose of trading the outcome of events. This article concerns using the Obyte platform to do this.<br />
<br />
==Definition of "prediction market"==<br />
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%.<br />
<br />
Research has suggested that prediction markets are at least as accurate as other institutions predicting the same events with a similar pool of participants.<br />
<br />
Source: Wikipedia<ref>https://en.wikipedia.org/wiki/Prediction_market</ref><br />
<br />
==Current available markets==<br />
<br />
===Sports-betting on upcoming soccer matches===<br />
See the wiki [[Sports betting]] article for details<br />
<br />
===Betting on random numbers===<br />
See the wiki [[Oracle#Random_numbers]] article/section for details, including a video<br />
<br />
===Betting on crypto exchange rates===<br />
Crypto exchange rates oracle: '''JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC'''<br />
<br />
See wiki [[Oracle]] article for a step-by-step write-up <br />
<br />
Reference<ref>[https://medium.com/byteball/making-p2p-great-again-episode-iii-prediction-markets-f40d49c0abab Making P2P Great Again, Episode III: Prediction Markets]</ref><br />
<br />
<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).<br />
<br />
The new data feed names for smart contracts are: <br />
*TOTAL_CAP - total market cap in billions <br />
*BTC_PERCENTAGE - BTC percentage of total market cap<br />
<br />
<hr /><br />
<br />
===BinaryBalls===<br />
A commercial site, BinaryBalls<ref>https://binaryballs.com</ref>, from November 2017 was doing binary options trading with Obyte 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.<br />
<br />
====Update====<br />
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.<br />
<br />
===Betting on flight delays===<br />
<br />
Flight delay tracker for flight delays insurance<br /><br />
GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN<br /><br />
Reference<ref>[https://medium.com/byteball/making-p2p-great-again-episode-iv-p2p-insurance-cbbd1e59d527 Making P2P Great Again, Episode IV: P2P Insurance]</ref><br />
<br />
There is a video of betting on a flight delay on the [[Oracle]] page.<br />
<br />
==External links==<br />
*[https://discordapp.com/invite/Qn6JWfT Obyte Discord]<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Features]]<br />
[[Category:Trading]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Wallet&diff=1520Wallet2020-01-12T14:26:30Z<p>Slackjore: updated paper wallet info, removed old syntax</p>
<hr />
<div>'''Terminology:''' What you download and install on a device (smartphone, laptop, pc etc) is here referred to as the Obyte 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. <br />
<br />
[[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.<br />
<br />
==Obyte platform==<br />
To start, download and install a platform from those listed at obyte.org or Github: releases<ref>https://github.com/byteball/byteball/releases</ref> (includes win32, but not for XP). <br />
<br />
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.<br />
<br />
===Multiple devices===<br />
If you want a connected Obyte wallet on your pc and another one on your Android smartphone, choose the multi-device option [[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.<br />
<br />
====Convenience vs security====<br />
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. <br />
<br />
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.<br />
<br />
===Independent or connected?===<br />
'''Independent:''' Useful for experimenting, seeing what happens when you interact with another Obyte user in chat. Use (plain) default Small Expenses Wallet on each device.<br />
<br />
'''Connected:''' Useful for security. Will show the same balance and history across all devices.<br />
<br />
===Pairing===<br />
Alice has Obyte 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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
===Light/easy or full/hard platform?===<br />
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><br />
<br />
===Single-address wallet===<br />
A single-address wallet (platform version 1.11.0 on) you create will not generate the usual new [[change address]]. Change will always go to the one-and-only address the wallet contains.<br />
<br />
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 [[Trading prediction markets|prediction market]] for a future event, enable users to make contracts (bets) referencing your address as an [[Oracle#Personal_oracles|oracle]], and when the outcome of the event is known you post its result from your wallet.<br />
<br />
In this version you can also manually attest other users and post arbitrary data into the Obyte DAG.<br />
<br />
====Attestation====<br />
To facilitate [[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><br />
<br />
==Multiple screens==<br />
<br />
The default wallet is named "Small Expenses Wallet", and has two screens: one for bytes, one for blackbytes. Every [[Asset|new asset]] you receive (CK1's, [[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.<br />
<br />
==Update==<br />
When doing a routine update, first do a full back-up using the Obyte 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. <br />
<br />
==Main menu options==<br />
<br />
===Add wallet===<br />
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.<br />
<br />
A multi-device wallet is duplicated across each of the paired devices, showing the same transactions, addresses, balances etc.<br />
<br />
====Signatures====<br />
*A 1-of-2 set-up means two devices and either one is sufficient to send a transaction. <br />
*A 2-of-2 set-up means two devices and both signatures are needed to send a transaction. <br />
*A 2-of-4 set-up means four devices and two signatures are needed to send a transaction.<br />
<br />
===Paired devices===<br />
<br />
====Contacts====<br />
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.<br />
<br />
====Bot store====<br />
Currently shows about 20 bots. See wiki article [[Chatbot]] for details.<br />
<br />
===Settings = Global preferences===<br />
<br />
'''Device name:''' Change it if you wish. If you chat to someone, they will see this name<br />
<br />
'''Hub:''' Default is <code>obyte.org/bb</code>. You can change it<br />
<br />
'''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<br />
<br />
'''Language:''' Select from 18 or so<br />
<br />
'''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<br />
<br />
'''Unit for blackbytes:''' Select from kBB, MBB or GBB<br />
<br />
'''Enable push notifications:''' (Android) toggle on or off<br />
<br />
'''TRUSTED NODES'''<br />
<br />
'''Witnesses:''' Easiest to select "Auto-update the witness list from the hub". See wiki [[Witness]] article for harder options<br />
<br />
'''Email attestor''' <code>H5EZTQE7ABFH27AUDTQFMZIALANK6RBG</code> is the default. You can change this, but don't unless you know what you are doing<br />
<br />
'''DEVICE ADDRESS:''' <code>0VCPO8MYDRN2E3N5JDRHRSTVEVZSZYARM</code> for example. This doesn't change, and will be visible to anyone you pair with for chat<br />
<br />
SPENDING RESTRICTIONS<br /><br />
'''Request password:''' Lets you set up a password that will encrypt your platform/wallets. Don't forget it! There is no password recovery option<br />
<br />
'''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")<br />
<br />
'''Recovery from seed:''' Recovery is available in single-sig (i.e., not multi-sig) light wallets from version 1.10.1. <br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''About Obyte:''' Version number, commit hash (developer thing), terms of use, translators credits, session log<br />
<br />
==Cogwheel preferences==<br />
<br />
'''Wallet alias:''' change local name (it means "platform alias")<br />
<br />
'''Color:''' 12 to choose from<br />
<br />
'''Single address wallet:''' Will not create new change addresses for every transaction. Change will always go to the one and only address the wallet contains. Needed for registered/attested addresses, personal oracles, and more.<br />
<br />
'''Hidden assets:''' Toggle on/off any of your assets. Useful for reducing clutter.<br />
<br />
'''Advanced:''' (under next heading)<br />
<br />
===Wallet information===<br />
<br />
'''Wallet name (at creation):''' whatever name you gave the wallet first<br />
<br />
'''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<br />
<br />
'''Wallet configuration (m-n):''' multiple-signature configuration, like 1 of 1, 1 of 2, 2 of 2, 2 of 3 etc<br />
<br />
'''Derivation strategy:''' BIP44: standard method of deriving new keys for addresses<ref> [https://en.bitcoin.it/wiki/BIP_0044 Improvement Proposal 44]</ref><br />
<br />
'''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.<br />
<br />
'''CO-SIGNERS'''<br />
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<br />
<br />
'''EXTENDED PUBLIC KEYS:'''<br />
*'''Me''' xpub... (this wallet's xpub) <br />
<br />
*(Other wallet's name, if multi-sig) xpub... (that wallet's xpub)<br />
<br />
'''ALL WALLET ADDRESSES:''' (examples shown)<br />
<br />
65C...AW6<br /><br />
m/44'/0'/1'/0/0 · April 19th 2017, 3:00 pm<br />
<br />
7SV...MMM<br /><br />
m/44'/0'/1'/0/1 · April 22nd 2017, 5:47 pm<br />
<br />
MR3...APD<br /><br />
m/44'/0'/1'/1/0 · April 26th 2017, 1:34 pm<br />
<br />
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 [[change address]]es.<br />
<br />
'''BALANCE BY ADDRESS:''' (examples shown)<br />
7SV...MMM<br /><br />
0.04 GBB<br />
<br />
O3J...YL5<br /><br />
0.024402 MB<br />
<br />
RAZ...LIM<br /><br />
0.05966 MB<br /><br />
55 Zwib by Jore Bohne (new [[asset]], registered)<br /><br />
576 of 3kc7H8A2oiWr8mv7AcWJeLCA0Cp8c3BLK04kYQ+5pfU= (new asset, unregistered)<br /><br />
0.085248 GBB<br />
<br />
UQX...EC6<br /><br />
0.117889 MB<br />
<br />
===Sweep paper wallet===<br />
Obyte paper wallets are just textcoins. Scan the paper wallet's QR code using the camera icon in the upper right corner or input the 12 words of the textcoin manually on the "Receive" tab<br />
<br />
===Delete wallet===<br />
What it says, big red button on the next screen<br />
<br />
==Smart wallets==<br />
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.<br />
<br />
===Confirmed funds===<br />
You need transactions to confirm before <br />
*A smart wallet first becomes visible <br />
*You can spend funds from it<br />
<br />
===Transaction fees are paid in bytes===<br />
If you are in a new smart wallet and trying to send blackbytes, or some [[asset|new asset]] (like [[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.<br />
<br />
====Zero out the smart wallet====<br />
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.<br />
<br />
When all balances in a smart wallet are zero, it will disappear (hooray!).<br />
<br />
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.<br />
<br />
==Backup==<br />
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.<br />
<br />
==Convert==<br />
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. <br />
<br />
In this case, follow these steps to get access to your bytes (not blackbytes):<br />
<br />
#On a separate device, download and install a light platform<br />
#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<br />
#That person then sends your funds to your new light platform<br />
#Continue to use the light platform<br />
<br />
To get access to your blackbytes, either <br />
*Wait until the full platform syncs, then send the blackbytes to the light platform (after pairing); or<br />
*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).<br />
<br />
User data directory in Windows, for example, is found at C:\Users\Alice\AppData\Local\byteball\User Data<br />
<br />
==Reinstall platform==<br />
To start from scratch, you have to rename or delete the Obyte 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.<br />
<br />
===Rename or delete this folder before reinstall===<br />
*Windows: %LOCALAPPDATA%\obyte<br />
*MacOS: ~/Library/Application Support/obyte<br />
*Linux: ~/.config/obyte<br />
<br />
===Changing operating systems===<br />
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.<br />
<br />
==Wallet and explorer differ==<br />
Does explorer.obyte.org show some new bytes have arrived, but they don't show in your wallet? <br />
<br />
'''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 [[error]], this lack of proper connection must get fixed. <br />
<br />
*Firewall problem? <br />
*Tor turned on by mistake? ('''Check''' this at Settings > TOR, don't just assume it isn't turned on)<br />
*Something else wrong?<br />
<br />
'''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.<br />
<br />
'''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. <br />
<br />
'''Latest version?''' You '''are''' running the latest version, right?<br />
<br />
==Sync problems==<br />
<br />
===Android===<br />
<br />
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.<br />
<br />
===Full platform may be better===<br />
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.<br />
<br />
==External links==<br />
*Bitcoin Improvement Proposal 44<ref>https://en.bitcoin.it/wiki/BIP_0044</ref><br />
*Paper Wallet generator: https://bonuschain.github.io/byteball-paperwallet/<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Features]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Wallet&diff=1519Wallet2020-01-12T14:12:28Z<p>Slackjore: updated cogwheel menu information</p>
<hr />
<div>'''Terminology:''' What you download and install on a device (smartphone, laptop, pc etc) is here referred to as the Obyte 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. <br />
<br />
[[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.<br />
<br />
==Obyte platform==<br />
To start, download and install a platform from those listed at obyte.org or Github: releases<ref>https://github.com/byteball/byteball/releases</ref> (includes win32, but not for XP). <br />
<br />
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.<br />
<br />
===Multiple devices===<br />
If you want a connected Obyte wallet on your pc and another one on your Android smartphone, choose the multi-device option [[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.<br />
<br />
====Convenience vs security====<br />
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. <br />
<br />
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.<br />
<br />
===Independent or connected?===<br />
'''Independent:''' Useful for experimenting, seeing what happens when you interact with another Obyte user in chat. Use (plain) default Small Expenses Wallet on each device.<br />
<br />
'''Connected:''' Useful for security. Will show the same balance and history across all devices.<br />
<br />
===Pairing===<br />
Alice has Obyte 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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
===Light/easy or full/hard platform?===<br />
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><br />
<br />
===Single-address wallet===<br />
A single-address wallet (platform version 1.11.0 on) you create will not generate the usual new [[change address]]. Change will always go to the one-and-only address the wallet contains.<br />
<br />
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 [[Trading prediction markets|prediction market]] for a future event, enable users to make contracts (bets) referencing your address as an [[Oracle#Personal_oracles|oracle]], and when the outcome of the event is known you post its result from your wallet.<br />
<br />
In this version you can also manually attest other users and post arbitrary data into the Obyte DAG.<br />
<br />
====Attestation====<br />
To facilitate [[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><br />
<br />
==Multiple screens==<br />
<br />
The default wallet is named "Small Expenses Wallet", and has two screens: one for bytes, one for blackbytes. Every [[Asset|new asset]] you receive (CK1's, [[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.<br />
<br />
==Update==<br />
When doing a routine update, first do a full back-up using the Obyte 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. <br />
<br />
==Main menu options==<br />
<br />
===Add wallet===<br />
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.<br />
<br />
A multi-device wallet is duplicated across each of the paired devices, showing the same transactions, addresses, balances etc.<br />
<br />
====Signatures====<br />
*A 1-of-2 set-up means two devices and either one is sufficient to send a transaction. <br />
*A 2-of-2 set-up means two devices and both signatures are needed to send a transaction. <br />
*A 2-of-4 set-up means four devices and two signatures are needed to send a transaction.<br />
<br />
===Paired devices===<br />
<br />
====Contacts====<br />
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.<br />
<br />
====Bot store====<br />
Currently shows about 20 bots. See wiki article [[Chatbot]] for details.<br />
<br />
===Settings = Global preferences===<br />
<br />
'''Device name:''' Change it if you wish. If you chat to someone, they will see this name<br />
<br />
'''Hub:''' Default is <code>obyte.org/bb</code>. You can change it<br />
<br />
'''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<br />
<br />
'''Language:''' Select from 18 or so<br />
<br />
'''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<br />
<br />
'''Unit for blackbytes:''' Select from kBB, MBB or GBB<br />
<br />
'''Enable push notifications:''' (Android) toggle on or off<br />
<br />
'''TRUSTED NODES'''<br />
<br />
'''Witnesses:''' Easiest to select "Auto-update the witness list from the hub". See wiki [[Witness]] article for harder options<br />
<br />
'''Email attestor''' <code>H5EZTQE7ABFH27AUDTQFMZIALANK6RBG</code> is the default. You can change this, but don't unless you know what you are doing<br />
<br />
'''DEVICE ADDRESS:''' <code>0VCPO8MYDRN2E3N5JDRHRSTVEVZSZYARM</code> for example. This doesn't change, and will be visible to anyone you pair with for chat<br />
<br />
SPENDING RESTRICTIONS<br /><br />
'''Request password:''' Lets you set up a password that will encrypt your platform/wallets. Don't forget it! There is no password recovery option<br />
<br />
'''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")<br />
<br />
'''Recovery from seed:''' Recovery is available in single-sig (i.e., not multi-sig) light wallets from version 1.10.1. <br />
<br />
'''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.<br />
<br />
'''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.<br />
<br />
'''About Obyte:''' Version number, commit hash (developer thing), terms of use, translators credits, session log<br />
<br />
==Cogwheel preferences==<br />
<br />
'''Wallet alias:''' change local name (it means "platform alias")<br />
<br />
'''Color:''' 12 to choose from<br />
<br />
'''Single address wallet:''' Will not create new change addresses for every transaction. Change will always go to the one and only address the wallet contains. Needed for registered/attested addresses, personal oracles, and more.<br />
<br />
'''Hidden assets:''' Toggle on/off any of your assets. Useful for reducing clutter.<br />
<br />
'''Advanced:''' (under next heading)<br />
<br />
===Wallet information===<br />
<br />
'''Wallet name (at creation):''' whatever name you gave the wallet first<br />
<br />
'''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<br />
<br />
'''Wallet configuration (m-n):''' multiple-signature configuration, like 1 of 1, 1 of 2, 2 of 2, 2 of 3 etc<br />
<br />
'''Derivation strategy:''' BIP44: standard method of deriving new keys for addresses<ref> [https://en.bitcoin.it/wiki/BIP_0044 Improvement Proposal 44]</ref><br />
<br />
'''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.<br />
<br />
'''CO-SIGNERS'''<br />
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<br />
<br />
'''EXTENDED PUBLIC KEYS:'''<br />
*'''Me''' xpub... (this wallet's xpub) <br />
<br />
*(Other wallet's name, if multi-sig) xpub... (that wallet's xpub)<br />
<br />
'''ALL WALLET ADDRESSES:''' (examples shown)<br />
<br />
65C...AW6<br /><br />
m/44'/0'/1'/0/0 · April 19th 2017, 3:00 pm<br />
<br />
7SV...MMM<br /><br />
m/44'/0'/1'/0/1 · April 22nd 2017, 5:47 pm<br />
<br />
MR3...APD<br /><br />
m/44'/0'/1'/1/0 · April 26th 2017, 1:34 pm<br />
<br />
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.<br />
<br />
'''BALANCE BY ADDRESS:''' (examples shown)<br />
7SV...MMM<br /><br />
0.04 GBB<br />
<br />
O3J...YL5<br /><br />
0.024402 MB<br />
<br />
RAZ...LIM<br /><br />
0.05966 MB<br /><br />
55 Zwib by Jore Bohne (new [[asset]], registered)<br /><br />
576 of 3kc7H8A2oiWr8mv7AcWJeLCA0Cp8c3BLK04kYQ+5pfU= (new asset, unregistered)<br /><br />
0.085248 GBB<br />
<br />
UQX...EC6<br /><br />
0.117889 MB<br />
<br />
===Sweep paper wallet===<br />
*This gives an option to scan QR code of paper wallet private key <br />
*If anyone sees an Obyte paper wallet generator (not a textcoin), please tell me (Slackjore)<br />
<br />
===Delete wallet===<br />
What it says, big red button on the next screen<br />
<br />
==Smart wallets==<br />
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.<br />
<br />
===Confirmed funds===<br />
You need transactions to confirm before <br />
*A smart wallet first becomes visible <br />
*You can spend funds from it<br />
<br />
===Transaction fees are paid in bytes===<br />
If you are in a new smart wallet and trying to send blackbytes, or some [[asset|new asset]] (like [[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.<br />
<br />
====Zero out the smart wallet====<br />
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.<br />
<br />
When all balances in a smart wallet are zero, it will disappear (hooray!).<br />
<br />
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.<br />
<br />
==Backup==<br />
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.<br />
<br />
==Convert==<br />
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. <br />
<br />
In this case, follow these steps to get access to your bytes (not blackbytes):<br />
<br />
#On a separate device, download and install a light platform<br />
#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<br />
#That person then sends your funds to your new light platform<br />
#Continue to use the light platform<br />
<br />
To get access to your blackbytes, either <br />
*Wait until the full platform syncs, then send the blackbytes to the light platform (after pairing); or<br />
*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).<br />
<br />
User data directory in Windows, for example, is found at C:\Users\Alice\AppData\Local\byteball\User Data<br />
<br />
==Reinstall platform==<br />
To start from scratch, you have to rename or delete the Obyte 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.<br />
<br />
===Rename or delete this folder before reinstall===<br />
*Windows: %LOCALAPPDATA%\obyte<br />
*MacOS: ~/Library/Application Support/obyte<br />
*Linux: ~/.config/obyte<br />
<br />
===Changing operating systems===<br />
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.<br />
<br />
==Wallet and explorer differ==<br />
Does explorer.obyte.org show some new bytes have arrived, but they don't show in your wallet? <br />
<br />
'''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 [[error]], this lack of proper connection must get fixed. <br />
<br />
*Firewall problem? <br />
*Tor turned on by mistake? ('''Check''' this at Settings > TOR, don't just assume it isn't turned on)<br />
*Something else wrong?<br />
<br />
'''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.<br />
<br />
'''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. <br />
<br />
'''Latest version?''' You '''are''' running the latest version, right?<br />
<br />
==Sync problems==<br />
<br />
===Android===<br />
<br />
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.<br />
<br />
===Full platform may be better===<br />
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.<br />
<br />
==External links==<br />
*Bitcoin Improvement Proposal 44<ref>https://en.bitcoin.it/wiki/BIP_0044</ref><br />
*Paper Wallet generator: https://bonuschain.github.io/byteball-paperwallet/<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Features]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Chatbot&diff=1518Chatbot2020-01-12T13:21:00Z<p>Slackjore: updated bot list</p>
<hr />
<div>The [[wallet]] contains a Bot Store under the Chat [[tab]]. Inside the Bot Store are Chatbots.<br />
==Introduction==<br />
You can [[glossary|PAIR]] your platform with another platform on a separate device, via the Chat tab. If both devices are present, this is useful for practising with [[textcoin]]s and [[smart contract]]s. It also works when the other device is remote, enabling end-to-end-encrypted chat with strangers online, as well as sending private payments and using smart contracts with them.<br />
<br />
You can also pair your device with a bot, which emulates the experience of chatting with a live person. The bot will have very limited responses, but enough to get the job done. A merchant bot could allow you to select from a range of pizzas, for example, then pay for your order with two clicks while still in that chat session.<br />
<br />
These bots '''are''' the applications on the Obyte [[platform]].<br />
<br />
===Translations===<br />
A project to translate these bots started in March 2018. The [[All translations]] page tracks which languages have been completed for which bots. <br />
<br />
==Botstore bots==<br />
Obyte v.1.9.0+ has a "bot store". Your hub provides the list, sorted alphabetically or in suggested order. The default hub has these currently (alphabetically):<br />
<br />
*Accredited investor attestation bot<br />
*Blackbyte Exchange (Semi-trustless^)<br />
*BTC oracle<br />
*Buy blackbytes (trustless)<br />
*Byte-BTC exchange <br />
*Draw Airdrop<br />
*Email attestation bot<br />
*Exchange bot<br />
*Flight delay insurance<br />
*Flight delays oracle <br />
*Fun-coins faucet<br />
*Know-it-all Bot<br />
*Obyte Asset Manager<br />
*Poll bot<br />
*Private room chat bot<br />
*Real name attestation bot<br />
*Slice&Dice MUD <br />
*Sports betting bot (Semi-trustless)<br />
*Sports oracle<br />
*Steem attestation bot<br />
*Username registration bot<br />
*WhiteLittle Airdrop<br />
*Whitelittle reward chat room<br />
*World Community Grid linking bot<br />
*Zork | game <br />
*Luckybytes<br />
<br />
^ Ideally, crypto transactions are trustless, in that neither the sender nor the receiver need trust the other. The more trustful the situation is, the less ideal.<br />
<br />
==Other bots==<br />
*Byteball-to-TCP proxy<br />
<br />
==Other bots descriptions==<br />
===Byteball-to-TCP proxy===<br />
With the help of this specialized chatbot it is possible to develop one's new bot in any programming language. See the [[Dev|Obyte-to-TCP Proxy]] article section.<br />
<br />
==Botstore bots descriptions==<br />
Bot links are not needed in this article. Access them via the Bot Store in your platform/wallet Chat.<br />
<br />
===Accredited investor attestation bot===<br />
If you are an accredited investor, have your accredited status verified by a licensed attorney and get access to ICOs that sell security tokens to accredited investors only.<br />
<br />
Actual verification is outsourced to verifyinvestor.com which already provided this service to a number of ICOs. A licensed attorney checks the submitted documents and confirms the accredited status, then our bot (which is also a witness) posts the attestation record to the DAG. With this record, the issuers can easily see that an investor is accredited, therefore allowed to buy securities.<ref>https://medium.com/byteball/attestation-of-accredited-investors-d4a8dabf683b</ref><br />
<br />
=== Blackbytes Exchange (Semi-trustless) ===<br />
Instantly exchange Blackbytes and Bytes or create your own orders in the book. It's trustless when selling Blackbytes, meaning all users are always in control of their own Blackbytes, and trustful when buying. Need help or want to socialize? You can directly chat with many other users.<br />
<br />
===BTC oracle===<br />
This oracle posts Merkle Roots of all Bitcoin transactions in a block every time a new Bitcoin block is mined. You can use its data to p2p trade bytes and bitcoins. If you are receiving bytes (sending btc), chat with the oracle after sending your bitcoins to get the Merkle Proof of your Bitcoin transaction and unlock your bytes from the smart contract.<br />
<br />
===Buy blackbytes (trustless)===<br />
Instantly buy blackbytes for bytes. The sale is done via a conditional payment smart contract, so the seller can't scam you.<br />
<br />
Source code: https://github.com/byteball/conditional-token-sale, you can use it to sell your tokens.<br />
<br />
===Byte-BTC exchange===<br />
This provides a book for users. See the wiki article [[Trading]] for details. Note that Bitcoin transaction fees may cause problems with this bot, and you might find a regular exchange better.<br />
<br />
===Draw Airdrop===<br />
Get a chance to win a weekly prize just by linking your existing balance. The greater is your balance, the greater is your chance to win. No payment is required. The prizes are paid from the undistributed funds.<br />
<br />
If you refer new users to the draw and one of them wins, you also win.<br />
<br />
See Medium article<ref>https://medium.com/byteball/weekly-draw-for-the-byteball-community-f464ae731c88</ref> and Steemit article<ref>https://steemit.com/byteball/@byteball.org/weekly-draw-for-the-byteball-community</ref><br />
<br />
===Email attestation bot===<br />
Verify your email address, and your payers don't need to know your Obyte address any longer: they just write your email address as recipient. Note that sending funds to your email address only works with a public attestation in the bot, not a private one. <br />
<br />
See the [[Attestation#Email_attestation|Attestation]] article for detailed instructions for people new to Obyte.<br />
<br />
After the first successful verification, you are rewarded with $10.00 worth of Bytes from the distribution fund if your email is on one of the whitelisted domains (@harvard.edu and @eesti.ee).<ref>https://medium.com/byteball/distribution-to-verified-emails-and-sending-cryptocurrency-to-email-episode-ii-cb955fe19d7e</ref><br />
<br />
===Exchange bot===<br />
Exchange Obyte-issued tokens against Bytes or token vs token. The exchange is based on smart contracts, so you don't have to trust the exchange operator. This is intended for proper ICOs, not for some casual [[token]] you just created.<br />
<br />
After opening the bot, type "pairs" to see what is available.<br />
<br />
=== Flight delay insurance ===<br />
This allows one to take out insurance on a possible flight delay one day to three months in the future. See the wiki article [[Oracle]] for details.<br />
<br />
===Flight delays oracle===<br />
Used in conjunction with flight delay insurance.<br />
<br />
===Fun-coins faucet===<br />
[[File:Faucet.jpg|thumb|upright=0.66]]This bot gives out free Tangos, Tingos, Zangos, Zingos and Credits. These [[fun-coins]] have zero monetary value so you can practise textcoins and smart contracts with zero risk.<br />
<br />
* '''NOTE: To send fun-coins from your wallet, you will need Bytes to cover the transaction fees, less than 1000 bytes per transaction.'''<br />
<br />
If you wish, you can donate small amounts of Bytes for transaction fees to the sending address, CARJFJ6SKDC2XGLX2XSNMIITAVRDEW2R, but it is not necessary.<br />
<br />
Developer<ref>https://papabyte.com (@neversaynever)</ref><br />
<br />
=== Know-it-all Bot ===<br />
This bot is all about user participation and giving gratitude using incentivized Q&A. Users pose questions and add reward with bytes for faster replies, better answers and more importantly to give thanks to participants. Bring in experts on any social platform using a simple link, vote for the right answer and both of you can get rewarded!<br />
<br />
This bot was first developed for the [[Use-a-thon/botwar|Byteball Bot War]] in December 2018.<br />
<br />
Developer: Terence Lee, https://github.com/whoisterencelee/know-it-all-bot<br />
<br />
===Obyte Asset Manager===<br />
See the wiki article [[Asset]] for details.<br />
<br />
===Poll bot===<br />
Now we can have referendums. This bot assists in making a vote. A vote is a small transaction that pays to yourself and is signed by your most funded addresses; the '''weight''' of the vote is the combined balance of the signing addresses. Note that there is a privacy concern because by making a vote you associate a number of your addresses. <br />
<br />
===Private Room Chat bot===<br />
This chatbot allows several persons to chat together using the Obyte messaging system. The bot decrypts messages and relays them to other users after re-encryption. For best privacy, run your own instance of this bot using the source code below; any cheap Virtual Private Server is enough to host it.<br />
<br />
Developer: Papabyte, https://github.com/Papabyte/Private-chat-room<br />
<br />
===Real name attestation bot===<br />
Verify your real name to get access to services that require KYC. Attestation that proves your verification is saved on the public database, but no personal data is published without your request. Your data is saved in your wallet and you can easily disclose it to the service that needs the data. After first successful verification, you are rewarded with $20.00 worth of Bytes from the distribution fund. See [[Identity verification]] article for details.<br />
<br />
===Slice&Dice MUD [Multi-User Dungeon]===<br />
Combining the elements of provably fair online gambling and role-playing games, Slice&Dice Dungeon delivers a unique gaming experience for everyone. The player takes a role of a dungeon inhabitant who has come across a violent underground casino. The main goal in this game is to become a powerful and respected member of the community. Doing so requires one to gamble on the Obyte tokens and to get into fights with other players as part of the endless struggle for power.<br />
<br />
Developer<ref>https://CoinGaming.io</ref><br />
<br />
===Sports betting bot (Semi-trustless)===<br />
Bet on sport fixtures by taking the trustless offers immediately available. Or be the bookmaker and develop a business by proposing competitive odds for popular events.<br />
<br />
There's an extensive wiki article about [[Sports_betting|sports betting]] and this bot.<br />
<br />
Developer<ref>https://papabyte.com</ref><br />
<br />
===Sports oracle===<br />
The sports oracle posts a [[Glossary|DATAFEED]] line only for those fixtures requested by users through the chat. See the wiki article [[Sports betting]] for details.<br />
<br />
===Steem attestation bot===<br />
Verify your Steem username, and your payers don't need to know your Obyte address any longer: they just write <code>steem/username</code> as recipient. After first successful verification you get a reward in Bytes, the amount depending on your Steem reputation. Other apps offer discounts or bonuses to users with high reputation. These apps include: ICOs, Real name attestation bot, Buy Bytes with Visa or Mastercard bot.<br />
<br />
Also see the wiki [[Attestation#Steem_attestation|Attestation]] article.<br />
<br />
If you have a question regarding steem attestations please submit the details through [https://docs.google.com/forms/d/e/1FAIpQLSdpZ4xwMCbndTsdKdoxT3O-LmAZx0h_R4dzxncA-jH9FOTlcQ/viewform?usp=sf_link this Google Form].<br />
<br />
===Username registration bot===<br />
Buy a username and receive money to your @username instead of a less user-friendly cryptocurrency address. Proceeds from the sale of usernames go the [[Obyte community fund]] and help fund the development and promotion of the platform.<br />
<br />
===WhiteLittle Airdrop===<br />
This is for the Chinese market.<br />
<br />
Project website: http://123cb.net, in Chinese only.<br />
<br />
===Whitelittle reward chat room===<br />
Whitelittle is a chat room (in Chinese) for newcomers who want to enter the blockchain industry. The purpose is to build an information discovery ecological platform that provides effective help for newcomers based on the Obyte technology. Here you can chat and help others without being censored and get some rewards.<br />
<br />
===World Community Grid linking bot===<br />
Donate your device’s spare computing power to help scientists solve the world’s biggest problems in health and sustainability, and [[Distribution#From_the_WCG_linking_bot|earn some Bytes]] in the meantime. This bot allows you to link your Obyte address and WCG account in order to receive daily rewards for your contribution to WCG computations.<ref>https://medium.com/byteball/computing-for-good-again-3795336bdaed</ref><br />
<br />
WCG is an IBM sponsored project; more info at https://www.worldcommunitygrid.org<br />
<br />
===Zork | game===<br />
Play one of the earliest interactive fiction computer games developed between 1977 and 1979. The game unfolds in a maze-like dungeon, where the user must battle trolls and solve puzzles in order to find twenty trophies to bring back to the house outside which the game begins.<br />
<br />
Developer: @Hyena<br />
<br />
=== Luckybytes ===<br />
A lottery which you can play using your Bytes. Three different game modes to participate in and follow the principle of "the winner takes all". All games are provably fair. Each lottery comes with a game proof hash which lets player validate and prove the results against manipulation. [Available in Chinese too]<br />
<br />
https://lucky.obytechina.org<br />
<br />
==Security==<br />
<blockquote>'''Slack comment from @vakar 2018-01-10:''' A bot has no way to connect to the private part of a paired wallet. It can only send text messages to the chat. As long as we only have text (and no html) all bots are safe and cannot "steal coins".</blockquote><br />
<br />
==External links==<br />
*[https://byteroll.com/chatbox Main article source]<br />
*[https://medium.com/@wekkelekkel/byteball-e-mail-attestation-tutorial-5b4b9dfc4e04 Email attestation tutorial]<br />
*[https://medium.com/obyte/new-methods-for-identity-verification-3d5045287533 Alternative method for residents of Estonia, Latvia, Lithuania, and e-residents of Estonia]<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Features]]<br />
[[Category:Chatbots]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=PolloPollo&diff=1517PolloPollo2020-01-01T13:47:43Z<p>Slackjore: added explanatory video</p>
<hr />
<div>== Overview ==<br />
PolloPollo is an Obyte project run by Casper Niebe to:<br />
*Facilitate charitable donations being used as the donor intended, initially in Venezuela<br />
*Showcase the use of standard Obyte tools to do this<br />
<br />
The project website at www.pollopollo.org is online, but not yet (December 2019) fully up to speed.<br />
<br />
{{#ev:youtube|https://www.youtube.com/watch?v=v8nxs0YRwUQ|200|right}}<br />
*Here is a short 2-minute video in English explaining how the platform works<br />
{{clear}}<br />
<br />
== External links ==<br />
*[https://www.telegraph.co.uk/global-health/science-and-disease/cyptocurrency-platform-delivers-food-medicine-struggling-venezuelans/ Telegraph article 22 July 2019]<br />
*[https://www.cityam.com/wp-content/uploads/2019/07/016-017Crypto-23Jul2019-1.pdf CityAm article 23 July 2019 (PDF)]<br />
*[https://www.youtube.com/watch?v=2W3XCSLQsAA Explainer video in Spanish]<br />
*[https://es.cointelegraph.com/news/blockchain-solutions-to-help-venezuelans-were-awarded-at-the-b4h-awards-2019 CoinTelegraph article in Spanish about B4H award for PolloPollo]<br />
<br />
== References ==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Chatbot&diff=1516Chatbot2020-01-01T12:22:13Z<p>Slackjore: updated info on the 4 ICO bots</p>
<hr />
<div>The [[wallet]] contains a Bot Store under the Chat [[tab]]. Inside the Bot Store are Chatbots.<br />
==Introduction==<br />
You can [[glossary|PAIR]] your platform with another platform on a separate device, via the Chat tab. If both devices are present, this is useful for practising with [[textcoin]]s and [[smart contract]]s. It also works when the other device is remote, enabling end-to-end-encrypted chat with strangers online, as well as sending private payments and using smart contracts with them.<br />
<br />
You can also pair your device with a bot, which emulates the experience of chatting with a live person. The bot will have very limited responses, but enough to get the job done. A merchant bot could allow you to select from a range of pizzas, for example, then pay for your order with two clicks while still in that chat session.<br />
<br />
These bots '''are''' the applications on the Obyte [[platform]].<br />
<br />
===Translations===<br />
A project to translate these bots started in March 2018. The [[All translations]] page tracks which languages have been completed for which bots. <br />
<br />
==Botstore bots==<br />
Obyte v.1.9.0+ has a "bot store". Your hub provides the list, sorted alphabetically or in suggested order. The default hub has these currently (alphabetically):<br />
<br />
*Accredited investor attestation bot<br />
*Blackbyte Exchange (Semi-trustless^)<br />
*BTC oracle<br />
*Buy blackbytes (trustless)<br />
*Byte-BTC exchange <br />
*Byteball [Obyte] Asset Manager<br />
*ClearCost ICO booking hotels at cost price<br />
*Dice bot<br />
*Draw Airdrop<br />
*Email attestation bot<br />
*Exchange bot<br />
*Flight delay insurance<br />
*Flight delays oracle <br />
*Fun-coins faucet<br />
*Know-it-all Bot<br />
*Nousplatform ICO<br />
*Poll bot<br />
*Private room chat bot<br />
*Real name attestation bot<br />
*Slice&Dice MUD <br />
*Sports betting bot (Semi-trustless)<br />
*Sports oracle<br />
*Steem attestation bot<br />
*TitanCoin ICO<br />
*Username registration bot<br />
*WhiteLittle Airdrop<br />
*Whitelittle reward chat room<br />
*World Community Grid linking bot<br />
*Worldopoly ICO<br />
*Zork | game <br />
<br />
^ Ideally, crypto transactions are trustless, in that neither the sender nor the receiver need trust the other. The more trustful the situation is, the less ideal.<br />
<br />
==Other bots==<br />
*Byteball-to-TCP proxy<br />
<br />
==Other bots descriptions==<br />
===Byteball-to-TCP proxy===<br />
With the help of this specialized chatbot it is possible to develop one's new bot in any programming language. See the [[Dev|Obyte-to-TCP Proxy]] article section.<br />
<br />
==Botstore bots descriptions==<br />
Bot links are not needed in this article. Access them via the Bot Store in your platform/wallet Chat.<br />
<br />
===Accredited investor attestation bot===<br />
If you are an accredited investor, have your accredited status verified by a licensed attorney and get access to ICOs that sell security tokens to accredited investors only.<br />
<br />
Actual verification is outsourced to verifyinvestor.com which already provided this service to a number of ICOs. A licensed attorney checks the submitted documents and confirms the accredited status, then our bot (which is also a witness) posts the attestation record to the DAG. With this record, the issuers can easily see that an investor is accredited, therefore allowed to buy securities.<ref>https://medium.com/byteball/attestation-of-accredited-investors-d4a8dabf683b</ref><br />
<br />
=== Blackbytes Exchange (Semi-trustless) ===<br />
Instantly exchange Blackbytes and Bytes or create your own orders in the book. It's trustless when selling Blackbytes, meaning all users are always in control of their own Blackbytes, and trustful when buying. Need help or want to socialize? You can directly chat with many other users.<br />
<br />
===BTC oracle===<br />
This oracle posts Merkle Roots of all Bitcoin transactions in a block every time a new Bitcoin block is mined. You can use its data to p2p trade bytes and bitcoins. If you are receiving bytes (sending btc), chat with the oracle after sending your bitcoins to get the Merkle Proof of your Bitcoin transaction and unlock your bytes from the smart contract.<br />
<br />
===Buy blackbytes (trustless)===<br />
Instantly buy blackbytes for bytes. The sale is done via a conditional payment smart contract, so the seller can't scam you.<br />
<br />
Source code: https://github.com/byteball/conditional-token-sale, you can use it to sell your tokens.<br />
<br />
===Byte-BTC exchange===<br />
This provides a book for users. See the wiki article [[Trading]] for details. Note that Bitcoin transaction fees may cause problems with this bot, and you might find a regular exchange better.<br />
<br />
===Byteball [Obyte] Asset Manager===<br />
See the wiki article [[Asset]] for details.<br />
<br />
=== ClearCost ICO: booking hotels at cost price===<br />
At 1 Jan 2020, their website says "This blockchain project finished. The idea of creating a discount club for crypto-enthusiasts turned out to be wrong."<br />
<br />
Website: https://clearcost.io<br />
<br />
===Dice bot===<br />
A very simple, and provably fair, dice game.<br />
<br />
Developer: Evgeny Stulnikov<br />
<br />
===Draw Airdrop===<br />
Get a chance to win a weekly prize just by linking your existing balance. The greater is your balance, the greater is your chance to win. No payment is required. The prizes are paid from the undistributed funds.<br />
<br />
If you refer new users to the draw and one of them wins, you also win.<br />
<br />
See Medium article<ref>https://medium.com/byteball/weekly-draw-for-the-byteball-community-f464ae731c88</ref> and Steemit article<ref>https://steemit.com/byteball/@byteball.org/weekly-draw-for-the-byteball-community</ref><br />
<br />
===Email attestation bot===<br />
Verify your email address, and your payers don't need to know your Obyte address any longer: they just write your email address as recipient. Note that sending funds to your email address only works with a public attestation in the bot, not a private one. <br />
<br />
See the [[Attestation#Email_attestation|Attestation]] article for detailed instructions for people new to Obyte.<br />
<br />
After the first successful verification, you are rewarded with $10.00 worth of Bytes from the distribution fund if your email is on one of the whitelisted domains (@harvard.edu and @eesti.ee).<ref>https://medium.com/byteball/distribution-to-verified-emails-and-sending-cryptocurrency-to-email-episode-ii-cb955fe19d7e</ref><br />
<br />
===Exchange bot===<br />
Exchange Obyte-issued tokens against Bytes or token vs token. The exchange is based on smart contracts, so you don't have to trust the exchange operator. This is intended for proper ICOs, not for some casual [[token]] you just created.<br />
<br />
After opening the bot, type "pairs" to see what is available.<br />
<br />
=== Flight delay insurance ===<br />
This allows one to take out insurance on a possible flight delay one day to three months in the future. See the wiki article [[Oracle]] for details.<br />
<br />
===Flight delays oracle===<br />
Used in conjunction with flight delay insurance.<br />
<br />
===Fun-coins faucet===<br />
[[File:Faucet.jpg|thumb|upright=0.66]]This bot gives out free Tangos, Tingos, Zangos, Zingos and Credits. These [[fun-coins]] have zero monetary value so you can practise textcoins and smart contracts with zero risk.<br />
<br />
* '''NOTE: To send fun-coins from your wallet, you will need Bytes to cover the transaction fees, less than 1000 bytes per transaction.'''<br />
<br />
If you wish, you can donate small amounts of Bytes for transaction fees to the sending address, CARJFJ6SKDC2XGLX2XSNMIITAVRDEW2R, but it is not necessary.<br />
<br />
Developer<ref>https://papabyte.com (@neversaynever)</ref><br />
<br />
=== Know-it-all Bot ===<br />
This bot is all about user participation and giving gratitude using incentivized Q&A. Users pose questions and add reward with bytes for faster replies, better answers and more importantly to give thanks to participants. Bring in experts on any social platform using a simple link, vote for the right answer and both of you can get rewarded!<br />
<br />
This bot was first developed for the [[Use-a-thon/botwar|Byteball Bot War]] in December 2018.<br />
<br />
Developer: Terence Lee, https://github.com/whoisterencelee/know-it-all-bot<br />
<br />
===Nousplatform ICO===<br />
At 1 Jan 2020 this operation now uses AIV, an ERC20 (Ethereum) token. Around July 2019 Nousplatform was rebranded to AIVIA, website https://aivia.io.<br />
<br />
===Poll bot===<br />
Now we can have referendums. This bot assists in making a vote. A vote is a small transaction that pays to yourself and is signed by your most funded addresses; the '''weight''' of the vote is the combined balance of the signing addresses. Note that there is a privacy concern because by making a vote you associate a number of your addresses. <br />
<br />
===Private Room Chat bot===<br />
This chatbot allows several persons to chat together using the Obyte messaging system. The bot decrypts messages and relays them to other users after re-encryption. For best privacy, run your own instance of this bot using the source code below; any cheap Virtual Private Server is enough to host it.<br />
<br />
Developer: Papabyte, https://github.com/Papabyte/Private-chat-room<br />
<br />
===Real name attestation bot===<br />
Verify your real name to get access to services that require KYC. Attestation that proves your verification is saved on the public database, but no personal data is published without your request. Your data is saved in your wallet and you can easily disclose it to the service that needs the data. After first successful verification, you are rewarded with $20.00 worth of Bytes from the distribution fund. See [[Identity verification]] article for details.<br />
<br />
===Slice&Dice MUD [Multi-User Dungeon]===<br />
Combining the elements of provably fair online gambling and role-playing games, Slice&Dice Dungeon delivers a unique gaming experience for everyone. The player takes a role of a dungeon inhabitant who has come across a violent underground casino. The main goal in this game is to become a powerful and respected member of the community. Doing so requires one to gamble on the Obyte tokens and to get into fights with other players as part of the endless struggle for power.<br />
<br />
Developer<ref>https://CoinGaming.io</ref><br />
<br />
===Sports betting bot (Semi-trustless)===<br />
Bet on sport fixtures by taking the trustless offers immediately available. Or be the bookmaker and develop a business by proposing competitive odds for popular events.<br />
<br />
There's an extensive wiki article about [[Sports_betting|sports betting]] and this bot.<br />
<br />
Developer<ref>https://papabyte.com</ref><br />
<br />
===Sports oracle===<br />
The sports oracle posts a [[Glossary|DATAFEED]] line only for those fixtures requested by users through the chat. See the wiki article [[Sports betting]] for details.<br />
<br />
===Steem attestation bot===<br />
Verify your Steem username, and your payers don't need to know your Obyte address any longer: they just write <code>steem/username</code> as recipient. After first successful verification you get a reward in Bytes, the amount depending on your Steem reputation. Other apps offer discounts or bonuses to users with high reputation. These apps include: ICOs, Real name attestation bot, Buy Bytes with Visa or Mastercard bot.<br />
<br />
Also see the wiki [[Attestation#Steem_attestation|Attestation]] article.<br />
<br />
If you have a question regarding steem attestations please submit the details through [https://docs.google.com/forms/d/e/1FAIpQLSdpZ4xwMCbndTsdKdoxT3O-LmAZx0h_R4dzxncA-jH9FOTlcQ/viewform?usp=sf_link this Google Form].<br />
<br />
===TitanCoin ICO===<br />
At 1 Jan 2020 the website at https://titan-coin.com looks abandoned. The token "Titan Coin" on CoinMarketCap is not related.<br />
<br />
===Username registration bot===<br />
Buy a username and receive money to your @username instead of a less user-friendly cryptocurrency address. Proceeds from the sale of usernames go the [[Obyte community fund]] and help fund the development and promotion of the platform.<br />
<br />
===WhiteLittle Airdrop===<br />
This is for the Chinese market.<br />
<br />
Project website: http://123cb.net, in Chinese only.<br />
<br />
===Whitelittle reward chat room===<br />
Whitelittle is a chat room (in Chinese) for newcomers who want to enter the blockchain industry. The purpose is to build an information discovery ecological platform that provides effective help for newcomers based on the Obyte technology. Here you can chat and help others without being censored and get some rewards.<br />
<br />
===World Community Grid linking bot===<br />
Donate your device’s spare computing power to help scientists solve the world’s biggest problems in health and sustainability, and [[Distribution#From_the_WCG_linking_bot|earn some Bytes]] in the meantime. This bot allows you to link your Obyte address and WCG account in order to receive daily rewards for your contribution to WCG computations.<ref>https://medium.com/byteball/computing-for-good-again-3795336bdaed</ref><br />
<br />
WCG is an IBM sponsored project; more info at https://www.worldcommunitygrid.org<br />
<br />
===Worldopoly ICO===<br />
Bot text: <br />
<blockquote>Worldopoly is the world’s first mobile game combining AR (Augmented Reality), AI (Artificial Intelligence), Geolocationing, Blockchain, and DAG. The ICO is active until 17 May 2018, and you can buy WPT tokens with Bytes, BTC, or Ether. WPT token is issued both on Obyte and Ethereum platforms but investors on Obyte platform receive increased bonus (even if they pay in ETH or BTC) for investments up to 30 ETH.</blockquote><br />
<br />
At 1 Jan 2020 the name and website has changed to Worldopo at https://worldopo.io, but the organization and WPT token lives on.<br />
<br />
===Zork | game===<br />
Play one of the earliest interactive fiction computer games developed between 1977 and 1979. The game unfolds in a maze-like dungeon, where the user must battle trolls and solve puzzles in order to find twenty trophies to bring back to the house outside which the game begins.<br />
<br />
Developer: @Hyena<br />
<br />
==Security==<br />
<blockquote>'''Slack comment from @vakar 2018-01-10:''' A bot has no way to connect to the private part of a paired wallet. It can only send text messages to the chat. As long as we only have text (and no html) all bots are safe and cannot "steal coins".</blockquote><br />
<br />
==External links==<br />
*[https://byteroll.com/chatbox Main article source]<br />
*[https://medium.com/@wekkelekkel/byteball-e-mail-attestation-tutorial-5b4b9dfc4e04 Email attestation tutorial]<br />
*[https://medium.com/obyte/new-methods-for-identity-verification-3d5045287533 Alternative method for residents of Estonia, Latvia, Lithuania, and e-residents of Estonia]<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Features]]<br />
[[Category:Chatbots]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Blackbytes&diff=1515Blackbytes2019-12-31T16:47:04Z<p>Slackjore: typo</p>
<hr />
<div>One of the two Obyte currencies. When you want complete privacy, pay in blackbytes, a cash-like untraceable currency whose transactions are not visible on the public database. They are sent peer-to-peer instead. Blackbytes work better on laptop/desktop machines with more CPU power than smartphones.<br />
<br />
==Blackbytes==<br />
Blackbytes is the name of one, the first, defined private asset in Obyte. Obyte supports user-defined [[asset]]s, the assets has properties such as private or public, amount of coins, coin-denominations and if any authentifiers is required for transferring, or if the asset is transferrable.<br />
<br />
Blackbytes are defined as a private asset, meaning its never posted to the public Obyte database, it is ever only transferred when Obyte wallets have paired, private assets are sent encrypted through the Obyte network from device address to device address. When used over Tor, blackbytes become anonymous, and only the device-address can be known to the Obyte network.<br />
<br />
To verify that a peer has not sent the same blackbyte to another peer before attempting to trick you into accepting it again, a spend-proof is posted to the public Obyte database. Upon receiving the blackbyte your full-wallet/light-wallet-hub provider, checks the spend-proof. The spend-proof does not contain amounts or sender/receiver information, it is merely a signature.<br />
<br />
===Blackbyte Exchange===<br />
If blackbytes are traded on a centralized exchange, the exchange would have enough information to reveal the origin and destination of blackbytes, and amounts traded, which defeats their purpose. <br />
<br />
Blackbytes hence can only be traded on decentralized exchanges, with conditional payments in the Obyte wallet. Peer discovery has to happen outside the Obyte wallet. Such an exchange is yet (August 2018) to appear.<br />
<br />
===Recommended usage===<br />
#Start a light wallet on one of your computers/smartphones, do not use revealing device name for the wallet, pick something like localhost or Obyte. <br />
#Enable Tor in the Global settings menu, this requires that you have tor installed or Orbot on Android, a tor-proxy for any Android app. <br />
#Send your blackbytes to this wallet, and use it to trade with and pay for goods and services. <br />
<br />
===All private assets===<br />
With wallet 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.<br />
<br />
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><br />
<br />
==Good links==<br />
*Technical discussions<ref>https://bitcointalk.org/index.php?topic=1574508.msg15806728#msg15806728</ref><br />
<br />
*@loyce's bitcointalk Blackbytes FAQ<ref>https://bitcointalk.org/index.php?topic=2020882</ref><br />
<br />
==Sending==<br />
To receive blackbytes (BB/GBB) if you do not have any yet, try doing it this way: start a chat with paired device, click INSERT ADDRESS in chat menu, now the owner of the blackbytes can click your address and he will see an option to send blackbytes to you. You will need some bytes in your wallet to pay the fee for the blackbyte transfer.<br />
<br />
===Byte-BTC exchange===<br />
It is also possible to trade BTC and GBB as described in [[Trading#Peer-to-peer_Byte-BTC_exchange]], only using GBB instead of GB.<br />
<br />
==Buying/selling bytes/blackbytes==<br />
===Bot store===<br />
*[[Chatbot#Blackbytes_Exchange_.28Semi-trustless.29|Blackbyte Exchange (Semi-trustless)]]<br />
<br />
*[[Chatbot#Buy_blackbytes_.28trustless.29|Buy blackbytes (trustless)]]<br />
<br />
===Website===<br />
*https://blackbytes.io<br />
<br />
==External links==<br />
<br />
==References==<br />
<references /><br />
[[Category:Features]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Blackbytes&diff=1514Blackbytes2019-12-31T16:44:23Z<p>Slackjore: updated bots</p>
<hr />
<div>One of the two Obyte currencies. When you want complete privacy, pay in blackbytes, a cash-like untraceable currency whose transactions are not visible on the public database. They are sent peer-to-peer instead. Blackbytes work better on laptop/desktop machines with more CPU power than smartphones.<br />
<br />
==Blackbytes==<br />
Blackbytes is the name of one, the first, defined private asset in Obyte. Obyte supports user-defined [[asset]]s, the assets has properties such as private or public, amount of coins, coin-denominations and if any authentifiers is required for transferring, or if the asset is transferrable.<br />
<br />
Blackbytes are defined as a private asset, meaning its never posted to the public Obyte database, it is ever only transferred when Obyte wallets have paired, private assets are sent encrypted through the Obyte network from device address to device address. When used over Tor, blackbytes become anonymous, and only the device-address can be known to the Obyte network.<br />
<br />
To verify that a peer has not sent the same blackbyte to another peer before attempting to trick you into accepting it again, a spend-proof is posted to the public Obyte database. Upon receiving the blackbyte your full-wallet/light-wallet-hub provider, checks the spend-proof. The spend-proof does not contain amounts or sender/receiver information, it is merely a signature.<br />
<br />
===Blackbyte Exchange===<br />
If blackbytes are traded on a centralized exchange, the exchange would have enough information to reveal the origin and destination of blackbytes, and amounts traded, which defeats their purpose. <br />
<br />
Blackbytes hence can only be traded on decentralized exchanges, with conditional payments in the Obyte wallet. Peer discovery has to happen outside the Obyte wallet. Such an exchange is yet (August 2018) to appear.<br />
<br />
===Recommended usage===<br />
#Start a light wallet on one of your computers/smartphones, do not use revealing device name for the wallet, pick something like localhost or Obyte. <br />
#Enable Tor in the Global settings menu, this requires that you have tor installed or Orbot on Android, a tor-proxy for any Android app. <br />
#Send your blackbytes to this wallet, and use it to trade with and pay for goods and services. <br />
<br />
===All private assets===<br />
With wallet 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.<br />
<br />
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><br />
<br />
==Good links==<br />
*Technical discussions<ref>https://bitcointalk.org/index.php?topic=1574508.msg15806728#msg15806728</ref><br />
<br />
*@loyce's bitcointalk Blackbytes FAQ<ref>https://bitcointalk.org/index.php?topic=2020882</ref><br />
<br />
==Sending==<br />
To receive blackbytes (BB/GBB) if you do not have any yet, try doing it this way: start a chat with paired device, click INSERT ADDRESS in chat menu, now the owner of the blackbytes can click your address and he will see an option to send blackbytes to you. You will need some bytes in your wallet to pay the fee for the blackbyte transfer.<br />
<br />
===Byte-BTC exchange===<br />
It is also possible to trade BTC and GBB as described in [[Trading#Peer-to-peer_Byte-BTC_exchange]], only using GBB instead of GB.<br />
<br />
==Buying/selling bytes/blackbytes==<br />
===Bot store===<br />
*[[Chatbot#Blackbytes_Exchange_.28Semi-trustless|Blackbyte Exchange (Semi-trustless)]]<br />
<br />
*[[Chatbot#Buy_blackbytes_.28trustless.29|Buy blackbytes (trustless)]]<br />
<br />
===Website===<br />
*https://blackbytes.io<br />
<br />
==External links==<br />
<br />
==References==<br />
<references /><br />
[[Category:Features]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Chatbot&diff=1513Chatbot2019-12-31T16:15:08Z<p>Slackjore: updated bot list</p>
<hr />
<div>The [[wallet]] contains a Bot Store under the Chat [[tab]]. Inside the Bot Store are Chatbots.<br />
==Introduction==<br />
You can [[glossary|PAIR]] your platform with another platform on a separate device, via the Chat tab. If both devices are present, this is useful for practising with [[textcoin]]s and [[smart contract]]s. It also works when the other device is remote, enabling end-to-end-encrypted chat with strangers online, as well as sending private payments and using smart contracts with them.<br />
<br />
You can also pair your device with a bot, which emulates the experience of chatting with a live person. The bot will have very limited responses, but enough to get the job done. A merchant bot could allow you to select from a range of pizzas, for example, then pay for your order with two clicks while still in that chat session.<br />
<br />
These bots '''are''' the applications on the Obyte [[platform]].<br />
<br />
===Translations===<br />
A project to translate these bots started in March 2018. The [[All translations]] page tracks which languages have been completed for which bots. <br />
<br />
==Botstore bots==<br />
Obyte v.1.9.0+ has a "bot store". Your hub provides the list, sorted alphabetically or in suggested order. The default hub has these currently (alphabetically):<br />
<br />
*Accredited investor attestation bot<br />
*Blackbyte Exchange (Semi-trustless^)<br />
*BTC oracle<br />
*Buy blackbytes (trustless)<br />
*Byte-BTC exchange <br />
*Byteball [Obyte] Asset Manager<br />
*ClearCost ICO booking hotels at cost price<br />
*Dice bot<br />
*Draw Airdrop<br />
*Email attestation bot<br />
*Exchange bot<br />
*Flight delay insurance<br />
*Flight delays oracle <br />
*Fun-coins faucet<br />
*Know-it-all Bot<br />
*Nousplatform ICO<br />
*Poll bot<br />
*Private room chat bot<br />
*Real name attestation bot<br />
*Slice&Dice MUD <br />
*Sports betting bot (Semi-trustless)<br />
*Sports oracle<br />
*Steem attestation bot<br />
*TitanCoin ICO<br />
*Username registration bot<br />
*WhiteLittle Airdrop<br />
*Whitelittle reward chat room<br />
*World Community Grid linking bot<br />
*Worldopoly ICO<br />
*Zork | game <br />
<br />
^ Ideally, crypto transactions are trustless, in that neither the sender nor the receiver need trust the other. The more trustful the situation is, the less ideal.<br />
<br />
==Other bots==<br />
*Byteball-to-TCP proxy<br />
<br />
==Other bots descriptions==<br />
===Byteball-to-TCP proxy===<br />
With the help of this specialized chatbot it is possible to develop one's new bot in any programming language. See the [[Dev|Obyte-to-TCP Proxy]] article section.<br />
<br />
==Botstore bots descriptions==<br />
Bot links are not needed in this article. Access them via the Bot Store in your platform/wallet Chat.<br />
<br />
===Accredited investor attestation bot===<br />
If you are an accredited investor, have your accredited status verified by a licensed attorney and get access to ICOs that sell security tokens to accredited investors only.<br />
<br />
Actual verification is outsourced to verifyinvestor.com which already provided this service to a number of ICOs. A licensed attorney checks the submitted documents and confirms the accredited status, then our bot (which is also a witness) posts the attestation record to the DAG. With this record, the issuers can easily see that an investor is accredited, therefore allowed to buy securities.<ref>https://medium.com/byteball/attestation-of-accredited-investors-d4a8dabf683b</ref><br />
<br />
=== Blackbytes Exchange (Semi-trustless) ===<br />
Instantly exchange Blackbytes and Bytes or create your own orders in the book. It's trustless when selling Blackbytes, meaning all users are always in control of their own Blackbytes, and trustful when buying. Need help or want to socialize? You can directly chat with many other users.<br />
<br />
===BTC oracle===<br />
This oracle posts Merkle Roots of all Bitcoin transactions in a block every time a new Bitcoin block is mined. You can use its data to p2p trade bytes and bitcoins. If you are receiving bytes (sending btc), chat with the oracle after sending your bitcoins to get the Merkle Proof of your Bitcoin transaction and unlock your bytes from the smart contract.<br />
<br />
===Buy blackbytes (trustless)===<br />
Instantly buy blackbytes for bytes. The sale is done via a conditional payment smart contract, so the seller can't scam you.<br />
<br />
Source code: https://github.com/byteball/conditional-token-sale, you can use it to sell your tokens.<br />
<br />
===Byte-BTC exchange===<br />
This provides a book for users. See the wiki article [[Trading]] for details. Note that Bitcoin transaction fees may cause problems with this bot, and you might find a regular exchange better.<br />
<br />
===Byteball [Obyte] Asset Manager===<br />
See the wiki article [[Asset]] for details.<br />
<br />
=== ClearCost ICO: booking hotels at cost price===<br />
<blockquote>Clearcost.Club books accommodations in hotels worldwide cheaper than the lowest market price by 5% to 15% and more. ClearCost = Cost price + membership fee. The membership fee in CCWT tokens is about four times less than in USD, and this ratio will grow. CCWT are unique tokens with the economic justification for the price. Our ITO is active until October 31, 2018.</blockquote><br />
<br />
Website: https://clearcost.io<br />
<br />
===Dice bot===<br />
A very simple, and provably fair, dice game.<br />
<br />
Developer: Evgeny Stulnikov<br />
<br />
===Draw Airdrop===<br />
Get a chance to win a weekly prize just by linking your existing balance. The greater is your balance, the greater is your chance to win. No payment is required. The prizes are paid from the undistributed funds.<br />
<br />
If you refer new users to the draw and one of them wins, you also win.<br />
<br />
See Medium article<ref>https://medium.com/byteball/weekly-draw-for-the-byteball-community-f464ae731c88</ref> and Steemit article<ref>https://steemit.com/byteball/@byteball.org/weekly-draw-for-the-byteball-community</ref><br />
<br />
===Email attestation bot===<br />
Verify your email address, and your payers don't need to know your Obyte address any longer: they just write your email address as recipient. Note that sending funds to your email address only works with a public attestation in the bot, not a private one. <br />
<br />
See the [[Attestation#Email_attestation|Attestation]] article for detailed instructions for people new to Obyte.<br />
<br />
After the first successful verification, you are rewarded with $10.00 worth of Bytes from the distribution fund if your email is on one of the whitelisted domains (@harvard.edu and @eesti.ee).<ref>https://medium.com/byteball/distribution-to-verified-emails-and-sending-cryptocurrency-to-email-episode-ii-cb955fe19d7e</ref><br />
<br />
===Exchange bot===<br />
Exchange Obyte-issued tokens against Bytes or token vs token. The exchange is based on smart contracts, so you don't have to trust the exchange operator. This is intended for proper ICOs, not for some casual [[token]] you just created.<br />
<br />
After opening the bot, type "pairs" to see what is available.<br />
<br />
=== Flight delay insurance ===<br />
This allows one to take out insurance on a possible flight delay one day to three months in the future. See the wiki article [[Oracle]] for details.<br />
<br />
===Flight delays oracle===<br />
Used in conjunction with flight delay insurance.<br />
<br />
===Fun-coins faucet===<br />
[[File:Faucet.jpg|thumb|upright=0.66]]This bot gives out free Tangos, Tingos, Zangos, Zingos and Credits. These [[fun-coins]] have zero monetary value so you can practise textcoins and smart contracts with zero risk.<br />
<br />
* '''NOTE: To send fun-coins from your wallet, you will need Bytes to cover the transaction fees, less than 1000 bytes per transaction.'''<br />
<br />
If you wish, you can donate small amounts of Bytes for transaction fees to the sending address, CARJFJ6SKDC2XGLX2XSNMIITAVRDEW2R, but it is not necessary.<br />
<br />
Developer<ref>https://papabyte.com (@neversaynever)</ref><br />
<br />
=== Know-it-all Bot ===<br />
This bot is all about user participation and giving gratitude using incentivized Q&A. Users pose questions and add reward with bytes for faster replies, better answers and more importantly to give thanks to participants. Bring in experts on any social platform using a simple link, vote for the right answer and both of you can get rewarded!<br />
<br />
This bot was first developed for the [[Use-a-thon/botwar|Byteball Bot War]] in December 2018.<br />
<br />
Developer: Terence Lee, https://github.com/whoisterencelee/know-it-all-bot<br />
<br />
===Nousplatform ICO===<br />
Nousplatform is a decentralized next-gen investment ecosystem. Nousplatform is set to disrupt the traditional AuM market with the introduction of smart contracts and blockchain technology. The platform empowers everyone with simple and efficient access to the investment world. Discounts apply for Obyte and Steem users.<br />
<br />
Website: https://nousplatform.com<br />
<br />
===Poll bot===<br />
Now we can have referendums. This bot assists in making a vote. A vote is a small transaction that pays to yourself and is signed by your most funded addresses; the '''weight''' of the vote is the combined balance of the signing addresses. Note that there is a privacy concern because by making a vote you associate a number of your addresses. <br />
<br />
===Private Room Chat bot===<br />
This chatbot allows several persons to chat together using the Obyte messaging system. The bot decrypts messages and relays them to other users after re-encryption. For best privacy, run your own instance of this bot using the source code below; any cheap Virtual Private Server is enough to host it.<br />
<br />
Developer: Papabyte, https://github.com/Papabyte/Private-chat-room<br />
<br />
===Real name attestation bot===<br />
Verify your real name to get access to services that require KYC. Attestation that proves your verification is saved on the public database, but no personal data is published without your request. Your data is saved in your wallet and you can easily disclose it to the service that needs the data. After first successful verification, you are rewarded with $20.00 worth of Bytes from the distribution fund. See [[Identity verification]] article for details.<br />
<br />
===Slice&Dice MUD [Multi-User Dungeon]===<br />
Combining the elements of provably fair online gambling and role-playing games, Slice&Dice Dungeon delivers a unique gaming experience for everyone. The player takes a role of a dungeon inhabitant who has come across a violent underground casino. The main goal in this game is to become a powerful and respected member of the community. Doing so requires one to gamble on the Obyte tokens and to get into fights with other players as part of the endless struggle for power.<br />
<br />
Developer<ref>https://CoinGaming.io</ref><br />
<br />
===Sports betting bot (Semi-trustless)===<br />
Bet on sport fixtures by taking the trustless offers immediately available. Or be the bookmaker and develop a business by proposing competitive odds for popular events.<br />
<br />
There's an extensive wiki article about [[Sports_betting|sports betting]] and this bot.<br />
<br />
Developer<ref>https://papabyte.com</ref><br />
<br />
===Sports oracle===<br />
The sports oracle posts a [[Glossary|DATAFEED]] line only for those fixtures requested by users through the chat. See the wiki article [[Sports betting]] for details.<br />
<br />
===Steem attestation bot===<br />
Verify your Steem username, and your payers don't need to know your Obyte address any longer: they just write <code>steem/username</code> as recipient. After first successful verification you get a reward in Bytes, the amount depending on your Steem reputation. Other apps offer discounts or bonuses to users with high reputation. These apps include: ICOs, Real name attestation bot, Buy Bytes with Visa or Mastercard bot.<br />
<br />
Also see the wiki [[Attestation#Steem_attestation|Attestation]] article.<br />
<br />
If you have a question regarding steem attestations please submit the details through [https://docs.google.com/forms/d/e/1FAIpQLSdpZ4xwMCbndTsdKdoxT3O-LmAZx0h_R4dzxncA-jH9FOTlcQ/viewform?usp=sf_link this Google Form].<br />
<br />
===TitanCoin ICO===<br />
Invest in Titan Coin -- a new token pegged to the price of 1 kg of ilmenite concentrate. Ilmenite concentrate is the main raw material used for production of titanium dioxide.<br />
<br />
Project page and investor information<ref>https://titan-coin.com/?lang=en</ref><br />
<br />
===Username registration bot===<br />
Buy a username and receive money to your @username instead of a less user-friendly cryptocurrency address. Proceeds from the sale of usernames go the [[Obyte community fund]] and help fund the development and promotion of the platform.<br />
<br />
===WhiteLittle Airdrop===<br />
This is for the Chinese market.<br />
<br />
Project website: http://123cb.net, in Chinese only.<br />
<br />
===Whitelittle reward chat room===<br />
Whitelittle is a chat room (in Chinese) for newcomers who want to enter the blockchain industry. The purpose is to build an information discovery ecological platform that provides effective help for newcomers based on the Obyte technology. Here you can chat and help others without being censored and get some rewards.<br />
<br />
===World Community Grid linking bot===<br />
Donate your device’s spare computing power to help scientists solve the world’s biggest problems in health and sustainability, and [[Distribution#From_the_WCG_linking_bot|earn some Bytes]] in the meantime. This bot allows you to link your Obyte address and WCG account in order to receive daily rewards for your contribution to WCG computations.<ref>https://medium.com/byteball/computing-for-good-again-3795336bdaed</ref><br />
<br />
WCG is an IBM sponsored project; more info at https://www.worldcommunitygrid.org<br />
<br />
===Worldopoly ICO===<br />
Worldopoly is the world’s first mobile game combining AR (Augmented Reality), AI (Artificial Intelligence), Geolocationing, Blockchain, and DAG. The ICO is active until 17 May 2018, and you can buy WPT tokens with Bytes, BTC, or Ether. WPT token is issued both on Obyte and Ethereum platforms but investors on Obyte platform receive increased bonus (even if they pay in ETH or BTC) for investments up to 30 ETH.<br />
<br />
Website: https://worldopoly.io<br />
<br />
===Zork | game===<br />
Play one of the earliest interactive fiction computer games developed between 1977 and 1979. The game unfolds in a maze-like dungeon, where the user must battle trolls and solve puzzles in order to find twenty trophies to bring back to the house outside which the game begins.<br />
<br />
Developer: @Hyena<br />
<br />
==Security==<br />
<blockquote>'''Slack comment from @vakar 2018-01-10:''' A bot has no way to connect to the private part of a paired wallet. It can only send text messages to the chat. As long as we only have text (and no html) all bots are safe and cannot "steal coins".</blockquote><br />
<br />
==External links==<br />
*[https://byteroll.com/chatbox Main article source]<br />
*[https://medium.com/@wekkelekkel/byteball-e-mail-attestation-tutorial-5b4b9dfc4e04 Email attestation tutorial]<br />
*[https://medium.com/obyte/new-methods-for-identity-verification-3d5045287533 Alternative method for residents of Estonia, Latvia, Lithuania, and e-residents of Estonia]<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Features]]<br />
[[Category:Chatbots]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Witness&diff=1512Witness2019-12-31T14:50:11Z<p>Slackjore: tidied up witness functions section</p>
<hr />
<div><br />
==What is a witness?==<br />
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://obyte.org/Byteball.pdf</ref><br />
<br />
==How to replace a witness==<br />
Wallet menu > Settings > Witnesses displays the 12 witnesses set in one's wallet.<br />
<br />
*If "Auto-update the witness list from the hub" is turned 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.<br />
<br />
*If Auto-update is turned on, one's witness list will be updated to match the hub's default list automatically.<br />
<br />
=== New default witness ===<br />
After a new default witness has been approved, the next time one's wallet is turned on a screen will suggest replacing a particular Founder's Witness with the new one. So select either "Replace" or "Maybe later."<br />
<br />
==Non-Founder's witnesses==<br />
===Why change?===<br />
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. Obyte 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.<br />
<br />
===portabella, the first independent witness===<br />
No real-world identity posted. Known in the Obyte community as a veteran Byteball developer and contributor, who started this very wiki. Also operated the first independent Byteball hubs (see [[hub]] list) from January 2017. Currently (2019) not active in Obyte.<br />
<br />
===seb486, the cashback witness===<br />
No real-world identity posted. Known in the Obyte community as seb486 on Slack and Bytefan on BitcoinTalk. Not operating as a witness since July 2018.<br />
<br />
=== Rogier Eijkelhof ===<br />
The first default decentralized witness, from the Netherlands.<ref>https://medium.com/obyte/first-decentralized-witness-candidate-rogier-eijkelhof-9e5619166334</ref><br />
<br />
=== Fabien Marino ===<br />
The second default independent witness, co-founder of Busy.org and SteemConnect, involved with Obyte since February 2017.<ref>https://medium.com/obyte/second-independent-witness-candidate-fabien-marino-d4e8dccadee</ref><br />
<br />
=== Bosch Connectory ===<br />
This is the third default independent witness, overwhelmingly approved by vote (178:2 addresses, 31320 GB : 68 MB).<ref>https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03</ref><br />
<br />
==Witness monitoring service==<br />
This is a useful page: https://stats.obyte.org/witnesses.php<br />
<br />
==Witness list==<br />
{| class="wikitable"<br />
|-<br />
! Witness ID !! Owner !! Discord ID !! Started<br />
|-<br />
| BVVJ2K7ENPZZ3VYZFWQWK7ISPCATFIW3 || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| DJMMI5JYA5BWQYSXDPRZJVLW3UGL3GJS || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| H5EZTQE7ABFH27AUDTQFMZIALANK6RBG || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| JEDZYC2HMGDBIDQKG3XSTXUSHMCBK725 || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| OYW2XTDKSNKGSEZ27LMGNOPJSYIXHBHC || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| S7N5FE42F6ONPNDQLCF64E2MGFYKQR2I || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| TKT4UESIKTTRALRRLWS4SENSTJX6ODCW || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| UENJPVZ7HVHM6QGVGT6MWOJGGRTUTJXQ || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| MEJGDND55XNON7UU3ZKERJIZMMXJTVCV || anon || @seb486 || 2017-05-25<br />
|-<br />
| 4GDZSXHEFVFMHCUCSHZVXBVF5T2LJHMU || Rogier Eijkelhof || @Rogier || 2018-10-23<br />
|-<br />
| FAB6TH7IRAVHDLK2AAWY5YBE6CEBUACF || Fabien Marino || @fabien || 2019-04-16<br />
|-<br />
| 2TO6NYBGX3NF5QS24MQLFR7KXYAMCIE5 || Bosch Connectory || N/A || 2019-12-27<br />
|}<br />
<br />
<hr /><br />
<br />
==FAQ about witnesses, double spending, finality==<br />
<br />
===Witnesses and consensus===<br />
<br />
Q: Those witnesses that wallet has chosen that will try to determine the validity of the transaction/message?<br /><br />
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. <br />
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.<br />
<br />
Q: Are witnesses required to validate all transactions?<br /><br />
A: Witnesses are required to be full nodes, hence validate all transactions<br />
<br />
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?<br /><br />
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)<br />
<br />
Q: Does a full node need to receive and validate all transactions?<br /><br />
A: Yes, that's the definition of a full node<br />
<br />
Q: To illustrate how little a witness has to decide:<br /><br />
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.<br />
<br />
Q: The witnesses together they decide which branch of the transaction tree is the real one?<br /><br />
A: More accurate wording: they don't decide but enable others to decide, by looking at witnesses as markers of reality<br />
<br />
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?<br /><br />
A: Correct.<br />
<br />
Q: Are the “witnessing” units specialised by any means?<br /><br />
A: There are no specialised witnessing units. Any witness-authored unit counts as “witnessing” unit<br />
<br />
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?<br /><br />
A: Correct<br />
<br />
Q: The protocol requires that transactors have an overlap of 11 (out of 12) witnesses, correct?<br /><br />
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<br />
<br />
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?<br /><br />
A: No, witnesses do not determine the chain state<br />
<br />
Q: is there an option of organic replacement of one or more witnesses?<br /><br />
A: Edit the list in the wallet settings<br />
<br />
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?<br /><br />
A: If we define users as those who post transactions to the DAG, No.<br />
<br />
Q: Is it possible to choose 12 completely new witnesses for my wallet? What would happen?<br /><br />
A: Possible but you won’t be able to post any transactions until all active users migrate to roughly the same list<br />
<br />
Q: What does “predominant witnesses” mean?<br /><br />
A: Those that you see on the most recently posted units (they can be slightly different)<br />
<br />
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?<br /><br />
A: Yes, the majority of the current predominant witnesses<br />
<br />
Q: If an individual, company or government seizes a witness (or all), would they be able to censor transactions?<br /><br />
A: If "a" witness, no, they will only censor out themselves. If all witnesses, yes.<br />
<br />
Q: What happens if all witnesses are shut down?<br /><br />
A: There will be no confirmations. The MC will still be there but the “stability point” will stop advancing.<br />
<br />
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?<br /><br />
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.<br />
<br />
===Double spending===<br />
Q: Are full (or light) nodes capable of identifying and solving double spend attempts without the use of witnesses?<br /><br />
A: No, they need the witness-authorized units’ positions on the DAG to build the MC, and they use the MC to resolve doublespends<br />
<br />
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?<br /><br />
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.<br />
<br />
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?<br /><br />
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.<br />
<br />
===Finality in Byteball===<br />
Q: What is “finality” in Byteball?<br /><br />
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”)<br />
<br />
Q:.What is “stability point” in Byteball?<br /><br />
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.<br />
<br />
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).<br /><br />
A: No, it is not allowed.<br />
<br />
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? <br />
A: if the colluding witnesses are a majority, the network will get into undefined state once they publish the shadow chain<br />
<br />
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?<br /><br />
A: Every full node replays the entire history and recalculates the stability point itself<br />
<br />
==Additional comments==<br />
[Slack 11:00 PM 2017-06-22]<br /><br />
<br />
<blockquote>'''markcross:''' And it's those witnesses that wallet has chosen that will try to determine the validity of the transaction/message?</blockquote><br />
<br />
<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. <br />
<br />
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.<br />
</blockquote><br />
<br />
[Bitcointalk 2017-02-06]<br />
<br />
<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><br />
<br />
===Decentralizing witnesses===<br />
[Bitcointalk 2018-03-21]<br />
<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><br />
<br />
<br />
===Witness functions===<br />
[Slack 2018-05-14]<br />
<br />
<blockquote>'''tonych:'''<br />
> · Are witnesses required to validate all transactions?<br /><br />
witnesses are required to be full nodes, hence validate all transactions<br /><br />
> · What happens if all witnesses are shut down?<br /><br />
there will be no confirmations. The MC [main chain] will still be there but the stability point will stop advancing<br /><br />
> · If an individual, company or government seizes a witness (or all), would they be able to censor transactions?<br /><br />
If "a" witness, no, they will only censor out themselves. If all witnesses, yes.<br /><br />
> So in effect, a witness has the same role as any other full node, except when attempts of double spends without partial order occur?<br /><br />
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<br /><br />
> Every full node validates all transactions?<br /><br />
Yes, that's the definition of a full node<br />
> · Are full (or light) nodes capable of identifying and solving double-spend attempts without the use of witnesses?<br /><br />
No, they need witness positions on the DAG to build the MC, and they use the MC to resolve doublespends</blockquote><br />
<br />
<blockquote>'''Tsonko Mirchev:''' Is that mean that full node doesn't need MC to resolve doublespends?</blockquote><br />
<br />
<blockquote>'''tonych:''' no, it needs the MC</blockquote><br />
<br />
<blockquote>'''tonych:''' another thing to illustrate how little a witness has to decide:<br />
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><br />
<br />
<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><br />
<br />
<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. <br />
<br />
Which of these is wrong?</blockquote><br />
<br />
<blockquote>'''tonych:''' no, witnesses do not "stamp", stamping would make them gatekeepers</blockquote><br />
<br />
<blockquote>'''tonych:''' the functions are just to 1) be honest, and 2) be there<br />
<br />
> because together they decide which branch of the transaction tree is the real one<br />
more accurate wording: they don't decide but enable others to decide, by looking at witnesses as markers of reality<br />
> Hm, I added Bittrex as a witness and the explorer considers the tx stable, but my wallet doesn't<br />
<br />
if your wallet is light, it sees stability later</blockquote><br />
<br />
<blockquote>'''slackjore:''' OK. I was using the word "stamp" wrongly, to mean basically "comment upon". How about my other assumptions?</blockquote><br />
<br />
<blockquote>'''tonych:'''(2) correct<br /><br />
(3) correct, the "additional software" is anything responsible for frequent posting of transactions<br /><br />
(4) correct<br /><br />
(5) correct<br /><br />
(6) of course</blockquote><br />
<br />
<blockquote>'''slackjore:''' Thank you. So how can Bittrex act as an unknowing witness, if a witness has to author units?</blockquote><br />
<br />
<blockquote>'''tonych:''' they do withdrawals and other txs from this address</blockquote><br />
<br />
<blockquote>'''slackjore:'''yes, but you said: https://byteball.slack.com/archives/C9GDDLW0N/p1526293317000487<br />
tonych<br />
another thing to illustrate how little a witness has to decide:<br />
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.<br />
Posted in #marketing_discussionToday at 11:21 AM</blockquote><br />
<br />
<blockquote>'''tonych:''' yes, any contradiction?</blockquote><br />
<br />
<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><br />
<br />
<blockquote>'''tonych:''' there are no specialised witnessing units, any witness-authored unit counts</blockquote><br />
<br />
<blockquote>'''slackjore:''' I mean a unit like this: https://explorer.byteball.org/#OaMFZKr+2zQp4Ce0Oxz0tpTaB4Jb2jLDYcrLACxt+jA=<br />
arbitrary, first one I saw</blockquote><br />
<br />
<blockquote>'''tonych:''' nothing special in it</blockquote><br />
<br />
<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.<br />
<br />
Is that correct?</blockquote><br />
<br />
<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><br />
<br />
<blockquote>'''slackjore:''' ok, great, now I understand how Bittrex could be an unknowing witness. Thank you very much indeed.</blockquote><br />
<br />
-----<br />
<br />
<blockquote>'''Person:''' Hi @tonych please help to answer some questions. I would like to understand the WP. <br />
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?<br />
<br />
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”?<br />
<br />
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?<br />
<br />
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?</blockquote><br />
<br />
<blockquote>'''tonych:''' 1. the witnesses of the newly added unit<br />
<br />
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.<br />
<br />
3. correct<br />
<br />
4. correct</blockquote><br />
<br />
<blockquote>'''Person:''' tony: Is it correct to state that the “current MC” is determined by the witnesses of the unit in the current stability point?</blockquote><br />
<br />
<blockquote>'''tonych:''' No, no witness list matters at all at this step. You just define the best parent using witnessed level and level</blockquote><br />
<br />
<blockquote>'''Person:''' [question lost]</blockquote><br />
<br />
<blockquote>'''tonych:'''. 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.</blockquote><br />
<br />
==How to become a witness==<br />
To become a winess, you are expected to:<br />
<br />
*have a publicly known real name, no anonymity<br />
*be well known in the community<br />
*be trusted<br />
*have a lot to lose (material and/or nonmaterial) in case of misbehavior. The loss is your business (outside Byteball) and/or reputation<br />
*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)<br />
*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.<br />
<br />
If you think that you satisfy these criteria, this is your course of action: <snip><ref>https://github.com/byteball/byteball-witness</ref><br />
<br />
==External links==<br />
*[https://www.youtube.com/watch?v=N1aWPAm0SdY&feature=youtu.be Video: Byteball Witnesses - the basics explained]<br />
*[https://medium.com/obyte/first-decentralized-witness-candidate-rogier-eijkelhof-9e5619166334 First decentralized witness candidate]<br />
*[https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03 Bosch Connectory Approved as Obyte Witness]<br />
<br />
==References==<br />
<references /><br />
[[Category:Features]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Witness&diff=1511Witness2019-12-31T14:00:10Z<p>Slackjore: adjusted "how to replace a witness" section</p>
<hr />
<div><br />
==What is a witness?==<br />
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://obyte.org/Byteball.pdf</ref><br />
<br />
==How to replace a witness==<br />
Wallet menu > Settings > Witnesses displays the 12 witnesses set in one's wallet.<br />
<br />
*If "Auto-update the witness list from the hub" is turned 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.<br />
<br />
*If Auto-update is turned on, one's witness list will be updated to match the hub's default list automatically.<br />
<br />
=== New default witness ===<br />
After a new default witness has been approved, the next time one's wallet is turned on a screen will suggest replacing a particular Founder's Witness with the new one. So select either "Replace" or "Maybe later."<br />
<br />
==Non-Founder's witnesses==<br />
===Why change?===<br />
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. Obyte 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.<br />
<br />
===portabella, the first independent witness===<br />
No real-world identity posted. Known in the Obyte community as a veteran Byteball developer and contributor, who started this very wiki. Also operated the first independent Byteball hubs (see [[hub]] list) from January 2017. Currently (2019) not active in Obyte.<br />
<br />
===seb486, the cashback witness===<br />
No real-world identity posted. Known in the Obyte community as seb486 on Slack and Bytefan on BitcoinTalk. Not operating as a witness since July 2018.<br />
<br />
=== Rogier Eijkelhof ===<br />
The first default decentralized witness, from the Netherlands.<ref>https://medium.com/obyte/first-decentralized-witness-candidate-rogier-eijkelhof-9e5619166334</ref><br />
<br />
=== Fabien Marino ===<br />
The second default independent witness, co-founder of Busy.org and SteemConnect, involved with Obyte since February 2017.<ref>https://medium.com/obyte/second-independent-witness-candidate-fabien-marino-d4e8dccadee</ref><br />
<br />
=== Bosch Connectory ===<br />
This is the third default independent witness, overwhelmingly approved by vote (178:2 addresses, 31320 GB : 68 MB).<ref>https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03</ref><br />
<br />
==Witness monitoring service==<br />
This is a useful page: https://stats.obyte.org/witnesses.php<br />
<br />
==Witness list==<br />
{| class="wikitable"<br />
|-<br />
! Witness ID !! Owner !! Discord ID !! Started<br />
|-<br />
| BVVJ2K7ENPZZ3VYZFWQWK7ISPCATFIW3 || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| DJMMI5JYA5BWQYSXDPRZJVLW3UGL3GJS || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| H5EZTQE7ABFH27AUDTQFMZIALANK6RBG || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| JEDZYC2HMGDBIDQKG3XSTXUSHMCBK725 || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| OYW2XTDKSNKGSEZ27LMGNOPJSYIXHBHC || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| S7N5FE42F6ONPNDQLCF64E2MGFYKQR2I || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| TKT4UESIKTTRALRRLWS4SENSTJX6ODCW || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| UENJPVZ7HVHM6QGVGT6MWOJGGRTUTJXQ || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| MEJGDND55XNON7UU3ZKERJIZMMXJTVCV || anon || @seb486 || 2017-05-25<br />
|-<br />
| 4GDZSXHEFVFMHCUCSHZVXBVF5T2LJHMU || Rogier Eijkelhof || @Rogier || 2018-10-23<br />
|-<br />
| FAB6TH7IRAVHDLK2AAWY5YBE6CEBUACF || Fabien Marino || @fabien || 2019-04-16<br />
|-<br />
| 2TO6NYBGX3NF5QS24MQLFR7KXYAMCIE5 || Bosch Connectory || N/A || 2019-12-27<br />
|}<br />
<br />
<hr /><br />
<br />
==FAQ about witnesses, double spending, finality==<br />
<br />
===Witnesses and consensus===<br />
<br />
Q: Those witnesses that wallet has chosen that will try to determine the validity of the transaction/message?<br /><br />
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. <br />
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.<br />
<br />
Q: Are witnesses required to validate all transactions?<br /><br />
A: Witnesses are required to be full nodes, hence validate all transactions<br />
<br />
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?<br /><br />
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)<br />
<br />
Q: Does a full node need to receive and validate all transactions?<br /><br />
A: Yes, that's the definition of a full node<br />
<br />
Q: To illustrate how little a witness has to decide:<br /><br />
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.<br />
<br />
Q: The witnesses together they decide which branch of the transaction tree is the real one?<br /><br />
A: More accurate wording: they don't decide but enable others to decide, by looking at witnesses as markers of reality<br />
<br />
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?<br /><br />
A: Correct.<br />
<br />
Q: Are the “witnessing” units specialised by any means?<br /><br />
A: There are no specialised witnessing units. Any witness-authored unit counts as “witnessing” unit<br />
<br />
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?<br /><br />
A: Correct<br />
<br />
Q: The protocol requires that transactors have an overlap of 11 (out of 12) witnesses, correct?<br /><br />
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<br />
<br />
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?<br /><br />
A: No, witnesses do not determine the chain state<br />
<br />
Q: is there an option of organic replacement of one or more witnesses?<br /><br />
A: Edit the list in the wallet settings<br />
<br />
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?<br /><br />
A: If we define users as those who post transactions to the DAG, No.<br />
<br />
Q: Is it possible to choose 12 completely new witnesses for my wallet? What would happen?<br /><br />
A: Possible but you won’t be able to post any transactions until all active users migrate to roughly the same list<br />
<br />
Q: What does “predominant witnesses” mean?<br /><br />
A: Those that you see on the most recently posted units (they can be slightly different)<br />
<br />
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?<br /><br />
A: Yes, the majority of the current predominant witnesses<br />
<br />
Q: If an individual, company or government seizes a witness (or all), would they be able to censor transactions?<br /><br />
A: If "a" witness, no, they will only censor out themselves. If all witnesses, yes.<br />
<br />
Q: What happens if all witnesses are shut down?<br /><br />
A: There will be no confirmations. The MC will still be there but the “stability point” will stop advancing.<br />
<br />
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?<br /><br />
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.<br />
<br />
===Double spending===<br />
Q: Are full (or light) nodes capable of identifying and solving double spend attempts without the use of witnesses?<br /><br />
A: No, they need the witness-authorized units’ positions on the DAG to build the MC, and they use the MC to resolve doublespends<br />
<br />
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?<br /><br />
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.<br />
<br />
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?<br /><br />
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.<br />
<br />
===Finality in Byteball===<br />
Q: What is “finality” in Byteball?<br /><br />
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”)<br />
<br />
Q:.What is “stability point” in Byteball?<br /><br />
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.<br />
<br />
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).<br /><br />
A: No, it is not allowed.<br />
<br />
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? <br />
A: if the colluding witnesses are a majority, the network will get into undefined state once they publish the shadow chain<br />
<br />
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?<br /><br />
A: Every full node replays the entire history and recalculates the stability point itself<br />
<br />
==Additional comments==<br />
[Slack 11:00 PM 2017-06-22]<br /><br />
<br />
<blockquote>'''markcross:''' And it's those witnesses that wallet has chosen that will try to determine the validity of the transaction/message?</blockquote><br />
<br />
<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. <br />
<br />
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.<br />
</blockquote><br />
<br />
[Bitcointalk 2017-02-06]<br />
<br />
<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><br />
<br />
===Decentralizing witnesses===<br />
[Bitcointalk 2018-03-21]<br />
<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><br />
<br />
<br />
===Witness functions===<br />
[Slack 2018-05-14]<br />
<br />
<blockquote>'''tonych:'''<br />
> · Are witnesses required to validate all transactions?<br /><br />
witnesses are required to be full nodes, hence validate all transactions<br /><br />
> · What happens if all witnesses are shut down?<br /><br />
there will be no confirmations. The MC [main chain] will still be there but the stability point will stop advancing<br /><br />
> · If an individual, company or government seizes a witness (or all), would they be able to censor transactions?<br /><br />
If "a" witness, no, they will only censor out themselves. If all witnesses, yes.<br /><br />
> So in effect, a witness has the same role as any other full node, except when attempts of double spends without partial order occur?<br /><br />
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<br /><br />
> Every full node validates all transactions?<br /><br />
Yes, that's the definition of a full node<br />
> · Are full (or light) nodes capable of identifying and solving double-spend attempts without the use of witnesses?<br /><br />
No, they need witness positions on the DAG to build the MC, and they use the MC to resolve doublespends</blockquote><br />
<br />
<blockquote>'''Tsonko Mirchev:''' Is that mean that full node doesn't need MC to resolve doublespends?</blockquote><br />
<br />
<blockquote>'''tonych:''' no, it needs the MC</blockquote><br />
<br />
<blockquote>'''tonych:''' another thing to illustrate how little a witness has to decide:<br />
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><br />
<br />
<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><br />
<br />
<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. <br />
<br />
Which of these is wrong?</blockquote><br />
<br />
<blockquote>'''tonych:''' no, witnesses do not "stamp", stamping would make them gatekeepers</blockquote><br />
<br />
<blockquote>'''tonych:''' the functions are just to 1) be honest, and 2) be there<br />
<br />
> because together they decide which branch of the transaction tree is the real one<br />
more accurate wording: they don't decide but enable others to decide, by looking at witnesses as markers of reality<br />
> Hm, I added Bittrex as a witness and the explorer considers the tx stable, but my wallet doesn't<br />
<br />
if your wallet is light, it sees stability later</blockquote><br />
<br />
<blockquote>'''slackjore:''' OK. I was using the word "stamp" wrongly, to mean basically "comment upon". How about my other assumptions?</blockquote><br />
<br />
<blockquote>'''tonych:'''(2) correct<br /><br />
(3) correct, the "additional software" is anything responsible for frequent posting of transactions<br /><br />
(4) correct<br /><br />
(5) correct<br /><br />
(6) of course</blockquote><br />
<br />
<blockquote>'''slackjore:''' Thank you. So how can Bittrex act as an unknowing witness, if a witness has to author units?</blockquote><br />
<br />
<blockquote>'''tonych:''' they do withdrawals and other txs from this address</blockquote><br />
<br />
<blockquote>'''slackjore:'''yes, but you said: https://byteball.slack.com/archives/C9GDDLW0N/p1526293317000487<br />
tonych<br />
another thing to illustrate how little a witness has to decide:<br />
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.<br />
Posted in #marketing_discussionToday at 11:21 AM</blockquote><br />
<br />
<blockquote>'''tonych:''' yes, any contradiction?</blockquote><br />
<br />
<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><br />
<br />
<blockquote>'''tonych:''' there are no specialised witnessing units, any witness-authored unit counts</blockquote><br />
<br />
<blockquote>'''slackjore:''' I mean a unit like this: https://explorer.byteball.org/#OaMFZKr+2zQp4Ce0Oxz0tpTaB4Jb2jLDYcrLACxt+jA=<br />
arbitrary, first one I saw</blockquote><br />
<br />
<blockquote>'''tonych:''' nothing special in it</blockquote><br />
<br />
<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.<br />
<br />
Is that correct?</blockquote><br />
<br />
<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><br />
<br />
<blockquote>'''slackjore:''' ok, great, now I understand how Bittrex could be an unknowing witness. Thank you very much indeed.</blockquote><br />
<br />
-----<br />
<br />
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?<br />
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”?<br />
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?<br />
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?<br />
<br />
tonych [12:18 PM]<br />
1. the witnesses of the newly added unit<br />
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.<br />
3. correct<br />
4. correct<br />
<br />
tony:<br />
1.<br />
> Is it correct to state that the “current MC” is determined by the witnesses of the unit in the current stability point?<br />
No, no witness list matters at all at this step. You just define the best parent using witnessed level and level<br />
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<br />
<br />
===Experiment===<br />
<blockquote>slackjore [2018-05-26 1:16 PM]: <br />
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)<br />
<br />
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.<br />
now it's confirmed in my wallet, 11 minutes after the tx<br />
<br />
Bittrex is still set as a witness, as I had turned off the update-witnesses-from-hub switch</blockquote><br />
<br />
<br />
==How to become a witness==<br />
To become a winess, you are expected to:<br />
<br />
*have a publicly known real name, no anonymity<br />
*be well known in the community<br />
*be trusted<br />
*have a lot to lose (material and/or nonmaterial) in case of misbehavior. The loss is your business (outside Byteball) and/or reputation<br />
*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)<br />
*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.<br />
<br />
If you think that you satisfy these criteria, this is your course of action: <snip><ref>https://github.com/byteball/byteball-witness</ref><br />
<br />
==External links==<br />
*[https://www.youtube.com/watch?v=N1aWPAm0SdY&feature=youtu.be Video: Byteball Witnesses - the basics explained]<br />
*[https://medium.com/obyte/first-decentralized-witness-candidate-rogier-eijkelhof-9e5619166334 First decentralized witness candidate]<br />
*[https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03 Bosch Connectory Approved as Obyte Witness]<br />
<br />
==References==<br />
<references /><br />
[[Category:Features]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Witness&diff=1510Witness2019-12-31T13:24:42Z<p>Slackjore: adjusted replacing witnesses section</p>
<hr />
<div><br />
==What is a witness?==<br />
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://obyte.org/Byteball.pdf</ref><br />
<br />
==How to replace a witness==<br />
Wallet menu > Settings > Witnesses displays the 12 witnesses set in one's wallet.<br />
<br />
*If "Auto-update the witness list from the hub" is turned on, after a new default witness has been approved, upon opening the wallet a screen will suggest replacing a particular Founder's Witness with the new one. So select either "Replace" or "Maybe later."<br />
<br />
*If Auto-update is turned 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.<br />
<br />
==Non-default witnesses==<br />
===Why change?===<br />
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. Obyte 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.<br />
<br />
===@portabella, the first independent witness===<br />
No real-world identity posted. Known in the Obyte community as a veteran Byteball developer and contributor, who started this very wiki. Also operated the first independent Byteball hubs (see [[hub]] list) from January 2017. Currently (2019) not active in Obyte.<br />
<br />
==@seb486, the cashback witness==<br />
No real-world identity posted. Known in the Obyte community as seb486 on Slack and Bytefan on BitcoinTalk. Not operating as a witness since July 2018.<br />
<br />
In his own words:<br />
<br />
<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.<br />
<br />
'''You earn back bytes for free.''' It is as simple as that!<ref>https://byteball-cashback-witness.com</ref><br />
</blockquote><br />
<br />
Contact info: #cashback_witness channel at our Slack <br />
<br />
==Witness monitoring service==<br />
This is a useful page: https://stats.obyte.org/witnesses.php<br />
<br />
==Witness list==<br />
{| class="wikitable"<br />
|-<br />
! Witness ID !! Owner !! Discord ID !! Started<br />
|-<br />
| BVVJ2K7ENPZZ3VYZFWQWK7ISPCATFIW3 || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| DJMMI5JYA5BWQYSXDPRZJVLW3UGL3GJS || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| H5EZTQE7ABFH27AUDTQFMZIALANK6RBG || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| JEDZYC2HMGDBIDQKG3XSTXUSHMCBK725 || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| OYW2XTDKSNKGSEZ27LMGNOPJSYIXHBHC || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| S7N5FE42F6ONPNDQLCF64E2MGFYKQR2I || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| TKT4UESIKTTRALRRLWS4SENSTJX6ODCW || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| UENJPVZ7HVHM6QGVGT6MWOJGGRTUTJXQ || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| MEJGDND55XNON7UU3ZKERJIZMMXJTVCV || anon || @seb486 || 2017-05-25<br />
|-<br />
| 4GDZSXHEFVFMHCUCSHZVXBVF5T2LJHMU || Rogier Eijkelhof || @Rogier || 2018-10-23<br />
|-<br />
| FAB6TH7IRAVHDLK2AAWY5YBE6CEBUACF || Fabien Marino || @fabien || 2019-04-16<br />
|-<br />
| 2TO6NYBGX3NF5QS24MQLFR7KXYAMCIE5 || Bosch Connectory || N/A || 2019-12-27<br />
|}<br />
<br />
<hr /><br />
<br />
==FAQ about witnesses, double spending, finality==<br />
<br />
===Witnesses and consensus===<br />
<br />
Q: Those witnesses that wallet has chosen that will try to determine the validity of the transaction/message?<br /><br />
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. <br />
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.<br />
<br />
Q: Are witnesses required to validate all transactions?<br /><br />
A: Witnesses are required to be full nodes, hence validate all transactions<br />
<br />
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?<br /><br />
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)<br />
<br />
Q: Does a full node need to receive and validate all transactions?<br /><br />
A: Yes, that's the definition of a full node<br />
<br />
Q: To illustrate how little a witness has to decide:<br /><br />
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.<br />
<br />
Q: The witnesses together they decide which branch of the transaction tree is the real one?<br /><br />
A: More accurate wording: they don't decide but enable others to decide, by looking at witnesses as markers of reality<br />
<br />
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?<br /><br />
A: Correct.<br />
<br />
Q: Are the “witnessing” units specialised by any means?<br /><br />
A: There are no specialised witnessing units. Any witness-authored unit counts as “witnessing” unit<br />
<br />
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?<br /><br />
A: Correct<br />
<br />
Q: The protocol requires that transactors have an overlap of 11 (out of 12) witnesses, correct?<br /><br />
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<br />
<br />
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?<br /><br />
A: No, witnesses do not determine the chain state<br />
<br />
Q: is there an option of organic replacement of one or more witnesses?<br /><br />
A: Edit the list in the wallet settings<br />
<br />
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?<br /><br />
A: If we define users as those who post transactions to the DAG, No.<br />
<br />
Q: Is it possible to choose 12 completely new witnesses for my wallet? What would happen?<br /><br />
A: Possible but you won’t be able to post any transactions until all active users migrate to roughly the same list<br />
<br />
Q: What does “predominant witnesses” mean?<br /><br />
A: Those that you see on the most recently posted units (they can be slightly different)<br />
<br />
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?<br /><br />
A: Yes, the majority of the current predominant witnesses<br />
<br />
Q: If an individual, company or government seizes a witness (or all), would they be able to censor transactions?<br /><br />
A: If "a" witness, no, they will only censor out themselves. If all witnesses, yes.<br />
<br />
Q: What happens if all witnesses are shut down?<br /><br />
A: There will be no confirmations. The MC will still be there but the “stability point” will stop advancing.<br />
<br />
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?<br /><br />
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.<br />
<br />
===Double spending===<br />
Q: Are full (or light) nodes capable of identifying and solving double spend attempts without the use of witnesses?<br /><br />
A: No, they need the witness-authorized units’ positions on the DAG to build the MC, and they use the MC to resolve doublespends<br />
<br />
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?<br /><br />
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.<br />
<br />
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?<br /><br />
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.<br />
<br />
===Finality in Byteball===<br />
Q: What is “finality” in Byteball?<br /><br />
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”)<br />
<br />
Q:.What is “stability point” in Byteball?<br /><br />
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.<br />
<br />
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).<br /><br />
A: No, it is not allowed.<br />
<br />
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? <br />
A: if the colluding witnesses are a majority, the network will get into undefined state once they publish the shadow chain<br />
<br />
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?<br /><br />
A: Every full node replays the entire history and recalculates the stability point itself<br />
<br />
==Additional comments==<br />
[Slack 11:00 PM 2017-06-22]<br /><br />
<br />
<blockquote>'''markcross:''' And it's those witnesses that wallet has chosen that will try to determine the validity of the transaction/message?</blockquote><br />
<br />
<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. <br />
<br />
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.<br />
</blockquote><br />
<br />
[Bitcointalk 2017-02-06]<br />
<br />
<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><br />
<br />
===Decentralizing witnesses===<br />
[Bitcointalk 2018-03-21]<br />
<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><br />
<br />
<br />
===Witness functions===<br />
[Slack 2018-05-14]<br />
<br />
<blockquote>'''tonych:'''<br />
> · Are witnesses required to validate all transactions?<br /><br />
witnesses are required to be full nodes, hence validate all transactions<br /><br />
> · What happens if all witnesses are shut down?<br /><br />
there will be no confirmations. The MC [main chain] will still be there but the stability point will stop advancing<br /><br />
> · If an individual, company or government seizes a witness (or all), would they be able to censor transactions?<br /><br />
If "a" witness, no, they will only censor out themselves. If all witnesses, yes.<br /><br />
> So in effect, a witness has the same role as any other full node, except when attempts of double spends without partial order occur?<br /><br />
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<br /><br />
> Every full node validates all transactions?<br /><br />
Yes, that's the definition of a full node<br />
> · Are full (or light) nodes capable of identifying and solving double-spend attempts without the use of witnesses?<br /><br />
No, they need witness positions on the DAG to build the MC, and they use the MC to resolve doublespends</blockquote><br />
<br />
<blockquote>'''Tsonko Mirchev:''' Is that mean that full node doesn't need MC to resolve doublespends?</blockquote><br />
<br />
<blockquote>'''tonych:''' no, it needs the MC</blockquote><br />
<br />
<blockquote>'''tonych:''' another thing to illustrate how little a witness has to decide:<br />
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><br />
<br />
<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><br />
<br />
<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. <br />
<br />
Which of these is wrong?</blockquote><br />
<br />
<blockquote>'''tonych:''' no, witnesses do not "stamp", stamping would make them gatekeepers</blockquote><br />
<br />
<blockquote>'''tonych:''' the functions are just to 1) be honest, and 2) be there<br />
<br />
> because together they decide which branch of the transaction tree is the real one<br />
more accurate wording: they don't decide but enable others to decide, by looking at witnesses as markers of reality<br />
> Hm, I added Bittrex as a witness and the explorer considers the tx stable, but my wallet doesn't<br />
<br />
if your wallet is light, it sees stability later</blockquote><br />
<br />
<blockquote>'''slackjore:''' OK. I was using the word "stamp" wrongly, to mean basically "comment upon". How about my other assumptions?</blockquote><br />
<br />
<blockquote>'''tonych:'''(2) correct<br /><br />
(3) correct, the "additional software" is anything responsible for frequent posting of transactions<br /><br />
(4) correct<br /><br />
(5) correct<br /><br />
(6) of course</blockquote><br />
<br />
<blockquote>'''slackjore:''' Thank you. So how can Bittrex act as an unknowing witness, if a witness has to author units?</blockquote><br />
<br />
<blockquote>'''tonych:''' they do withdrawals and other txs from this address</blockquote><br />
<br />
<blockquote>'''slackjore:'''yes, but you said: https://byteball.slack.com/archives/C9GDDLW0N/p1526293317000487<br />
tonych<br />
another thing to illustrate how little a witness has to decide:<br />
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.<br />
Posted in #marketing_discussionToday at 11:21 AM</blockquote><br />
<br />
<blockquote>'''tonych:''' yes, any contradiction?</blockquote><br />
<br />
<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><br />
<br />
<blockquote>'''tonych:''' there are no specialised witnessing units, any witness-authored unit counts</blockquote><br />
<br />
<blockquote>'''slackjore:''' I mean a unit like this: https://explorer.byteball.org/#OaMFZKr+2zQp4Ce0Oxz0tpTaB4Jb2jLDYcrLACxt+jA=<br />
arbitrary, first one I saw</blockquote><br />
<br />
<blockquote>'''tonych:''' nothing special in it</blockquote><br />
<br />
<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.<br />
<br />
Is that correct?</blockquote><br />
<br />
<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><br />
<br />
<blockquote>'''slackjore:''' ok, great, now I understand how Bittrex could be an unknowing witness. Thank you very much indeed.</blockquote><br />
<br />
-----<br />
<br />
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?<br />
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”?<br />
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?<br />
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?<br />
<br />
tonych [12:18 PM]<br />
1. the witnesses of the newly added unit<br />
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.<br />
3. correct<br />
4. correct<br />
<br />
tony:<br />
1.<br />
> Is it correct to state that the “current MC” is determined by the witnesses of the unit in the current stability point?<br />
No, no witness list matters at all at this step. You just define the best parent using witnessed level and level<br />
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<br />
<br />
===Experiment===<br />
<blockquote>slackjore [2018-05-26 1:16 PM]: <br />
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)<br />
<br />
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.<br />
now it's confirmed in my wallet, 11 minutes after the tx<br />
<br />
Bittrex is still set as a witness, as I had turned off the update-witnesses-from-hub switch</blockquote><br />
<br />
<br />
==How to become a witness==<br />
To become a winess, you are expected to:<br />
<br />
*have a publicly known real name, no anonymity<br />
*be well known in the community<br />
*be trusted<br />
*have a lot to lose (material and/or nonmaterial) in case of misbehavior. The loss is your business (outside Byteball) and/or reputation<br />
*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)<br />
*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.<br />
<br />
If you think that you satisfy these criteria, this is your course of action: <snip><ref>https://github.com/byteball/byteball-witness</ref><br />
<br />
==External links==<br />
*[https://www.youtube.com/watch?v=N1aWPAm0SdY&feature=youtu.be Video: Byteball Witnesses - the basics explained]<br />
*[https://medium.com/obyte/first-decentralized-witness-candidate-rogier-eijkelhof-9e5619166334 First decentralized witness candidate]<br />
*[https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03 Bosch Connectory Approved as Obyte Witness]<br />
<br />
==References==<br />
<references /><br />
[[Category:Features]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Witness&diff=1509Witness2019-12-31T13:05:31Z<p>Slackjore: added "new witness" section</p>
<hr />
<div><br />
==What is a witness?==<br />
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://obyte.org/Byteball.pdf</ref><br />
<br />
==How to replace a witness==<br />
=== New witnesses ===<br />
When a new default witness has been approved, upon opening the wallet a screen will suggest replacing a particular Founder's Witness with the new one. So select either "Replace" or "Maybe later."<br />
<br />
Wallet menu > Settings > Witnesses > then either<br />
<br />
*Turn on "Auto-update the witness list from the hub"; or<br />
*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.<br />
<br />
==Non-default witnesses==<br />
===Why change?===<br />
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. Obyte 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.<br />
<br />
===@portabella, the first independent witness===<br />
No real-world identity posted. Known in the Obyte community as a veteran Byteball developer and contributor, who started this very wiki. Also operated the first independent Byteball hubs (see [[hub]] list) from January 2017. Currently (2019) not active in Obyte.<br />
<br />
==@seb486, the cashback witness==<br />
No real-world identity posted. Known in the Obyte community as seb486 on Slack and Bytefan on BitcoinTalk. Not operating as a witness since July 2018.<br />
<br />
In his own words:<br />
<br />
<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.<br />
<br />
'''You earn back bytes for free.''' It is as simple as that!<ref>https://byteball-cashback-witness.com</ref><br />
</blockquote><br />
<br />
Contact info: #cashback_witness channel at our Slack <br />
<br />
==Witness monitoring service==<br />
This is a useful page: https://stats.obyte.org/witnesses.php<br />
<br />
==Witness list==<br />
{| class="wikitable"<br />
|-<br />
! Witness ID !! Owner !! Discord ID !! Started<br />
|-<br />
| BVVJ2K7ENPZZ3VYZFWQWK7ISPCATFIW3 || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| DJMMI5JYA5BWQYSXDPRZJVLW3UGL3GJS || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| FOPUBEUPBC6YLIQDLKL6EW775BMV7YOH || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| GFK3RDAPQLLNCMQEVGGD2KCPZTLSG3HN || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| H5EZTQE7ABFH27AUDTQFMZIALANK6RBG || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| I2ADHGP4HL6J37NQAD73J7E5SKFIXJOT || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| JEDZYC2HMGDBIDQKG3XSTXUSHMCBK725 || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| JPQKPRI5FMTQRJF4ZZMYZYDQVRD55OTC || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| OYW2XTDKSNKGSEZ27LMGNOPJSYIXHBHC || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| S7N5FE42F6ONPNDQLCF64E2MGFYKQR2I || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| TKT4UESIKTTRALRRLWS4SENSTJX6ODCW || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| UENJPVZ7HVHM6QGVGT6MWOJGGRTUTJXQ || Anton Churyumov || @tonych || 2016-12-25<br />
|-<br />
| MEJGDND55XNON7UU3ZKERJIZMMXJTVCV || anon || @seb486 || 2017-05-25<br />
|-<br />
| 4GDZSXHEFVFMHCUCSHZVXBVF5T2LJHMU || Rogier Eijkelhof || @Rogier || 2018-10-23<br />
|-<br />
| FAB6TH7IRAVHDLK2AAWY5YBE6CEBUACF || Fabien Marino || @fabien || 2019-04-16<br />
|-<br />
| 2TO6NYBGX3NF5QS24MQLFR7KXYAMCIE5 || Bosch Connectory || N/A || 2019-12-27<br />
|}<br />
<br />
<hr /><br />
<br />
==FAQ about witnesses, double spending, finality==<br />
<br />
===Witnesses and consensus===<br />
<br />
Q: Those witnesses that wallet has chosen that will try to determine the validity of the transaction/message?<br /><br />
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. <br />
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.<br />
<br />
Q: Are witnesses required to validate all transactions?<br /><br />
A: Witnesses are required to be full nodes, hence validate all transactions<br />
<br />
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?<br /><br />
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)<br />
<br />
Q: Does a full node need to receive and validate all transactions?<br /><br />
A: Yes, that's the definition of a full node<br />
<br />
Q: To illustrate how little a witness has to decide:<br /><br />
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.<br />
<br />
Q: The witnesses together they decide which branch of the transaction tree is the real one?<br /><br />
A: More accurate wording: they don't decide but enable others to decide, by looking at witnesses as markers of reality<br />
<br />
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?<br /><br />
A: Correct.<br />
<br />
Q: Are the “witnessing” units specialised by any means?<br /><br />
A: There are no specialised witnessing units. Any witness-authored unit counts as “witnessing” unit<br />
<br />
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?<br /><br />
A: Correct<br />
<br />
Q: The protocol requires that transactors have an overlap of 11 (out of 12) witnesses, correct?<br /><br />
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<br />
<br />
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?<br /><br />
A: No, witnesses do not determine the chain state<br />
<br />
Q: is there an option of organic replacement of one or more witnesses?<br /><br />
A: Edit the list in the wallet settings<br />
<br />
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?<br /><br />
A: If we define users as those who post transactions to the DAG, No.<br />
<br />
Q: Is it possible to choose 12 completely new witnesses for my wallet? What would happen?<br /><br />
A: Possible but you won’t be able to post any transactions until all active users migrate to roughly the same list<br />
<br />
Q: What does “predominant witnesses” mean?<br /><br />
A: Those that you see on the most recently posted units (they can be slightly different)<br />
<br />
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?<br /><br />
A: Yes, the majority of the current predominant witnesses<br />
<br />
Q: If an individual, company or government seizes a witness (or all), would they be able to censor transactions?<br /><br />
A: If "a" witness, no, they will only censor out themselves. If all witnesses, yes.<br />
<br />
Q: What happens if all witnesses are shut down?<br /><br />
A: There will be no confirmations. The MC will still be there but the “stability point” will stop advancing.<br />
<br />
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?<br /><br />
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.<br />
<br />
===Double spending===<br />
Q: Are full (or light) nodes capable of identifying and solving double spend attempts without the use of witnesses?<br /><br />
A: No, they need the witness-authorized units’ positions on the DAG to build the MC, and they use the MC to resolve doublespends<br />
<br />
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?<br /><br />
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.<br />
<br />
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?<br /><br />
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.<br />
<br />
===Finality in Byteball===<br />
Q: What is “finality” in Byteball?<br /><br />
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”)<br />
<br />
Q:.What is “stability point” in Byteball?<br /><br />
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.<br />
<br />
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).<br /><br />
A: No, it is not allowed.<br />
<br />
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? <br />
A: if the colluding witnesses are a majority, the network will get into undefined state once they publish the shadow chain<br />
<br />
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?<br /><br />
A: Every full node replays the entire history and recalculates the stability point itself<br />
<br />
==Additional comments==<br />
[Slack 11:00 PM 2017-06-22]<br /><br />
<br />
<blockquote>'''markcross:''' And it's those witnesses that wallet has chosen that will try to determine the validity of the transaction/message?</blockquote><br />
<br />
<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. <br />
<br />
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.<br />
</blockquote><br />
<br />
[Bitcointalk 2017-02-06]<br />
<br />
<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><br />
<br />
===Decentralizing witnesses===<br />
[Bitcointalk 2018-03-21]<br />
<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><br />
<br />
<br />
===Witness functions===<br />
[Slack 2018-05-14]<br />
<br />
<blockquote>'''tonych:'''<br />
> · Are witnesses required to validate all transactions?<br /><br />
witnesses are required to be full nodes, hence validate all transactions<br /><br />
> · What happens if all witnesses are shut down?<br /><br />
there will be no confirmations. The MC [main chain] will still be there but the stability point will stop advancing<br /><br />
> · If an individual, company or government seizes a witness (or all), would they be able to censor transactions?<br /><br />
If "a" witness, no, they will only censor out themselves. If all witnesses, yes.<br /><br />
> So in effect, a witness has the same role as any other full node, except when attempts of double spends without partial order occur?<br /><br />
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<br /><br />
> Every full node validates all transactions?<br /><br />
Yes, that's the definition of a full node<br />
> · Are full (or light) nodes capable of identifying and solving double-spend attempts without the use of witnesses?<br /><br />
No, they need witness positions on the DAG to build the MC, and they use the MC to resolve doublespends</blockquote><br />
<br />
<blockquote>'''Tsonko Mirchev:''' Is that mean that full node doesn't need MC to resolve doublespends?</blockquote><br />
<br />
<blockquote>'''tonych:''' no, it needs the MC</blockquote><br />
<br />
<blockquote>'''tonych:''' another thing to illustrate how little a witness has to decide:<br />
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><br />
<br />
<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><br />
<br />
<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. <br />
<br />
Which of these is wrong?</blockquote><br />
<br />
<blockquote>'''tonych:''' no, witnesses do not "stamp", stamping would make them gatekeepers</blockquote><br />
<br />
<blockquote>'''tonych:''' the functions are just to 1) be honest, and 2) be there<br />
<br />
> because together they decide which branch of the transaction tree is the real one<br />
more accurate wording: they don't decide but enable others to decide, by looking at witnesses as markers of reality<br />
> Hm, I added Bittrex as a witness and the explorer considers the tx stable, but my wallet doesn't<br />
<br />
if your wallet is light, it sees stability later</blockquote><br />
<br />
<blockquote>'''slackjore:''' OK. I was using the word "stamp" wrongly, to mean basically "comment upon". How about my other assumptions?</blockquote><br />
<br />
<blockquote>'''tonych:'''(2) correct<br /><br />
(3) correct, the "additional software" is anything responsible for frequent posting of transactions<br /><br />
(4) correct<br /><br />
(5) correct<br /><br />
(6) of course</blockquote><br />
<br />
<blockquote>'''slackjore:''' Thank you. So how can Bittrex act as an unknowing witness, if a witness has to author units?</blockquote><br />
<br />
<blockquote>'''tonych:''' they do withdrawals and other txs from this address</blockquote><br />
<br />
<blockquote>'''slackjore:'''yes, but you said: https://byteball.slack.com/archives/C9GDDLW0N/p1526293317000487<br />
tonych<br />
another thing to illustrate how little a witness has to decide:<br />
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.<br />
Posted in #marketing_discussionToday at 11:21 AM</blockquote><br />
<br />
<blockquote>'''tonych:''' yes, any contradiction?</blockquote><br />
<br />
<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><br />
<br />
<blockquote>'''tonych:''' there are no specialised witnessing units, any witness-authored unit counts</blockquote><br />
<br />
<blockquote>'''slackjore:''' I mean a unit like this: https://explorer.byteball.org/#OaMFZKr+2zQp4Ce0Oxz0tpTaB4Jb2jLDYcrLACxt+jA=<br />
arbitrary, first one I saw</blockquote><br />
<br />
<blockquote>'''tonych:''' nothing special in it</blockquote><br />
<br />
<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.<br />
<br />
Is that correct?</blockquote><br />
<br />
<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><br />
<br />
<blockquote>'''slackjore:''' ok, great, now I understand how Bittrex could be an unknowing witness. Thank you very much indeed.</blockquote><br />
<br />
-----<br />
<br />
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?<br />
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”?<br />
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?<br />
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?<br />
<br />
tonych [12:18 PM]<br />
1. the witnesses of the newly added unit<br />
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.<br />
3. correct<br />
4. correct<br />
<br />
tony:<br />
1.<br />
> Is it correct to state that the “current MC” is determined by the witnesses of the unit in the current stability point?<br />
No, no witness list matters at all at this step. You just define the best parent using witnessed level and level<br />
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<br />
<br />
===Experiment===<br />
<blockquote>slackjore [2018-05-26 1:16 PM]: <br />
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)<br />
<br />
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.<br />
now it's confirmed in my wallet, 11 minutes after the tx<br />
<br />
Bittrex is still set as a witness, as I had turned off the update-witnesses-from-hub switch</blockquote><br />
<br />
<br />
==How to become a witness==<br />
To become a winess, you are expected to:<br />
<br />
*have a publicly known real name, no anonymity<br />
*be well known in the community<br />
*be trusted<br />
*have a lot to lose (material and/or nonmaterial) in case of misbehavior. The loss is your business (outside Byteball) and/or reputation<br />
*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)<br />
*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.<br />
<br />
If you think that you satisfy these criteria, this is your course of action: <snip><ref>https://github.com/byteball/byteball-witness</ref><br />
<br />
==External links==<br />
*[https://www.youtube.com/watch?v=N1aWPAm0SdY&feature=youtu.be Video: Byteball Witnesses - the basics explained]<br />
*[https://medium.com/obyte/first-decentralized-witness-candidate-rogier-eijkelhof-9e5619166334 First decentralized witness candidate]<br />
*[https://medium.com/obyte/bosch-connectory-approved-as-obyte-witness-670845eb9e03 Bosch Connectory Approved as Obyte Witness]<br />
<br />
==References==<br />
<references /><br />
[[Category:Features]]</div>Slackjorehttp://wiki.obyte.org/mediawiki/index.php?title=Glossary&diff=1508Glossary2019-12-31T12:08:09Z<p>Slackjore: added DRAW (weekly airdrop)</p>
<hr />
<div>Obyte terms, not too technical, but assuming some familiarity with cryptocurrencies <br />
<br />
==Entries==<br />
'''ADDRESS:''' (Disambiguation) <br />
<br />
* A device address is all upper case, starts with 0, looks like 0VCPO8MYDRN2E6N5JDRHRLTVEVZSZYARM<br />
<br />
* A payment address in a wallet is all upper case, looks like K7RMH5EFPZW67JTS5B5GA6PDZA4MYX4LY<br />
<br />
* A wallet ID looks like lNeHNjLs3u38SJ9dPb+SUZ+aZX3a7RWI1osYJH9QHRw=<br />
<br />
* A unit address, like a transaction you sent, looks like Ip241kkFRkZnaVF61Z6+/JW3YELOaHn9C6PAjeMp8fs= <br />
<br />
* A bitcoin address looks like 13AM4VW2dhxYgXeQepoHkHSQuy6NgaEb94, may also start with "3" or "bc1".<br />
<br />
'''AIR-DROP:''' The final snapshot for distribution of new bytes to payment addresses linked to proven BTC balances occurred on 4 November 2017 at 05:23 UTC. <br />
<br />
* For each 1 BTC linked --> 6.25MB (0.00625GB) <br />
<br />
* For each 1 BTC linked --> 2.1111 x 6.25 million blackbytes (money supply of blackbytes is 2.1111 times as much as that of bytes)<br />
<br />
* For every 10 (white)bytes on any address --> 1 new (white)byte<br />
<br />
* For every 10 (white)bytes on a '''linked''' address --> 2.1111 new blackbytes.<br />
<br />
See wiki [[Airdrop]] article.<br />
<br />
'''ASSET:''' Users can issue new assets and define rules that govern their transferability. For example: ICOs, shares, bonds, fiat-pegged coins, loyalty points, minutes of airtime, assets in online games, whatever you can imagine. You can do this in Obyte right now. See wiki article [[Asset]] for instructions<br />
<br />
'''ATOMIC EXCHANGE:''' When two parties sign a single unit that executes both legs of the exchange, the two transactions either happen simultaneously or don't happen at all. It is no longer necessary to trust any centralized exchanges. Note this uses a definition of "atomic" related to databases, and has nothing to do with the usual "extremely small" senses.<ref>https://obyte.org Front page, other features</ref><br />
<br />
'''ATTESTOR:''' The attestor who attests the email addresses through the [[Chatbot#Email_attestation_bot|Email attestation bot]] is <code>H5EZTQE7ABFH27AUDTQFMZIALANK6RBG</code>, and it is also a WITNESS. The attestor is trusted to post only true Obyte-address-to-email-address links to the DAG.<ref>https://medium.com/byteball/distribution-to-verified-emails-and-sending-cryptocurrency-to-email-episode-ii-cb955fe19d7e</ref><br />
<br />
'''AUTHOR:''' (In explorer) Authors are payment addresses that signed the transaction, similar to bitcoin sending address.<br />
<br />
'''AUTONOMOUS AGENT:''' An [[Autonomous Agent]] (AA) is a special address (account) on the ledger that acts according to a program associated with it. Its behavior is similar to that of a vending machine that receives coins and data entered on a keypad and in response, releases a cup of coffee, plays a song, or does whatever it was programmed to do.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
'''BBIP:''' Byteball Improvement Proposal. Replaced by OIP.<br />
<br />
'''BIND:''' See CONDITIONAL PAYMENTS<br />
<br />
'''BLACKBYTE:''' One of the two native Obyte currencies (also see BYTE). When you want complete privacy pay in blackbytes, a cash-like untraceable currency whose transactions are not visible on the public database. They are sent peer-to-peer instead.<ref>https://obyte.org Front page</ref>. With wallet version 2.3 they can be sent by digital file to someone not in Obyte yet.<ref>https://medium.com/byteball/private-textcoins-6a2288d80757</ref><br />
<br />
'''BOT:''' See CHATBOT<br />
<br />
'''BOT STORE:''' The section in the Obyte platform, available from the CHAT tab, that contains about 20 bots you can add to your contacts.<br />
<br />
'''BYTE:''' One of the two native currencies of the Obyte network (also see BLACKBYTE). It is also a basic general computing term: *A sequence of adjacent bits, usually eight, operated on as a unit, e.g. 0 1 0 1 1 1 0 1. One byte can store one character, e.g. 'A' or 'x' or '$'.* There are 10^15 total Bytes in the system. The unit traded on exchanges is the "GByte", 10^9 Bytes.<br />
<br />
'''BYTEBALL (NAME):''' (1) Once a unit is broadcast into the network, and other users start building their units on top of it (referencing it as parent), the number of secondary revisions required to edit this unit hence grows like a snowball. That’s why we call this design '''Byteball''' (our snowflakes are bytes of data).<ref>https://obyte.org/Byteball.pdf p.5</ref> [Rebranded to ''Obyte'' on 17 Jan 2019]<br />
<br />
(2) ''Byteball'' (upper-case "B") was the name of the platform, the protocol; ''byteball'' (lower-case "b") was sometimes (mis)used very loosely to represent the currency, as in "Hey, I see a byteball [1 GB] is now worth $250!" or "Use blackbytes for private transactions and byteballs for the open ones".<br />
<br />
'''BYTEROLL:''' The original Byteball wiki was hosted at byteroll.com on @portabella's private server. The Byteball wiki subdomain forwarded to Byteroll.<br />
<br />
'''CASHBACK:''' We want to get this coin into the hands of as many people as possible. In addition to the regular monthly airdrop, we are going to partner with several categories of companies, like merchants, payment processors, and "Bitcoin debit card" companies. We will offer 10% [[cashback]], paid in Bytes, for all qualifying purchases (no matter how the purchases are paid). <br />
<br />
'''CHAT:''' The platform incorporates a chat function, allowing the user to exchange end-to-end-encrypted messages using AES with a peer or bot when their devices are paired. It's end-to-end encrypted using AES. The hubs only forward the encrypted messages; they can't see anything. To deliver your message, your platform connects to the recipient's hub (if it's different from your home hub).<ref>https://bitcointalk.org/index.php?topic=1608859.msg21798347#msg21798347</ref><br />
<br />
'''CHATBOT:''' You can pair your platform with a bot, which emulates the experience of chatting with a live person. The bot will have very limited responses, but enough to get the job done. A merchant bot could allow you to select from a range of pizzas, for example, then pay for your order with two clicks while still in that chat session. See the wiki [[Chatbot]] article for a list.<br />
<br />
'''CHILDREN:''' (In explorer) Children and parents are pointers to later and earlier units in the DAG (see the arrows between units).<br />
<br />
'''CONDITIONAL PAYMENTS:''' This is the '''killer feature''' of Obyte, and the "smart payments" in the [[slogan]]. You can choose to bind a payment to a condition. If/when that condition is satisfied the payment is unlocked and only the recipient can collect it. If the condition fails the payment can only be collected by the issuer. See the wiki [[Trading blackbytes]] article for an example.<br />
<br />
'''CONFIRMED:''' An Obyte payment is confirmed/stable once it has become sufficiently buried by later transactions to be unalterable, similar to confirmations on a blockchain. It usually takes about five minutes.<br />
<br />
'''DAG:''' [[Directed_acyclic_graph]], the radically-different immutable data structure used in the Obyte platform instead of the usual cryptocurrency blockchain. No mining, no proof-of-work, no proof-of-stake.<ref>https://obyte.org/Byteball.pdf White paper</ref><br />
<br />
'''DATAFEED:''' A line item posted into the DAG by an oracle. The data is of the form [Datafeed name] then [Datafeed value], for example <code>BTC_USD: 6788.0</code>.<br />
<br />
'''DISTRIBUTION:''' See AIRDROP. For current campaigns to give away undistributed bytes, see https://obyte.org/#dist.<br />
<br />
'''DOUBLE-SPEND:''' In case of doublespend, the version that comes earlier on the main chain wins. Therefore, if your node is well-connected and you see a few other transactions piling up on top of the new unconfirmed transaction, and the time since its arrival is significantly larger than the typical network latency, then you can be reasonably sure that even if a doublespend appears later it will be sorted later, hence voided.<br />
<br />
'''DRAW:''' A weekly random airdrop to existing bytes holders, started Dec 8, 2018.<ref>https://medium.com/obyte/weekly-draw-for-the-byteball-community-f464ae731c88</ref> As a distribution method it was superseded July 18, 2019 by the Autonomous Agent developer contest.<ref>https://medium.com/obyte/distribution-outlook-bb28ff0b91aa</ref><br />
<br />
'''FREE UNIT:''' A unit that has no children.<br />
<br />
'''FULLY FUNDED:''' The state of a SMART CONTRACT when the agreed payments from both parties have been locked in the contract until certain conditions are satisfied. See the wiki [[Smart contract]] article.<br />
<br />
'''FUN-COIN:''' A freely-available token on the Obyte platform having zero monetary value, intended for practice with various features like textcoin and smart contracts. See the wiki [[fun-coins]] article.<br />
<br />
'''GENESIS UNIT:''' The Obyte analog to Bitcoin's genesis block, including the creation of the entire global supply of its native currencies: 1,000,000 GBytes and 2,111,100 GBBytes. <br />
<br />
'''GRANTS:''' Obyte Grants Program. We’ll pay for work that improves the ecosystem. We want the contributors to both come up with new ideas and realize them.<ref>https://medium.com/byteball/byteball-grants-program-906a71b93d3c)</ref><br />
<br />
'''HUB:''' This is a node for the Obyte network that serves as a relay, plus it facilitates the exchange of end-to-end encrypted messages among devices connected to the Obyte network. The hub does not hold any private keys and cannot send payments itself, nor can it read the messages. Users set their hub address in their wallet settings. The default hub is wss://obyte.org/bb but users can change it.<ref>https://github.com/byteball/byteball-hub) Github readme.md</ref> See wiki [[Hub]] article.<br />
<br />
'''ICO:''' An '''initial coin offering''' is a controversial means of crowdfunding centered around cryptocurrency, which can be a source of capital for startup companies. In an ICO, a quantity of the crowdfunded cryptocurrency is preallocated to investors in the form of "tokens", in exchange for legal tender or other cryptocurrencies such as bitcoin or ethereum. These tokens supposedly become functional units of currency if or when the ICO's funding goal is met and the project launches.<ref>https://en.wikipedia.org/wiki/Initial_coin_offering</ref> Obyte has an ICO bot, and anyone can issue tokens on the platform.<br />
<br />
'''IDENTITY VERIFICATION:''' Proving one's real-world identity with government-issued documentation using the [[Chatbot#Real_name_attestation_bot|REAL NAME ATTESTATION bot]], but after this one can verify age or country of origin without disclosing further identifying information. Same as REAL NAME ATTESTATION<br />
<br />
'''LINKED:''' Concerning airdrops, it refers to (white)bytes at one of your wallet addresses linked to bitcoins, where the link has been verified by the transition bot. All such pairs were visible on the transition pages<ref>https://transition.byteball.org</ref>.<br />
<br />
'''MOVED:''' In a wallet history, shows funds moving from one address in your wallet to a different address in the same wallet. Either you deliberately sent them there, or they moved as change. See wiki article [[Change address]].<br />
<br />
'''MULTI SIGNATURE:''' For security, you can require that your funds be spendable only when several signatures are provided, e.g. from your laptop and from your phone. For shared control of funds, signatures from different people may be required.<ref>https://obyte.org front page, other features</ref><br />
<br />
'''NODE:''' Imagine a fishing net: the nodes would be the knots holding the lines of rope together. Every device in the Obyte network is technically a node, whether a light client/platform, a full platform, a relay or a hub. Informally, node is used to mean full platform. See wiki article [[Node]] for different roles.<br />
<br />
'''O:''' [Tony:] O in Obyte stands for Open. When we renamed, many people wondered what O stands for. While it is true that it replaces the former "ball", I also want to make it clear that O stands for Open. It speaks about the core values of the platform: open access to the ledger, not encumbered by miners or other intermediaries, which simply do not exist here in a DAG. We are going to have more O-names for the products built on top of the platform.<ref>https://www.reddit.com/r/obyte/comments/aioub3/o_in_obyte_stands_for_open</ref><br />
<br />
'''OBYTE COMMUNITY FUND:''' The [[Obyte_community_fund|Obyte Community Fund]]'s goal is to support and encourage the Obyte crypto platform. Fundraising is done by voluntary donations from investors, stakeholders and enthusiasts. <br />
<br />
'''ODEX:''' DEX is a Decentralized Exchanged. [[ODEX]] is Obyte's DEX.<br />
<br />
'''OIP:''' Obyte Improvement Proposal. Based on the Bitcoin BIP system. See [[OIP]] wiki article.<br />
<br />
'''ORACLE:''' A trusted third party that monitors specific external events and registers selected data-feed items to the Obyte database. An example is a list of cryptocurrency exchange rates updated every ten minutes. When dealing with untrusted counterparties, you can lock the funds on a payment address that is spendable either by you or by the counterparty, depending on the oracle's data collection and registration.<ref>https://obyte.org front page, other features</ref> See wiki article [[Oracle]].<br />
<br />
'''OSCRIPT:''' AUTONOMOUS AGENTS are written in Oscript — a new programming language developed specifically for this purpose.<ref>https://medium.com/obyte/introducing-autonomous-agents-6fe12fb12aa3</ref><br />
<br />
'''P2P INSURANCE:''' Insurance against a negative event provided by another peer instead of a faceless company. An example is flight delays insurance.<ref>https://medium.com/byteball/making-p2p-great-again-episode-iv-p2p-insurance-cbbd1e59d527</ref><br />
<br />
'''PAIR:''' To link with another Obyte device, either remote or face-to-face, use a pairing code generated by either device. In your wallet, '''Chat > add a new device > invite the other device''' OR '''Chat > add a new device > accept invitation'''. The code can then be sent by pasting it into a non-platform messaging app, or by QR code.<br />
<br />
'''PARENTS:''' (In explorer) Children and parents are pointers to later and earlier units in the DAG (see the arrows between units).<br />
<br />
'''PLATFORM:''' (1) Generally, refers to the entire Obyte protocol, as in "You can easily create new custom assets that will run on the platform." (2) An instance of the Obyte platform software installed on one of your devices, sometimes called a ''wallet''. But that name is confusing as this platform instance can contain many wallets, for example a Single-Address Wallet, a Small Expenses Wallet, a Savings Wallet, etc. A full platform/wallet downloads the whole Obyte database, a light platform/wallet doesn't. See wiki article [[Node]] for different roles, and [[Wallet]] for many more details.<br />
<br />
'''POLL:''' See VOTE. Also marketing [[polls]] via Twitter etc, in usual meaning of the word.<br />
<br />
'''PREDICTION MARKETS:''' Prediction markets are (usually) exchange-traded markets created for the purpose of trading the outcome of events. The purpose of the Slack<ref>https://obyte.slack.com</ref> #prediction_markets channel was "Finding a counterpart for bets on future events". See wiki article [[Trading prediction markets]].<br />
<br />
'''PROSAIC CONTRACT:''' See the wiki [[Prosaic contract]] article. Compare SMART CONTRACT<br />
<br />
'''REAL NAME ATTESTATION:''' See IDENTITY VERIFICATION<br />
<br />
'''RECOVER:''' Recovery is available in single-sig (i.e., not multi-sig) light platforms from version 1.10.1, and full platforms too. Note that blackbytes are not included. Also see RESTORE<br />
<br />
'''REFERRAL:''' A [[referral]] is getting a second person to install the Obyte wallet on his own device (smartphone or computer) and doing an attestation from that device/wallet, using Bytes received from the first person.<br />
<br />
'''REGULATED ASSETS:''' Regulated institutions can issue assets that are compatible with KYC/AML requirements. Every transfer of such asset is to be cosigned by the issuer, and if there is anything that contradicts the regulations, the issuer won't cosign.<ref>https://obyte.org front page, other features</ref><br />
<br />
'''RELAY:''' This is a node for the Obyte network that stores the entire database and forwards new storage units to peers. The relay does not hold any private keys and cannot send payments itself.<ref>https://github.com/byteball/byteball-relay readme.md</ref> See wiki article [[Node]] for different roles.<br />
<br />
'''RESTORE:''' To restore from a full backup. This also includes private assets. Works with any wallet type. Also see RECOVER<br />
<br />
'''SINGLE-ADDRESS WALLET:''' These wallets have only one payment address and the change always returns to the same address, supporting applications that require a stable identity. For example, you can run a manual oracle right from your wallet without having to run a node on a server. This allows you to run a PREDICTION MARKET for a future event, enabling users to make contracts (bets) referencing your payment address as an oracle, and when the outcome of the event is known you post its result from your wallet. See the wiki [[Wallet]] article.<br />
<br />
'''SMART CONTRACT/WALLET:''' See the wiki [[Smart contract]] article. See CONDITIONAL PAYMENTS. Compare PROSAIC CONTRACT <br />
<br />
'''SMART VOUCHER:''' A coupon to fund IDENTITY VERIFICATION / REAL NAME ATTESTATION for new users. See the wiki [Smart Voucher]] article.<br />
<br />
'''STABLE:''' See CONFIRMED<br />
<br />
'''STORAGE UNIT:''' Obyte 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]. <ref>https://obyte.org/Byteball.pdf</ref><br />
<br />
'''TANGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Tangos]] article.<br />
<br />
'''TEXTCOIN:''' Sending Obyte funds from one's wallet through a text app, such as an email, Telegram, WhatsApp etc. See the wiki [[Textcoin]] article. <br />
<br />
'''TINGOS:''' A Obyte fun-coin created in January 2018. See the wiki [[Tingos]] article.<br />
<br />
'''TRANSACTION FEE:''' The fee you pay is identical to the size of the data you want stored. So a storage unit that takes up 18,000 bytes in the distributed Obyte database will cost 18,000 (white)Bytes to send there. Currently a usual transaction fee is maybe 500 Bytes, with a blackbytes fee being maybe 1000 Bytes or so. If 1GB = $750, then 1MB = $0.75, and 1KB (1000 bytes) = $0.00075. So that's less than 1/10 cent US.<br />
<br />
'''TRANSITION BOT:''' After installing the wallet, one chatted with the Transition Bot to participate in the next distribution round. See the wiki article [[Airdrop]].<br />
<br />
'''UNIT:''' (In explorer) Unit is hash of data unit, similar to bitcoin transaction ID, but a unit can have more than just a transaction.<br />
<br />
'''VOTE:''' (In platform [[chatbot|Poll bot]]) A vote is a small transaction that pays to yourself and is signed by your most funded addresses; the weight of the vote is the combined balance of the signing addresses. Note that there is a privacy concern because by making a vote you associate a number of your addresses. <br />
<br />
'''WALLET:''' The Obyte PLATFORM software a regular user downloads/installs comes with a default SINGLE-ADDRESS WALLET, but you can create as many more wallets as you wish. See wiki article [[wallet]] for many more wallet details, and other wiki articles for what you can do with the platform and wallets you create.<br />
<br />
'''WITNESS:''' A witness is a highly reputable user with a real-world identity, who stamps 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. This list varies very little from transaction to transaction. If 11 witnesses say no to a bad transaction and 1 says yes, that witness gets deemed unreliable and effectively fired. It would be unthinkable for all 12 to collude and allow a fraudulent transaction through. In this way the network is safeguarded.<ref>https://obyte.org/Byteball.pdf</ref><br />
<br />
'''ZANGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Zangos]] article.<br />
<br />
'''ZINGOS:''' An Obyte fun-coin created in January 2018. See the wiki [[Zingos]] article.<br />
<br />
'''ZWIB:''' The first Obyte new asset/token traded on Slack. The name comes from the unit address, *ZW1b...* <br />
<br />
==External links==<br />
<br />
==References==<br />
<references /><br />
<br />
[[Category:Browse]]</div>Slackjore