Difference between revisions of "Use-a-thon/steem"
(→Known participants: added link to blog post) |
(→Known participants: added entrants) |
||
| Line 75: | Line 75: | ||
|- | |- | ||
| [https://steemit.com/@malos10 @malos10] || [https://explorer.byteball.org/#Z9odHgkCr/FZBteKt/PGE6LOMY5zTY3T2BTiTU9/UfQ= OFPKEGARWOZ6VPTB4GV5QGCNBC4DLDCN] || [https://steemit.com/byteball/@malos10/byteball-use-a-thon-byteball-a-new-method-of-paymet-to-improve-the-quality-of-life-for-venezuelans blog post #1], [https://steemit.com/byteball/@malos10/byteball-use-a-thon-byteball-bytes-as-a-new-method-of-payment-in-venezuela-report-1 #2], [https://steemit.com/byteball/@malos10/byteball-use-a-thon-byteball-bytes-as-a-new-method-of-payment-in-venezuela-report-2 #3],[https://explorer.byteball.org/#H6FUufTcSgN6gmxPDqt3l8hEl76fJJQYZogjQ9Cnsc4= 16 Sept 1 GB award] | | [https://steemit.com/@malos10 @malos10] || [https://explorer.byteball.org/#Z9odHgkCr/FZBteKt/PGE6LOMY5zTY3T2BTiTU9/UfQ= OFPKEGARWOZ6VPTB4GV5QGCNBC4DLDCN] || [https://steemit.com/byteball/@malos10/byteball-use-a-thon-byteball-a-new-method-of-paymet-to-improve-the-quality-of-life-for-venezuelans blog post #1], [https://steemit.com/byteball/@malos10/byteball-use-a-thon-byteball-bytes-as-a-new-method-of-payment-in-venezuela-report-1 #2], [https://steemit.com/byteball/@malos10/byteball-use-a-thon-byteball-bytes-as-a-new-method-of-payment-in-venezuela-report-2 #3],[https://explorer.byteball.org/#H6FUufTcSgN6gmxPDqt3l8hEl76fJJQYZogjQ9Cnsc4= 16 Sept 1 GB award] | ||
| + | |- | ||
| + | | [https://steemit.com/@jrswab @jrswab] || [https://explorer.byteball.org/#W++uaDE9VcoUmLtJcyEUawfuUGcYWBL8sS6TDzNzw2w= COXXXCJ7Q74ZHKXNLMCPRZE3GO6563NY] || | ||
| + | |- | ||
| + | | [https://steemit.com/@alvaro017 @alvaro017] || [https://explorer.byteball.org/#+K1aiDK+p3qXxghj9oM2uIG7vDMxzlOcAvD1MYyrOMc= O725SR6OAQEKYAMBV526EAO4IDLCSMHT] || | ||
| + | |- | ||
| + | | [https://steemit.com/@mcassani @mcassani] || [https://explorer.byteball.org/#NzVeAvCu0Blq6VLV2FnfXoTe4U9212glN4WJVX/scKw= ZRDH5XEPHEXYEX7MJOKCCVACF6GSJNHI] || | ||
|} | |} | ||
| − | === | + | ===Improper entries=== |
| − | These | + | These appear to be attempted entries, but aren't (yet) valid: |
| − | * | + | |
| + | *GJY5BHZXWNGRS2E4UVPJKY3D4ATKHF4O (only 25 KB paid) | ||
| + | *LW3RB3A6BYD646TA3NWCTCRF7N7HDZ2J (only 25 KB paid) | ||
| + | *MSC2MVQBSWOV7XN3UNCARHZKCGXR36E5 (only 24 MB paid) | ||
| + | *MFKTFQ5K3FXEF3BF5H6WGIHRH6ILCN3U (only 25 bytes paid) | ||
| + | *URP3QER4DDV5PO22D6ROIWHKGUMKZP7J (25 MB paid but from private attestation) | ||
==Weekly Updates on Byteball.org's blog on Steem== | ==Weekly Updates on Byteball.org's blog on Steem== | ||
Revision as of 09:37, 24 September 2018
Contents
Here’s your chance to get more Bytes
Since the airdrop, almost 70,000 Steem users have linked their Steem username to their Byteball wallet. 5,400 GBYTE was distributed to users while 8,500 GBYTE are locked in smart contracts to be released next year.
To encourage users to explore the Byteball platform and the possibilities it offers, Byteball hereby announces a contest in creating innovative use cases during the contest period. Steem users are encouraged to compete.
Main prizes
- 1st place: 10 GBYTE
- 2nd place: 5 GBYTE
- 3rd place: 2 GBYTE
Weekly prizes
Users are encouraged to share their progress on their Steem blog. Every Sunday during the contest period (Sept 2, 9, 16, 23), a jury of Byteball staff and veterans will pick the most interesting, promising, fun, ingenious or remarkable progress report and the user will be rewarded with 1 GBYTE. The weekly winner will be announced in a weekly contest update posted on the @Byteball blog[1]. All prizes will be transferred to the wallet used when paying the entry fee.
How to participate
To join the contest, participants pay an entry fee of 25 MB. The entry fee must be paid from a publicly attested Steem user’s Byteball wallet. This allows us to keep track of participants and to follow your progress on your blogs. All entry fees are added to the prize pool and distributed on a 10:5:2 ratio between the prizes.
Send your 25 MB entry fee from your publicly-attested Steem address to EPZEMB73FGY7O6XMTGA2SFQIDUUV4NT5
What is a Use-a-Thon?
You have probably heard about hack-a-thons, where developers and engineers develop new features for a given product by altering code, hardware or tweaking the product.
A Use-a-Thon doesn’t require development or engineering skills. The aim is to explore, experiment and apply the existing features to solve a real-world problem or fulfill an existing need either online or offline in a local community. So while creating new chat bots and oracles is an option, it’s not required at all. A previous Byteball Use-a-Thon proved that users are able to apply the platform to real-world use cases without knowing programming or underlying technologies at all.
What is a use case?
A use case is a real-world problem or need that can be addressed with the given tool. Some (but not all) examples could be: introducing smart contracts to enable trustless value exchange between two parties, a web-based mini-game, disrupting an existing market, creating a new service allowing Byteball users to purchase products, allowing Steem users to send tips to each other, creating a private token to be used in an incentive program, or even creating a small business that potentially generates profit for you.
Basically, anything goes as long as it involves using the Byteball platform and its features.
When is the contest?
NOW! From the date of this announcement, users can join by paying the entry fee. You can enter as an individual or gather a team to help explore, develop and realize your use case. Each participant is free to create more than one entry.
The contest ends 30 September 2018, 11:59:59 UTC. You must create a post on your blog by this date, describing your use case, current progress, plan for realization, milestones and any relevant information allowing the Jury to evaluate your project. The post must be in English, with the title “Byteball Use-a-Thon: [plus your own title]”, start with a summary (150 words or less), and then the additional information as described above. First tag must be “#byteball” and second tag must be “#useathon”.
After the deadline, a Jury consisting of @Punqtured, @Slackjore, @Tarmo888 and @Suirelav will evaluate all contributions and determine the winners, who will be announced about a week later.
Where can I get more information?
With a constantly growing community, there is a vast library of available resources. Here are some relevant resources:
- Use-a-Thon presentation: https://docs.google.com/presentation/d/e/2PACX-1vSIX6sQtVjM-zD9aPzGqNj2dIexehHb2UOArZgIqi1sYX7go_MLOXM_BSJSp7or6xwhiFmG76AnoE9n/pub?start=true&loop=false&delayms=3000 (Use arrow keys to pause and navigate between slides)
- Steem Use-a-Thon Wiki page (this page you are currently reading) where all relevant information for the contest can be found
- Byteball Slack where users can seek help, ask questions and collaborate: https://slack.byteball.org - please state that you are a participant in the Use-a-Thon.
- Byteball Wiki (you're reading it) contains information about all features, references to external sources etc
Additional resources for techies:
- Developer guides for those wanting to build new stuff: https://github.com/byteball/byteballcore/wiki/Byteball-Developer-Guides
- Easy-to-use JavaScript library to easily integrate Byteball features on websites without the need of headless wallets: https://bonustrack.gitbook.io/byteball/getting-started/quick-start
- Byteball main GitHub repository for those wanting to dig deep: https://github.com/byteball/byteball
Known participants
- List derived from each publicly-attested source of a 25 MB payment as above.[2]
- Look up username at byteball.co, for example
https://byteball.co/@2EVEJTQWQGP3IGPVG24D7AP732TUN6N4/attestations - Notes includes links to blog Use-a-Thon posts, and also winners of the 1 GB weekly prizes (Sept 2, 9, 16, 23)
Improper entries
These appear to be attempted entries, but aren't (yet) valid:
- GJY5BHZXWNGRS2E4UVPJKY3D4ATKHF4O (only 25 KB paid)
- LW3RB3A6BYD646TA3NWCTCRF7N7HDZ2J (only 25 KB paid)
- MSC2MVQBSWOV7XN3UNCARHZKCGXR36E5 (only 24 MB paid)
- MFKTFQ5K3FXEF3BF5H6WGIHRH6ILCN3U (only 25 bytes paid)
- URP3QER4DDV5PO22D6ROIWHKGUMKZP7J (25 MB paid but from private attestation)
