{"signature": "0xae70bdec541b6e0f74576fc502ad8c2b7a8745b0fae5da1e10742f4d1bdf2c2c146fe719ebd8006bceb8e502e4b638f64501d7fc995bea65c3b4ad60f2781a011c", "application": {"round": "0x3E93205B786796Cf7Ea70404E89c7dda3b84D07a", "answers": [{"type": "email", "answer": "yuki.kawabe@code4japan.org", "hidden": true, "question": "Email Address", "questionId": 0}, {"type": "short-answer", "answer": "yu23ki14", "hidden": true, "question": "Telegram Handle We Can Use To Contact You", "questionId": 1}, {"type": "short-answer", "answer": "https://github.com/hackdays-io/toban", "hidden": false, "question": "Project GitHub Repo", "questionId": 2}, {"type": "link", "hidden": false, "question": "Link to your Public Group Chat", "questionId": 3}, {"type": "paragraph", "answer": "GG22 OSS Rounds\nhttps://builder.gitcoin.co/#/chains/42161/registry/0x/projects/0x4a16bd8a8366c8491b91558d249d192d696702e3037a63238c6acf648b69051e", "hidden": false, "question": "Have you participated in a previous Gitcoin Grants Round? If so, please name the rounds or link the builder profile associated with previous rounds.", "questionId": 4}, {"type": "paragraph", "answer": "Our project, Toban, is a tool designed to help communities record contributions and distribute rewards fairly. While contributing to OSS is easy to start, few people stay long enough to make sustained contributions — a major challenge for OSS maintainers.\n\nNo matter how much effort is spent onboarding new contributors, if they leave quickly, it’s hard to create lasting impact. This is especially true for new or experimental projects that haven't yet proven successful.\n\nToban is inspired by the Protocol Guild model — it rewards contributors more the longer they stay involved and allows for retrospective reward distribution when a project succeeds.\n\nAnother unique aspect is that Toban originated in Japan and aims to empower OSS activity throughout Asia, creating more vibrant, regional OSS ecosystems.", "hidden": false, "question": "How does your project contribute to the growth of the OSS ecosystem? Please provide specific examples of how your application enhances or expands the current ecosystem.", "questionId": 5}, {"type": "paragraph", "answer": "Toban’s key innovation is role-based contribution tracking. There are many great tools like Dework, Coordinape, and Praise that we've used ourselves, but most rely on task-based management or peer evaluation.\n\nTask-based tools struggle with fair pricing of tasks, and the steps from creating to reviewing tasks are often too cumbersome to maintain. Peer evaluations require deep awareness of the community’s activities and can be emotionally challenging when it comes to ranking others.\n\nToban addresses these issues by using role NFTs (representing abstracted responsibilities) and peer-to-peer tokens that members send when they’ve received help. These tokens act as signals to calculate contribution levels in a lightweight and ongoing way.\n\nBeyond tracking, Toban integrates with Splits Protocol to automate ERC20 or native token distribution to contributors, all at once — a powerful feature that reduces operational overhead.", "hidden": false, "question": "What features or use cases does your dApp/App present? How is it differentiated?", "questionId": 6}, {"type": "paragraph", "answer": "Our main goals for 2025 are to refine our current MVP, conduct smart contract audits, and continuously explore use cases through pilot programs with real communities.\n\nWe plan to use the grant funds primarily to reward our own contributors through Toban itself, reinforcing ongoing commitment. Additionally, part of the grant will be used to cover beta operational costs and security audits to ensure robustness and reliability.", "hidden": false, "question": "What are your plans for further development, and how will the grant funds be used to achieve these goals?", "questionId": 7}, {"type": "paragraph", "answer": "0x9B08FBe814985856a561eeEC57e105ae71AF38EC, 8453", "hidden": false, "question": "For any project deploying smart contracts on blockchain networks, please list all your deployer addresses and their corresponding blockchain networks. Use this format for each entry: [deployer_address], [chain_id]—for example, 0x123abc..., 42161 (This represents a deployer address on the Arbitrum network). Please include a separate line for each unique deployer address and blockchain combination.", "questionId": 8}], "project": {"id": "0x4a16bd8a8366c8491b91558d249d192d696702e3037a63238c6acf648b69051e", "title": "Toban -当番-", "logoImg": "bafkreidd46qgocj65yvabjgcboxt7oxjwv76s42uqtucd566jjf6h3rikq", "metaPtr": {"pointer": "bafkreici52ojrvmthivdloswzibdn3dq2okwk56qtedtdvrknykva6qwrm", "protocol": "undefined"}, "website": "https://github.com/hackdays-io/toban", "bannerImg": "bafkreihyljrog264f7hwwekn6easnorny5x6bzexhddbt3du76skwewxz4", "createdAt": 1728304600313, "userGithub": "yu23ki14", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..clOdPM3zeid7-0Lm_jS0TXJLN0dFtqDwLu7UU8mVTYEgbVhuBBcR9R7zBRqeANDyzFv8d423_KEDjEGuHdCADg", "type": "Ed25519Signature2018", "created": "2024-10-07T12:34:44.218Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-10-07T12:34:44.218Z", "expirationDate": "2025-01-05T12:34:44.218Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xD238C2bCeB99BBac56647b852A59683a3924e00a", "hash": "v0.0.0:NJnaCFuVTDo98VyBWeXUBrw1Pb9mh0jn934KbQRTnWU=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#hackdays-io#18475563"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..v3VruPVrRdeuWFRde0ohXD7WCecwmBFf2Xd5wZS70-Z0neClR9ZF2-Sz75R4K7ZAtj30yG3R8euA8-qU9oEyCg", "type": "Ed25519Signature2018", "created": "2024-10-07T12:33:57.530Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-10-07T12:33:57.530Z", "expirationDate": "2025-01-05T12:33:57.530Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xD238C2bCeB99BBac56647b852A59683a3924e00a", "hash": "v0.0.0:XKxkWAP816NplB5wVkqiPyaZPRDrq/1dC6pnIus9hbk=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#0xtoban"}}}, "description": "# Overview\n\nToban is a DAO Tool that realizes the simplest and most effective way of recording contributions and distributing rewards. It supports contribution tracking and reward distribution in a way that aligns with the operational needs of internet-native collaborative activities.\nIt mainly aims to support sustainable activities in open-source software (OSS) communities, collaborative art creation, and DAO-based regional revitalization projects. By providing role-based contribution tracking and reward distribution based on contribution levels, Toban promotes the long-term growth of communities.\n\n# Objective\n\nToban's objective is to provide a system where every contribution in internet-native collaborations is recognized and properly evaluated, leading to sustainable activities.\nProjects and communities conducted over the internet have the potential to create new value through the collaboration of diverse individuals, unrestricted by distance or time. However, volunteer and remote-based contributions often go undervalued, and the lack of proper reward mechanisms can make it difficult to sustain participation. Toban aims to increase the number of projects where contributions are recorded and visualized so that participants are recognized and rewarded.\n\nAdditionally, although Toban originated in Japan, it is being developed in collaboration with contributors from across Asia, ensuring interoperability with global DAO tools and protocols. This allows Toban to offer a unique approach rooted in Japanese and Asian culture while also providing new insights and perspectives to other global projects.\n\n# Features\n\nWhile there are other DAO tools for tracking contributions and distributing rewards, Toban's key feature is its \"Role-Based Rewards Distribution\" system. \nTraditional task-based contribution tracking often becomes cumbersome and prone to being overlooked, making it difficult to sustain.\nPeer-based evaluation systems can also introduce subjective bias, sometimes leading to all participants being rated similarly, diluting the value of the evaluation.\nThere are also tools that calculate contribution scores based on activity on platforms like GitHub or Discord, but these struggle to capture contributions made outside the platform.\n\nToban addresses these issues through the following elements:\n\n- Contribution Tracking: Toban records contributions based on slightly abstracted \"roles\" while also offering a mechanism to capture smaller contributions through P2P token distribution.\n- Reward Distribution: When a project generates revenue or receives donations, Toban calculates contribution levels based on contribution time, P2P token balances, and role-based weighting, automatically distributing rewards. The system is built using tools like Splits and Superfluid to manage ERC20 and native tokens.\n- Interoperability: Toban is designed to be interoperable with other DAO tools and protocols, such as Hats Protocol, DAOHAUS, and ENS, enabling flexible decision-making and reward distribution that scale with the community’s size and growth.\n\n# Target Users\n\n- Communities or project teams involved in internet-native activities\n- DAOs (decentralized autonomous organizations) or communities looking to implement contribution-based reward systems\n- Projects aiming to automate contribution tracking and evaluation, boosting participant motivation\n\n# Roadmap\n\n- 2025.4: Start to conduct 3 pilot projects\n- 2025.5: Collect user feedbacks and work on feature improvements\n- 2025.6: Enritch documentation and use case guide book\n- 2025.7: Mager update for mainnet contract\n- 2025.8: Expansion of the user and developer community", "lastUpdated": 0, "projectGithub": "hackdays-io", "projectTwitter": "0xtoban"}, "recipient": "0x6a245A9DDA257e45f532AA4BBed46E6D9F480B82"}}