Bounties are a set of priority initiatives that CyberBrokers needs help with in a short timeframe, and we're offering them to the community to create for a fee. If you're interested in learning more about the program, check out the Community Fund Overview. If you're ready to submit a proposal for this Bounty, just use the Community Fund Submission Form.
We are thrilled to announce we have an exciting new Bounty for our community - a Survivor-inspired, interactive game that will keep you on the edge of your seat! This idea was proposed by one of our community members, Delso, and a lot of thought and planning has gone into making it a reality.
The game will last approximately one week and be divided into several rounds, with a specific number of players voted out each round. The finale will be a 2-hour livestream where players will be voted out every 15 minutes until only 3 remain, and then a final vote will determine the ultimate "Broker Survivor."
The game will be played through a website interface that utilizes delegate.cash for web3 connections, registration, broker selection, voting, and displaying the current state of the game. Game updates and reminders will be sent through Discord and potentially Twitter.
Initially, the game will be open to CyberBrokers holders with a pool for non-holders to participate. Our goal is to expand the game to other communities over time. Additional features will be discussed with the winning submission.
We are offering a Bounty for the development of this game, and once awarded, we would like a functional website and game delivered within five weeks for testing, with a launch scheduled for one week later. Please include the cost in USD when submitting a proposal. This is an opportunity to showcase your skills and be a part of creating a fun and engaging experience for our community.
A discord bot with basic game mechanics has been created and can be used as a reference for implementing similar mechanics. It is unclear if the feature of grouping rounds into stages is necessary.
The bot's code can be found on GitHub.
There is also a Google Sheet with information about various game configurations and the SQL table structure for the implementation.
The original idea is also available in a Google Doc.
The following is the initial concept of how we would like the game to work. This concept may be refined through conversations with the person who is awarded the Bounty.
Website with appealing basic interface.
We may apply CyberBroker styling to it later.
Page: Home - Summary of upcoming/current games. We will provide additional content for this page.
Page: About - We will provide content for this page.
Page: Game Play -We will provide content for this page.
Page: Play - This will be where the game functions exist.
Page: Admin - Secured access to game setup, modification, logs, etc.
Admin
Settings
Twitter/Discord connections and settings.
Other site level settings.
Create new game.
Autoplay or registration based.
Registration period & number of players.
Game settings including definition of each round specifics.
Manage existing game.
Methods to pick final players from registrations.
Change game settings before game starts.
Logging
Download past game statistics.
Play
Register
Web3 connect/sign.
Pick owned CyberBroker or from pool of loaners.
Save player wallet and CyberBroker in database.
Vote
Web3 connect/sign.
Verify ability to vote in this round.
Select existing player to vote out.
Save vote in database.
Automated
Game Rounds
See Google Sheet for this logic.
Results shown on website and pushed to Discord/Twitter.
Technical
Would prefer use of mySQL for data storage.
Use of a javascript web framework for UI design.
Support delegate.cash for hot wallet connection to view assets in connected cold wallets.
Additional features to be discussed with winning submission.
Bounty awarded
Finalize requirements and delivery timeline through design and technical discussions.
Conduct checkpoint halway for adjustments during delivery.
Conduct internal testing for 1 week post-delivery, including bug fixes and final adjustments.
Launch and observe for 1 week before payment.
The submitter represents they have the required technical skills necessary to deliver this Bounty.
The submitter must be available for four weeks after launch to address any bug fixes
Payment for the Bounty will take place one week after launch
For any questions or clarifications about this bounty, please contact our Community Fund Manager, Mike, on Discord at CarTarL#3042 or by email at mike@cyberbrokers.io.