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

[theboccet]

Big ICO maybe means good features coming!
So please if any can vote my delegate : Boccet 6500625890907671168L
Also followed on twitter

[1714745215]

1714745215

[1714745215]

1714745215

[1714745215]

1714745215

[bitcoinuserz]

I tried sending crypti, but it says :
Recipient does not match exchange address
what is wrong??

[theboccet]

I tried sending crypti, but it says :
Recipient does not match exchange address
what is wrong??

If you was trying to send me lisk or to vote so the address is 6500625890907671168L
to vote you must search manually the delegates in the list.
I already sent 2 transactions,one for forging and another for auto vote and all was ok
if you want,pm me your address,i'll test sending to you.
hope it helps

[houlala1]

 Proof of Belugia Caviar ?

[theboccet]

Proof of Belugia Caviar ?

Beluga Caviar 

[bitcoinuserz]

I tried sending crypti, but it says :
Recipient does not match exchange address
what is wrong??

If you was trying to send me lisk or to vote so the address is 6500625890907671168L
to vote you must search manually the delegates in the list.
I already sent 2 transactions,one for forging and another for auto vote and all was ok
if you want,pm me your address,i'll test sending to you.
hope it helps

W...What? your talking about the ICO of lisk right? Do I need to tweak the delegates just to participate in ICO?

[cannabanana]

I tried sending crypti, but it says :
Recipient does not match exchange address
what is wrong??

If you was trying to send me lisk or to vote so the address is 6500625890907671168L
to vote you must search manually the delegates in the list.
I already sent 2 transactions,one for forging and another for auto vote and all was ok
if you want,pm me your address,i'll test sending to you.
hope it helps

W...What? your talking about the ICO of lisk right? Do I need to tweak the delegates just to participate in ICO?

It's over 9000!!!!1!!

[Bigcabrito]

I tried sending crypti, but it says :
Recipient does not match exchange address
what is wrong??

If you was trying to send me lisk or to vote so the address is 6500625890907671168L
to vote you must search manually the delegates in the list.
I already sent 2 transactions,one for forging and another for auto vote and all was ok
if you want,pm me your address,i'll test sending to you.
hope it helps

W...What? your talking about the ICO of lisk right? Do I need to tweak the delegates just to participate in ICO?

Network is not live. There is a current test network running but it's for, well, testing

[theboccet]

I tried sending crypti, but it says :
Recipient does not match exchange address
what is wrong??

If you was trying to send me lisk or to vote so the address is 6500625890907671168L
to vote you must search manually the delegates in the list.
I already sent 2 transactions,one for forging and another for auto vote and all was ok
if you want,pm me your address,i'll test sending to you.
hope it helps

W...What? your talking about the ICO of lisk right? Do I need to tweak the delegates just to participate in ICO?

nope."Delegates" are equal to "mining" in usual crypto.like "forging" in NXT.
the ICO is ICO,it's about buying LISK with BTC.
"Delegates" must be approved buy admins after the users votes like "workers" in bitshares network
it's in test phase for now

[FNetV1]

Can I have more than one delegates running under the same IP address?

Example:  I have 6 computers at home that I am not using that I am more than willing to setup as delegates for the main net Lisk network.

Is it true that Admin will have to approve a delegate after getting voted in by the community?  If so, will Admin have trouble approving a delegate from the same IP address as another delegate that got already approved and is already voted in by the community under the same IP address?

Does Admin have any objections in regards to a user running, say 20 delegates all in his house under the same IP address?

Are there any limitations in regards to users running more than 1 delegates on his/her house besides the 100 Lisk fee.

In regards to the 100 Lisk fee, what happens if a user decides to stop being a delegate, will this user get their 100 Lisk fee returned? 

Will the 100 Lisk fee qualify the user to be a delegate forever?

[Bigcabrito]

Can I have more than one delegates running under the same IP address?

Example:  I have 6 computers at home that I am not using that I am more than willing to setup as delegates for the main net Lisk network.

Is it true that Admin will have to approve a delegate after getting voted in by the community?  If so, will Admin have trouble approving a delegate from the same IP address as another delegate that got already approved and is already voted in by the community under the same IP address?

An admin who approves or disapproves a delegate does not exist. You have to get voted into the 101 delegate list by the owners of Lisk. There is no limit on how many nodes you can have up at one time, just make sure to have excellent uptime and get enough people to vote for you. There are 100,000,000 million votes out there (1 vote per Lisk, e.g. if you hold 1 million Lisk in a wallet your vote counts as 1% of the total 100% possible).

Does Admin have any objections in regards to a user running, say 20 delegates all in his house under the same IP address?

Nope, there aren't any rules stating one delegate per person. You decide how many nodes you want to have and the voters (the community, Lisk holders) decide whether they get into the 101 delegates.

Are there any limitations in regards to users running more than 1 delegates on his/her house besides the 100 Lisk fee.

No.

In regards to the 100 Lisk fee, what happens if a user decides to stop being a delegate, will this user get their 100 Lisk fee returned?  

Will the 100 Lisk fee qualify the user to be a delegate forever?

The fee makes you a delegate forever, but, it doesn't guarantee you will be in the top 101 delegates (you will be a standby delegate until people vote you up). You do not get your fee returned.

[Pitchblackroom]

I tried sending crypti, but it says :
Recipient does not match exchange address
what is wrong??

If you was trying to send me lisk or to vote so the address is 6500625890907671168L
to vote you must search manually the delegates in the list.
I already sent 2 transactions,one for forging and another for auto vote and all was ok
if you want,pm me your address,i'll test sending to you.
hope it helps

W...What? your talking about the ICO of lisk right? Do I need to tweak the delegates just to participate in ICO?

Network is not live. There is a current test network running but it's for, well, testing

I believe the actual network launches after the ICO

[punkrock]

Sure. Everything is currently running on testnet. All delegates will be removed before the mainnet goes online. So it's nothing more than "playing around" if someone asks for votes for his testnet-delegate-account.

[CryptoMaik]

The ico goes sky high. At the moment 1300btc+

[FNetV1]

In regards to running a delegate, lets say I want my delegate(s) to have a 100% uptime status, if I have to take down a deletage to update its corresponding software will that affect my uptime "status", or will there be fair grace period allowing me sufficient time to update my core software without loosing my 100 % uptime status.

Also, lets assume that I experience a brief downtime from my ISP which would affect my uptime % and get reduced from 100% down to maybe 99.x%, assuming no further downtime occurs, will my uptime status get reset back to 100%?  If so, in how many days?

[Bigcabrito]

In regards to running a delegate, lets say I want my delegate(s) to have a 100% uptime status, if I have to take down a deletage to update its corresponding software will that affect my uptime "status", or will there be fair grace period allowing me sufficient time to update my core software without loosing my 100 % uptime status.

Also, lets assume that I experience a brief downtime from my ISP which would affect my uptime % and get reduced from 100% down to maybe 99.x%, assuming no further downtime occurs, will my uptime status get reset back to 100%?  If so, in how many days?

If you take down a delegate, uptime % will decrease. So to answer, yes it will affect your uptime "status". As far as I know there is no grace period.

Same thing with your ISP issue, your uptime % will suffer and it does not reset. The best you can do is keep it up as much as possible and try to reach that 99.9%

https://lisk.io/documentation?i=lisk-whitepaper/LiskWhitepaper#3-consensus

[FNetV1]

In regards to running a delegate, lets say I want my delegate(s) to have a 100% uptime status, if I have to take down a deletage to update its corresponding software will that affect my uptime "status", or will there be fair grace period allowing me sufficient time to update my core software without loosing my 100 % uptime status.

Also, lets assume that I experience a brief downtime from my ISP which would affect my uptime % and get reduced from 100% down to maybe 99.x%, assuming no further downtime occurs, will my uptime status get reset back to 100%?  If so, in how many days?

If you take down a delegate, uptime % will decrease. So to answer, yes it will affect your uptime "status". As far as I know there is no grace period.

Same thing with your ISP issue, your uptime % will suffer and it does not reset. The best you can do is keep it up as much as possible and try to reach that 99.9%

https://lisk.io/documentation?i=lisk-whitepaper/LiskWhitepaper#3-consensus

What? No grace period and it doesn't reset?  You are making me nervous now specially since 2 days ago my Verizon FiOS connection decided to take a 6 hours "vacation" after 1:30AM due to a storm.  So you are telling me that if my uptime status were to change from 100% to 99 or 98% that I will never have a 100% uptime status for this delegate EVER AGAIN? I think that it should reset every months to make it fair.

Also, I see users very hesistant to taking down their servers to update the software if it means that they get to perpetually lose their 100% uptime status.  So, if Admin decides to perform a mandatory update for the software the delegates are running, that means that users lose their 100% status.

Also, once I loose my 100% status, even at no fault to me (say there was a mandatory Lisk software update that I HAVE to install), so I lose 100% status forever, and a new user that comes online and is 100% uptime will get the favor of the community, so all those Raspbery Pi 2 computers I would be running would be a waste.

Question: Would having a redundant internet connection in case if the first one fail cause me to still loose the 100% uptime status?  Example: My Fios Connection goes down, therefore My backup Cable ISP connection kicks in automatically maintaining my computers up, since this switch over took lets say 5 seconds to complete because I would have a watch dog monitoring in realtime, would that still cause me to loose my 100% uptime status?  The only issue I could see with this is all of a sudden running under a new public IP address.

Note for admin: If there is not any provisions for "forgiving" a delegate for briefly going down, then you should implement one, implement a 30 days reset, that way everyone that wants to be seen as 100% uptime always gets that change of showing responsibility.

[MalReynolds]

In regards to running a delegate, lets say I want my delegate(s) to have a 100% uptime status, if I have to take down a deletage to update its corresponding software will that affect my uptime "status", or will there be fair grace period allowing me sufficient time to update my core software without loosing my 100 % uptime status.

Also, lets assume that I experience a brief downtime from my ISP which would affect my uptime % and get reduced from 100% down to maybe 99.x%, assuming no further downtime occurs, will my uptime status get reset back to 100%?  If so, in how many days?

If you take down a delegate, uptime % will decrease. So to answer, yes it will affect your uptime "status". As far as I know there is no grace period.

Same thing with your ISP issue, your uptime % will suffer and it does not reset. The best you can do is keep it up as much as possible and try to reach that 99.9%

https://lisk.io/documentation?i=lisk-whitepaper/LiskWhitepaper#3-consensus

What? No grace period and it doesn't reset?  You are making me nervous now specially since 2 days ago my Verizon FiOS connection decided to take a 6 hours "vacation" after 1:30AM due to a storm.  So you are telling me that if my uptime status were to change from 100% to 99 or 98% that I will never have a 100% uptime status for this delegate EVER AGAIN? I think that it should reset every months to make it fair.

Also, I see users very hesistant to taking down their servers to update the software if it means that they get to perpetually lose their 100% uptime status.  So, if Admin decides to perform a mandatory update for the software the delegates are running, that means that users lose their 100% status.

Also, once I loose my 100% status, even at no fault to me (say there was a mandatory Lisk software update that I HAVE to install), so I lose 100% status forever, and a new user that comes online and is 100% uptime will get the favor of the community, so all those Raspbery Pi 2 computers I would be running would be a waste.

Question: Would having a redundant internet connection in case if the first one fail cause me to still loose the 100% uptime status?  Example: My Fios Connection goes down, therefore My backup Cable ISP connection kicks in automatically maintaining my computers up, since this switch over took lets say 5 seconds to complete because I would have a watch dog monitoring in realtime, would that still cause me to loose my 100% uptime status?  The only issue I could see with this is all of a sudden running under a new public IP address.

Note for admin: If there is not any provisions for "forgiving" a delegate for briefly going down, then you should implement one, implement a 30 days reset, that way everyone that wants to be seen as 100% uptime always gets that change of showing responsibility.

Dude, relax.  NOBODY maintains 100% uptime, not at Crypti, not at Lisk, not anybody.  

It's a lot more important to participate routinely in the community so your name is known and people have some trust in you and will recognize your name on a ballot.  Having a single perfect number, especially one that gets reset every so often, is a poor way to choose somebody.  Plus, poor runtime numbers are how you decide to vote somebody DOWN and OUT of the top 101 delegates.  You certainly don't want to hide the facts about a person's runtime with a periodic reset.  Also, a poor active delegate gets replaced by a standby delegate with 0% uptime, so what good is voting by uptime numbers at that point?

Being a Delegated Proof of Stake (DPoS) delegate is a lot more about campaigning under your own name than it is focusing on one number.

[FNetV1]

In regards to running a delegate, lets say I want my delegate(s) to have a 100% uptime status, if I have to take down a deletage to update its corresponding software will that affect my uptime "status", or will there be fair grace period allowing me sufficient time to update my core software without loosing my 100 % uptime status.

Also, lets assume that I experience a brief downtime from my ISP which would affect my uptime % and get reduced from 100% down to maybe 99.x%, assuming no further downtime occurs, will my uptime status get reset back to 100%?  If so, in how many days?

If you take down a delegate, uptime % will decrease. So to answer, yes it will affect your uptime "status". As far as I know there is no grace period.

Same thing with your ISP issue, your uptime % will suffer and it does not reset. The best you can do is keep it up as much as possible and try to reach that 99.9%

https://lisk.io/documentation?i=lisk-whitepaper/LiskWhitepaper#3-consensus

What? No grace period and it doesn't reset?  You are making me nervous now specially since 2 days ago my Verizon FiOS connection decided to take a 6 hours "vacation" after 1:30AM due to a storm.  So you are telling me that if my uptime status were to change from 100% to 99 or 98% that I will never have a 100% uptime status for this delegate EVER AGAIN? I think that it should reset every months to make it fair.

Also, I see users very hesistant to taking down their servers to update the software if it means that they get to perpetually lose their 100% uptime status.  So, if Admin decides to perform a mandatory update for the software the delegates are running, that means that users lose their 100% status.

Also, once I loose my 100% status, even at no fault to me (say there was a mandatory Lisk software update that I HAVE to install), so I lose 100% status forever, and a new user that comes online and is 100% uptime will get the favor of the community, so all those Raspbery Pi 2 computers I would be running would be a waste.

Question: Would having a redundant internet connection in case if the first one fail cause me to still loose the 100% uptime status?  Example: My Fios Connection goes down, therefore My backup Cable ISP connection kicks in automatically maintaining my computers up, since this switch over took lets say 5 seconds to complete because I would have a watch dog monitoring in realtime, would that still cause me to loose my 100% uptime status?  The only issue I could see with this is all of a sudden running under a new public IP address.

Note for admin: If there is not any provisions for "forgiving" a delegate for briefly going down, then you should implement one, implement a 30 days reset, that way everyone that wants to be seen as 100% uptime always gets that change of showing responsibility.

Dude, relax.  NOBODY maintains 100% uptime, not at Crypti, not at Lisk, not anybody.  

It's a lot more important to participate routinely in the community so your name is known and people have some trust in you and will recognize your name on a ballot.  Having a single perfect number, especially one that gets reset every so often, is a poor way to choose somebody.  Plus, poor runtime numbers are how you decide to vote somebody DOWN and OUT of the top 101 delegates.  You certainly don't want to hide the facts about a person's runtime with a periodic reset.  Also, a poor active delegate gets replaced by a standby delegate with 0% uptime, so what good is voting by uptime numbers at that point?

Being a Delegated Proof of Stake (DPoS) delegate is a lot more about campaigning under your own name than it is focusing on one number.

Ok, I am beginning to understand how this delegate stuff more or less is going to be working.

So, it would be a bad idea for a person to create say 20 different names for 20 different delegates as the hassle wont be worth it to going to the chat rooms or forums to present all these 20 different names as different persons to vote for them (too much work).

But, if the same person decides to run 20 delegates, all under the same name then the community would only vote for one of them, and not for all of them, even if the campaign happens to be a nice one because I assume the community doesn't want one single person running like 20 delegates.

Just like Bitcoin mining where we all went crazy and purchased at first lots of GPU's, then LOTS of USB Block Erupters (because with just one we weren't making enough money), I would want to be able to run more than one delegate to make more money and also hope that all of my delegates gets voted in the the 101 spots.  IF I show up to the community and I announce that I have 20 servers up and ready to delegate, would the community be fine with it?

Also, do we get some type of recompense for being a "stand-by" delegate?

Are Stand-by delegates immediately summoned up for "work" as active delegates if any of the 101 delegates were to become suddenly offline? Or is there a time frame that the community waits before calling that node "dead" and putting the stand-by delegate to work (active).

[MalReynolds]

Dude, relax.  NOBODY maintains 100% uptime, not at Crypti, not at Lisk, not anybody.  

It's a lot more important to participate routinely in the community so your name is known and people have some trust in you and will recognize your name on a ballot.  Having a single perfect number, especially one that gets reset every so often, is a poor way to choose somebody.  Plus, poor runtime numbers are how you decide to vote somebody DOWN and OUT of the top 101 delegates.  You certainly don't want to hide the facts about a person's runtime with a periodic reset.  Also, a poor active delegate gets replaced by a standby delegate with 0% uptime, so what good is voting by uptime numbers at that point?

Being a Delegated Proof of Stake (DPoS) delegate is a lot more about campaigning under your own good name than it is focusing on one number.

Ok, I am beginning to understand how this delegate stuff more or less is going to be working.

So, it would be a bad idea for a person to create say 20 different names for 20 different delegates as the hassle wont be worth it to going to the chat rooms or forums to present all these 20 different names as different persons to vote for them (too much work).

But, if the same person decides to run 20 delegates, all under the same name then the community would only vote for one of them, and not for all of them, even if the campaign happens to be a nice one because I assume the community doesn't want one single person running like 20 delegates.

Just like Bitcoin mining where we all went crazy and purchased at first lots of GPU's, then LOTS of USB Block Erupters (because with just one we weren't making enough money), I would want to be able to run more than one delegate to make more money and also hope that all of my delegates gets voted in the the 101 spots.  IF I show up to the community and I announce that I have 20 servers up and ready to delegate, would the community be fine with it?

Also, do we get some type of recompense for being a "stand-by" delegate?

Are Stand-by delegates immediately summoned up for "work" as active delegates if any of the 101 delegates were to become suddenly offline? Or is there a time frame that the community waits before calling that node "dead" and putting the stand-by delegate to work (active).

Lisk is most secure when 101 individuals are running 101 separate Active Delegate nodes and this should be our goal.  You don't want 5 people running 20 nodes each in secret.  You don't want 5 people running 20 nodes openly, either, if there are other good candidates who could take some of those slots as Active Delegates.  But despite this ideal, you can certainly show up and say you've got 20 servers ready to go if you want.  Who knows how people will vote?  Maybe you will get them all on line, maybe only some, maybe only one on line.  It all depends on the votes.

The reality of the situation is that two people, Max and Olivier, will be setting up the 101 initial Lisk Foundation servers to get the Lisk blockchain going.  Max and Olivier will also control around 15% of the Lisk votes in the beginning with the Lisk Foundation funds.  This is a huge amount of centralized voting power.  Unless they specifically say they will refrain from voting, I believe they will exercise these votes as required to get the community Lisk Active Delegates off to a good start.  I personally am 100% certain they will vote in a way to replace Lisk Foundation nodes with individuals as much as possible instead of "forging farms" run by a single mastermind.  This is just how Max and Olivier think, they believe in decentralization of Lisk as a primary goal, which is a good thing.

The rest of the delegate votes (85%) are going to be split over a much larger group of people (hundreds if not thousands of people) who get their votes from the 85M Lisk being distributed.  It will be very hard to get these people to vote at all, much less in a coordinated manner.  The most common feeling, in my opinion, will be "why bother to vote, my share is so small it won't matter, I'm just in this to make some money on this coin, not get involved in a community".  The situation will be much different than it was in Crypti, which never really had a crowd of small-holdings voters in control of picking the active delegates.  Lisk could very well be a mess in the beginning that trails off to apathy in the future where very few people vote at all after the initial spurt of interest in launching Lisk.  This potential for a mess is why I believe Max and Olivier will step in at the beginning to organize the community active delegate setup and get it on its feet.  

Your questions about standby delegates are critical and important ones.  In year one of Lisk, an Active Delegate can make as much as 150K Lisk.  Somebody that remains a Standby delegate for a year and never gets enough votes to go Active will make zero Lisk.   So...what is the motivation for them to keep a Lisk node server ready to go on hot standby if they are suddenly and unexpectedly voted up?  What happened at Crypti is that standby delegates were suddenly voted up one day only to discover not only was there no running node server, the person himself had long since left the party and was nowhere to be found.  

Here's a side thought.  The Bitcoin miner "get-rich-quick" mentality of fielding as much gear as possible to get as big a piece of the pie as possible - that attitude really isn't what Lisk is about.  Lisk is about cooperation to further the community, not competition to further one person.  You would help Lisk much more if you took a deep breath, purged yourself of your dreams of being a dragon sitting atop a big pile of coins, and tried to think of a different was to apply that drive and energy that would help Lisk as a whole instead of you personally.  For example, use the time you would spend running 20 nodes to learn JavaScript and go write a dapp!

Bottom line, the DPoS voting / forging part of Lisk is just as important as the price swings of the coin and further development of the code.  Nobody really knows yet how well the Lisk DPoS delegate system is really going to work as a social system.   Honestly, we are off in uncharted territory.  Lisk is different from Crypti in that it pays Active Delegates significant rewards to motivate them.  Whether this will be enough to make the whole system run smoothly will be very interesting to watch.