Difference between revisions of "Use-a-thon/botwar"
(→Known participants: added blog posts) |
(updated name) |
||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[File:botwar.png|thumb]] | [[File:botwar.png|thumb]] | ||
| − | == The Great | + | == The Great [Obyte] Bot War == |
| − | We invite developers to create [[chatbot|Chat Bots]] for the | + | 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. |
==Contest format== | ==Contest format== | ||
| Line 14: | Line 14: | ||
===Weekly prizes=== | ===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 | + | 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=== | ===Referral rewards=== | ||
| Line 42: | Line 42: | ||
==Evaluation and jury== | ==Evaluation and jury== | ||
The jury will consist of: | 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 | + | 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 | *Solve a real world problem | ||
*Reduce friction in a process | *Reduce friction in a process | ||
*Have a clear and easily-understood purpose | *Have a clear and easily-understood purpose | ||
| − | *Add something new and interesting to the | + | *Add something new and interesting to the Obyte ecosystem |
*Be able to run sustainably without huge costs for the operator. | *Be able to run sustainably without huge costs for the operator. | ||
==Useful help and resources== | ==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. | |
| − | Don’t have any experience with the | + | 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]. |
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]. | Some sections you may find useful are [https://developer.byteball.org/writing-chatbots-for-byteball Writing chatbots], [https://developer.byteball.org/issuing-assets-on-byteball Issuing assets] and [https://developer.byteball.org/smart-contracts Smart contract definitions]. | ||
| − | The developer site documents multiple APIs that you may want to explore, has guides and tutorials showcasing | + | 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. |
| − | If you have coding skills but lack ideas, drop by the | + | 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]. |
| − | On Telegram, we have a [https://t.me/devbyteball dedicated developer’s group] as well. You are also encouraged to join the [https://slack. | + | 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. |
| − | ==Get your bot listed in the | + | ==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. | 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. | ||
| Line 79: | Line 79: | ||
! User/Link !! Entrant address !! Referral address !! Notes | ! User/Link !! Entrant address !! Referral address !! Notes | ||
|- | |- | ||
| − | | [https://github.com/kaiurin Andrii] || [https://explorer. | + | | [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. | + | | [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. | + | | [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. | + | | [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. | + | | [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] |
| + | |- | ||
| + | | [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)] | ||
|} | |} | ||
| Line 93: | Line 95: | ||
* [https://steemit.com/byteball/@byteball.org/byteball-bot-war-week-1 Week 1] | * [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-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
Contents
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
- Each contestant must fill out this form to enter the contest.
- All code must be published under MIT license on GitHub.
- The bot must apply at least one DAG feature (e.g. payments, storage, attestation etc.)
Weekly progress reports must be submitted to the jury by Friday to be eligible to win the weekly progress award announced on Sunday. Progress reports can be articles, blog posts, videos or similar must be publicly accessible. Submit your report using 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
...
