{"action":"created","issue":{"url":"https://api.github.com/repos/aragon/nest/issues/66","repository_url":"https://api.github.com/repos/aragon/nest","labels_url":"https://api.github.com/repos/aragon/nest/issues/66/labels{/name}","comments_url":"https://api.github.com/repos/aragon/nest/issues/66/comments","events_url":"https://api.github.com/repos/aragon/nest/issues/66/events","html_url":"https://github.com/aragon/nest/pull/66","id":346353308,"node_id":"MDExOlB1bGxSZXF1ZXN0MjA1MjM4NTIw","number":66,"title":"EthSignals request for funding","user":{"login":"arrose","id":3519634,"node_id":"MDQ6VXNlcjM1MTk2MzQ=","avatar_url":"https://avatars2.githubusercontent.com/u/3519634?v=4","gravatar_id":"","url":"https://api.github.com/users/arrose","html_url":"https://github.com/arrose","followers_url":"https://api.github.com/users/arrose/followers","following_url":"https://api.github.com/users/arrose/following{/other_user}","gists_url":"https://api.github.com/users/arrose/gists{/gist_id}","starred_url":"https://api.github.com/users/arrose/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arrose/subscriptions","organizations_url":"https://api.github.com/users/arrose/orgs","repos_url":"https://api.github.com/users/arrose/repos","events_url":"https://api.github.com/users/arrose/events{/privacy}","received_events_url":"https://api.github.com/users/arrose/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-31T20:51:28Z","updated_at":"2018-07-31T20:51:38Z","closed_at":null,"author_association":"NONE","pull_request":{"url":"https://api.github.com/repos/aragon/nest/pulls/66","html_url":"https://github.com/aragon/nest/pull/66","diff_url":"https://github.com/aragon/nest/pull/66.diff","patch_url":"https://github.com/aragon/nest/pull/66.patch"},"body":"# EthSignals request for funding (#47)\r\n\r\n**Team name**: EthSignals\r\n\r\n**Proof of concept / research whitepaper**: N/A\r\n\r\n**Burn rate**: $30k/month (once ramped up)\r\n\r\n**Legal structure**: Giveth Social Coding Project (No legal entity, but currently exploring available options)\r\n\r\n**[Team and roadmap](https://github.com/arrose/nest/tree/master/grants/Ethsignals)**\r\n\r\n\r\n\r\n## Proposal\r\n\r\nOur project aims to track and aggregate information and signals from around the ethereum ecosystem and present this in a way that allows the community to get a clearer picture of the reality of the space. \r\nAs the Ethereum blockchain grows, so does its community. In turn, the governance of its decision-making process becomes more complicated. And yet the ability to successfully make decisions becomes ever more critical for the success of the project. Decisions can only be taken with access to high quality objective information. \r\n\r\nTherefore the goal of this project is to provide an additional tool and source of high-quality information to help the Ethereum community self govern. \r\n\r\nWe will be focused on mapping three key areas:\r\n- The general state of Ethereum\r\n- Signals of support for or against individual EIPs\r\n- On-chain and credible third party information about individual Ethereum Based Projects\r\n\r\nThis project will be built by a small dev/product team in collaboration with the ethereum core devs and members of the larger community.\r\n\r\n## Target Audience\r\n\r\nWe aim to focus first on the needs of Ethereum core devs in order to provide them with relevant info. However the extensive list of audience stakeholders are as follows: Core devs, Miners, Full nodes, Ethereum working groups (Rings), DApp devs, DApp users, Researchers, Educators, Investors, Ecosystem orgs, and Gov/Regulators. As part of the research for the project, we will be looking into how each group gathers information, how they use this, and what they are missing through a series of interviews. \r\n\r\n## Signals\r\n\r\nThe primary deliverable of this project will be a website that brings together various signals from the community. Given that some of the signals will require additional research and development before they can be properly incorporated, we will break the delivery of the site into 5 parts based on the different signals. \r\n\r\nSignals that we aim to include are *Gas Voting, Coin Staking, Node Voting, Hashrate Voting* and  *Community Statements*. For this project, we will be combining our own research and new data aggregation tools with existing tools and platforms. \r\n\r\n**Brief description of the 5 signals:**\r\n\r\n*Gas Voting*: A new concept being built by the slock.it team in which voters favor/reject a proposal by attributing an address to it, and the gas spent by each address is added up to produce an amount favoring/rejecting a proposal. Individual users can say they favor a proposal with an address they own. Developers vote can be deduced by the gas used by their account’s deployed contracts. Thus the more active (more gas used) the account or contract/dapp deployed is, the more influence one would have in this signaling mechanism.\r\n\r\n*Coin Staking*: Also know as a coin vote, in this setup individual addresses containing tokens are able to signal in one way or another that they favor one side of an issue. In tallying up the vote, the number of tokens placed towards each option are calculated and compared. This can be recorded for ETH or other tokens.\r\n\r\n*Node Voting*: In this setup, each node is able to vote. Every node operator can declare which proposal they favor/reject and set up all of their nodes to signal appropriately. Some node operators may have more nodes than others. The number of nodes on each side of the vote is tallied up at a particular time, or over a span of time they are online.\r\n\r\n*Hashrate Voting*: When a miner or mining pool is mining, they will be able to tag the hashrate of their miners to a vote. In tallying up the vote, the total hashrates for each option is calculated and compared.\r\n\r\n*Community Stances*: a collection of the positions and feedback about specific EIPs from the top contributors in the space. [Note: The exact methods that will be used in determining who is included and which sources are to be used is something that we will be determined during the research and testing period of the project. This will be done together with the community and the stakeholders who will be using this site.]\r\n\r\nThe aim here is to aggregate multiple signals and offer a platform to sort and view this data. Each of the signals is known to have pros and cons - as explored in this presentation at Fellowship of Ethereum Magicians in Berlin, July 2018 - and as such, no individual signal should be taken as the sole source of truth. However, we do believe that in combining these signals and providing a meta view of how decisions are being viewed in different circles, we will be able to better paint the picture of the sentiments of the larger ecosystem. \r\n\r\nAs the project develops, we will also remain open to additional signals. As they are identified, we will also look to incorporate these into our site. To quote one of our team members James, “We want to provide many 2D views of a 3D object, to get us closer to the real picture”\r\n\r\n## Prototype Design\r\n\r\nBelow is a first idea board / design of what we envision building:\r\n\r\n![skarfvpuqf_nfqrescks5ow 1](https://user-images.githubusercontent.com/3519634/43484549-eb7b2112-950e-11e8-84f9-cd4ec9031e89.png)\r\n\r\n**This is a prototype design and not final. Versions will add signals incrementally as we implement them.*\r\n*[Google Drawing Link](https://docs.google.com/drawings/d/1TVEkH4n4PQOGh9b-iJVkAhwQwSpk5dW0LsPO9Dltesg)*\r\n*[Image LInk](https://docs.google.com/drawings/d/e/2PACX-1vQnz3fu-Xej_S0k0mamjSxz7ImmRv2httlBeH-Rnsl3UTcEc6maNykX7MEJyevAs8ovzVgP4A697BBE/pub?w=1311&h=1077)**\r\n\r\n## POC / Tech Design \r\n\r\nBelow is the Core Feature Map including 3 modules that make up the larger build\r\n\r\n![ssfyveodymo3j2fjvcsrrzg](https://user-images.githubusercontent.com/3519634/43484617-1d11807c-950f-11e8-8ebc-a5ef4f441e06.png)\r\n\r\n*[Google Drawing Link](https://docs.google.com/drawings/d/1JeBHsvi2IppJE_s58Hm7o0vP3RREMr6o8Ru8C6WPikE)*\r\n*[Image Link](https://docs.google.com/drawings/d/e/2PACX-1vTMkDVqwJY384tPXCiBSpg26cnyS-3LLSVmlv3iOeO5St50GxjlO3EJ5LIw_TuCOJkb3sagipIpRjm6/pub?w=1016&h=721)*\r\n\r\n\r\n## Deliverables\r\nThe site will initially focus on Module 1 (m1) for EIP community stance and will include:\r\n\r\n**A home page with EIPs and their current stance:**\r\n- A single space on the Webpage that communicates the current stances and voting on an EIP\r\n\r\n**Two signals for each EIP:**\r\n- A voting score (such as Coin Voting)\r\n- Influencer Stances viewable in 3 different groupings. An influencer can be in multiple views.\r\n    - Core devs organized into Magicians Rings\r\n    - Ethereum Influencers integrating the work of Maciek Laskus who is creating a list inspired by https://cryptoinfluencers.io/ but for Ethereum using many signals from the development community.\r\n    - Other, which will include remaining stakeholders as well as functionality to custom sort based on user preference.\r\n\r\n\r\nMaintaining the site will be managed in a Github Repo that the community is encouraged to pull request any updates on current Influencer Stances.\r\n\r\nSubsequent to the delivery of this first version of the site, we will begin implementing modules 2 & 3 (m2, m3), including additional signals. \r\n\r\n\r\n## Accountability\r\nIn order to remain accountable and transparent we commit to:\r\n- Publishing core calls weekly (Tuesdays)\r\n- Hosting open invitational community feedback calls (Bi-weekly)\r\n \r\n## Team Communication and Updates\r\nWe communicate our updates through the following channels: \r\n[EthSignaling Riot](https://riot.im/app/#/room/#ethsignaling:matrix.org)\r\n[Signaling Ring on Ethereum Magicians](https://ethereum-magicians.org/c/working-groups/signaling-ring) "},"comment":{"url":"https://api.github.com/repos/aragon/nest/issues/comments/409363626","html_url":"https://github.com/aragon/nest/pull/66#issuecomment-409363626","issue_url":"https://api.github.com/repos/aragon/nest/issues/66","id":409363626,"node_id":"MDEyOklzc3VlQ29tbWVudDQwOTM2MzYyNg==","user":{"login":"CLAassistant","id":11571300,"node_id":"MDQ6VXNlcjExNTcxMzAw","avatar_url":"https://avatars1.githubusercontent.com/u/11571300?v=4","gravatar_id":"","url":"https://api.github.com/users/CLAassistant","html_url":"https://github.com/CLAassistant","followers_url":"https://api.github.com/users/CLAassistant/followers","following_url":"https://api.github.com/users/CLAassistant/following{/other_user}","gists_url":"https://api.github.com/users/CLAassistant/gists{/gist_id}","starred_url":"https://api.github.com/users/CLAassistant/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CLAassistant/subscriptions","organizations_url":"https://api.github.com/users/CLAassistant/orgs","repos_url":"https://api.github.com/users/CLAassistant/repos","events_url":"https://api.github.com/users/CLAassistant/events{/privacy}","received_events_url":"https://api.github.com/users/CLAassistant/received_events","type":"User","site_admin":false},"created_at":"2018-07-31T20:51:38Z","updated_at":"2018-07-31T20:51:38Z","author_association":"NONE","body":"[![CLA assistant check](https://cla-assistant.io/pull/badge/not_signed)](https://cla-assistant.io/aragon/nest?pullRequest=66) <br/>Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our [Contributor License Agreement](https://cla-assistant.io/aragon/nest?pullRequest=66) before we can accept your contribution.<br/><sub>You have signed the CLA already but the status is still pending? Let us [recheck](https://cla-assistant.io/check/aragon/nest?pullRequest=66) it.</sub>"}}
{"actor":{"display_login":"CLAassistant"}}