[ANN][KEK] Kekcoin | PoS | MemeTech | Tipbot

[demyan7]

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

[pa6a24]

It is a pity that I can not participate. My account has not been properly upgraded

[vitaxa]

How many more before the start?

[malekbaba]

The airdrop is still active ? Please answer me ASAP.

[Sanglotslongs2]

Why buy rads ?

[sud]

RADs are great!

Airdrop still active AFAIK.

All hail KEK!

[Frinky]

Joined the airdrop 

[yurimir]

Hi
I am joined airdrop in radium smartchain earlier, my signed records File Kekcoin Airdrop - current Owner: yurimir , date signed: 17.07.2017 1:02:57 GMT
digital signature: e2a9b73f207694c368a446d209623e2100f6f3ee64efe5a86bd94181e0d12509
Thank you

[kekcoindev]

ANNOUNCEMENT:

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.

https://docs.google.com/document/d/17tDTgNumsgYQtTzhc4J82s5yVwFIf6_sPw-qts8g4Qg/edit?usp=sharing

If 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 and 7 ONLY again (this should take about 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.

TOO LONG DIDN'T READ:  Check if you are on the list of invalid addresses. If so, re-do steps 2, 4, 5 & 7 ONLY and save your new public and private keys (this should take about a minute).

[jukKas]

Hi!

New Airdrop coin again, sweet. I think airdrops give some boost to these coins community, since it have been flooded with almost only ICOs recently.

Will be looking forward to this and hope this is success!

[eindbaasje]

Poor schmucks like me getting in on an airdrop feels like a ticket to something greater.
I hope this project does well with cashual crypto users.

For now I see the /biz/ and /pol/ guys getting ready to meme this coin into the stratosphere.

cheers

[bitkapp]

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.

[Kvanko]

ANNOUNCEMENT:

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.

https://docs.google.com/document/d/17tDTgNumsgYQtTzhc4J82s5yVwFIf6_sPw-qts8g4Qg/edit?usp=sharing

If 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 and 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.

TOO LONG DIDN'T READ:  Check if you are on the list of invalid addresses. If so, re-do steps 2 & 7 ONLY and save your new public and private keys (this should take less than a minute).

Done. But I don't understand why we should perform only 2 & 7 steps. Maybe we should also sign our new public keys as we did with the previous ones? Because otherwise anyone can submit a new pub key to you using someone else's nickname or I don't understand something?

[oogone]

Registered for Airdrop.
Exited!

[Klangburg]

ANNOUNCEMENT:

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.

https://docs.google.com/document/d/17tDTgNumsgYQtTzhc4J82s5yVwFIf6_sPw-qts8g4Qg/edit?usp=sharing

If 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 and 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.

TOO LONG DIDN'T READ:  Check if you are on the list of invalid addresses. If so, re-do steps 2 & 7 ONLY and save your new public and private keys (this should take less than a minute).

Done. But I don't understand why we should perform only 2 & 7 steps. Maybe we should also sign our new public keys as we did with the previous ones? Because otherwise anyone can submit a new pub key to you using someone else's nickname or I don't understand something?

Yea, me too. Just curious why creation of the new file with the correct public key isn't needed.
But we're all fine if it works this way though.

[Jarod1231]

ANNOUNCEMENT:

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.

https://docs.google.com/document/d/17tDTgNumsgYQtTzhc4J82s5yVwFIf6_sPw-qts8g4Qg/edit?usp=sharing

If 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 and 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.

TOO LONG DIDN'T READ:  Check if you are on the list of invalid addresses. If so, re-do steps 2 & 7 ONLY and save your new public and private keys (this should take less than a minute).

Was on the list, just did steps 2-7 again

[prospecta]

ANNOUNCEMENT:

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.

https://docs.google.com/document/d/17tDTgNumsgYQtTzhc4J82s5yVwFIf6_sPw-qts8g4Qg/edit?usp=sharing

If 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 and 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.

TOO LONG DIDN'T READ:  Check if you are on the list of invalid addresses. If so, re-do steps 2 & 7 ONLY and save your new public and private keys (this should take less than a minute).

Have repeated steps 2 and 7 as advised.

However, just wanting to confirm that we ARE NOT required to perform steps 4/5 again? The previously signed records we have uploaded contain our old incorrect public keys and this is OK - we don't need to resign a new record with our new public key?

Thanks.

[Adriano2010]

ANNOUNCEMENT:

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.

https://docs.google.com/document/d/17tDTgNumsgYQtTzhc4J82s5yVwFIf6_sPw-qts8g4Qg/edit?usp=sharing

If 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 and 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.

TOO LONG DIDN'T READ:  Check if you are on the list of invalid addresses. If so, re-do steps 2 & 7 ONLY and save your new public and private keys (this should take less than a minute).

Have redone steps 2 and 7.

[Jarod1231]

ANNOUNCEMENT:

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.

https://docs.google.com/document/d/17tDTgNumsgYQtTzhc4J82s5yVwFIf6_sPw-qts8g4Qg/edit?usp=sharing

If 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 and 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.

TOO LONG DIDN'T READ:  Check if you are on the list of invalid addresses. If so, re-do steps 2 & 7 ONLY and save your new public and private keys (this should take less than a minute).

Have repeated steps 2 and 7 as advised.

However, just wanting to confirm that we ARE NOT required to perform steps 4/5 again? The previously signed records we have uploaded contain our old incorrect public keys and this is OK - we don't need to resign a new record with our new public key?

Thanks.

Ah shit! I didn't see that you only had to do 2 and 7, I did all steps 2-7... whoops

[tsik]

just redone steps 2 and 7 as instructed