Pages:
Author

Topic: [ABCS] Airdrop and Bounty Campaign Standards - page 2. (Read 394 times)

member
Activity: 378
Merit: 10
December 21, 2018, 12:50:34 AM
#3
Creating standards for airdrop and bounty campaigns is a very timely and good idea. Recently, a huge number of incomprehensible projects have spawned, which gives the impression that even schoolchildren create ICOs.
member
Activity: 322
Merit: 10
I'm creative and work how you need for ETH and BTC
member
Activity: 322
Merit: 10
I'm creative and work how you need for ETH and BTC
December 19, 2018, 10:04:10 AM
#1
There are lots of airdrops and bounty campaigns that borns everyday. Some users says that more than 80% of them are scam, and others are disrespecting users. For a user's more secure participation on these campaigns, a standard is now created where airdrop/bounty campaigns can publicly show that they are committed to comply with.

Quote
Infos:

Projects can show on their campaigns a seal/badge of ABCS and their score (and if they are eligible), with link to an post containing our report of the given project. This seal can't be modified by the airdrop/bounty campaign, because it will be hosted on our site and is the user's responsibility to verify the URL of the image.

Before publishing a airdrop or bounty campaign, an project needs the following:
  • Be original
  • Website
  • Screenshots/concept images of the product
  • Profiles on most need social networks: Facebook, Twitter, Medium, YouTube, Telegram Channel, Telegram Chat, LinkedIn
  • Whitepaper
  • Onepager
  • Make clear where to post the airdrop/bounty reports: on BitcoinTalk thread or an online form
  • On report forms, warn that the forms will be closed on the date and user will be unable to report its work
  • When reviewing the time on your campaign, always use UTC timezone
  • Make explicit that rules:
Quote
You also must be a citizen or legal resident of a geographic area in which purchase, holding or use of [PROJECT] Token and tokens of its partners is not prohibited by applicable law, decree, regulation, treaty, or administrative act; not be a citizen or resident of, or located in, a geographic area that is subject to U.S. or other applicable sanctions or embargoes or be an individual, or an individual employed by or associated with an entity, identified on the U.S. Department of Commerce Denied Persons or Entity List, the U.S. Department of Treasury’s Specially Designated Nationals List, the U.S. Department of State’s Debarred Parties List or other applicable sanctions lists; not be resident or domiciled in the United States, China or the Cayman Islands; and be at least 18 years of age.
  • Instead of text, use images as the heading of each social network. Example: "PROJECT NAME | Twitter campaign"
  • Public participation sheet, containing user name, its social networks, if is approved and their tasks with their tokens (participation sheet can be individual for each social network)
  • If using different participation sheets for each social network, don't use the same title on all, but put the social network name on them. Example: "PROJECT NAME bounty participation sheet - Twitter"
  • Don't say that the payment will vary according to quality, but say what is need to achieve that quality and what will be paid according to quality

Spin-off rule: be human

  • When flagging/banning users from airdrop or bounty campaign, create a appeal form
  • If user submits an appeal form or airdrop/bounty report out of the date, your project needs to not be systematic, but human; with good support, and listen to users individually and attend them
  • Don't be happy when a user losses their tokens because of not obbeying to dates or any other reason: if you want to distribute the coins for the minor user amount as possible, better if you use stakes (divisible between any amount of users) than limiting with your project's tokens
  • Be fair with your project, but at same time, be compreensive and human to help users
  • That doesn't means you need to accept spammers/scammers/bots, but when a user is flagged as so, an appeal form needs to be accessible
  • When you reject to attend a user because of dates (and the distribution of airdrop/bounty tokens didn't happened yet, and there is not just 1 day left till the distribution) you're not being "a fair manager that is following the rules", but you're being a not-human systematic

Optional things (also worth points):
  • Professional website
  • Professional whitepaper
  • Professional BTT signature design
  • Working prototype
  • Smart contract already deployed
  • Working product
  • Profile on AngelList
  • Built-on-site airdrop
  • Built-on-site bounty campaign
  • Participation "sheet" on a GitHub issue's first comment (cannot be deleted, but edited - unlike Google Forms, its untamperable and really transparent)
  • The project is an solution/idea that is different from any other crypto project

Badge/seal:


Code:
Don't copy ABCS: it's registered on Namecoin's blockchain and Web Archive.

Soon: guide about how to participate on airdrops/bounty campaigns, and a guide to start your own crypto project.
Pages:
Jump to: