[IMPACT] Please describe your proposed solution.

<u>Current status of learning Cardano</u>

Cardano key concepts, and related technologies such as Haskell and Plutus, are not widely-known. It's hard for newcomers, especially for people who come from other developer backgrounds.

Many developers give up because Cardano is hard to learn even the basic concepts of Cardano can be hard to learn; and there is a lack of accessible learning resources such as structured, categorized documents and short codes with explanations

From our and others' experience, it takes around 1,000 hours of learning and practice for a beginner to get enough confidence to start to work as a Cardano developer.

<u>An example</u>

If a java or nodeJs developer wishes to become a Cardano developer, they need to learn:

• Haskell
• General Cardano concepts
• Plutus concepts
• Plutus APIs
• Cardano web3

They have to find documents, learn and code in the lab before starting work as a Cardano developer. This takes around 3 months, so many aspiring Cardano developers get stuck and give up at this stage.

If there was a service that provided short and refined learning materials on specific issues, e.g “general Cardano understanding”, “what is Cardano?”, “What is an UTXO?”, this would help. Developers also want to confirm whether or not their understanding is correct. A good way to do this is to structure their learning by using multiple-choice-question (MCQ) tests with increasing levels of difficulty:

• “General Cardano” to verify their knowledge about Cardano
• “Plutus” to verify theory and practical experience of Plutus smart contract.

These small sets of questions and tests will help a developer learn easier and faster. Once a developer passes the multiple choice tests, they are good to start work with Cardano projects.

That is what b-Learn ultimately intends to do. Please try a test with our demo to better understand the idea:

<https://blearn.bworks.app/mcq>

<u>Multiple-Choice Questions: a proven method to self-learn and assess </u>

Multiple-Choice Question (MCQ) tests are a widely-used learning tool that assists understanding. They are used as a primary tool to deeply assess knowledge and abilities at state-of-the-art learning platforms such as Coursera and Turing.

<u>How it works</u>

On our platform, anyone will be able to contribute their proven knowledge and code samples as MCQs once it is approved, it will be used in the MCQs test session so that others can use it to learn and verify their knowledge until they have a clear background to go with Cardano.

Our MCQ contents will focus only on Cardano and related subjects, e.g Haskell or general blockchain knowledge.

<u>An example</u>

Imagine someone has developed a Plutus script with signer’s public key validation logic. They can create a set of MCQs about it, as in the screenshot below:

Other developers on b-Learn can then learn this proven solution, and code quickly and trustfully to apply it to their project.

The more MCQs added by users, the more knowledge and experience is shared to help others strengthen their understanding.

<u>Architecture</u>

The project is designed with following 6 modules:

• Backend APIs to provide REST endpoints for client requests and performance logics.
• Microservices to handle system-specific jobs e.g count the votes to freeze the confirm.
• Contributor frontend for community members to contribute their MCQs, vote and comment on MCQs from others.
• CMS for admin to manage the platform overall.
• MCQ frontend for users to take the tests.

<u>Functions</u>

• Submit an MCQ
• Vote and comment on MCQs
• Take an MCQ test
• Job suggestion for passed participants
• Suggestions for learning resources for failed participants
• Developer and contributor ranking
• Reports
• Dashboard
• Payment
• Search

Demo screenshot to show the idea intuitively

<u>Features</u>

• Systematic and structured learning through increasing levels of difficulty:

• Understanding level, e.g “What is UTXO?”

• Deep understanding level, e.g “How does Plutus validate the transaction signer signature?”

• Practical level, which requires real code experiences.

• Short learning time through selection of only the categories of MCQs that you need

• Difficulty levels increase gradually:

• Level 1: questions are 100% general understand and first logic MCQs

• Level 2: questions are 60% general understanding and first logic MCQs, 30% deep understanding MCQs, 10% practical coding MCQs

• Level 3: questions are 30% general understanding and first logic MCQs, 40% deep understanding MCQs, 30% practical coding MCQs

• Community-driven through voting, commenting and consensus process

• Payments to contributors, and rewards to high-scoring developers

• Continuous learning and self-test loop

• Email or Cardano wallet authentication

<u>Users</u>

• MCQ contributors
• MCQ participants

<u>Approach to creating MCQs</u>

The initial MCQs will be:

• MCQs developed by our team from existing Cardano resources
• Paid MCQs submitted by community members

Cardano has excellent official documentation covering all of its aspects. This is the primary resource we will use to create initial sets of MCQs by categories:

• General Cardano
• Plutus & smart contract

The team will be responsible for translating official Cardano documents to MCQs as initial content for the platform, plus our own knowledge and source code samples to have an estimated 300 MCQs for the initial launch.

<u>User acquisition</u>

Our user acquisition strategy will target users from two groups - within the Cardano community, and outside of Cardano - at 2 different periods.

<u>At development and trial launch periods</u>

We will firstly target users from existing Cardano communities. We can reach them through Cardano community groups on Telegram, Twitter and Discord channels in each country.

The project will keep communicating with and welcoming Cardano community users to be involved as contributors and advisors. The community can always comment, give feedback on our project functions, and suggest new features they think we should add.

At this stage we aim to have around 50 paid and unpaid members to join the project. These members form an initial community who well understand project ideas for viral communication strategy next stage.

<u>After launch product period</u>

At this stage we will focus on users from Cardano communities and from outside, through user engagement, communication and campaigns.

• User engagement

• Through word of mouth

• Through communication channels, github repo, and the product itself

• User acquisition through communication campaigns. The different campaigns are designed separately to solve problems with specific groups of users:

• Users from Cardano communities: these users are friendly to Cardano technologies, so the campaigns will focus on our product features, functions and values

• Non-Cardano developers: the campaigns will focus on the unique features of building on Cardano, and how b-Learn can help them transition from other developer environments

• Crypto users: the campaigns focus on showing the advantages of Cardano and how the product solves problems through Cardano technologies e.g Plutus versus other chains e.g Ethereum.

• Non crypto users: the campaigns focus on showing blockchain’s unique values versus traditional technologies.

The target is to have around 1,500 users by 1 year after the product launch. This includes around 1,000 users from the Cardano community and 500 users from outside.

<u>Conclusion</u>

With our effective and interactive approach to learning, the project will result in attracting developers from outside with different backgrounds to join Cardano by:

• Removing the barriers that prevent developers from starting with Cardano
• Reducing the time needed to learn, research and code labs. We estimate that a prospective developer’s overall learning time will reduce from 1,000 hours to 300 hours - and with less boredom.

With required capacities, the developer is no longer stuck, and is able to do their own Cardano project, or get a job through the in-platform suggestions based on their abilities.

[IMPACT] How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?

<u>Directly solve the challenge</u>

• Equip developers with required Cardano understanding and practice in advance, before they go with Cardano.
• Attract more developers from outside and with other backgrounds by offering an easier learning approach with gradually-increasing levels of difficulty.
• Build a knowledge base through MCQ content, explanations, and sample codes.

<u>Indirectly solve the challenge </u>

• Once developers confirm their abilities by passing b-Learn’s MCQ tests, they are capable of building on Cardano, which will result in more quality Cardano dApps.
• With continued contributed understandings and verified code samples, b-Lean will become a place to share, similar to how stack overflow impacts the development world.

<u>Conclusion</u>

By offering a new approach to self-learning then self-assessing, with organized MCQs that cover the main aspects of Cardano at all levels from definition, to theory, to code samples, our project well addresses the challenge’s aims to equip and support developers and make Cardano the first choice to build dApps.

[IMPACT] How do you intend to measure the success of your project?

As seen many developers gave up because the difficultly of learning Cardano, many dApps are stuck at smart contracts and web3 development step. The success of this project will result in growing of quality dApps and developer workforce. This positively impact to Cardano’s productivity and growth, in both the short and the long term.

For detail numeric performance indicators definitions please refer to "What are the main goals for the project and how will you validate if your approach is feasible".

<u>Measure the success of the product development</u>

The success of the development stage is decided by:

• All proposed functions and features are complete and deployed.
• The simplicity and the speed of product.
• System stability and security.

<u>Measure the success of the running product</u>

Our key performance indicators will be:

• How it helps developers learn and confirm their Cardano knowledge quickly and effectively:
• The hours a developer needs to acquire enough solid Cardano experience to start work; e.g if newbies from different developer backgrounds can reach the stage of being able to develop Cardano smart contracts in &lt; 500 hours, we should consider this a very successful outcome.
• How many code samples from b-Learn are re-used by developers in their dApps. The more samples are applied, the more success is confirmed.
• Number of learning categories created on the system to cover Cardano subjects
• Number of MCQs created with classification:
• General understanding MCQs
• Theory, practical and code sample MCQs
• Confirmed MCQs through community votes and high quality MCQs
• Number of developers who take MCQ tests
• How many of them pass the tests
• How many developers get jobs in the Catalyst ecosystem after using b-Learn
• How many hours developers have to spend with bLearn to become a solid engineer.
• Number of proven code samples with clear explanations.
• Number of positive feedback and comments about the product.

This measurement data is always realtime public on the dashboard of b-Learn where everyone can have a look.

Bottom line: We aim to make b-Learn an effective tool for developers who want self-guided learning and self-assessment of their Cardano knowledge and experience. Others, such as employers and PAs, will be able to assess the ability of a developer by their MCQ test score.

[IMPACT] Please describe your plans to share the outputs and results of your project?

The works, problems and outputs are communicated across the process through a public github repo, staging server and checklist and documents:

• Github commits show our work in term of source code
• Staging server where we deploy the latest code to test, shows the updated version of the product.
• CheckList show what we are working on & its status
• Screenshot folder captures the product screens for each code commit
• Telegram and other communication channels

The community can always keep track of the project activities and outputs, and try the newest function through the following links:

Checklist: https://docs.google.com/spreadsheets/d/1dk7x_hC54qAP3nMkeVGyi28IipOVsZJsTUt3_P6u24Y/edit

ScreenShoot: <https://drive.google.com/drive/folders/1AJTzx4WeK1aedoaBqYJSIvYRhhOzbz4l>

GitHub: https://github.com/saigonbitmaster/bLearn_1.0

API: <https://blearn.bworks.app/api>

CMS: <https://blearn.bworks.app/cms>

MCQ: <https://blearn.bworks.app/mcq>

Through the above links, the community is easily able to track our works, timeline and commitment:

• What tasks we are working on
• Who is working on the task
• The pass or fail result of a task or job
• How the code presents product functions and features

<u>An example</u>

Community verify out work if we say "complete the create CMQ task":

git commit: https://github.com/saigonbitmaster/bLearn_1.0/commit/382c136f529fc1050e3a5db03c61ee878b61c4eb

App screenShoot: <https://drive.google.com/drive/folders/1AJTzx4WeK1aedoaBqYJSIvYRhhOzbz4l>

then they can visit staging server to see if how the task result in at: https://blearn.bworks.app/

Our GitHub is also open for the community to comment and raise issues about what features or functions they want to add to the product. By getting more comments from the community we will ensure the project is focused on users’ needs.

[CAPABILITY/ FEASIBILITY] What is your capability to deliver your project with high levels of trust and accountability?

The team consists of experienced members capable in various domains which are required to lead project into success:

• Seasoned software, DevOps engineers
• Experienced Cardano web3, plutus smart contract engineers
• People skilled in community engagement and marketing
• Experienced operations management and project management people
• People skilled in learning and training design

Please reference our similar works with F8 Catalyst projects: all these projects have completed their development stage and are deployed for beta test:

• bWorks - the seamless smart contract and Cardano web3 integration project:

https://www.bworks.app/

<https://bworks.app/emp>

<https://github.com/saigonbitmaster>

<https://github.com/saigonbitmaster/bworks-smart-contracts>

• cReport - a community analytic application with Cardano web3 integration project:

<https://creport.bworks.app/>

https://github.com/saigonbitmaster/creport_2.0

Our methodology to ensure the success of a project is solving critical risks in advance before submitting. This is to make sure we submit only what we are capable of fulfilling, then later move the project smoothly.

We have worked on this proposal for a month before submitting it, to clear out key logics and technologies:

• Product architecture: backend, frontend & Cardano web3 integration
• Set of sample MCQ content around Cardano.

All of us believe learning is key to work. b-Learn is our effort to make a learning tool where new Cardano developers can learn and assess themselves faster and better.

Please see our demo and github link:

https://docs.google.com/spreadsheets/d/1dk7x_hC54qAP3nMkeVGyi28IipOVsZJsTUt3_P6u24Y/edit#gid=0 - project checklist

<https://blearn.bworks.app/mcq> - demo mcq participant test frontend

<https://blearn.bworks.app/cms> - contact our Telegram channel to get a demo user to create MCQs, vote and comment on the content.

[CAPABILITY/ FEASIBILITY] What are the main goals for the project and how will you validate if your approach is feasible?

<u>List of main project goals:</u>

• Build a successful product as proposed
• Create rich and high-quality MCQ content which addresses all aspects of Cardano
• Acquire users to join the platform as contributors, community members and test participants

Validate the approach to reach the main goals

The methodology to validate the approach to reach the goals:

• Solve critical risks in advance before submitting the proposal:
• System architecture and frameworks we use
• Cardano web3 part for dev and build the applications.

Build a team that is capable to work on its responsibility:

• Technical people
• MCQ content creators
• Community engagement and marketing people
• People who love to share and learn

Apply a simple and clear process to get the works into accountable and manageable:

• Define clearly the main tasks and subtasks.
• Task management and checklist to show what we are working on and who is responsible for what.
• Github commits to show the result of our work in terms of source code.
• Staging server to show how our works ultimately result in product features and functions.

Please visit the below links where we validated our approach in term of demo functions and features:

Checklist: https://docs.google.com/spreadsheets/d/1dk7x_hC54qAP3nMkeVGyi28IipOVsZJsTUt3_P6u24Y/edit#gid=0

Github repo: https://github.com/saigonbitmaster/bLearn_1.0

bLern MCQ frontend: <https://blearn.bworks.app/mcq>

bLearn demo CMS: <https://blearn.bworks.app/cms>

(Contact our Telegram in the contact section to have demo credentials)

[CAPABILITY/ FEASIBILITY] Please provide a detailed breakdown of your project’s milestones and each of the main tasks or activities to reach the milestone plus the expected timeline for the delivery.

Q2-2023

Pre-works

POC to verify the possibilities of selected technologies and capacity to implement the approach

• Develop a demo version of b-Learn
• Create set of MCQ contents to test
• Verify everything is working before proposal submission.

Setup environment

• Github
• Dev servers
• Documentations
• IDE

Develop and submit proposal.

Q3-2023

Milestone 01: Paper works

Time: Month 01. Budget: 40,000 Ada (c. 8.3% of budget)

System design with detail diagram and specifications: 5,000 Ada

Define end user functions & system features: 5,000 Ada

03 EC2 servers for 10 months development periods: 17,000 Ada

Project management cost for 10 months development periods: 18,000 Ada

Note: The cost for staging servers is not a one-time payment; we have to arrange across the development period 10 months.

Milestone 02: Develop APIs and Microservices

Time: Month 02-03. Budget: 90,000 Ada (c. 18,7% of budget)**

Common libraries & web components

DB models

Backend APIs

• Category and MCQ APIs
• Vote APIs
• Comment APIs
• MCQs participant test APIs
• Cardano asset payment APIs
• Report APIs
• Dashboard APIs
• Common CMS APIs
• User APIs

Backend logics & microservices

• Random MCQs selected for a test
• Vote aggregation services
• Analytic services

Q4-2023

Milestone 03: Develop CMS frontend

Time: Month 04-05. Budget: 70,000 Ada (c. 14,5% of budget)**

• General admin management
• MCQ content management
• User management
• Analytic and reports: contributor, test participants
• Dashboard
• Cardano Web3 for payment with Cardano asset (Ada)
• Promotion function to run marketing events

Milestone 04: Develop Contributor frontend

Time: Month 05-06. Budget: Budget: 70,000 Ada (c. 14,5% of budget)

Contributor frontend

• Create/edit/delete an MCQ
• Vote and comment other MCQs
• Track the usage, rate and comment of owned MCQs
• Payment tracking
• Dashboard

Q1-2024

Milestone 05: Develop MCQs frontend

Time: Month 07. Budget: 70,000 Ada (c. 14,5% of budget)

• Select a category, the difficulty level and perform a MCQs test
• Learn through taken MCQs
• Record the test history
• Job suggestion based on participant’s current knowledge and abilities level via MCQs score.
• Learn, vet and re-vet loop to improve user abilities until they are passed.

Milestone 6: Initial MCQ content

Time: Month 8. Budget: 30,000 Ada (c. 6.25% of budget)**

• Decide the category which cover all Cardano and related aspects e.g general Cardano, Haskell and Plutus
• Translate official Cardano documents into MCQs

Q4-2023

Milestone 7: QA/QC feedback & improvement. Beta launch platform, trial users with key functions

Time: Month 09. Budget: 30,000 Ada (c. 6.25% of budget)**

• Perform all function and feature test
• Feedback, fix bugs and improvement loop until all is set.
• Create MCQ for contributor
• Vote a MCQ for community user
• Realtime vote, confirm to list MCQ to participant frontend

Milestone 8: Launch platform

Time: Month 10. Budget: 80,000 Ada (c. 16,6% of budget)

• User acquisition and engagement

• Paid MCQs from community

• Platform & content improvement

• Put the platform to fully community driven

• Project final report and close-out.

  [CAPABILITY/ FEASIBILITY] Please describe the deliverables, outputs and intended outcomes of each milestone.

Q2-2023

Pre works

<u>POC to verify the possibilities of selected technologies and capacity to implementation the approach</u>

• Develop a demo version of bLearn
• Create set of MCQ contents to test
• Verify key selected technologies, libraries and framework.

Setup environment

• Github
• Dev servers
• Documentations
• IDE

Deliverables, outputs and intended outcomes

• The b-Learn demo is available for the community to try and understand the proposal idea and what we intend to develop:
• <https://blearn.bworks.app/cms#/>
• <https://blearn.bworks.app/mcq>
• Dev environment is set
• https://github.com/saigonbitmaster/bLearn_1.0
• Staging server is ready to go and updated with the latest master code.

Q3-2023

Milestone 01: Paper works and project initiation.

Time: Month 01.

Paper works

System design specifications

Define end user functions & features

Deliverables, outputs and intended outcomes

• All the features, function are defined
• Diagram app workflow and platform structure
• Document system specifications

Milestone 02: Develop APIs and microservices

Time: Month 02-03.**

Deliverables, outputs and intended outcomes

• All common libraries and components are developed and ready to use across the project e.g the MCQ components, fetch libraries.
• All db schemas are designed and verified.
• All APIs are developed and available to use through its endpoints
• Backend logics & microservices are developed and ready to integrate to the backend e.g to form a random MCQs set for a test session.
• All the APIs deployed and ready to use for frontend app to fetch through internet:

https://blearn.bworks.app/api/

Community can verify the works of APIs by try POST, GET its endpoints:

<https://blearn.bworks.app/api/quizzes>

Q4-2023

Milestone 03: Develop CMS frontend

Time: Month 04-05.**

CMS Frontend functions and features are developed, tested and deployed at:

<https://blearn.bworks.app/cms>

Admin users are able to use the cms functions:

• To manage overall the the platform
• To pay MCQ contributors with Cardano assets e.g ADA

Milestone 04: Develop Contributor frontend

Time: Month 05-06.

Contributor Frontend functions and features are developed and deployed at:

<https://blearn.bworks.app/contributor>

Q1-2024

Milestone 05: Develop MCQs frontend

Time: Month 07.

MCQs Frontend functions and features are developed and deployed at:

<https://blearn.bworks.app/mcq>

Milestone 6: Initial MCQ content

Time: Month 8.**

Deliverables, outputs and intended outcomes

• Complete define category list to cover Cardano and its related subjects e.g General cardano, Catalyst, Smart contract & Plutus
• Complete define at least 500 MCQs for defined categories from general understanding to code sample with 03 difficulty levels to make a random list of MCQs for participants to test.

Please see sheet with sample:

https://docs.google.com/spreadsheets/d/1dk7x_hC54qAP3nMkeVGyi28IipOVsZJsTUt3_P6u24Y/edit#gid=1179420225

Q4-2023

Milestone 7: QA/QC feedback & improvement. Beta launch platform, trial users with key functions

Time: Month 09.**

Deliverables, outputs and intended outcomes

The QA/QC checklist which show passed/not passed to the developed functions, features

The bugs, fix commits and test result

The beta version of platform is launched with proposed functions, features for user to try at:

<https://blearn.bworks.app/mcq>

User can use trial version to:

• Create a MCQs
• Attend a test
• Learn with suggestion resource if the test if failed

Milestone 8: Launch platform

Time: Month 10.

Deliverables, outputs and intended outcomes

• Deploy the platform to AWS in a production environment with fully defined functions. It is available for usage.
• Anyone can become:
• A contributor to create its own MCQs
• A participant to attend the test, learns from the MCQs explanation to strengthen its knowledge and abilities.

We expect to have, 1 year after launching the platform:

• 40% MCQs created by the b-Learn team
• 60% MCQs content created by community users

MCQs content type:

• 40% level 1 general understanding MCQs
• 40% level 2 deep understanding MCQs
• 20% level 3 code practice MCQs

Note that the tasks are defined with priority, and a milestone is confirmed as complete only when all tasks with high priority level are passed and at least 80% of low priority level are passed.

Task validation method

A task is confirmed as completed once it gets confirmed from the QA or reviewer person that checks:

• Code commit
• Staging server feature or function
• The response time of an API &lt; 200 ms
• Total loading time of a web function &lt; 5 seconds

Once the check is passed, it is marked as completed, otherwise it returns feedback that further work is required.

[RESOURCES & VALUE FOR MONEY] Please provide a detailed budget breakdown of the proposed work and resources.

Project cost structure: The budget includes the following types of costs:

1) Internal costs

• Engineering cost to pay software and devops engineers
• Project management costs
• Communication, marketing and operation costs

2) External costs for the trial free period

• Infrastructure cost: pay AMAZON EC2 staging and production servers.
• Marketing campaigns and events cost: paid ads on Google ads, Facebook etc to acquire users.

Q2-2023

Pre-works

POC to verify the possibilities of selected technologies and capacity to implement the approach

• Develop a demo version of b-Learn
• Create set of MCQ contents to test
• Verify everything is working before proposal submission.

Setup environment

• Github
• Dev servers
• Documentations
• IDE

Proposal submission

Q3-2023

Milestone 01: Paper works

Time: Month 01. Budget: 40,000 Ada (c. 8.3% of budget)

System design with detail diagram and specifications: 4,000 Ada

Define end user functions & system features: 4,000 Ada

3 x EC2 servers for whole 10 month development period: 15,000 Ada

Project management for whole 10 month development period: 17,000 Ada

Milestone 02: Develop APIs and microservices

Time: Month 02-03. Budget: 90,000 Ada (c. 18,7% of budget)**

Estimated 1,000 work hours of 04 developers in 02 months.

Common libraries & web components: 10,000 Ada

DB models 10,000 Ada

Backend APIs 55,000 Ada

• Category and MCQ APIs
• Vote APIs
• Comment APIs
• MCQs participant test APIs
• Cardano asset payment APIs
• Report APIs
• Dashboard APIs
• Common CMS APIs
• User APIs

Backend logics & microservices 15,000 Ada

• Random MCQs selected for a test
• Vote aggregation services
• Analytic services

Q4-2023

Milestone 03: Develop CMS frontend

Time: Month 04-05. Budget: 70,000 Ada (c. 14,5% of budget)**

Estimated 700 work hours of 03 developers in 02 months.

• General admin management: 8,000
• MCQ content management: 12,000
• User management: 9,000
• Analytics and reports: contributors, test participants: 12,000
• Dashboard: 9,000
• Cardano Web3 for payment with Cardano asset (Ada): 12,000
• Promotion and marketing events: 8,000

Milestone 04: Develop Contributor frontend

Time: Month 05-06. Budget: 70,000 Ada (c. 14,5% of budget)

Estimated 700 work hours of 03 developers in 02 months.

Contributor frontend

• Create/edit/delete a MCQ: 10,000
• Vote and comment other MCQs: 15,000
• Track the usage, rate and comment of owned MCQs: 15,000
• Payment tracking: 15,000
• Dashboard: 15,000

Q1-2024

Milestone 05: Develop MCQs frontend (c. 14,5% of budget)

Time: Month 07. Budget: 70,000 Ada

• Select a category, the difficulty level and perform an MCQ test and scoring: 10,000
• Learn through taken MCQs: 15,000
• Record test history, lock the test after a duration if user fail: 15,000
• Job suggestions based on participant’s current knowledge and abilities, assessd via their MCQ score: 15000.
• Learn, vet and re-vet loop to improve user abilities until they are passed: 15,000.

Milestone 7: Initial MCQ content

Time: Month 8. Budget: 30,000 Ada (c. 6.25% of budget)**

Estimated 500 MCQs with average cost 50 Ada for a MCQ

• Decide MCQ categories, e.g general Cardano, Haskell and Plutus, etc: 7,000
• Translate official Cardano documents into MCQs: 13,000
• Create special set of MCQs based on practical experiences: 10,000

Q4-2023

Milestone 6: QA/QC feedback & improvement. Beta launch platform, trial users with key functions

Time: Month 9. Budget: 30,000 Ada (c. 6,25% of budget)**

Estimated 400 work hours for 06 developers, QA/QC and MCQ creators work in 01 month.

• Perform all function and feature tests
• Feedback, fix bugs and improvement loop until all is set.
• Create MCQ for contributor to post a MCQs
• Vote on a MCQ for community user to vote and comment to a MCQ
• Realtime vote, confirm to list MCQ to participant frontend

Milestone 8: Launch platform

Time: Month 10. Budget: 80,000 Ada (c. 16,6% of budget)

This cost to pay for marketing online, to community MCQ contributors and server cost for 01 year after launching.

• User acquisition, publicity/marketing, and engagement: 30,000 (to acquire 1500 users at cost 20 Ada for 1 user)
• Paid MCQs from community: 30,000 (to have 1000 MCQs at average cost 30 Ada for 1 MCQ)
• Platform & content improvement: 20,000
• Put the platform to fully community driven
• Project final report and close-out.

TOTAL: 480,000 ADA

(four hundred eighty thousand Ada)

[RESOURCES & VALUE FOR MONEY] Who is in the project team and what are their roles?

We team up the responsible members and capable to work on specific domains required by the project, to make sure we have proper resource to lead project into success:

• Software and Cardano web3 engineers
• MCQ content creators and learning experts
• Community engagement and marketing people
• People who love to share and learn

List of 12 project members:

1-Thang Tran

GitHub: <https://github.com/saigonbitmaster>

Software expert, practical Plutus smart contract & web3 engineer and engineering manager.

Roles: Product designer, engineering and project manager. Full stack and Cardano developer.

Responsibilities:

Product design & implementation.

Overall project development and operation.

Plutus smart contract and web3 developer.

Backend and frontend developer.

2-Vanessa Cardui

Telegram: @VanCardui

GitHub: https://github.com/VanCardui

Role: Project coordinator, product manager, learning design, community engagement.

Responsibilities: Project coordinator, product release. Communication and community.

3-Thang Vu

Senior software and web3 developer.

<https://github.com/vmthang>

Roles: Web3 and backend developer.

Responsibilities:

• Implement web3 part of the project.
• Develop backend APIs, logic and Microservice

4-Thanh Ngoc

Senior full stack and database developer.

<https://www.linkedin.com/in/ngocthanhit/>

Roles: Full stack developer.

Responsibilities:

• Database design and Implement.
• Develop backend APIs, logic and Microservice.
• Develop frontend functions and features.

5-Bao Dinh

Senior full stack developer.

<https://gitlab.com/baolue>

Roles: Fullstack developer.

Responsibilities:

• Database design and Implement.
• Develop backend APIs, logic and Microservice.
• Develop frontend functions and features.

6-Thanh Nguyen

Senior full stack engineer

Linkedin: https://www.linkedin.com/in/congthanh-nguyen-b152361a0

GitHub: https://github.com/makotovnjp

Roles: Fullstack developer.

Responsibilities:

• Database design and Implement.
• Develop backend APIs, logic and microservice.
• Develop frontend functions and features.

7-Oanh Ngo

Experienced QA/QC leader.

Linkedin: https://www.linkedin.com/in/oanh-ngo-06b331100

Role: QA/QC leader

Responsibilities: QA/QC leader, develop test scripts.

8-Xo Nguyen

Senior full stack developer.

<https://github.com/hongxo>

Roles: Full stack developer.

Responsibilities:

Develop backend APIs, logics.

Develop frontend functions and features.

9-Chuong Pham

Senior devOps and experienced Cardano engineer.

<https://github.com/jackchuong>

Roles: devOps engineer.

Responsibilities: Develop cardano scripts, product build and deployment.

10-Dung Phan

Senior infrastructure engineer.

<https://www.linkedin.com/in/phan-d%C5%A9ng-6682b5245/>

Roles: devOps engineer.

Responsibilities: System provisioning and operation.

11-Thanh Luu

Professional online marketing and customer service manager

<https://www.linkedin.com/in/thanh-luu-354409257>

Roles: Marketing and community.

Responsibilities: Product promotion, user acquisition and engagement.

12-David do

Professional social marketing manager

<https://www.linkedin.com/in/david-do-0bb52b283/>

Roles: Marketing and community.

Responsibilities: Product promotion, user acquisition and engagement.

And other resources that hire through https://www.bworks.app

Reference Cardano projects we did:

bWorks seamless Cardano smart contract HR platform, complete development already, running on trial mode:

<https://www.bworks.app>

<https://www.bworks.app/milestones>

https://github.com/saigonbitmaster/bworks_2.0

<https://github.com/saigonbitmaster/bworks-smart-contracts>

cReports, catalyst audit withCardano web3 implemented. Launched at:

<https://creport.bworks.app>

https://github.com/saigonbitmaster/creport_2.0

[RESOURCES & VALUE FOR MONEY] How does the cost of the project represent value for money for the Cardano ecosystem?

Cost optimization strategies

In software development

• All the components, libraries and frameworks we use to develop the product are free and open source, to drop the license cost.
• We maximize generalization in our software development to reduce the cost of duplication works across modules.
• We maximize use of inherited technologies, libraries and frameworks from the Cardano ecosystem, such as MeshJs and BlockFrost, so as not to incur the cost of developing components that others did well already.
• We maximize use of inherited technologies, libraries, logics and code from our previous Cardano projects e.g bWorks, cReports, to lower our costs by not developing parts that we have already done.

In human resources

• We team up with responsible and productive members to form an unstructured and no-bias team. This lets members take maximum ownership and be responsible for the works they are good at.
• We minimize middle activities and focus on more direct work, to have the highest possible performance and outputs.
• With clear objectives of milestones and tasks, we ensure that every ADA leads to valuable outputs.

In operation

As stated in the impact section, we intend to run the services for free for at least one year. Within this period, we will have to pay various expenses, including:

• AWS infrastructure costs
• Operation and marketing costs
• Development costs to improve the product

The platform will operate using our internal resources, with contributed works from the community. We will reduce hardware costs by optimizing the source code and using techniques such as docker, serverless.

Conclusion

By using the fund effectively and efficiently so that every ADA pays for a counted return, the proposal presents the best value for money for the Cardano ecosystem.

Note: As we are a flat and global team with members from Europe, Japan, Singapore and Vietnam it is not possible to provide the average local wage.