|
So I will try to answer as many questions as I can.
- If you've redone the steps 2,4,5 and 7 as we've instructed but are still on the list, this is because we aren't updating that list lol (pretty obvious). We will release a list of validated addresses tomorrow at some point and you will be able to check then if you are validated (giving you about half a day to redo everything just in case you messed up).
- The meme bounty was already concluded and we have already selected 10 winners. These bounties will be distributed AFTER the airdrop.
- If you are new, yes you have to follow all the steps (no offense but if there are steps and you don't follow them then you won't get an airdrop, duuhh)
- The airdrop registration concludes on Sunday.
|
|
|
|
The remote server returned an error: (500) Internal Server Error. that is what happening can anyone have a fix on it thank you i do have balance on my address thank you.
Please read the detailed how-to, you need to choose an address to make your identity that holds some RADS balance. |
|
|
|
|
Yes you are encouraged to do the .txt file verification again but it will be pretty obvious to us which addresses are the correct ones to send to. We will do further checks using the PMs sent to us as part of the validation process.
|
|
|
|
when distribution ?
We should begin and complete distribution on the 23rd of July (this Sunday). But you can find out if some kind of table and how much each participant will have his share thanks No at the moment, we can say that about 130 people have verified successfully, we will publish a list of verified addresses closer to the end of the registration period. The airdrop is still active ? Please answer me ASAP.
Yes, please look at the countdown timer on the website. |
|
|
|
when distribution ?
We should begin and complete distribution on the 23rd of July (this Sunday). |
|
|
|
You need to send a PM guys, we were informed soliciting posts in the way we were doing is against the bitcointalk rules so we adjusted and are asking everyone to PM kekcoindev instead https://bitcointalk.org/index.php?action=profile;u=1051655 (as is clear in the instructions and the detailed guide). |
|
|
|
Yes, you have to put the public key address NOT the private key in the .txt file. If you have made an error you simply have to record the correct file (with the public address) onto the SmartChain with the identity you created earlier, if you have done everything else correctly (don't forget to send a message to kekcoindev https://bitcointalk.org/index.php?action=profile;u=1051655;sa=summary) you will receive your airdrop. Weird because it always has to be the public key. Where can we check the KEK balance once airdrop received? We don't need to know your private key (you do of course!) to send you KEKs once we launch the mainnet. When we launch the mainnet you will be able to import your private key into the wallet we will release and that will allow you to use and transact using the wallet with the airdropped amount.
NOTICE:
In some of the PMs people seem to have been putting the private key address in the .txt file. This is wrong. You need to put the public address (the normal address starting with a K) in the .txt file and record that on the SmartChain. We have no access to the private keys since they are generated on client (in your browser) and we will not be able to verify private keys!
In the medium description ( https://medium.com/@KekCore/how-to-sign-up-for-the-kekcoin-airdrop-8988dc5e6edc) it is said to put the private key in the txt file and signing it on the Radium SmartChain and register the public key under http://kekcoin.co/airdrop/. What is correct now? It is for sure the public key Yes, it seems like. They changed the decription now to public. I already signed my private key. I assume i have to repeat all steps under "The airdrop process for a synced wallet with at least 1 RADS" now. Yes, you have to put the public key address NOT the private key in the .txt file. If you have made an error you simply have to record the correct file (with the public address) onto the SmartChain with the identity you created earlier, if you have done everything else correctly (don't forget to send a message to kekcoindev https://bitcointalk.org/index.php?action=profile;u=1051655;sa=summary) you will receive your airdrop. So it's no security problem if i signed the file with my private key. I mean nobody can find it out? Except us no. It would be good security practice however to generate another public / private key pair and add the public address to the .txt file and store the private key somewhere safe (so you can claim the airdrops once we launch the mainnet). |
|
|
|
NOTICE:
In some of the PMs people seem to have been putting the private key address in the .txt file. This is wrong. You need to put the public address (the normal address starting with a K) in the .txt file and record that on the SmartChain. We have no access to the private keys since they are generated on client (in your browser) and we will not be able to verify private keys!
In the medium description ( https://medium.com/@KekCore/how-to-sign-up-for-the-kekcoin-airdrop-8988dc5e6edc) it is said to put the private key in the txt file and signing it on the Radium SmartChain and register the public key under http://kekcoin.co/airdrop/. What is correct now? It is for sure the public key Yes, it seems like. They changed the decription now to public. I already signed my private key. I assume i have to repeat all steps under "The airdrop process for a synced wallet with at least 1 RADS" now. Yes, you have to put the public key address NOT the private key in the .txt file. If you have made an error you simply have to record the correct file (with the public address) onto the SmartChain with the identity you created earlier, if you have done everything else correctly (don't forget to send a message to kekcoindev https://bitcointalk.org/index.php?action=profile;u=1051655;sa=summary) you will receive your airdrop. |
|
|
|
|
NOTICE:
In some of the PMs people seem to have been putting the private key address in the .txt file. This is wrong. You need to put the public address (the normal address starting with a K) in the .txt file and record that on the SmartChain. We have no access to the private keys since they are generated on client (in your browser) and we will not be able to verify private keys!
|
|
|
|
nice project KEK
joined airdrop yesterday
If you registered yesterday make sure you read the updated instructions concerning the PM to kekcoindev on bitcointalk  |
|
|
|
Stop the spam, your activity can only rise by 14/14 days, so there is no way you will be junior until the deadline.
Yes this is correct, we fully discourage trying to get Jr. Membership if you are not already a Jr. Member (unless your posting actual non-spam posts on other threads etc. and get to Jr. Member before the end of the airdrop). Is there a overview how much KEKs are already claimed for airdrop?
Not yet but once we've gathered at least a minimum amount we will post how many airdrops have been validated. |
|
|
|
i am also confused about their free airdrop. at one side, they are saying all coins will be distributed free and on other end, they are asking for some buying to get coins.
You need a minimal amount (less than $1 worth) of RADS to complete the procedure. If you don't like this then its up to you to register or not. |
|
|
|
ANNOUNCEMENT: We have been in contact with the bitcointalk forum admin team and the reason the original thread was deleted was that it is against the rules to require people to make “insubstantial posts”. So, we now ask that you do not post on this thread, but instead directly message kekcoindev on bitcointalk (the content of this message is irrelevant). This will allow us to confirm that your SmartChain identity and Bitcointalk forum accounts are valid. All those who have participated by verifying their identity on the SmartChain will still receive an airdrop if they direct message ‘kekcoindev’. You do NOT need to re-register an identity on the SmartChain if you have done so already. The winners of Meme Bounty #1 have already been noted and will receive an additional airdrop provided they have completed all the smart chain verify steps, and direct messaged ‘kekcoindev’. We apologise for any inconvenience! Check the full tutorial on how to participate: https://medium.com/@KekCore/how-to-sign-up-for-the-kekcoin-airdrop-8988dc5e6edckekcoindev profile link: https://bitcointalk.org/index.php?action=profile;u=1051655;sa=summary
|
|
|
|
remote server returned an error: (500) Internal Server Error
when i create identity
Make sure the address tied to your identity is credit with some RADS. We will have a more thorough How-To posted later today or tomorrow! |
|
|
|
ANNOUNCEMENT:Check the full tutorial on how to participate: https://medium.com/@KekCore/how-to-sign-up-for-the-kekcoin-airdrop-8988dc5e6edcANNOUNCEMENT:In generating the list of verified participants we noticed that many of you have inserted all-capitalised public key addresses. Both public keys and private keys are case-sensitive. After some investigation, it appears that certain web browsers (Safari & Chrome) rendered the private and public keys in all-caps. For Edge and Firefox users there should not be a problem (but you should check just in case). What this means is that participants may have to generate their keys again, so that we have valid addresses to send the airdrop to. We have produced a list of users who inputted all-capitalised addresses (or who have failed to input a correct address in some other way). https://docs.google.com/document/d/10zF2y0ySlHAYPUEgyAhSAHZQX0PcN67bT9BpKLs7Mmo/edit?usp=sharingIf you are on this list, and still wish to participate in the airdrop, you must go to http://kekcoin.co/airdrop/ and complete steps 2, 4, 5 & 7 ONLY again (this should take less than a minute). The issue has now been resolved and all future participants must proceed as usual. We will work hard to ensure all participants who have been validated will receive their airdrop. A preliminary list of users who have been verified can be found here: https://docs.google.com/document/d/1V9Jw1MthBABcVFzEUj9QLCOKjUcJ7YQLyQZIpIyI9As/edit?usp=sharingTOO LONG DIDN'T READ: Check if you are on the list of unverified addresses. If so, re-do steps 2, 4, 5 & 7 ONLY and save your new public and private keys (this should take less than a minute). NOTICE:In some of the PMs people seem to have been putting the private key address in the .txt file. This is wrong. You need to put the public address (the normal address starting with a K) in the .txt file and record that on the SmartChain. We have no access to the private keys since they are generated on client (in your browser) and we will not be able to verify private keys!
|
|
|
|
How long do you have to leave the rads in your wallet for stake to happen?
On average you get 1 stake every 24h hours for every 1,000 RADS you are staking. |
|
|
|
|
Use the /help functions and this should guide you as to how to use it.
|
|
|
|
|
For those who have PMed me I already sold my DRPs.
Thanks again for the interest.
|
|
|
|
|
Show Posts
