Kore Twitter Campaign [PromoPlugs] 🔹~.00015 BTC🔹6/28/17-7/05/17🔹steemCreated with Sketch.

in #cryptocurrency7 years ago

Kore has started a Twitter Bounty Campaign at Promoplugs.com/

NEW ACTIONS ADDED DAILY!

Campaign will start on 6/28/2017

Steps to Claim Bounty:

  1. Go to https://promoplugs.com/SelectedCampaign.aspx?CID=271
  2. Authorize through your Twitter Account.
  3. Enter in your KORE coin address. Bounties are paid out in KORE
  4. Click each button - Each action is automatically completed and recorded with your coin address!
  5. Check out our other giveaways at: https://promoplugs.com/OngoingCampaigns.aspx

Requirements:

  1. All actions must be completed to earn the full reward
  2. Tweets, Retweets, and Follows must remain in effect until the close of the Campaign.
  3. One Entry per action per person. PromoPlugs takes steps towards assuring dummy accounts are not used for multiple entries!
  4. You must have at least 100 followers to participate
    Bounty Rewards will be paid out at the end of the campaign

Wallet download: https://mega.co.nz/#!lBlGmL7R!UW-lzmtfHa1OeC0dn_D18jq4KXejST32oyeNApQVqOE
Linux download: https://mega.nz/#!Nk110QaT!yuf_cVCyKtXoJufgi3kJk6VcvsC4r92WP4ZMtnBrbeY
Mac download: https://mega.nz/#!LN9UTIiB!keSf4dFGeF0qlMQ5xmXNIAZIpdEl8mwTvtJLmYbLRoI
Source: https://github.com/KoreTeam/KoreCoin
Announcement Thread:https://bitcointalk.org/index.php?topic=668886.5260

****If you enter the campaign more than once, by using multiple twitter accounts or any other method, you will disqualify all assumed, earned bounty****

Sort:  

Server Error in '/' Application.

Invalid request token. - Please visit the LINQ to Twitter FAQ (at the HelpLink) for help on resolving this error.

This is the message I receive when I try to follow or retweet.

When this is fixed I would be more than happy to try again.

chrome windows 10

2 days and no response? Not good...

oh not good, less prepare

day three still no reply

I'm having trouble reproducing the error? have you attempted to enter again? It's possible high traffic was an issue? Have you tried a second device?

it has been fixed. it is working now.

its working again thank you