Carbonvote 2.0
{"title": "Carbonvote 2.0", "logoImg": "bafkreia7zplb5rb3thewvmot5jcl2ms57gxthhwn3ufy7br4uzjjwabpia", "website": "https://beta.carbonvote.com/", "bannerImg": "bafkreid75egggzodqlfdxbtdo4vl5cvqsxckmmsmu7edns3ihzbr3fvjha", "createdAt": 1706456448810, "userGithub": "wentianyang66", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..SP1PbyK02MEDj3LqiYOTTsync4eCj3-AdSvHaiYOGta-zf8sGCxOSumvlHG7PMl8FGfjwqYItWKEgb_doBd4Dg", "type": "Ed25519Signature2018", "created": "2024-01-28T15:39:47.139Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-01-28T15:39:47.139Z", "expirationDate": "2024-04-27T15:39:47.139Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x13cec25A38748f6E34c2B6e0ce9E60d0d952eCEb", "hash": "v0.0.0:W0KCerWOLzUKqH24yUAHsoc8ZKp6qEyY9iFlfW5ogJE=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#EthereumCommunityFund#79211462"}}}, "description": "# The emergence of Carbonvote 2.0\n\nCarbonvote.com's 2024 upgrade intends for it to be utilized in the Ethereum community, serving as a platform for gauging community sentiment on proposals related to the Ethereum network and as a tool that can be used for similar purposes in other community affairs. \n\nThis platform allows users to vote on issues offering a space for decentralized decision-making.\n\n## Background:\n\n[Carbonvote.com](https://beta.carbonvote.com) was a website built across several teams in the Ethereum Community. It facilitated a signaling mechanism for Ethereum stakeholders to express their preferences on important decisions. In the context of the DAO attack, it was used to conduct a carbon vote, a type of vote in which participants indicate their preferences by casting a certain amount of votes proportional to their stake in the network.\n\n[Carbonvote.com](https://beta.carbonvote.com) played a role in the aftermath of the 2016 Ethereum DAO (Decentralized Autonomous Organization) attack. As a response to the attack, one proposed solution was a fork in the Ethereum blockchain, which would roll back the transactions associated with the DAO attack. This proposal led to a significant debate within the Ethereum community. (See [Repo](https://github.com/consenlabs/carbonvote))\n\nEthereum stakeholders were asked to vote on whether they supported the implementation of a hard fork to reverse the effects of the DAO attack. The carbon vote on carbonvote.com showed that a significant majority of the community supported the hard fork option.\n\nThe name “Carbonvote” is composed of two elements: “Carbon” and “vote”. In this context, “Carbon” symbolizes something fundamental and elemental. Just like Carbonvote is a fundamental governance tool in the Ethereum community it provides the functionality of poll voting and counting for big community decisions.\n\n## Objective & Carbonvote V2.0:\n\nThe DAO incident and the subsequent hard fork highlighted the challenges and complexities inherent in decentralized governance, with divergent perspectives within the community on how to address critical issues. For this upgrade, beta.carbonvote.com needs to address some known issues found in the previous implementation.\n\nAs the Ethereum community continues to evolve, there is a recognition of the need for improved signaling mechanisms and platforms like Carbonvote.com to facilitate community input on proposed upgrades and changes. The development of effective and inclusive tools for signaling and decision-making remains a priority for fostering consensus and maintaining the decentralized nature of the Ethereum network.\n\nTo address the goal of going beyond Zuzalu and creating advanced signaling tools for the Ethereum community, especially in the context of discussing potential hard forks, it’s important to consider the specific needs and concerns of core developers. The aim is to provide a platform that not only facilitates community input but also ensures the legitimacy of proposals, instilling confidence in core developers.\n\n## Key Features \n\nCarbonVote is a platform that enables the creation of polls, with real-time display of results. It supports two types of polls: EthHolding and HeadCounting.\n\n### A. Voting Methods:\n\n#### A.1 EthHolding Method:\n\n- Utilizes smart contracts for on-chain voting.\n- Dynamically calculates ETH held by each voting address.\n- Voters cast zero-valued ballots to specific addresses, determining Yes or No based on the transaction destination.\n- Real-time display of total ETH voted for each option during the voting process.\n\n#### A.2 HeadCounting Method:\n\n- Each voter's vote has equal weight.\n- Results displayed in real-time.\n- Introduces a Credentials system.\n\n### B. Current Features: Credential Checking System\n\n#### B.1 Credential Types:\n\n- Zupass Credential (Zuzalu Ticket Holders, Zuconnect Ticket Holders, Devconnect Ticket Holders):\n  - Requires holding specific Zupass tickets for voting.\n  - Integrates well with Zupass for authentication.\n- Gitcoin Passport Credential:\n  - Requires an authenticated Gitcoin passport with a score above zero for voting (test version).\n  - Allows customization of score thresholds in future releases.\n- Ethereum Events POAPS Credential:\n  - Requires a user's wallet to have a certain number of Ethereum events POAPS for voting.\n  - Verification methods include API and smart contract.\n- Protocol Guild Membership Credential:\n  - Corresponds to the HeadCounting method that each vote has the same weight.\n  - Requires the user's address to be on the list of protocol guild members, verified using a smart contract which is similar to EthHolding poll.\n\n### C. Upcoming Features:\n\n#### C.1 Usage of Secret Message:\n\n- Allows users to prove ownership of an account by sending a transaction with a locally-generated secret message, providing an optimized method for user verification.\n\n#### C.2 Changes in Storage:\n\n- Shifts all polls to Web 3.0 stacks, making polling data transparent and aligning with the vision of CarbonVote becoming a dApp.\n\n#### C.3 Poll Counting for Different Groups:\n\n- Allows polls to be open to multiple credential groups.\n- Counts votes of each group individually, providing a better reflection of diverse views.\n- Supports overlapping credentials within groups.\n\n#### C.4 Optimized Storage Methods:\n\n- Explores cost-effective ways of storing and deploying polls while preserving validation possibilities.\n- Considers methods such as off-chain signatures and storing on IPFS.\n\n## Build with us!\n\nExplore Carbonvote 2.0 - Now Open for Testing! 🚀\n\nWe're excited to announce that Carbonvote 2.0 is now open for testing! Dive into the beta version and experience the latest features at [beta.carbonvote.com](https://beta.carbonvote.com/). Your feedback is invaluable as we strive to enhance and refine the platform.\n\nJoin the Zuzalu Community Toolkit Server! 🏆\n\nFor collaborative discussions, insights, and the exchange of expertise, we invite you to join the Zuzalu Community Toolkit Server. Your participation contributes to the growth and improvement of our tools. Connect with us at [Zuzalu Community Toolkit Server](https://matrix.to/#/!BnzxiLNyJtscpuATnZ:matrix.org?via=matrix.org&via=lemonade.social) and be part of shaping the future of decentralized governance in the Ethereum community. Let's build together!\n", "logoImgData": {}, "bannerImgData": {}, "projectGithub": "EthereumCommunityFund"}