metadata: {"signature": "0x4d039a84218ba13e1efda9c161ec92453a4247902a4860f5570fdbe5f1a21fdb094dcb545a751c46f86e33c2e5ee05ba689f557b206706a3cde3a0022fd3c6e01b", "application": {"round": "0x20c94c8d87175abcac8892636cd23b25515e10f3", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "QHsTSBVJe9Zh3ghGm1MPKDAREn69T/x6vnS5dorr+VXzUv5Piba/aGFthPpxJjom", "encryptedSymmetricKey": "9ed4ccdbfe4a5b4b337cf0e74b36992b10ccf69c998ced2a5f33feec8705efeac0844af3130266ef95f3fd86b47bd00e22ec5869646b740bf585c88680768908be51b5388f348184ec02cae2d484caf30bd745b8e459de9776c951448991cc9472a1a9f1c49a17159b902d3b561c2a5fdbafbec1ec31c2648b9158ca8027009e0000000000000020a19d347efef769ea983bafdb566b5a73a1ba9ccc0c882aa6c98580315da11d92f35c80e33187b23ca67030fcccf2608c"}}, {"type": "short-answer", "answer": "@mwunder", "hidden": true, "question": "Telegram Handle", "questionId": 1}, {"type": "short-answer", "answer": "https://github.com/HonorCodeDAO/honorcode", "hidden": true, "question": "Project GitHub Repo", "questionId": 2}, {"type": "short-answer", "hidden": true, "question": "Link to your Public Group Chat", "questionId": 3}, {"type": "short-answer", "answer": "GG19 & GG20", "hidden": true, "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": "ETHDenver https://app.buidlbox.io/projects/honor-code", "hidden": true, "question": "Which hackathon did your project participate in, and when? Please provide a link to your hackathon project page.", "questionId": 5}, {"type": "paragraph", "answer": "We have finished development and testing of the smart contracts, which are now deployed and ready to use. The UI rollout has lagged behind and is the natural next step. For instance, we\u2019ve had to integrate Graph support to make it easier to track interactions with a project\u2019s artifacts. We\u2019re aiming to achieve basic web functionality should be available sometime in coming months. However, lately the focus has detoured into making the case for why this type of on-chain reputation is needed. To that end, we have been putting out a series of blog posts and threads to construct the philosophical framework for on-chain reputation. ", "hidden": true, "question": "Describe the progress and development of your project since the hackathon. What milestones have you achieved?", "questionId": 6}, {"type": "paragraph", "answer": "This project is a prototype for on-chain reputation, which the community has increasing need for. This necessity becomes clear when people discuss how to allocate funding, for example. There is a desire to have funds propagate towards those contributing value and the dependency links between projects constitutes a form of reputation. HonorCode aims to show how an honor-centric approach can organize contributions as a demonstration of this philosophy in action.", "hidden": true, "question": "How does your project contribute to the OSS? What problem does it solve, or what value does it add?", "questionId": 7}, {"type": "paragraph", "answer": "While we've realized that much of the effort will have to go towards convincing the community of the significance of on-chain reputation, this will be accelerated by a working UI which is the next step of development. It's likely we'll have to bring on an extra developer to move forward quickly. ", "hidden": true, "question": "What are your plans for further development, and how will the grant funds be used to achieve these goals?", "questionId": 8}, {"type": "paragraph", "answer": "0x6e327292C378DD55D6aa49981cee8bD2a0a00fbb, 10", "hidden": true, "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]\u2014for 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": 9}], "project": {"id": "0x2407ce2fcd01ecc5096a6e79cf3db70ec5d4dd81626740afb0b1023e201c4b24", "title": "HonorCode", "logoImg": "bafkreih3fjscfscopbnqzen6sifuvnxcguu2xhjqrhhaszmwrq4xm4onaa", "metaPtr": {"pointer": "bafkreifktmn6xi72dbunihenytp77lubqvjsckxzyd4eg5vcxt7w6kmnza", "protocol": "undefined"}, "website": "https://docs-site-lac.vercel.app", "bannerImg": "bafkreic5whubsmvqvbfrmjteomkvfrh7vnkb2djitidx2facrscvenoksy", "createdAt": 1699230447789, "userGithub": "mwunder", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..wja3fU0OLbgGzNEA0cDRS9YL2Cm4MbzxSigT_n9_LkpUhAdFEK8Gha2xZOPZKTVJIQ3ZemyThP5w2mShr8eBCQ", "type": "Ed25519Signature2018", "created": "2023-11-07T03:51:04.033Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-11-07T03:51:04.032Z", "expirationDate": "2024-02-05T03:51:04.032Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x97a4abcFC3C99E42fb621Da62153bE5eCDf16677", "hash": "v0.0.0:pKVNe9/+AKtyB+o7dpkwf8sqK8ImjYUWKuTBJmGi8o4=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#HonorCodeDAO#5855345"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..z0OulyllyImtU3utyP5_pdPvYhGNR4VqHGepeVZ-c6xjqZvVXMi0X49lIx3OZK2McRzUkcrNZrNmbQ7jv9C9CA", "type": "Ed25519Signature2018", "created": "2023-11-07T03:48:35.176Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-11-07T03:48:35.176Z", "expirationDate": "2024-02-05T03:48:35.176Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x97a4abcFC3C99E42fb621Da62153bE5eCDf16677", "hash": "v0.0.0:Z7CyBuJ4VSuftaB9v7R6vZMsv0Py5TocxxtWtKqoCCs=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#RecursiveStakes"}}}, "description": "HonorCode is an open-source project reputation protocol for DAOs to recognize contributions from builders. It l consists of a semi-transferable token: a token that can only be transferred between a set of contracts belonging to the DAO. Flows of this STT creates a prediction market and results oracle, as well as an outlet for governance.\n\nBy insulating HONOR from direct convertibility, we allow for a community to define its own values and relation to outside capital. It therefore is free to search out ways to track and recognize impact over time, a problem faced by DAOs generally and especially in the public goods space.\n\nAt the same time we know how impact can become disconnected from fully transferable assets, while soul-bound tokens lack flexibility. STTs aim for the sweet spot between these extremes.\n\nHONOR tokens enable a number of actions and interactions.\n\n    * Stakers lock up yield-bearing assets (such as staked ETH) and farm HONOR\n    * Holders propose and vouch for project artifacts\n    * Builders earn HONOR for their artifacts\n    * Artifact Vouchers receive reward from the virtual staked asset\n    * Vouching also allows participants to allocate to other artifacts", "lastUpdated": 0, "projectGithub": "HonorCodeDAO", "projectTwitter": "RecursiveStakes"}, "recipient": "0x97a4abcFC3C99E42fb621Da62153bE5eCDf16677"}}