{"action":"opened","issue":{"url":"https://api.github.com/repos/forkdelta/tokenbase/issues/495","repository_url":"https://api.github.com/repos/forkdelta/tokenbase","labels_url":"https://api.github.com/repos/forkdelta/tokenbase/issues/495/labels{/name}","comments_url":"https://api.github.com/repos/forkdelta/tokenbase/issues/495/comments","events_url":"https://api.github.com/repos/forkdelta/tokenbase/issues/495/events","html_url":"https://github.com/forkdelta/tokenbase/issues/495","id":304159481,"number":495,"title":"Formalize Listing Procedure","user":{"login":"JonathonDunford","id":5281151,"avatar_url":"https://avatars1.githubusercontent.com/u/5281151?v=4","gravatar_id":"","url":"https://api.github.com/users/JonathonDunford","html_url":"https://github.com/JonathonDunford","followers_url":"https://api.github.com/users/JonathonDunford/followers","following_url":"https://api.github.com/users/JonathonDunford/following{/other_user}","gists_url":"https://api.github.com/users/JonathonDunford/gists{/gist_id}","starred_url":"https://api.github.com/users/JonathonDunford/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JonathonDunford/subscriptions","organizations_url":"https://api.github.com/users/JonathonDunford/orgs","repos_url":"https://api.github.com/users/JonathonDunford/repos","events_url":"https://api.github.com/users/JonathonDunford/events{/privacy}","received_events_url":"https://api.github.com/users/JonathonDunford/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-11T13:44:34Z","updated_at":"2018-03-11T13:44:34Z","closed_at":null,"author_association":"OWNER","body":"This change/proposal was brought about because we needed a more thorough listing procedure that the ForkDelta team can follow on every single token submission.\r\n\r\nBenefits:\r\nThis decreases the likelihood that we will list malicious tokens.\r\nThis increases the openness of our procedure and opens it up for community feedback.\r\nThis formalizes a procedure, so people understand the process for getting listed.\r\n\r\n----\r\n\r\n## Listing Procedure For ForkDelta\r\n\r\n1. A ForkDelta team member will make sure that the listing contains all of the information outlined above.\r\n\r\n    1a) If the listing is missing information, the issue will be marked `missing information`. The team member will also comment on the issue explaining what information is missing. If an issue has been marked `missing information` for 10 days and there has been no response from the token team, the issue will be closed.\r\n\r\n2. Then, several procedures must be followed to verify the validity of this submission:\r\n\r\n    - Thorough Google search using the requested name and ticker. Is this project claiming to be something it is not? Is the website linked a duplicate of the original?\r\n    - Look at the contract creator address in Etherscan. Are they associated with any other confirmed scams? Is there suspicious activity originating from their address?\r\n    - Make sure the token has proper ERC20 or ERC223 support.\r\n    - Look for any plagiarization including, but not limited to: pictures, names, descriptions. If plagiarization is found, listing request will be denied.\r\n    - Look for misrepresentations present in token issuer's website or marketing material. This includes falsified links, false company partnerships, etc.\r\n    - Look for fake team member information.\r\n    - Look for fake physical addresses.\r\n    - Triple check that the given website / whitepaper / etc. links are official. Utilize Google and social media to search for the specific project and go to the official links. \r\n\r\n3. Once the validity of the submission has been verified, the submitted contract address must be verified on official material.\r\n\r\n4. Once the validity is confirmed and the address is verified, the ForkDelta team member should label the issue `information complete`.\r\n\r\n5. Then, the team member should leave this in the comments:\r\n> Thanks for your request, we have verified that the information provided is accurate. We'll be listing the token in the next few days, you'll receive an update when we do.\r\n\r\n6. The team member should also leave the token address and website in the comment in the following format:\r\n> 0x00000000000000000000000000000,https://ethereum.org\r\n\r\n7. After the issue is marked as complete, either @freeatnet or @JonathonDunford will look through the issue as soon as they have time. They will do __1__, ___2___, and __3__ so that we have another set of eyes fully verifying the token.\r\n\r\n8. If the token passes these checks, it will be included in a token listing pull request to https://github.com/forkdelta/tokenbase/\r\n\r\n9. That pull request must be reviewed and verified by at least one other source.\r\n\r\n10. When that pull request is accepted, it will be merged into tokenbase.\r\n\r\n11. When the pull request is merged into tokenbase, @freeatnet or @JonathonDunford will run the necessary scripts to add it into https://github.com/forkdelta/forkdelta.github.io\r\n\r\n12. They will then create another pull request to https://github.com/forkdelta/forkdelta.github.io that will require a second review of its contents.\r\n\r\n13. Once that pull request is reviewed, verified, and accepted, it can be merged into the `master` branch on https://github.com/forkdelta/forkdelta.github.io\r\n\r\n#### Tools To Help\r\n\r\nhttps://icocheck.io/\r\nhttps://www.clearify.io/"}}
{"actor":{"display_login":"JonathonDunford"}}