Difference between revisions of "Use-a-thon/botwar"

From Obyte Wiki
(editing incomplete)
(updated name)
 
(37 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
[[File:useathon-banner-2.png|thumb]]
+
[[File:botwar.png|thumb]]
  
−
'''Editing very incomplete'''
+
== The Great [Obyte] Bot War ==
 +
We invite developers to create [[chatbot|Chat Bots]] for the [Obyte] platform in a contest to build the most awesome, useful, innovative and creative chat bot. The best ideas will be rewarded generously.
  
−
== Here’s your chance to get more Bytes ==
+
==Contest format==
−
Since the airdrop, almost 70,000 Steem users have linked their Steem username to their Byteball wallet. 5,400 GBYTE was distributed to users while 8,500 GBYTE are locked in smart contracts to be released next year.
+
Over a 4 week period, developers battle in the fine art of coding chat bots. There will be weekly reviews of each contestant’s progress (if the contestant share it) and a weekly award will be granted to the bot creator that provides the best, funniest or most engaging article, blog-post or video.
−
 
 
−
To encourage users to explore the Byteball platform and the possibilities it offers, Byteball hereby announces a contest in creating innovative use cases during the contest period. Steem users are encouraged to compete.  
 
  
 +
==Prizes==
 
===Main prizes===
 
===Main prizes===
−
*1st place: 10 GBYTE
+
*1st place: USD 1000 in Bytes (approx 25-35 GB)
−
*2nd place: 5 GBYTE
+
*2nd place: USD 500 in Bytes
−
*3rd place: 2 GBYTE
+
*3rd place: USD 250 in Bytes
  
 
===Weekly prizes===
 
===Weekly prizes===
−
Users are encouraged to share their progress on their Steem blog. Every Sunday during the contest period (Sept 2, 9, 16, 23), a jury of Byteball staff and veterans will pick the most interesting, promising, fun, ingenious or remarkable progress report and the user will be rewarded with 1 GBYTE. The weekly winner will be announced in a weekly contest update posted on the @Byteball blog<ref>https://steemit.com/@byteball.org</ref>. All prizes will be transferred to the wallet used when paying the entry fee.
+
Each Sunday, the jury will pick the best, most interesting, most informative, funniest or most engaging article, blog post or YouTube video showing the past week’s progress. The best will be awarded $50 worth of Bytes, sent to the dev's registered address. Developers must provide a link to a publicly visible blog, article or other medium by Friday 20:00 UTC. Participants and links to progress reports will be kept updated on this [Obyte] Wiki page.
 +
 
 +
===Referral rewards===
 +
Know an awesome developer that would surely win this contest? Then ask him to join and get a reward of 10% of the developer’s prize! Just make sure the developer adds your wallet address on the entry form. So $1000 prize has $100 referral reward, etc. It is OK to invite/refer oneself if there has been no genuine referral (we understand this will occur anyway).
 +
 
 +
==Schedule==
 +
Wednesday December 12: Announcement of contest and official start
 +
 
 +
*Friday December 21, 20.00 UTC: Deadline first weekly progress reports
 +
*Sunday December 23: Announcement of weekly winner of 2 GB award
 +
*Friday December 28, 20.00 UTC: Deadline second weekly progress reports
 +
*Sunday December 30: Announcement of weekly winner of 2 GB award
 +
*Friday January 4, 20.00 UTC: Deadline third weekly progress reports
 +
*Sunday January 6: Announcement of weekly winner of 2 GB award
  
−
== How to participate ==
+
Friday January 11, 23:59:59 UTC: Deadline for all contest entries
−
To join the contest, participants pay an entry fee of 25 MB. The entry fee must be paid from a publicly attested Steem user’s Byteball wallet. This allows us to keep track of participants and to follow your progress on your blogs. All entry fees are added to the prize pool and distributed on a 10:5:2 ratio between the prizes.
 
  
−
Send your 25 MB entry fee from your publicly-attested Steem address to <code>EPZEMB73FGY7O6XMTGA2SFQIDUUV4NT5</code>
+
==Rules and requirements==
 +
#Each contestant must fill out [https://docs.google.com/forms/d/e/1FAIpQLSfqDp80aN0F296m3C20GpFANWbLnNV4YudD0rZWlSHi2VU9cQ/viewform this form] to enter the contest.
 +
#All code must be published under MIT license on GitHub.
 +
#The bot must apply at least one DAG feature (e.g. payments, storage, attestation etc.)
  
−
== What is a Use-a-Thon? ==
+
Weekly progress reports must be submitted to the jury by Friday to be eligible to win the weekly progress award announced on Sunday. Progress reports can be articles, blog posts, videos or similar must be publicly accessible. Submit your report using [https://docs.google.com/forms/d/e/1FAIpQLSeVwr7VZXmeBg7e9coiyyq0Fwo9wYTHTcu8LPPUD11TKucczw/viewform this form].
−
You have probably heard about hack-a-thons, where developers and engineers develop new features for a given product by altering code, hardware or tweaking the product.
 
  
−
A Use-a-Thon doesn’t require development or engineering skills. The aim is to explore, experiment and apply the existing features to solve a real-world problem or fulfill an existing need either online or offline in a local community. So while creating new chat bots and oracles is an option, it’s not required at all. A previous Byteball Use-a-Thon proved that users are able to apply the platform to real-world use cases without knowing programming or underlying technologies at all.
+
All chat bots are welcome in the competition. Whether it’s a revenue-generating use case, an interface to an external resource or whatever you can think of - it’s fair game.
  
−
== What is a use case? ==
+
==Evaluation and jury==
−
A use case is a real-world problem or need that can be addressed with the given tool. Some (but not all) examples could be: introducing smart contracts to enable trustless value exchange between two parties, a web-based mini-game, disrupting an existing market, creating a new service allowing Byteball users to purchase products, allowing Steem users to send tips to each other, creating a private token to be used in an incentive program, or even creating a small business that potentially generates profit for you.
+
The jury will consist of:
 +
*[Obyte] User Acquisition Manager Casper Niebe (@Punqtured)
 +
*[Obyte] Core Developer Evgenii Stulnikov (@xjenek)
 +
*[Obyte] veteran @Slackjore.
 +
The mix of core staff, developers and users helps us evaluate each entry from different perspectives. This means that a brilliant technically-excellent bot with flawless code but no actual real world use would not necessarily have an advantage against a clumsily coded, semi-buggy bot that aims to solve an actual problem or make something easier for Obyte users. Bots should always aim to:
 +
*Solve a real world problem
 +
*Reduce friction in a process
 +
*Have a clear and easily-understood purpose
 +
*Add something new and interesting to the Obyte ecosystem
 +
*Be able to run sustainably without huge costs for the operator.
  
−
Basically, anything goes as long as it involves using the Byteball platform and its features.
+
==Useful help and resources==
 +
Obyte is easy to develop for. The main scripting language is [https://en.wikipedia.org/wiki/Node.js Node.js], which can be run on both backend and frontend.  Any other language works as well by connecting through the easy RPC API.  
  
−
== When is the contest? ==
+
Don’t have any experience with the Obyte platform or developing Chat Bots for it? Don’t panic - there’s plenty of help and inspiration to get! An excellent place to get started is our [https://developer.byteball.org new developer website].  
−
NOW! From the date of this announcement, users can join by paying the entry fee. You can enter as an individual or gather a team to help explore, develop and realize your use case. Each participant is free to create more than one entry.
 
  
−
The contest ends 30 September 2018, 11:59:59 UTC. You must create a post on your blog by this date, describing your use case, current progress, plan for realization, milestones and any relevant information allowing the Jury to evaluate your project. The post must be in English, with the title “Byteball Use-a-Thon: [plus your own title]”, start with a summary (150 words or less), and then the additional information as described above. First tag must be “#byteball” and second tag must be “#useathon”.
+
Some sections you may find useful are [https://developer.byteball.org/writing-chatbots-for-byteball Writing chatbots], [https://developer.byteball.org/issuing-assets-on-byteball Issuing assets] and [https://developer.byteball.org/smart-contracts Smart contract definitions].
  
−
After the deadline, a Jury consisting of @Punqtured, @Slackjore, @Tarmo888 and @Suirelav will evaluate all contributions and determine the winners, who will be announced about a week later.
+
The developer site documents multiple APIs that you may want to explore, has guides and tutorials showcasing Obyte’s most interesting features. [https://github.com/byteball Our GitHub] has loads of source code of existing bots working in production that you may also want to use in your apps.
  
−
== Where can I get more information? ==
+
If you have coding skills but lack ideas, drop by the Obyte Telegram, Slack or Subreddit to see if other users have an interesting idea. You might also be able to find inspiration from one of the previous Use-a-Thons that Obyte hosted. The most recent was for [https://steemit.com/byteball/@byteball.org/steem-use-a-thon-by-byteball-winners-announcement the Steem community].
−
With a constantly growing community, there is a vast library of available resources. Here are some relevant resources:
 
−
*'''Use-a-Thon presentation:''' https://docs.google.com/presentation/d/e/2PACX-1vSIX6sQtVjM-zD9aPzGqNj2dIexehHb2UOArZgIqi1sYX7go_MLOXM_BSJSp7or6xwhiFmG76AnoE9n/pub?start=true&loop=false&delayms=3000 (Use arrow keys to pause and navigate between slides)
 
−
*'''Steem Use-a-Thon Wiki page''' (this page you are currently reading) where all relevant information for the contest can be found
 
−
*'''Byteball Slack''' where users can seek help, ask questions and collaborate: https://slack.byteball.org - please state that you are a participant in the Use-a-Thon.
 
−
*'''Byteball Wiki''' (you're reading it) contains information about all features, references to external sources etc
 
  
−
Additional resources for techies:
+
On Telegram, we have a [https://t.me/devbyteball dedicated developer’s group] as well. You are also encouraged to join the [https://slack.obyte.org/ Byteball Slack] where you can exchange experience with other developers and the core team. Please state in your request, that you’re a participant in the contest. Finally, the Obyte Subreddit is also an excellent place for inspiration, pitching ideas, getting feedback or simply sharing your thoughts.
−
*'''Developer guides''' for those wanting to build new stuff: https://github.com/byteball/byteballcore/wiki/Byteball-Developer-Guides
+
 
−
*'''Easy-to-use JavaScript library''' to easily integrate Byteball features on websites without the need of headless wallets: https://bonustrack.gitbook.io/byteball/getting-started/quick-start
+
==Get your bot listed in the Obyte Bot Store==
−
*'''Byteball main GitHub repository''' for those wanting to dig deep: https://github.com/byteball/byteball
+
Obyte has a fully featured official wallet which contains a Bot Store where you can list your apps. The Bot Store is a prominent part of the wallet, meaning users can easily find your app.
 +
 
 +
With e.g. Ethereum, marketing your app is difficult and expensive. If users don’t find your app, its chance of success is remote. One reason Android and Apple apps have become so popular is because the Apple App Store and the Google Play Store connect users to developers’ apps. This is the way Byteball has chosen, too.
  
 
==Known participants==
 
==Known participants==
−
*List derived from each publicly-attested source of entry fee payment as above.<ref>https://explorer.byteball.org/#EPZEMB73FGY7O6XMTGA2SFQIDUUV4NT5</ref>
+
*[https://docs.google.com/forms/d/e/1FAIpQLSeVwr7VZXmeBg7e9coiyyq0Fwo9wYTHTcu8LPPUD11TKucczw/viewform Form] for weekly reports
−
*Look up username at byteball.co, for example <code>https://byteball.co/@2EVEJTQWQGP3IGPVG24D7AP732TUN6N4/attestations</code>
+
*'''Notes''' includes links to blog botwar posts, and also winners of the weekly prizes
−
*'''Notes''' includes links to blog Use-a-Thon posts, and also winners of the 1 GB weekly prizes (Sept 2, 9, 16, 23)
+
*'''Link''' may be to blog or to Github repo
  
 
{| class="wikitable sortable"
 
{| class="wikitable sortable"
 
|-
 
|-
−
! User/Link to blog !! Registered address/Link to entry fee !! Notes
+
! User/Link !! Entrant address !! Referral address !! Notes
 +
|-
 +
| [https://github.com/kaiurin Andrii] || [https://explorer.obyte.org/#XFYE362P4WGQ4IP6WBBMR5XUQPLEUDI6 XFYE3...] || [https://explorer.obyte.org/#R5YQ7N5N5EDI3CZ24HVKKG6CEUXTDWMT R5YQ7...] || SocialBoost  [https://steemit.com/byteball/@opposition/bot-wars-socialboost Blog post #1], [https://explorer.obyte.org/#f/vEYvUGQWxaB1B548SB3Bb9aMizX3yQeJYiwSiL+D8= 2GB Week 1], [https://steemit.com/byteball/@opposition/bot-wars-third-report-socialboost post #2 (week 3)], [https://steemit.com/utopian-io/@opposition/bot-wars-final-report-socialboost-launched-on-byteball-testnet post #3 (final)]
 +
|-
 +
| [https://steemit.com/@genievot Genievot] || [https://explorer.obyte.org/#D6Z5A3AC4O7IMFBKUNUDMFL33SGE5J2Z D6Z5A...] || [https://explorer.obyte.org/#D6Z5A3AC4O7IMFBKUNUDMFL33SGE5J2Z D6Z5A...] || DonateBytes [https://steemit.com/byteball/@genievot/progress-report-1st-for-byteball-bot-war-1545379943788 Blog post #1]
 +
|-
 +
| [https://github.com/whoisterencelee/know-it-all-bot whoisterencelee] || [https://explorer.obyte.org/#AAHRPI6UTISGNAEJROXPZZDSXJ4YUD52 AAHRP...] || [https://explorer.obyte.org/#AAHRPI6UTISGNAEJROXPZZDSXJ4YUD52 AAHRP...] || Know-it-all [https://steemit.com/byteball/@whoisterencelee/byteball-know-it-all-bot Blog post #1], [https://steemit.com/byteball/@whoisterencelee/byteball-know-it-all-bot-weekly-update-2 post #2], [https://steemit.com/byteball/@whoisterencelee/byteball-know-it-all-bot-weekly-update-3 post #3], [https://steemit.com/byteball/@whoisterencelee/byteball-know-it-all-bot-weekly-update-4 post #4]
 +
|-
 +
| [https://github.com/pmiklos/byteball-carpool Peter Miklos] || [https://explorer.obyte.org/#ETSFNK5RROAIZBPPZTUAI4K6KUV4WUTI ETSFN...] || [https://explorer.obyte.org/#ETSFNK5RROAIZBPPZTUAI4K6KUV4WUTI ETSFN...] || Carpooling for Byteballers [https://steemit.com/byteball/@byteball.market/carpooling-for-byteballers-the-great-byteball-bot-war Blog post #1], [https://steemit.com/byteball/@byteball.market/carpooling-for-byteballers-the-great-byteball-bot-war-week-2 post #2], [https://explorer.obyte.org/#3XsltvYbQMXCjZ16WLDXOA1Oic+9KgbWyIH5JQMFswM= 2GB Week 2], [https://steemit.com/byteball/@byteball.market/carpooling-for-byteballers-the-great-byteball-bot-war-week-3 post #3], [https://steemit.com/byteball/@byteball.market/carpooling-for-byteballers-the-great-byteball-bot-war-week-4 post #4]
 +
|-
 +
| [https://github.com/AnGrYxx/efa-bot AnGr] || [https://explorer.obyte.org/#BMKMY7VXXLKNPAFIGDVMMHUSTC7MJOU3 BMKMY...] || [https://explorer.obyte.org/#UPFWFMSAJDIRHUPJOCKUD6DXMOE5XFKL UPFWF...] || Error Fare Alerts Bot  [https://steemit.com/utopian-io/@angr/byteball-bot-wars-progress-report-1-monetizing-content-with-byteball-error-fare-alerts-bot Blog post #1 (week 3)], [https://explorer.obyte.org/#fojVziXt4OpHs8uCpYUYkXBgcWRtj+6qvUo5rUIkDuI= 2GB Week 3], [https://steemit.com/utopian-io/@angr/byteball-bot-wars-progress-report-2-monetizing-content-and-apis-with-byteball-error-fare-alerts-bot post #2]
 
|-
 
|-
−
| ... || ... || ... blog post #1]
+
| [https://github.com/git-ball/github-attestation DrSensor] || [https://explorer.obyte.org/#ZO3JNGYEKG7AH4YKV43EHEK5YEAVJ4IF ZO3JN...] || [https://explorer.obyte.org/#ZO3JNGYEKG7AH4YKV43EHEK5YEAVJ4IF ZO3JN...] || Github Attestation Bot  [https://steemit.com/byteball/@drsensor/byteball-bot-wars-progress-report-github-attestation-bot Blog post (final)]
 
|}
 
|}
−
 
 
−
===Improper entries===
 
−
These appear to be attempted entries, but aren't (yet) valid:
 
−
...
 
  
 
==Weekly Updates on Byteball.org's blog==
 
==Weekly Updates on Byteball.org's blog==
−
...
+
* [https://steemit.com/byteball/@byteball.org/byteball-bot-war-week-1 Week 1]
 +
* [https://steemit.com/byteball/@byteball.org/byteball-bot-war-week-2 Week 2]
 +
* [https://steemit.com/byteball/@byteball.org/byteball-bot-war-week-3 Week 3]
  
 
==Final winners==
 
==Final winners==

Latest revision as of 20:29, 20 January 2019

Botwar.png

The Great [Obyte] Bot War

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

Contest format

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

Prizes

Main prizes

  • 1st place: USD 1000 in Bytes (approx 25-35 GB)
  • 2nd place: USD 500 in Bytes
  • 3rd place: USD 250 in Bytes

Weekly prizes

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

Referral rewards

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

Schedule

Wednesday December 12: Announcement of contest and official start

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

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

Rules and requirements

  1. Each contestant must fill out this form to enter the contest.
  2. All code must be published under MIT license on GitHub.
  3. The bot must apply at least one DAG feature (e.g. payments, storage, attestation etc.)

Weekly progress reports must be submitted to the jury by Friday to be eligible to win the weekly progress award announced on Sunday. Progress reports can be articles, blog posts, videos or similar must be publicly accessible. Submit your report using this form.

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

Evaluation and jury

The jury will consist of:

  • [Obyte] User Acquisition Manager Casper Niebe (@Punqtured)
  • [Obyte] Core Developer Evgenii Stulnikov (@xjenek)
  • [Obyte] veteran @Slackjore.

The mix of core staff, developers and users helps us evaluate each entry from different perspectives. This means that a brilliant technically-excellent bot with flawless code but no actual real world use would not necessarily have an advantage against a clumsily coded, semi-buggy bot that aims to solve an actual problem or make something easier for Obyte users. Bots should always aim to:

  • Solve a real world problem
  • Reduce friction in a process
  • Have a clear and easily-understood purpose
  • Add something new and interesting to the Obyte ecosystem
  • Be able to run sustainably without huge costs for the operator.

Useful help and resources

Obyte is easy to develop for. The main scripting language is Node.js, which can be run on both backend and frontend. Any other language works as well by connecting through the easy RPC API.

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

Some sections you may find useful are Writing chatbots, Issuing assets and Smart contract definitions.

The developer site documents multiple APIs that you may want to explore, has guides and tutorials showcasing Obyte’s most interesting features. Our GitHub has loads of source code of existing bots working in production that you may also want to use in your apps.

If you have coding skills but lack ideas, drop by the Obyte Telegram, Slack or Subreddit to see if other users have an interesting idea. You might also be able to find inspiration from one of the previous Use-a-Thons that Obyte hosted. The most recent was for the Steem community.

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

Get your bot listed in the Obyte Bot Store

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

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

Known participants

  • Form for weekly reports
  • Notes includes links to blog botwar posts, and also winners of the weekly prizes
  • Link may be to blog or to Github repo
User/Link Entrant address Referral address Notes
Andrii XFYE3... R5YQ7... SocialBoost Blog post #1, 2GB Week 1, post #2 (week 3), post #3 (final)
Genievot D6Z5A... D6Z5A... DonateBytes Blog post #1
whoisterencelee AAHRP... AAHRP... Know-it-all Blog post #1, post #2, post #3, post #4
Peter Miklos ETSFN... ETSFN... Carpooling for Byteballers Blog post #1, post #2, 2GB Week 2, post #3, post #4
AnGr BMKMY... UPFWF... Error Fare Alerts Bot Blog post #1 (week 3), 2GB Week 3, post #2
DrSensor ZO3JN... ZO3JN... Github Attestation Bot Blog post (final)

Weekly Updates on Byteball.org's blog

Final winners

  • 1st Prize: ...
  • 2nd Prize: ...
  • 3rd Prize: ...
  • Honourable Mention(s): ...

Links

...

References

Retrieved from "http://wiki.obyte.org/mediawiki/index.php?title=Use-a-thon/botwar&oldid=1243"