why the list went low in yobit no volume
The lisk that are being sold in Yobit is an IOU coin the Lisk supply from the yobit admin has all run out, i remember i saw the price went up to 0.02 so anyone who bought from that pump have lost a lot of BTC. 
Topic: [ANN][LSK] Lisk | Blockchain Application Platform for JavaScript Developers - page 1661. (Read 3074324 times)
April 22, 2016, 12:43:05 AM
April 21, 2016, 11:11:24 PM
Have there been any updates on date of launch?
September.
If you don't know dont answer. Pretty simple.
No, not in September. Right after the San Andreas earthquakes
Uh, don't say that! I live a few miles away from that fault in Southern California!! At least let me get my LISK first!! LOL
Hum, might be worth selling some of your LISKS upon launch and using the funds to get the F**K out of there..........ze big one is coming...............
You could be right. I am approx. 5 miles from that fault. But I only was able to attain 1224 LISK.
I remember quite a few "big" ones. 7.3 is the biggest I've felt in my lifetime. Kinda scary. The Northridge quake was smaller, but was quite a shaky one, too!
Come on LISK... daddy needs a new home state! LOL
April 21, 2016, 10:57:34 PM
why the lisk went low in yobit no volume
April 21, 2016, 10:51:47 PM
Have there been any updates on date of launch?
September.
If you don't know dont answer. Pretty simple.
No, not in September. Right after the San Andreas earthquakes
Uh, don't say that! I live a few miles away from that fault in Southern California!! At least let me get my LISK first!! LOL
Hum, might be worth selling some of your LISKS upon launch and using the funds to get the F**K out of there..........ze big one is coming...............
You could be right. I am approx. 5 miles from that fault. But I only was able to attain 1224 LISK.
I remember quite a few "big" ones. 7.3 is the biggest I've felt in my lifetime. Kinda scary. The Northridge quake was smaller, but was quite a shaky one, too!
Come on LISK... daddy needs a new home state! LOL
April 21, 2016, 10:49:05 PM
Have there been any updates on date of launch?
September.
If you don't know dont answer. Pretty simple.
No, not in September. Right after the San Andreas earthquakes
Uh, don't say that! I live a few miles away from that fault in Southern California!! At least let me get my LISK first!! LOL
Hum, might be worth selling some of your LISKS upon launch and using the funds to get the F**K out of there..........ze big one is coming...............
April 21, 2016, 10:43:36 PM
Have there been any updates on date of launch?
September.
If you don't know dont answer. Pretty simple.
No, not in September. Right after the San Andreas earthquakes
Uh, don't say that! I live a few miles away from that fault in Southern California!! At least let me get my LISK first!! LOL
April 21, 2016, 10:31:05 PM
Have there been any updates on date of launch?
September.
If you don't know dont answer. Pretty simple.
No, not in September. Right after the San Andreas earthquakes
April 21, 2016, 10:19:26 PM
Speaking of delegates, the community should:
1. Have a central location where delegates should report what they are doing to add value to the system.
2. Set minimum expectations of how often delegates should update the community.
The most annoying aspect of DPoS was getting updates. As a community, we should not have to track down updates. It should be the delegate's responsibilty to communicate.
1. Have a central location where delegates should report what they are doing to add value to the system.
2. Set minimum expectations of how often delegates should update the community.
The most annoying aspect of DPoS was getting updates. As a community, we should not have to track down updates. It should be the delegate's responsibilty to communicate.
but this is not something you can enforce.
Now if you got a group of people together who will only vote for people who participate in your system it would be good at convincing some to join up.
I recommend the Lisk community really taking time to study how the dynamic worked in Bitshares. When delegates refused to update the community on what they were doing, voters would put pressure on them to either show value or get voted out. For the most part, it worked as intended. Nobody rides for free.
I'm not talking about some type of central code nonsense, just a recommendation to the community to set standards and vote accordingly. I went through about about 2 years of their threads on DPoS. Lot of lessons learned, it is in our best interest in the Lisk community to learn what went right and wrong and apply the best practices.
I'm not a DPoS expert, however, from everything I read here, there's still a LOT of misunderstanding. The OMG eyez will be rich by running a delegate is missing the point. If delegate pay is high enough, it will allow those delegates to hire workers to help build the ecosystem.
I'm not saying it's not a sensible thing to do. If someone thinks it's a great idea then I think they should step up and try to get something organized. If you know you have the skills to get it going and it seems reasonable then I don't mind following it.
But It's also worries me that it gives the person setting the rules a lot of authority. Who gets to decide who makes the rules and at what point does that just turn into a centralized system?
April 21, 2016, 10:19:00 PM
what is the signature bounty?
April 21, 2016, 10:06:30 PM
Speaking of delegates, the community should:
1. Have a central location where delegates should report what they are doing to add value to the system.
2. Set minimum expectations of how often delegates should update the community.
The most annoying aspect of DPoS was getting updates. As a community, we should not have to track down updates. It should be the delegate's responsibilty to communicate.
1. Have a central location where delegates should report what they are doing to add value to the system.
2. Set minimum expectations of how often delegates should update the community.
The most annoying aspect of DPoS was getting updates. As a community, we should not have to track down updates. It should be the delegate's responsibilty to communicate.
but this is not something you can enforce.
Now if you got a group of people together who will only vote for people who participate in your system it would be good at convincing some to join up.
I recommend the Lisk community really taking time to study how the dynamic worked in Bitshares. When delegates refused to update the community on what they were doing, voters would put pressure on them to either show value or get voted out. For the most part, it worked as intended. Nobody rides for free.
I'm not talking about some type of central code nonsense, just a recommendation to the community to set standards and vote accordingly. I went through about about 2 years of their threads on DPoS. Lot of lessons learned, it is in our best interest in the Lisk community to learn what went right and wrong and apply the best practices.
I'm not a DPoS expert, however, from everything I read here, there's still a LOT of misunderstanding. The OMG eyez will be rich by running a delegate is missing the point. If delegate pay is high enough, it will allow those delegates to hire workers to help build the ecosystem.
April 21, 2016, 09:58:50 PM
Have there been any updates on date of launch?
September.
If you don't know dont answer. Pretty simple.
April 21, 2016, 09:52:54 PM
I also vote for a 1001 delegate.. Much more for everyone 
and better safety for the whole network
and better safety for the whole network April 21, 2016, 09:19:21 PM
Hi guys! how and when to claim the signature btt bounty? thanks!
Send PM to Bigcabrito with your validated LISK address.
If you don't have one, you should wait the mainnet launch.
BCT Signature Bounty Rewards
THIS BOUNTY CAMPAIGN HAS ENDED!
THIS BOUNTY CAMPAIGN HAS ENDED!
Hey Guys,
The BCT Signature Campaign Bounty has been updated as there were duplicates in the data. Minor mistake, it's been fixed. Good news is, if you participated in the BCT Signature Campaign Bounty, you will now receive a bit more LISK!
Here are the new numbers:- If you had the signature since Week One, you will receive a total of 1011 LISK
- If you had the signature since Week Two, you will receive a total of 809 LISK
- If you had the signature since Week Three, you will receive a total of 607 LISK
- If you had the signature since Week Four, you will receive a total of 404 LISK
- If you had the signature since Week Five, you will receive a total of 202 LISK
Remember, if you participated in the ICO and have validated your Lisk Address, you may send me a PM (if you are on the list) with your address to receive priority on collecting this bounty after the launch.
Same procedure with the Facebook bounties, as I h ave begun collecting addresses through Facebook. Twitter and Newsletter will soon begin.
Thanks for reading! And sorry for the confusion. (Thank you bob75coin for noticing this
)Joel
April 21, 2016, 08:57:16 PM
exchange on yobit 
and deposit off what the..... 
and deposit off what the..... Mainnet has not launched. There is no where to withdraw to/deposit from until that happens. Yobit is only IOU tokens
April 21, 2016, 08:51:07 PM
exchange on yobit and deposit off what the.....
and deposit off what the..... April 21, 2016, 08:47:48 PM
Hi guys! how and when to claim the signature btt bounty? thanks!
If you participated in the signature campaign and have invested in the ICO, you may PM LiskHQ your LISK address and he will record it down for you. If you didn't participate in the ICO, then you have to wait until LISK launches.
April 21, 2016, 08:35:42 PM
Hi guys! how and when to claim the signature btt bounty? thanks!
April 21, 2016, 08:34:50 PM
Have there been any updates on date of launch?
September.
April 21, 2016, 08:16:13 PM
Have there been any updates on date of launch?
April 21, 2016, 07:56:51 PM
Speaking of delegates, the community should:
1. Have a central location where delegates should report what they are doing to add value to the system.
2. Set minimum expectations of how often delegates should update the community.
The most annoying aspect of DPoS was getting updates. As a community, we should not have to track down updates. It should be the delegate's responsibilty to communicate.
1. Have a central location where delegates should report what they are doing to add value to the system.
2. Set minimum expectations of how often delegates should update the community.
The most annoying aspect of DPoS was getting updates. As a community, we should not have to track down updates. It should be the delegate's responsibilty to communicate.
Why?
Jump to: