bluzelle / swarm-of-duty Goto Github PK

Description:
Look at: https://github.com/cosmostation/cosmostation-mobile. 

A version of the mobile app for iOS and Android that works with Bluzelle’s TestNet, allowing people to do the same functionality with their TestNet wallets. Should be reasonable skinned to have Bluzelle logos and colors and fonts.

Requirements:

• Please provide actual installable that we can test and use to evaluate your submission.

Rewards:

• USD $3,000 for both Android and iOS

Resources:

• Developer Documentation for BluzelleDB: https://docs.bluzelle.com/developers/
• Bluzelle Curie Testnet Github link: https://github.com/bluzelle/curium
• Bluzelle Javascript Library: https://github.com/bluzelle/blzjs
• Community discord chat (you can reach out to the team if you have any questions): https://discord.gg/KbDVsxE

Important points:

• Your submission will be a pull request.
• Your submission WILL be judged significantly based on how well you use Bluzelle DB. It is a key value store, so please use it effectively using best practices including proper data normalization/de-normalization.
• Update the README to reflect your submission including description, notes, and other pertinent details.
• You can participate in any of Bluzelle bounty, or even multiple ones, as you desire. You can be an individual or a team -- it is up to you.
• The code you submit will be under the MIT license, with you being credited as the author. When you submit this code, you agree to give all publishing and intellectual rights of the video freely over to the community via the terms of the MIT license.
• Ensure the code is written by you or your team. It is imperative that you own the rights to the code and are writing code that can be fully licensed under MIT.
• Please submit your code to Github with the proper MIT license file included in it, to be considered. If your submission includes a front end and back end, put these into separate FOLDERS and include them both in the same pull request with your submission.
• Be sure your submission is in a ready and demo-able state. We will not evaluate incomplete projects nor will code alone be an acceptable submission. Include all necessary details so we can try out your app.
• Record a screencast showing us how your submission works. Include a link to your video in the README.
• The Bluzelle team will be solely responsible for choosing the winners, and if warranted, multiple winners are possible for each bounty.
• The Bluzelle team will make the final decision, and reserves the right to not award a bounty for a challenge if no acceptable submissions are made.
• Once you have made your pull request, submit your work and include information on the link to your pull request.

Description:
Deploy a P2P mobile app (iOS and Android) that lets you create questions with multiple choice answers, as well as be able to answer questions already asked as well as view the results of existing questions already asked. People vote with their bluzelle TestNet address. You only get to vote once on a question. All data stored on Bluzelle TestNet database.

Requirements:

• Tied to phone number to create login.
• Please provide actual installable that we can test and use to evaluate your submission.

Rewards:

• USD $3,000 for both Android and iOS
• +$1,500: A voter’s BNT average stake over a reasonable time window (say the last 30 days) determines the weight of their answer… in tandem with this, questions can be flagged as weighted, to encourage staked voting.

Resources:

• Developer Documentation for BluzelleDB: https://docs.bluzelle.com/developers/
• Bluzelle Curie Testnet Github link: https://github.com/bluzelle/curium
• Bluzelle Javascript Library: https://github.com/bluzelle/blzjs
• Community discord chat (you can reach out to the team if you have any questions): https://discord.gg/KbDVsxE

Important points:

• Your submission will be a pull request.
• Your submission WILL be judged significantly based on how well you use Bluzelle DB. It is a key value store, so please use it effectively using best practices including proper data normalization/de-normalization.
• Update the README to reflect your submission including description, notes, and other pertinent details.
• You can participate in any of Bluzelle bounty, or even multiple ones, as you desire. You can be an individual or a team -- it is up to you.
• The code you submit will be under the MIT license, with you being credited as the author. When you submit this code, you agree to give all publishing and intellectual rights of the video freely over to the community via the terms of the MIT license.
• Ensure the code is written by you or your team. It is imperative that you own the rights to the code and are writing code that can be fully licensed under MIT.
• Please submit your code to Github with the proper MIT license file included in it, to be considered. If your submission includes a front end and back end, put these into separate FOLDERS and include them both in the same pull request with your submission.
• Be sure your submission is in a ready and demo-able state. We will not evaluate incomplete projects nor will code alone be an acceptable submission. Include all necessary details so we can try out your app.
• Record a screencast showing us how your submission works. Include a link to your video in the README.
• The Bluzelle team will be solely responsible for choosing the winners, and if warranted, multiple winners are possible for each bounty.
• The Bluzelle team will make the final decision, and reserves the right to not award a bounty for a challenge if no acceptable submissions are made.
• Once you have made your pull request, submit your work and include information on the link to your pull request.

Description:
Please refer to the BLZJS repo: https://github.com/bluzelle/blzjs

We need libraries similar to BLZJS in each of the following languages. We will look at the completeness of your submission, including unit tests and a sample folder with an example of use, config, etc.

Requirements:

• Use the BLZJS library as a reference for which API calls to make, and as an example of how to interact with the REST endpoint on our TestNet.
• For each language, please also provide a samples folder (like BLZJS) that shows an example crud program demonstrating the use of your library with our TestNet. These are critical so we can evaluate your submission.

Rewards:

USD $1,250 for each library

• C++ (GCC compliant on Windows,
• Linux, Mac)
• Java (Android)
• Swift (iOS)
• Python
• Ruby
• Java
• C#
• Go
• PHP

Resources:

• Developer Documentation for BluzelleDB: https://docs.bluzelle.com/developers/
• Bluzelle Curie Testnet Github link: https://github.com/bluzelle/curium
• Bluzelle Javascript Library: https://github.com/bluzelle/blzjs
• Community discord chat (you can reach out to the team if you have any questions): https://discord.gg/KbDVsxE

Important points:

• Your submission will be a pull request.
• Your submission WILL be judged significantly based on how well you use Bluzelle DB. It is a key value store, so please use it effectively using best practices including proper data normalization/de-normalization.
• Update the README to reflect your submission including description, notes, and other pertinent details.
• You can participate in any of Bluzelle bounty, or even multiple ones, as you desire. You can be an individual or a team -- it is up to you.
• The code you submit will be under the MIT license, with you being credited as the author. When you submit this code, you agree to give all publishing and intellectual rights of the video freely over to the community via the terms of the MIT license.
• Ensure the code is written by you or your team. It is imperative that you own the rights to the code and are writing code that can be fully licensed under MIT.
• Please submit your code to Github with the proper MIT license file included in it, to be considered. If your submission includes a front end and back end, put these into separate FOLDERS and include them both in the same pull request with your submission.
• Be sure your submission is in a ready and demo-able state. We will not evaluate incomplete projects nor will code alone be an acceptable submission. Include all necessary details so we can try out your app.
• Record a screencast showing us how your submission works. Include a link to your video in the README.
• The Bluzelle team will be solely responsible for choosing the winners, and if warranted, multiple winners are possible for each bounty.
• The Bluzelle team will make the final decision, and reserves the right to not award a bounty for a challenge if no acceptable submissions are made.
• Once you have made your pull request, submit your work and include information on the link to your pull request.

Please 100% ensure that the README for each of your library submissions follow these guidelines and assumptions:

• While the team members testing are each software engineers, they have no specific experience whatsoever in the language. So if it is C#, assume they do not know C#. They do not know how to setup an environment for C# and do not know how to write even a basic C# program. Even if they have C# experience, they might not know the latest standards and tools and conventions, so it is best to assume they know nothing about C#.
• The person is ssh'ed onto a fresh new Ubuntu 18.04 Linux install. There is nothing installed on this machine yet, whatsoever. Not even basic developer tools. There is no GUI. Just base OS.
• List out all the steps necessary to install all the tools/dependencies to get your library running. Nothing is too obvious.
• List out all the steps to actually copy and install your library submission to the machine. This could be a "git clone", but ideally, your library is installable through a suitable package manager in the language. Like "composer" for PHP, or "pip" for Python.
• Include with your submission at least one example program that can be run "out of the box". It should have all the credentials (for the Bluzelle DB, including mnemonic, endpoints, UUID, etc) so that it can just be run. Please include as many examples as possible. The more you submit, the better a showcase it is of the library and more likely to win.
• Include instructions on how to actually run your example program or programs.
• Include tests if you can, as well as clear instructions on how to run the tests and interpret their results.
  Most critical is ensuring that there are no blockers, so that the Bluzelle team can seamlessly test your submission. We 100% appreciate all the hard work and want to go through each submission diligently, and need your help to achieve this.
  Please ensure you "QA" all the instructions for your library on a fresh new Ubuntu 18.04 install by actually running through these steps and verifying it all works. Do not do this on your own dev machine, as there could be dependencies that are missed. We recommend using a VM with Ubuntu 18.04 or alternatively, use a free-tier Ubuntu 18.04 instance on AWS (or Azure or GCP).

Description:
Bluzelle allows leases to store data for periods of time, and charges in crypto for the length of the lease. Leases can range from seconds to minutes to hours to days to years to “forever”. 

Bluzelle is also keenly interested in free speech, and ensuring that information that gets censored by centralized authorities (governments, ************s, special interest groups, trolls, etc) is NOT lost. Often, it is the information that gets censored that is MOST important to the public interest. Bluzelle believes in the dissemination of true and honest information without being constrained by authorities. 

We ask the developer to build an application based on Bluzelle Testnet Database that has two parts:

A “crawler” that goes to websites (e.g. social media) and looks for posts with tags and content that are likely to get censored. Anything that matches such criteria might be a candidate. Any such “candidates” will be stored to Bluzelle with a very long lease. The lease would apply possibly based on the tags and the site in question. In some cases, a “forever” lease would make sense.
A responsive (PC, mobile-friendly) website that lets the user freely view the latest content that is “cached” on Bluzelle. It is vital for anybody to view what was censored and in fact, highlight more prominently what was censored more recently, with more force, etc. It is up to the developer of this bounty to determine these metrics. Our goal here is to ensure that any content that gets censored gets highlighted as relevant and ensure that censorship is “punished” by spotlighting information that gets censorship. 

Requirements:

• Please provide actual installable that we can test and use to evaluate your submission.

Rewards:

• USD $4,000
• +$2,000: Android or iOS apps to view content

Resources:

• Developer Documentation for BluzelleDB: https://docs.bluzelle.com/developers/
• Bluzelle Curie Testnet Github link: https://github.com/bluzelle/curium
• Bluzelle Javascript Library: https://github.com/bluzelle/blzjs
• Community discord chat (you can reach out to the team if you have any questions): https://discord.gg/KbDVsxE

Important points:

• Your submission will be a pull request.
• Your submission WILL be judged significantly based on how well you use Bluzelle DB. It is a key value store, so please use it effectively using best practices including proper data normalization/de-normalization.
• Update the README to reflect your submission including description, notes, and other pertinent details.
• You can participate in any of Bluzelle bounty, or even multiple ones, as you desire. You can be an individual or a team -- it is up to you.
• The code you submit will be under the MIT license, with you being credited as the author. When you submit this code, you agree to give all publishing and intellectual rights of the video freely over to the community via the terms of the MIT license.
• Ensure the code is written by you or your team. It is imperative that you own the rights to the code and are writing code that can be fully licensed under MIT.
• Please submit your code to Github with the proper MIT license file included in it, to be considered. If your submission includes a front end and back end, put these into separate FOLDERS and include them both in the same pull request with your submission.
• Be sure your submission is in a ready and demo-able state. We will not evaluate incomplete projects nor will code alone be an acceptable submission. Include all necessary details so we can try out your app.
• Record a screencast showing us how your submission works. Include a link to your video in the README.
• The Bluzelle team will be solely responsible for choosing the winners, and if warranted, multiple winners are possible for each bounty.
• The Bluzelle team will make the final decision, and reserves the right to not award a bounty for a challenge if no acceptable submissions are made.
• Once you have made your pull request, submit your work and include information on the link to your pull request.

Description:
Post photos or text or other miscellaneous files to IPFS while metadata and a hash of the file contents is stored to Bluzelle TestNet database. App provides a means to lookup previous notarized items, ability to pull up a proof, etc. Can also delete items. App allows you to select existing photos or take a new photo to post.

Requirements:

• Tied to phone number to create login.
• Please provide actual installable that we can test and use to evaluate your submission.

Rewards:

• USD $2,000 for both Android and iOS
• +$500: Web browser PC means to access account and view notarized items.

Resources:

• Developer Documentation for BluzelleDB: https://docs.bluzelle.com/developers/
• Bluzelle Curie Testnet Github link: https://github.com/bluzelle/curium
• Bluzelle Javascript Library: https://github.com/bluzelle/blzjs
• Community discord chat (you can reach out to the team if you have any questions): https://discord.gg/KbDVsxE

Important points:

• Your submission will be a pull request.
• Your submission WILL be judged significantly based on how well you use Bluzelle DB. It is a key value store, so please use it effectively using best practices including proper data normalization/de-normalization.
• Update the README to reflect your submission including description, notes, and other pertinent details.
• You can participate in any of Bluzelle bounty, or even multiple ones, as you desire. You can be an individual or a team -- it is up to you.
• The code you submit will be under the MIT license, with you being credited as the author. When you submit this code, you agree to give all publishing and intellectual rights of the video freely over to the community via the terms of the MIT license.
• Ensure the code is written by you or your team. It is imperative that you own the rights to the code and are writing code that can be fully licensed under MIT.
• Please submit your code to Github with the proper MIT license file included in it, to be considered. If your submission includes a front end and back end, put these into separate FOLDERS and include them both in the same pull request with your submission.
• Be sure your submission is in a ready and demo-able state. We will not evaluate incomplete projects nor will code alone be an acceptable submission. Include all necessary details so we can try out your app.
• Record a screencast showing us how your submission works. Include a link to your video in the README.
• The Bluzelle team will be solely responsible for choosing the winners, and if warranted, multiple winners are possible for each bounty.
• The Bluzelle team will make the final decision, and reserves the right to not award a bounty for a challenge if no acceptable submissions are made.
• Once you have made your pull request, submit your work and include information on the link to your pull request.

Description:
Deploy a P2P chat client, using the Bluzelle Testnet database.

Requirements:

• Support for IM and persistent rooms with owners.
• Tied to phone number to create login.
• Please provide an actual installable that we can test and use to evaluate your submission.

Rewards:

• USD $3,000 for both Android and iOS
• +$1,500: Web browser PC support. Must somehow use phone to authenticate web browser app, like WhatsApp.
• +$1,000: Use IPFS to enable file transfers, avatars, etc. All files must be encrypted.
• +$1,250: Room chat messages are encrypted and have signing proofs
• +$500: Ability for message owners to delete their own messages.

Resources:

• Developer Documentation for BluzelleDB: https://docs.bluzelle.com/developers/
• Bluzelle Curie Testnet Github link: https://github.com/bluzelle/curium
• Bluzelle Javascript Library: https://github.com/bluzelle/blzjs
• Community discord chat (you can reach out to the team if you have any questions): https://discord.gg/KbDVsxE

Important points:

• Your submission will be a pull request.
• Your submission WILL be judged significantly based on how well you use Bluzelle DB. It is a key value store, so please use it effectively using best practices including proper data normalization/de-normalization.
• Update the README to reflect your submission including description, notes, and other pertinent details.
• You can participate in any of Bluzelle bounty, or even multiple ones, as you desire. You can be an individual or a team -- it is up to you.
• The code you submit will be under the MIT license, with you being credited as the author. When you submit this code, you agree to give all publishing and intellectual rights of the video freely over to the community via the terms of the MIT license.
• Ensure the code is written by you or your team. It is imperative that you own the rights to the code and are writing code that can be fully licensed under MIT.
• Please submit your code to Github with the proper MIT license file included in it, to be considered. If your submission includes a front end and back end, put these into separate FOLDERS and include them both in the same pull request with your submission.
• Be sure your submission is in a ready and demo-able state. We will not evaluate incomplete projects nor will code alone be an acceptable submission. Include all necessary details so we can try out your app.
• Record a screencast showing us how your submission works. Include a link to your video in the README.
• The Bluzelle team will be solely responsible for choosing the winners, and if warranted, multiple winners are possible for each bounty.
• The Bluzelle team will make the final decision, and reserves the right to not award a bounty for a challenge if no acceptable submissions are made.
• Once you have made your pull request, submit your work and include information on the link to your pull request.

Main tasks

1. Deploy a P2P mobile app (iOS and Android) with the following features

• Users are able to create these types of poll questions: (a) Multiple choice answers (b) Yes/No answers (binary)
• Users are able to vote on questions that are open
• Users are able to change their votes for questions that are open and mutable
• Users are able to view the results of questions that are closed or viewable

2. Deploy a server process that supports the entire voting ecosystem. The server owns the DB and is the only one that reads from or writes to the DB. The server should be easily deployable on a cloud server.

Requirements:

• All data is stored exclusively in the Bluzelle database. No other data stores are used.
• The server component is the nexus by which all reads and writes to the DB occur. Client only ever talk directly with the server.
• All user private data (names, email, phone #) are encrypted by a private key owned by the server.
• The server encrypts all private data before storing to the DB, and decrypts and sends plaintext to the clients, when requested.
• All user accounts are tied to phone number to create login. You MUST have a phone number to create an account. Phone auth is used to create an account and to recover one. You are allowed to change your number if you are logged in already, and simply re-auth with the new phone number.
• People login with their Bluzelle address exclusively. They provide their mnemonic, which is their password and proof of who they are. This mnemonic should be protected at all costs by the user. The mnemonic is only loaded locally -- never travels over the wire.
• New users can create an account by simply logging in with their mnemonic or creating a new mnemonic. New users are optionally requested to provide their first name, last name, and email. All these are sent over SSL to the server (along with the phone number they authenticated with), and the server encrypts all this information before storing to the DB.
• You can only vote once for a question.
• Questions have several attributes:
  • Multiple Choice or Binary.
  • Question Text
  • Multiple Choice Options (each is text)
  • Draft/Open/Closed state. Questions that are open can still be voted on. Questions that are closed cannot be voted on anymore. Draft questions are not available yet and can be edited by the owner.
  • Mutable state. Questions that are mutable can be changed by a voter, as long as the question is mutable and still open.
  • Viewable state. Questions that are viewable can share their results even when still open. Otherwise, results are only viewable when closed.
  • Owner. The BNT user who created the question. Only they get to edit questions, set attribute values, etc.
  • Allowed users. The owner can leave it open, allowing any user to participate, or can select a whitelist of users that can participate. If a whitelist, the owner is expected to provide the BNT address of each participant they want to participate. They can add or remove users from a whitelist, as long as the question is open.

Main UI

1. A screen to see all the questions and results thereof, for any given user. They can view:

• Only the questions and results they own. They can edit, add, delete, change settings, or close. New questions are draft until made "open". Once opened, the question's whitelist, options, and question text cannot be changed. While draft, anything can be changed. Once closed, cannot be re-opened. Filters to see questions that are draft vs open vs closed or all.
• Only the questions they voted on. They can see also see results for questions that are viewable or closed. Checkbox to filter only questions they are whitelisted on. They can change answers on questions that are mutable. Filters for questions that are open vs closed and mutable vs not mutable and viewable vs not viewable.
• Only the questions they can vote on but have not yet voted on and are still open. They can see also see results for questions that are viewable. Checkbox to filter only questions they are whitelisted on. They can vote on these questions if they want. Filters for questions that mutable vs not mutable and viewable vs not viewable.

2. The user can filter what they see in any screen by date, with the ability to view everything or only everything in a date range, or before a certain date, or after a certain date.

Deliverable:

Both iOS & Android App

Rewards

$3000 USD paid in BLZ Tokens

Resources:

• Developer Documentation for BluzelleDB: https://docs.bluzelle.com/developers/
• Bluzelle Curie Testnet Github link: https://github.com/bluzelle/curium
• Bluzelle Javascript Library: https://github.com/bluzelle/blzjs
• Community discord chat (you can reach out to the team if you have any questions): https://discord.gg/KbDVsxE

Important Notes

• Your submission will be a pull request.
• Your submission WILL be judged significantly based on how well you use Bluzelle DB. It is a key value store, so please use it effectively using best practices including proper data normalization/de-normalization.
• Update the README to reflect your submission including description, notes, and other pertinent details.
• You can participate in any of Bluzelle bounty, or even multiple ones, as you desire. You can be an individual or a team -- it is up to you.
• The code you submit will be under the MIT license, with you being credited as the author. When you submit this code, you agree to give all publishing and intellectual rights of the video freely over to the community via the terms of the MIT license.
• Ensure the code is written by you or your team. It is imperative that you own the rights to the code and are writing code that can be fully licensed under MIT.
• Please submit your code to Github with the proper MIT license file included in it, to be considered. If your submission includes a front end and back end, put these into separate FOLDERS and include them both in the same pull request with your submission.
• Be sure your submission is in a ready and demo-able state. We will not evaluate incomplete projects nor will code alone be an acceptable submission. Include all necessary details so we can try out your app.
• Record a screencast showing us how your submission works. Include a link to your video in the README.
• The Bluzelle team will be solely responsible for choosing the winners, and if warranted, multiple winners are possible for each bounty.
• The Bluzelle team will make the final decision, and reserves the right to not award a bounty for a challenge if no acceptable submissions are made.
• Once you have made your pull request, submit your work and include information on the link to your pull request.

Needs smoother account transfer.

Description:
Note that Lunie is still early in test and might be harder to work with. A version of the mobile app for iOS and Android that works with Bluzelle’s TestNet, allowing people to do the same functionality with their TestNet wallets. Should be reasonable skinned to have Bluzelle logos and colors and fonts.

Requirements:

• Please provide actual installable that we can test and use to evaluate your submission.

Rewards:

• USD $1,750 for both Android and iOS

Resources:

• Developer Documentation for BluzelleDB: https://docs.bluzelle.com/developers/
• Bluzelle Curie Testnet Github link: https://github.com/bluzelle/curium
• Bluzelle Javascript Library: https://github.com/bluzelle/blzjs
• Community discord chat (you can reach out to the team if you have any questions): https://discord.gg/KbDVsxE

Important points:

• Your submission will be a pull request.
• Your submission WILL be judged significantly based on how well you use Bluzelle DB. It is a key value store, so please use it effectively using best practices including proper data normalization/de-normalization.
• Update the README to reflect your submission including description, notes, and other pertinent details.
• You can participate in any of Bluzelle bounty, or even multiple ones, as you desire. You can be an individual or a team -- it is up to you.
• The code you submit will be under the MIT license, with you being credited as the author. When you submit this code, you agree to give all publishing and intellectual rights of the video freely over to the community via the terms of the MIT license.
• Ensure the code is written by you or your team. It is imperative that you own the rights to the code and are writing code that can be fully licensed under MIT.
• Please submit your code to Github with the proper MIT license file included in it, to be considered. If your submission includes a front end and back end, put these into separate FOLDERS and include them both in the same pull request with your submission.
• Be sure your submission is in a ready and demo-able state. We will not evaluate incomplete projects nor will code alone be an acceptable submission. Include all necessary details so we can try out your app.
• Record a screencast showing us how your submission works. Include a link to your video in the README.
• The Bluzelle team will be solely responsible for choosing the winners, and if warranted, multiple winners are possible for each bounty.
• The Bluzelle team will make the final decision, and reserves the right to not award a bounty for a challenge if no acceptable submissions are made.
• Once you have made your pull request, submit your work and include information on the link to your pull request.

我是一名**的没有任何基本的，特别渴望知识的人，我想学习，如果挖出BLZ，最好有文字和视频说明。

testing