A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Promoting education through the development of Blockchain lecturer teams at universities in Vietnam (Phase 3) | ||||||||||||||||||||||||
2 | No | Name | Hour | Total (ADA) | %Budget | Timeline | |||||||||||||||||||
3 | |||||||||||||||||||||||||
4 | Milestone 1: Project Planning and Course introduction | 75 | 6500 | 9.38% | 1 month | 60 | |||||||||||||||||||
5 | Team and Roles Document: A public document introducing the key project team members and clearly describing the roles and responsibilities of each person (e.g., Project Manager, Lead Developer, Frontend Developer). | 10 | |||||||||||||||||||||||
6 | Work Environment Infrastructure:GitHub Repository: A public repository set up for the project. Community Channel: A Discord or Telegram channel created and opened for community participation.Task Management Tool: A Trello or Jira board set up and made publicly visible (in view-only mode) showing the milestones and main tasks. | 5 | |||||||||||||||||||||||
7 | Detailed dApp Scope Document: A complete document that clearly defines the features, limitations, and specific goals for each sample dApp in the project (HydraTipJar, HydraPact, HydraPoll, HydraTicTacToe, HydraTicket). | 30 | |||||||||||||||||||||||
8 | Detailed Development Plan: A document outlining the technical roadmap, technology stack, and a detailed work breakdown plan for the development of the 5 sample dApps, aligned with the proposed milestone | 20 | |||||||||||||||||||||||
9 | Server Budget (Development & Demo) | 2000 | |||||||||||||||||||||||
10 | Project managment | 10 | |||||||||||||||||||||||
11 | |||||||||||||||||||||||||
12 | Milestone 2: Development of dApp 1 (HydraTipJar) & dApp 2 (HydraPact) | 289 | 17340 | 25.04% | 2 months | ||||||||||||||||||||
13 | Part 1: HydraTipJar - Work Breakdown | 100 | |||||||||||||||||||||||
14 | 1. Backend & Off-chain Logic | ||||||||||||||||||||||||
15 | Transaction Flow Design: Architect the simple, two-party transaction flow for sending and receiving tips within the Head. | ||||||||||||||||||||||||
16 | Off-chain Code: Develop the client-side scripts to construct the basic payment (tip) transactions. | ||||||||||||||||||||||||
17 | 2. Frontend Development | ||||||||||||||||||||||||
18 | UI/UX Implementation: Build the user interface, including the tipping controls (e.g., amount input, "Send Tip" button) and a display for the total tips received. | ||||||||||||||||||||||||
19 | Wallet Integration: Integrate Cardano wallets to manage the two-party Head lifecycle (initiation, closing). | ||||||||||||||||||||||||
20 | 3. Integration & Testing | ||||||||||||||||||||||||
21 | System Integration: Connect the frontend UI to the hydra-node to submit tip transactions. | ||||||||||||||||||||||||
22 | End-to-End Testing: Test the complete user flow: opening a Head, sending multiple tips, and successfully closing the Head to settle on L1. | ||||||||||||||||||||||||
23 | Part 2: HydraPact - Work Breakdown | 120 | |||||||||||||||||||||||
24 | 1. Backend & Smart Contract (In-Head Logic) | ||||||||||||||||||||||||
25 | State Design: Design the shared state for the pact, defining the contribution requirements and the list of participants. | ||||||||||||||||||||||||
26 | Smart Contract (Plutus Validator): Develop the Plutus script that enforces the agreement, ensuring funds are only released when all parties have contributed their share. | ||||||||||||||||||||||||
27 | Backend Logic (Off-chain Code): Write the off-chain code to construct the contribution transactions that interact with the validator. | ||||||||||||||||||||||||
28 | Unit Testing: Create automated tests for the Plutus script to validate the fund-release logic. | ||||||||||||||||||||||||
29 | 2. Frontend Development | ||||||||||||||||||||||||
30 | UI/UX Implementation: Build the interface for creating a pact, inviting members, and viewing the contribution status of each participant. | ||||||||||||||||||||||||
31 | Wallet Integration: Implement the logic to handle multi-party Head initiation and transaction signing. | ||||||||||||||||||||||||
32 | Pact Interaction Logic: Develop the client-side logic to handle contribution submissions and display the pact's current status. | ||||||||||||||||||||||||
33 | 3. Integration & Testing | ||||||||||||||||||||||||
34 | System Integration: Ensure the frontend correctly calls the backend logic to build valid transactions for the smart contract. | ||||||||||||||||||||||||
35 | End-to-End Testing: Conduct tests with multiple simulated users to validate the entire pact lifecycle from creation to successful completion. | ||||||||||||||||||||||||
36 | Code Review & Refactoring: Perform a final review of both dApps to ensure the code is clean, commented, and ready for public release. | ||||||||||||||||||||||||
37 | |||||||||||||||||||||||||
38 | Live Demo Versions: Two separate public URLs, each leading to a live demo version of HydraTipJar and HydraPact. | 5 | |||||||||||||||||||||||
39 | Tutorial Documentation: Two separate tutorial articles, one for each dApp. The HydraTipJar article will focus on the "basic Head lifecycle," while the HydraPact article will explain "simple multi-party agreement logic." | 12 | |||||||||||||||||||||||
40 | Demonstration Videos: Two short YouTube videos, each showcasing the user flow of one dApp. | 12 | |||||||||||||||||||||||
41 | Event Marketing and communications | 20 | |||||||||||||||||||||||
42 | Project managment | 20 | |||||||||||||||||||||||
43 | Milestone 3: Development of dApp 3 (HydraPoll) | 229 | 13740 | 19.84% | 1 months | ||||||||||||||||||||
44 | 1. Backend & Smart Contract (In-Head Logic) | 50 | |||||||||||||||||||||||
45 | State Design: Architect the on-chain and off-chain data structures for the poll, including vote tallies and a list of participants who have already voted. | ||||||||||||||||||||||||
46 | Smart Contract (Plutus Validator): Develop the Plutus script that enforces poll rules within the Head, primarily focusing on the "one person, one vote" validation. | ||||||||||||||||||||||||
47 | Backend Logic (Off-chain Code): Write the off-chain code to construct valid voting transactions and correctly update the vote tally in the state UTXO. | ||||||||||||||||||||||||
48 | Unit Testing: Create automated tests for the validator and off-chain logic to ensure poll integrity and prevent invalid votes (e.g., duplicate voting). | ||||||||||||||||||||||||
49 | 2. Frontend Development | 70 | |||||||||||||||||||||||
50 | UI/UX Implementation: Build the user interface for both creating a poll (defining the question and options) and participating in one, including real-time visualization of the results. | ||||||||||||||||||||||||
51 | Wallet & Invite Flow: Integrate Cardano wallets for the poll session (Head) initiation and management of participants. | ||||||||||||||||||||||||
52 | Polling Interaction Logic: Implement client-side logic to handle vote submissions and dynamically update the displayed results as new state data is received from the Head. | ||||||||||||||||||||||||
53 | 3. Integration & Testing | 50 | |||||||||||||||||||||||
54 | System Integration: Ensure seamless communication between the frontend, the off-chain backend logic, and the on-chain Plutus validator. | ||||||||||||||||||||||||
55 | End-to-End Testing: Conduct tests simulating a complete poll with multiple participants to validate the entire workflow and rule enforcement. | ||||||||||||||||||||||||
56 | Code Review & Refactoring: Perform a final review to ensure the code is clean, well-commented, and ready for public release. | ||||||||||||||||||||||||
57 | Live Demo Version: A public URL where the community can directly access and test the dApp. | 3 | |||||||||||||||||||||||
58 | Tutorial Documentation: A detailed article explaining how the dApp works and providing setup instructions. | 8 | |||||||||||||||||||||||
59 | Demonstration Video: A short YouTube video showcasing the user flow of HydraPoll. | 8 | |||||||||||||||||||||||
60 | Event Marketing and communications | 20 | |||||||||||||||||||||||
61 | Project managment | 20 | |||||||||||||||||||||||
62 | Milestone 4: Development of dApp 4 (HydraTicTacToe) | 229 | 13740 | 19.84% | 1 months | ||||||||||||||||||||
63 | 1. Backend & Smart Contract (In-Head Logic) | 50 | |||||||||||||||||||||||
64 | State Design: Architect the on-chain and off-chain data structures for the game state, defining the datum managed by the smart contract. | ||||||||||||||||||||||||
65 | Smart Contract (Plutus Validator): Develop the Plutus script that enforces the game's rules within the Hydra Head by validating turns and state transitions. | ||||||||||||||||||||||||
66 | Backend Logic (Off-chain Code): Write the off-chain code responsible for constructing and signing transactions that interact with the smart contract, including the logic to check for win/draw conditions. | ||||||||||||||||||||||||
67 | Unit Testing: Create automated tests for both the Plutus validator and the off-chain logic to ensure game integrity. | ||||||||||||||||||||||||
68 | 2. Frontend Development | 70 | |||||||||||||||||||||||
69 | UI/UX Implementation: Build the interactive 3x3 game board and all necessary user notifications. | ||||||||||||||||||||||||
70 | Wallet & Invite Flow: Integrate Cardano wallets to manage the two-player setup and game session initiation. | ||||||||||||||||||||||||
71 | Game Interaction Logic: Implement client-side logic to capture user inputs, trigger the backend to create transactions, and update the UI based on new state data from the Head. | ||||||||||||||||||||||||
72 | 3. Integration & Testing | 50 | |||||||||||||||||||||||
73 | System Integration: Ensure that frontend interactions correctly trigger the backend, create valid transactions, and are successfully validated by the smart contract. | ||||||||||||||||||||||||
74 | Gameplay Testing (E2E): Conduct end-to-end tests with two players to validate all possible game scenarios. | ||||||||||||||||||||||||
75 | Code Review & Refactoring: Perform a final review to ensure the code is clean, well-commented, and ready for public release. | ||||||||||||||||||||||||
76 | Live Demo Version: A public URL where two players can access and play a full game of Tic-Tac-Toe against each other. | 3 | |||||||||||||||||||||||
77 | Tutorial Documentation: A detailed article explaining how to build a turn-based interactive application on Hydra, using the Tic-Tac-Toe game as the example. | 8 | |||||||||||||||||||||||
78 | Demonstration Video: A short YouTube video showcasing two players joining and completing a game. | 8 | |||||||||||||||||||||||
79 | Event Marketing and communications | 20 | |||||||||||||||||||||||
80 | Project managment | 20 | |||||||||||||||||||||||
81 | |||||||||||||||||||||||||
82 | Milestone 5: Development of dApp 5 (HydraTicket) and Closing project | 299 | 17940 | 25.90% | 1 months | ||||||||||||||||||||
83 | 1. Backend & Smart contract Logic (Hydra Head) | 40 | |||||||||||||||||||||||
84 | State Design: Architect the "ticket" data structure using UTXO metadata. | ||||||||||||||||||||||||
85 | Core Logic Development: Develop and unit-test the off-chain script that validates user payments and automatically issues a new "ticket" UTXO in response. | ||||||||||||||||||||||||
86 | 2. Frontend Development | 60 | |||||||||||||||||||||||
87 | UI/UX Implementation: Build the user interface for the locked content, the "Pay to Unlock" flow, and the final unlocked content view. | ||||||||||||||||||||||||
88 | Wallet Integration: Integrate Cardano wallets (e.g., Lace, Eternl) to manage Head creation and transaction signing. | ||||||||||||||||||||||||
89 | Dynamic Unlocking: Implement the client-side logic to monitor the user's in-head state and automatically reveal content when a valid ticket is detected. | ||||||||||||||||||||||||
90 | 3. Integration & Testing | 50 | |||||||||||||||||||||||
91 | System Integration: Ensure seamless communication between the frontend and the hydra-node for submitting transactions and monitoring state. | ||||||||||||||||||||||||
92 | End-to-End Testing: Test the complete user flow: viewing locked content, paying, receiving the ticket, and accessing the content. | ||||||||||||||||||||||||
93 | Code Review & Refactoring: Conduct a final review to ensure the code is clean, well-commented, and ready for public release. | ||||||||||||||||||||||||
94 | Live Demo Version: A public URL featuring locked content, allowing users to experience the payment flow to unlock and view the content. | 3 | |||||||||||||||||||||||
95 | Tutorial Documentation: A detailed article explaining the "pay-to-access" model and how to use transaction metadata as a digital "ticket" on Hydra. | 8 | |||||||||||||||||||||||
96 | Demonstration Video: A short YouTube video showcasing the entire process from seeing locked content to successfully paying and accessing it. | 8 | |||||||||||||||||||||||
97 | Organize AMA sessions to answer developer questions | 30 | |||||||||||||||||||||||
98 | Create a Project Close-Out Report on Google Drive. Create a Project Close-Out Video on Youtobe . | 50 | |||||||||||||||||||||||
99 | Event Marketing and communications | 20 | |||||||||||||||||||||||
100 | Project managment | 30 |