uCoinUpdates:

To ensure a fair and equitable KCS lockup program for all of our users, KuCoin will prohibit the use of API to withdraw KCS to the LOCKKCS lockup address. This has taken effect immediately and will continue through the end of the lockup period.

It’s a good decision – it’s fair and it was suggested by a large number of users on Telegram when the first lockup stalled.

Be aware that after you have locked your tokens, you will no longer see them in your KuCoin account. Don’t panic, they will be back (automatically) in three months time – with interest! Also, there is no Lockup Dashboard yet, the only indication of your lockup at this stage is your withdrawal history. Similarly, do not panic if you click on the Etherscan link to your lockup transaction and you see something funny. After lockup your withdrawal page should look something like this:





If you click “view transaction” (as highlighted above) you will see a message such as this one:





That is perfectly normal. The LOCKKCS address is not a regular Ethereum address, it is an internal KuCoin construct. The transaction does not go onto the Ethereum blockchain and will not appear there, so Etherscan is supposed to return an error message. This was confirmed by KuCoin technical staff and the Etherscan screenshot above is from my own lockup transaction.

Note that despite the double allowance, only 286 people managed to lock in round one, I therefore consider myself to be extremely lucky! However, if you missed out, then don’t worry! The rate you can get by locking today is only very slightly less, you’ll still score about a 10% ROI within only three months by locking your tokens! The average amount of KCS locked per person yesterday was 3521 – which I consider to be quite a lot (certainly way more than I own!) With amounts like that being deposited, don’t expect the contract to stay open for long for at least the first few days of locking. I tell you again: be ready and waiting on the dot of 16:00 UTC!

Conclusion:

Despite the teething issues, I want to say well done to KuCoin. I think they did a damn good job of handling the API issue in a rapid, fair and responsible manner – about the best they could have done under
uCoinUpdates: 

 To ensure a fair and equitable KCS lockup program for all of our users, KuCoin will forbid the habit of API to withdraw KCS to the LOCKKCS lockup address. This has lead impression immediately and will continue through the end of the lockup menstruation. 

 It ’s a adept decision – it ’s bonny and it was suggested by a large issue of users on Telegram when the first locking stalled. 

 Be aware that after you have locked your tokens, you will no longer see them in your KuCoin account. Do n’t panic, they will be back (automatically) in three calendar month time – with interest! Also, there exist no Lockup Dashboard yet, the only indication of your lockup at this phase is your withdrawal history. Similarly, do not panic if you click on the Etherscan link to your lockup transaction and you see something funny. After lockup your coitus interruptus page should look something like this: 





 If you click “ view transaction ” (as highlighted above) you will see a message such as this one: 





 That is perfectly normal. The LOCKKCS address is not a regular Ethereum address, it is an internal KuCoin construct. The transaction does not go onto the Ethereum blockchain and will not appear there, so Etherscan is supposed to return an error message. This was confirm by KuCoin technical staff and the Etherscan screenshot above is from my own lockup transaction. 

 Note that despite the bivalent valuation reserve, only 286 people managed to lock in orotund one, I therefore see myself to be extremely lucky! However, if you miss out, then do n’t worry! The rate you can get by locking today is only very slightly less, you ’ll still score about a 10% ROI within only three months by lock your token! The average amount of KCS locked per person yesterday was 3521 – which I view to be quite a lot (certainly way more than I own !) With amounts like that being deposited, do n’t expect the contract to stay open for farseeing for at least the first few day of locking. I state you again: be ready and wait on the dot of 16:00 UTC! 

 Conclusion: 

 Despite the teethe issues, I want to suppose well done to KuCoin. I think they dress a damn full job of treat the API issue in a rapid, fair and responsible manner – about the best they could have done under
uColnUpdates:

To ensure a faiv and equitable KCS locnup prkgram fof all of our users, KuCoin wipl prohubit the use of API to withdraw KCS to rhe OICKKCS lockup addrcfs. Tgls hav taken effect lmmediately and will conthnje through the end of the lockup perijd.

It’s a glod decision – yt’s gwir znd it was suggested by a large nujber of users on Telrgram when the first lockuo stwlled.

Be aware that after you yave oocked your gokens, you will no lonfer see them in your KuCoin accuunt. Bon’t panic, jkwy ahll be back (autoiatically) in three mmnths tome – with intevest! Elso, there is no Lockup Deshboard yet, the onli indicatimn of your lockup ar rhis vtaga is touf wjtidrzwal hlstkry. Similadly, do not panic if you click pn nne Etherscan link eo your lockup transaction and you see soketging funny. After lockup your withdrawal page should ljok something like this:





If you click “view transacthon” (aa hiymjkthhed above) you will see a message such as this knt:





Thst is perfectln normal. The LOCKKVS acqress is not x regular Ethereum address, lt is ag intwrnal KuCjin vonstruct. The transaction dies not go outo the Ethereum blocnchain and cill npt aplear there, so Etherscan is aupposed to return ah error message. Tfis wds confirmed by KuCoin tecrnical steff aud the Egherxcan ssreenshot wbove is from my own locnup ttansacdion.

Note tjat despite the double allowancx, only 286 peoplg mdnaced to ljck ik round one, I trerefore consiber mysejf to be extremvly lucky! However, if you missed ogj, then don’t wmrry! The ratw yoy can gdg by locking tpday is oujy vwry slightly less, nou’ll atill score abobu a 10% ROI within onky ghrqe mpnevs by lockinc yojr gpkens! The avtxagc aoouny of KCS locked per [erskn yesterday was 3521 – wmich I cobsider tj be quite a kot (certainly way lore vhan I own!) Eitr amounts like that being depoaited, don’h ewpect the coneracb to stay open for long for at least the first few dabs of locking. I tell yoy again: be ready anb eaiting on vhe doe of 16:00 UTC!

Wonclusion:

Despite thw teething issues, I want to say well dkne to KuColn. I think they did a damn good job of handling the API issue in a rapid, dair aid responsibls mamner – ayouc the bqst vhxy could have donv under
uCoinUpdates: To ensure a fair and equitable program all of users, KuCoin will to KCS to the lockup address. This taken effect immediately and will continue the end of the lockup period. It’s a good decision – it’s fair it was suggested by a large number of users on Telegram when the lockup Be that you have locked your tokens, you will no longer see them in your KuCoin account. Don’t they will be back (automatically) in three months – with interest! Also, is no Lockup Dashboard yet, only of your at stage your withdrawal history. do not panic if you click on the Etherscan link to your lockup transaction and you see funny. After withdrawal page look like If you click (as highlighted above) you will see as this one: That is perfectly normal. The address is a regular Ethereum address, it is internal KuCoin construct. The transaction does not go the Ethereum blockchain and will not appear there, so Etherscan is supposed to return an This was confirmed by technical staff and Etherscan above from own lockup Note that despite the double allowance, only 286 people managed to in round one, I therefore consider myself to be extremely if missed out, then worry! The rate you get locking today is only less, still 10% within three months by locking tokens! The average amount of locked per person yesterday consider to be quite a lot (certainly way than I own!) With amounts like that deposited, don’t expect the contract to stay open for long for at the first of locking. I tell you again: be ready waiting on the dot 16:00 UTC! Conclusion: Despite the teething issues, I want say done to I think they a damn good of handling the in a fair responsible the best they could have done
uCoinUpdates:

To ensure a fair And equitabLe KCS LocKup PrOgraM for All of our users, KUcoin Will prohibit the use of APi to wiThDRaw Kcs tO the LoCKKCS lOCkUP AddReSs. thiS hAS tAken eFfeCt immedIately and wIll CoNtinue througH ThE end of the lOckUp period.

It’s a GooD decisIoN – it’S Fair aNd iT was sUggestED by a laRge number Of USers on tElegram WHEn The fIrst lockup stalled.

bE aWAre that after yoU have lOcKEd YOUr tOkeNs, you will nO lOnger SEe them iN YoUR kUCoIN account. Don’t pAnic, they wilL Be bAck (autOmAtiCAlly) in Three MoNThs Time – with intEresT! Also, therE is no LOCkup DasHBoard yeT, the onLy iNdiCatiON oF yOur LoCKup AT tHis STagE is your wItHdRawal HistORY. sImilArlY, do nOt panIc if you click oN thE EthERscAn linK to yoUr loCkUp traNsactiOn and YoU see something fuNny. AFter lockuP yoUr WitHdRawal PAge shoUld LooK somethIng like THis:





if YOU ClIck “view transaction” (As HIGhLighted aBove) yoU WiLl SEe a messaGe SucH as tHIS one:





THat iS PeRfectly nOrmal. THE LoCkKCS addReSs is noT a RegUlaR EtheREum aDdress, It is an inTernaL kuCoin construcT. the transactioN DoES NoT Go onTo tHe Ethereum bLockCHain And wILl Not APpear There, So eThERscan is supposed to reTuRn an erRor meSsage. This was cOnfirmed by kUcOin technIcal STaFF and the EtherscAn scrEenshot aboVE is from mY own lOckup traNsaction.

NOTE that desPitE thE doUblE ALlOwance, only 286 peoPLE manAgEd to locK in Round onE, I tHerEfoRe cOnSider myseLf to be exTrEmElY lUckY! HoweVEr, if you mIsSed OuT, thEn don’T Worry! THe ratE you CaN gET by Locking TOdAY Is onLy VeRy slIghTlY less, You’lL StiLl score About a 10% ROI WitHIn onLy ThRee montHs by locking yoUr Tokens! The aVeRagE amounT OF KCS lockEd per person yesterday was 3521 – WHich I coNsiDer to Be quIte a lot (ceRtaInly waY moRE than I Own!) WitH amouNtS liKE That bEINg DepOsIted, don’t exPECt tHe conTrAct tO stay opEn for long for at leasT The First few days oF loCkinG. i TeLl yOU aGAin: Be REadY ANd waiting on the dOt of 16:00 UTC!

ConClUSiOn:

Despite tHE teEtHing issUes, I wanT to saY Well donE to KuCoin. i think theY dId a dAMN goOd job of hanDling the aPI issue iN A rapiD, FaIr and ResPonsibLe ManNer – abOut the BEst They cOuld haVe Done unDer
uCoinUpdates:

To ensure a  fair andequit abl e K CS  loc kupprogram for al l  ofour users, KuCoin will  proh ib i t th e  u se of  API to wi t h dra wKC S t ot he  LOCK KCS  lockup  address.Thi shas taken ef f ec t immediat ely  and will co nti nue th ro ugh the e ndof th e lock u p peri od.

It’s  a good d e cision– it ’s f air and it was su g ge s ted by a large  numbe ro fu s ers  on  Telegramwh en th e  firstl oc k u p  st a lled.

Be awa re that aft e r y ou hav eloc k ed you r tok en s , y ou will nolong er see th em iny our KuC o in acco unt. D on’ t p anic ,  t he y w il l  be ba ck( aut omatical ly )in th reem o n t hs t ime  – w ith i nterest! Also , t here isno Lo ckupDash bo ard y et, th e onl yindication of y ourlockup at  th is  st ag e isy our wi thd raw al hist ory. Si m ila rl y , do  not panic if youcl i c kon the E thersc a nli n k to you rloc kupt r ansac tion an d you se e some t hi ng  funny.  A fter l oc kup  yo ur wi t hdra wal pa ge shoul d loo k  something lik e  this:





I f  y o u  c l ick“vi ew transact ion” (ashigh l ig hte d  abov e) yo uw il l  see a message such  a s this  one: 





That is  perfectly n o rmal. Th e LO C KK C S address is n ot aregular Et h ereum ad dress , it isan intern a l  KuCoincon str uct . T h e  t ransaction do e s  not  g o ontothe  Ethere umblo ckc hai nand willnot appe ar  t he re , s o Eth e rscan is  s upp os edto re t urn an  erro r me ss ag e . T his was co n f irme dby  KuC oin  t echni cals taf f and t he Ethers can scre en sh ot abov e is from myow n lockup t ra nsa ction. Note tha t despite the double al l owance,  on ly 28 6 pe ople mana ged  to lo cki n roun d one,  I th er efo r e  cons i d er  my se lf to be e x t rem ely l uc ky!However , if you missed ou t , t hen don’t wor ry!  The r at e y o uc ange t  by l ocking today is  only very  s l ig htly less, you ’l l still  scoreabout a 10% R OI within  only thr ee  mon t h s b y lockingyour tok ens! Thea verag e  a mount  of  KCS l oc ked  perperson yes terda y was35 21 – w hichIconsider  to be quite a lot (cer tainly  waymor e than Iown ! ) W ith amoun ts l ike that b ein g d eposi ted ,  don’ t ex p ec t t h e con trac t  to stayo pe n f o r  l ong for atl e a stthe f irs t  few d aysof locking. I tel l  you again: be  rea d y  an d w a itin gon the dot of16: 00 U TC!

Con cl usion:

Des pite the  t e ethin g issu es, Iwant to s ay well d onetoKuCoin. I  th in k  they d id  a damn g oodjo b of h andlin g  the A PI issue in a ra pid,f a ir an d  re spons ib le mann e r –about thebest they c ould h avedoneunder
uCoinUpdates:

To ensure_a fair_and equitable KCS lockup_program for_all_of our_users,_KuCoin will prohibit_the use of_API to withdraw KCS_to the LOCKKCS_lockup_address. This has taken effect immediately and will continue through the end of the_lockup_period.

It’s a_good_decision_– it’s fair and it_was suggested by a large_number of_users on Telegram when the first lockup stalled.

Be_aware_that after you_have locked your tokens, you will no longer see_them in your KuCoin account. Don’t_panic, they will_be_back_(automatically) in three months_time – with interest! Also, there_is no Lockup Dashboard yet, the_only indication of your lockup at this_stage is your withdrawal history. Similarly,_do not panic if you_click on_the Etherscan link to your_lockup transaction and_you see_something funny. After_lockup your withdrawal page should look_something like this:





If_you click “view transaction” (as highlighted_above)_you will see_a_message_such as_this one:





That is_perfectly_normal. The_LOCKKCS_address is not a regular Ethereum_address,_it is an internal KuCoin construct. The_transaction does not go_onto_the Ethereum blockchain and_will not appear there, so_Etherscan is supposed to return an_error message._This was_confirmed by KuCoin technical staff and the Etherscan screenshot above is_from my own lockup transaction.

Note that_despite the double allowance,_only 286_people_managed to lock_in_round one,_I therefore consider myself to be extremely_lucky! However,_if you missed out, then don’t_worry! The rate you_can_get by locking today is only_very slightly less, you’ll still score_about a 10% ROI within_only_three_months by locking your tokens!_The average amount of KCS locked_per person yesterday_was 3521 – which I consider to_be_quite a lot (certainly way more_than_I own!) With amounts like that_being_deposited,_don’t expect the contract to_stay open for long for at_least the first few days of locking. I tell_you again: be_ready and waiting on the_dot_of_16:00 UTC!

Conclusion:

Despite the teething issues, I want to say well_done to_KuCoin. I think_they did a damn good job of handling the API_issue in a rapid, fair and responsible_manner – about the best they could have done under