[ANN][LSK] Lisk | Blockchain Application Platform for JavaScript Developers

[Its About Sharing]

Huge news




A very well known Developer in the JavaScript community is building Dapps for Lisk.

https://twitter.com/boxxa


 

Wow, really nice start. This again is the thing - So many Javascript developers out there. And those looking to create a potentially money making dapp now have a platform out there in LISK in which to do so and do so VERY VERY quickly.

Are there any downfalls in Javascript instead of a proprietary language like Ethereum is using? I saw something about memory usage but I'm not familiar here.

[LiskHQ]

As a non-technical LISK ICO holder I am struggling to understand the voting process.  I've read most of these posts and Section B in the handbook and it's not entirely clear.  In this thread I see a lot of confusion and questions.  Part of the confusion is that the term "vote" is overloaded - seems to define both a measure of support and the act of giving support to a max of 33 delegates.  Hence a "vote" can refer to both 0.00000001 Lisk and 1 Lisk.

It would be good if Section B was expanded to further explain
1) the process when a Lisk holder makes a vote (i.e. spends 1 Lisk) and how their holding affects the delegate approvals.
If a user makes a vote (spends 1 LISK) all the delegates he voted for receive the number of votes equally to the voters amount of LISK. E.g. if you own 1M LISK he will at the beginning get about 1% approval.

2) when do approvals change and when does the list of active delegates change
Every round they change, so about every 17 minutes.

3) when and how uptime changes the active delegate rankings
AFAIK the uptime is also updated every 17 minutes. However, the uptime is independent of the delegate rank. Only the amount the approval matters.

In the meantime could someone kindly answer the following:  There are two LISK holders: HolderA (10 Lisk) and HolderB (200 Lisk) and 200 Delegates: Delegate1 ... Delegate200.  
1) Presumably if HolderA votes for only Delegate1 then Delegate1 gets 1,000,000,000 votes, however, if HolderA votes for Delegate1 and Delegate2 then they both only get 500,000,000 votes?
Right now both receive 1,000,000,000 votes.

2) Presumably a holder can vote more than once a delegate round including withdrawing votes?
The vote always only has the power of your current LISK balance. You can't vote several times for 1 delegate, unless you remove your vote from him before.

3) Where are the approvals stored? In the blockchain?
Yes.

4) Presumably the block forger maintains the active delegate list?
What do you mean?

[bluedude]

As a non-technical LISK ICO holder I am struggling to understand the voting process.  I've read most of these posts and Section B in the handbook and it's not entirely clear.  In this thread I see a lot of confusion and questions.  Part of the confusion is that the term "vote" is overloaded - seems to define both a measure of support and the act of giving support to a max of 33 delegates.  Hence a "vote" can refer to both 0.00000001 Lisk and 1 Lisk.

It would be good if Section B was expanded to further explain
1) the process when a Lisk holder makes a vote (i.e. spends 1 Lisk) and how their holding affects the delegate approvals.
If a user makes a vote (spends 1 LISK) all the delegates he voted for receive the number of votes equally to the voters amount of LISK. E.g. if you own 1M LISK he will at the beginning get about 1% approval.

2) when do approvals change and when does the list of active delegates change
Every round they change, so about every 17 minutes.

3) when and how uptime changes the active delegate rankings
AFAIK the uptime is also updated every 17 minutes. However, the uptime is independent of the delegate rank. Only the amount the approval matters.

In the meantime could someone kindly answer the following:  There are two LISK holders: HolderA (10 Lisk) and HolderB (200 Lisk) and 200 Delegates: Delegate1 ... Delegate200.  
1) Presumably if HolderA votes for only Delegate1 then Delegate1 gets 1,000,000,000 votes, however, if HolderA votes for Delegate1 and Delegate2 then they both only get 500,000,000 votes?
Right now both receive 1,000,000,000 votes.

2) Presumably a holder can vote more than once a delegate round including withdrawing votes?
The vote always only has the power of your current LISK balance. You can't vote several times for 1 delegate, unless you remove your vote from him before.

3) Where are the approvals stored? In the blockchain?
Yes.

4) Presumably the block forger maintains the active delegate list?
What do you mean?

Thanks for the answers. Is much more clear to me now.

[ottobene]

Alternative Lisk Logo Ideas on forum.lisk.io by cryptoartist

Don't hesitate to share ideas there

[someonesomeone]

Wrong. The amount raised is for Lisk development and not Crypti...

LISK AND CRYPTI WILL GROW TOGETHER

New Link for the CryptiWallet is

https://cryptiwallet.lisk.io/


LiskHQ (Max) is trying to find Devs for Crypti

(source) https://bitcointalk.org/index.php?topic=654463.12260

I'm not trying to find developers. Just stated if someone wants to "take over" Crypti development, he should get in contact with me.

If I had the coding capabilities to do so, I would. But I'm sure developers will jump on it once they can use the Lisk development to improve Crypti.

7 million dollar for lisk development and Crypti improvement

[MaGNeT]

Wrong. The amount raised is for Lisk development and not Crypti...

It is.

But I'm sure a new influx of developers will start using the Lisk codebase to update Crypti to the same levels.
Probably they're already buying up XCR, why else did the price rise op from 1300 Satoshi's to what it is now?

[ttookk]

(snip)

In the meantime could someone kindly answer the following:  There are two LISK holders: HolderA (10 Lisk) and HolderB (200 Lisk) and 200 Delegates: Delegate1 ... Delegate200.  
1) Presumably if HolderA votes for only Delegate1 then Delegate1 gets 1,000,000,000 votes, however, if HolderA votes for Delegate1 and Delegate2 then they both only get 500,000,000 votes?

(snip)

As stated before, in the scenario mentioned, Delegates1 and 2 both get 1,000,000,000 votes. Which I don't like, because I think it scales badly. In the scenario, HolderB is in absolute control over who gets elected and who doesn't. If they would have to spread out their votes, HolderA could at least vote for some Delegates…

Ok, I did the math and apparently, I am stupid
As long as your voting power is evenly distributed, there is no difference between the two systems.
My bad.

[BoldNinja]

Crypti and Lisk can coexist and collaborate which is a good thing imo!

[tempus]

Crypti and Lisk can coexist and collaborate which is a good thing imo!

After the ICO the Lisk-team holds about 80% of the total supply of Crypti if I remember it correctly. So, I would say Crypti is done because it's centralized now.

[hmachado]

Wrong. The amount raised is for Lisk development and not Crypti...

It is.

But I'm sure a new influx of developers will start using the Lisk codebase to update Crypti to the same levels.
Probably they're already buying up XCR, why else did the price rise op from 1300 Satoshi's to what it is now?

Well, considering the REALLY low volume i think the price flutuation doesnt mean anything at all.
Its moving like 10 btc/day, 1 random guy alone could make the price go up or down and wouldnt even need to put much effort into it.

[Racer8]

As a non-technical LISK ICO holder I am struggling to understand the voting process.  I've read most of these posts and Section B in the handbook and it's not entirely clear.  In this thread I see a lot of confusion and questions.  Part of the confusion is that the term "vote" is overloaded - seems to define both a measure of support and the act of giving support to a max of 33 delegates.  Hence a "vote" can refer to both 0.00000001 Lisk and 1 Lisk.

It would be good if Section B was expanded to further explain
1) the process when a Lisk holder makes a vote (i.e. spends 1 Lisk) and how their holding affects the delegate approvals.
If a user makes a vote (spends 1 LISK) all the delegates he voted for receive the number of votes equally to the voters amount of LISK. E.g. if you own 1M LISK he will at the beginning get about 1% approval.

2) when do approvals change and when does the list of active delegates change
Every round they change, so about every 17 minutes.

3) when and how uptime changes the active delegate rankings
AFAIK the uptime is also updated every 17 minutes. However, the uptime is independent of the delegate rank. Only the amount the approval matters.

In the meantime could someone kindly answer the following:  There are two LISK holders: HolderA (10 Lisk) and HolderB (200 Lisk) and 200 Delegates: Delegate1 ... Delegate200.  
1) Presumably if HolderA votes for only Delegate1 then Delegate1 gets 1,000,000,000 votes, however, if HolderA votes for Delegate1 and Delegate2 then they both only get 500,000,000 votes?
Right now both receive 1,000,000,000 votes.

2) Presumably a holder can vote more than once a delegate round including withdrawing votes?
The vote always only has the power of your current LISK balance. You can't vote several times for 1 delegate, unless you remove your vote from him before.

3) Where are the approvals stored? In the blockchain?
Yes.

4) Presumably the block forger maintains the active delegate list?
What do you mean?

Thanks for the answers - just some further clarification:

"3) when and how uptime changes the active delegate rankings
AFAIK the uptime is also updated every 17 minutes. However, the uptime is independent of the delegate rank. Only the amount the approval matters."

So if your uptime is 1% and your approval is greater than delegate 101 then you remain an active delegate?  If so what is the point of uptime?


"4) Presumably the block forger maintains the active delegate list?
What do you mean?"

What mechanism changes the active delegate list?

[LiskHQ]

So if your uptime is 1% and your approval is greater than delegate 101 then you remain an active delegate?  If so what is the point of uptime?
Yes. The uptime is just a reference how good a delegate's node is performing. So if you see a node is performing really bad, you simply remove your votes from the delegate. So it isn't amongst the top 101.

Presumably the block forger maintains the active delegate list?
What mechanism changes the active delegate list?
The approval. Every round (~17 minutes) Lisk checks the approval rates and re-arranges all delegates automatically.

[pinkman12345]

Hypothetically.. if I own 2 million lisk. And I create 33 separate accounts with nodes off 1 computer. Then vote for my nodes.. then I am going to secure all of them with the weight of my vote. I'm not a pessimist but I doubt even 60% of people in the ICO will vote.

If I am right and this can happen.. it almost definitely will happen because of greed. But it doesn't help secure the network. Please revise your plans on delegates and come up with a better formula. I said it before about having a calculation involved when it comes to voting.

[superlegitaccount]

Wonder if this will take off.

[Gr33nDrag0n]

I'm curently finalizing the testnet node security.
Do you want the node to be accesible from TOR ?
I ask because on some of my servers I use dynamic autoban of TOR exit nodes to prevent DDOS by TOR.
I think that active delegate node won't be using TOR, it would be too slow, so I don't see a problem with active delegate blocking those IP. Do you ?

[ThradEO]

Honestly guys, this delegate idea is the worst thing I have ever seen on this forum. If you think that giving plenty of money will motivate people to secure the network, you are already screwed. How could you seriously think that this is not a centralized system? God, I really thought that the Lisk concept was good at the beginning (I took part of the ICO) but now I see myself dump this already dead coin during the first bump.

[MaGNeT]

Honestly guys, this delegate idea is the worst thing I have ever seen on this forum. If you think that giving plenty of money will motivate people to secure the network, you are already screwed. How could you seriously think that this is not a centralized system? God, I really thought that the Lisk concept was good at the beginning (I took part of the ICO) but now I see myself dump this already dead coin during the first bump.

Since this is your first post on this forum, I'm taking your word for it 

[ThradEO]

Honestly guys, this delegate idea is the worst thing I have ever seen on this forum. If you think that giving plenty of money will motivate people to secure the network, you are already screwed. How could you seriously think that this is not a centralized system? God, I really thought that the Lisk concept was good at the beginning (I took part of the ICO) but now I see myself dump this already dead coin during the first bump.

Since this is your first post on this forum, I'm taking your word for it 

I just created my account to post this. Not posting 10 times a day does not mean you are not part of the altcoin ecosystem, anyway I am not here to justify the validity of my opinion (basing yours on the number of posts is at least less valid though). Still, I though Lisk had a great potential but now with this shitty idea, I give it less less than 2 years to disappear.

[Arrakeen]

Anyone have a guess on when we can actually hold the LISK we bought? Instead of having it sit on someone else's server?

[cannabanana]

Anyone have a guess on when we can actually hold the LISK we bought? Instead of having it sit on someone else's server?

Dude, we fucking answer this question like every single page.  Anyone have a guess when idiots like you will read a few pages back instead of asking this very question every single page?