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

[g3rszpi]

Great news
http://www.econotimes.com/Blockchain-app-platform-Lisk-to-issue-block-rewards-to-delegates-386827

BAM! Excellent news!!!

Yeah, yeah its good, but the Delegate Cartel problem must be resolved first.

[1714983572]

1714983572

[1714983572]

1714983572

[1714983572]

1714983572

[1714983572]

1714983572

[BigKush]

“We’re excited to share great news with our community. Upon reaching block 1451520, the platform will automatically initiate the issuance of block rewards, whereby 5 LSK will be sent directly to each elected delegate for every block they forge. We can now announce that this block will be reached before the end of 2016,” said Max Kordek, CEO and Co-Founder of Lisk.  

Now it is  1288875 block   

[Bigcabrito]

Read Full Details Here: Weekly Summary - 008

We are happy to announce that the imminent completion of our first milestone named “Mainchain stabilisation” is in sight. The most important achievement for our user base this year comes with the subsequent activation of community forging. With that, we will also enable forging rewards so that delegates are able to finance community projects, and foster a growing ecosystem.

This marks a historic turning point for the Lisk project, going forward we can now put the majority of our efforts into our sidechain technology and the Lisk App SDK.

Read Full Details Here: First milestone in sight: Forging Rewards Activation

[LiskHQ]

[O_Omaha]

This is good news, but what if the Lisk core is not stabilized by that date?  (Which it won't be) Then what?

[LiskHQ]

This is good news, but what if the Lisk core is not stabilized by that date?  (Which it won't be) Then what?

It will be.

[Bigcabrito]

This is good news, but what if the Lisk core is not stabilized by that date?  (Which it won't be) Then what?

With 0.5.0 we are confident with the improvements made and have it considered a safe beta candidate. As such, our community should not have problems securing the network while being active delegates.

0.5.0 is currently in open public testing, and is scheduled for release to the main network very soon if no problems arise.

[trader19]

This is good news, but what if the Lisk core is not stabilized by that date?  (Which it won't be) Then what?

With 0.5.0 we are confident with the improvements made and have it considered a safe beta candidate. As such, our community should not have problems securing the network while being active delegates.

0.5.0 is currently in open public testing, and is scheduled for release to the main network very soon if no problems arise.

great news )) go go Lisk

[O_Omaha]

snip

This is good news, but what if the Lisk core is not stabilized by that date?  (Which it won't be) Then what?

With 0.5.0 we are confident with the improvements made and have it considered a safe beta candidate. As such, our community should not have problems securing the network while being active delegates.

0.5.0 is currently in open public testing, and is scheduled for release to the main network very soon if no problems arise.

"if no problems arise"  problems always arise. so what happen when problem arise? hardfork to move community forging far away or let community forging crash the chain?

[cesmak]

snip

This is good news, but what if the Lisk core is not stabilized by that date?  (Which it won't be) Then what?

With 0.5.0 we are confident with the improvements made and have it considered a safe beta candidate. As such, our community should not have problems securing the network while being active delegates.

0.5.0 is currently in open public testing, and is scheduled for release to the main network very soon if no problems arise.

"if no problems arise"  problems always arise. so what happen when problem arise? hardfork to move community forging far away or let community forging crash the chain?

If no problems arise (during testnet before official release) this is what i've read, so if some problems come, they will be solved BEFORE going live.....

[Bigcabrito]

snip

This is good news, but what if the Lisk core is not stabilized by that date?  (Which it won't be) Then what?

With 0.5.0 we are confident with the improvements made and have it considered a safe beta candidate. As such, our community should not have problems securing the network while being active delegates.

0.5.0 is currently in open public testing, and is scheduled for release to the main network very soon if no problems arise.

"if no problems arise"  problems always arise. so what happen when problem arise? hardfork to move community forging far away?

If a problem arises it will get worked on and fixed, insuring code quality. The procedure remains the same:

• Step 1: Problem arises > Find a fix; move onward to step 2
• Step 2: Internal testing of fix; if pass go to step 3; if fail fix/re-write and go to step 1
• Step 3: Release alpha candidate to alpha testers; if pass go to step 4; if fail fix/re-write and go to step 1
• Step 4: Release public beta candidate; if pass go to step 5; if fail fix/re-write and go to step 1
• Step 5: Release candidate if ready for main network; announce it

The block where community forging is set to begin is set in stone, and it will not be moved. We've made great progress these months.

[nyanhtet]

snip

This is good news, but what if the Lisk core is not stabilized by that date?  (Which it won't be) Then what?

With 0.5.0 we are confident with the improvements made and have it considered a safe beta candidate. As such, our community should not have problems securing the network while being active delegates.

0.5.0 is currently in open public testing, and is scheduled for release to the main network very soon if no problems arise.

"if no problems arise"  problems always arise. so what happen when problem arise? hardfork to move community forging far away?

If a problem arises it will get worked on and fixed, insuring code quality. The procedure remains the same:

• Step 1: Problem arises > Find a fix; move onward to step 2
• Step 2: Internal testing of fix; if pass go to step 3; if fail fix/re-write and go to step 1
• Step 3: Release alpha candidate to alpha testers; if pass go to step 4; if fail fix/re-write and go to step 1
• Step 4: Release public beta candidate; if pass go to step 5; if fail fix/re-write and go to step 1
• Step 5: Release candidate if ready for main network; announce it

The block where community forging is set to begin is set in stone, and it will not be moved. We've made great progress these months.

Smart and Professional!

[O_Omaha]

snip

This is good news, but what if the Lisk core is not stabilized by that date?  (Which it won't be) Then what?

With 0.5.0 we are confident with the improvements made and have it considered a safe beta candidate. As such, our community should not have problems securing the network while being active delegates.

0.5.0 is currently in open public testing, and is scheduled for release to the main network very soon if no problems arise.

"if no problems arise"  problems always arise. so what happen when problem arise? hardfork to move community forging far away?

If a problem arises it will get worked on and fixed, insuring code quality. The procedure remains the same:

• Step 1: Problem arises > Find a fix; move onward to step 2
• Step 2: Internal testing of fix; if pass go to step 3; if fail fix/re-write and go to step 1
• Step 3: Release alpha candidate to alpha testers; if pass go to step 4; if fail fix/re-write and go to step 1
• Step 4: Release public beta candidate; if pass go to step 5; if fail fix/re-write and go to step 1
• Step 5: Release candidate if ready for main network; announce it

The block where community forging is set to begin is set in stone, and it will not be moved. We've made great progress these months.

I know you are sure it will happen, but please understand my reservation as it seem like more a PR move than being based on reality.  You are just starting a new testnet today after a complete failure testnet and havent even really begin tested the release candidate, and now you are saying It's stable for community forging.  sorry it just do not add up.

[Bigcabrito]

snip

This is good news, but what if the Lisk core is not stabilized by that date?  (Which it won't be) Then what?

With 0.5.0 we are confident with the improvements made and have it considered a safe beta candidate. As such, our community should not have problems securing the network while being active delegates.

0.5.0 is currently in open public testing, and is scheduled for release to the main network very soon if no problems arise.

"if no problems arise"  problems always arise. so what happen when problem arise? hardfork to move community forging far away?

If a problem arises it will get worked on and fixed, insuring code quality. The procedure remains the same:

• Step 1: Problem arises > Find a fix; move onward to step 2
• Step 2: Internal testing of fix; if pass go to step 3; if fail fix/re-write and go to step 1
• Step 3: Release alpha candidate to alpha testers; if pass go to step 4; if fail fix/re-write and go to step 1
• Step 4: Release public beta candidate; if pass go to step 5; if fail fix/re-write and go to step 1
• Step 5: Release candidate if ready for main network; announce it

The block where community forging is set to begin is set in stone, and it will not be moved. We've made great progress these months.

I know you are sure it will happen, but please understand my reservation as it seem like more a PR move than being based on reality.  You are just starting a new testnet today after a complete failure testnet and havent even really begin tested the release candidate, and now you are saying It's stable for community forging.  sorry it just do not add up.

Lisk v0.5.0b is in Step 4 at the moment. It's been more than a week since it passed internal and alpha testing. With 0.5.0, the community has a stable beta candidate, and can begin delegating once the block has arrived.

[Number 1]

Hi all,

I am an early adoptor of LISK I am not overly technically minded and don't have much processing power in terms of computer hardware. I am however active in the world of crypto and medical apps/ healthcare blockchain with a decent Lisk holding

Is there any point in me registering as a delegate or active delegate for forging. In my understanding Lisk isnt Proof of stake, therefore does having a good balance of Lisk benefit in any way in terms of forging? Also to be a delegate do I need my computer hardware to be always on?

Appreciate your feedback

[Diplo]

Hi all,

I am an early adoptor of LISK I am not overly technically minded and don't have much processing power in terms of computer hardware. I am however active in the world of crypto and medical apps/ healthcare blockchain with a decent Lisk holding

Is there any point in me registering as a delegate or active delegate for forging. In my understanding Lisk isnt Proof of stake, therefore does having a good balance of Lisk benefit in any way in terms of forging? Also to be a delegate do I need my computer hardware to be always on?

Appreciate your feedback

To run your own node you'll want to use a VPS (Virtual Private Server) with specific minimum specs (mine and others have been ~4 CPU, 4GB RAM, etc on Vultr).

You'll also need to make it known publicly on the forums, lisk.chat, slack channels, wherever, that you intend to run a node and need vote support. Depending on how the Lisk team (or other whales/groups) decides to vote you may need a little as 3-4 million (lisk) votes, or as much as 12 million+ to secure a spot among the 101 delegates.  This is all a guess though, hope that helps some  .

[Number 1]

Thanks or your reply. So does the delegate's Lisk balance have any bearing on forging rewards?
Also surely a delegate could vote themselves into the 101 using their Lisk balance.

[redsn0w]

“We’re excited to share great news with our community. Upon reaching block 1451520, the platform will automatically initiate the issuance of block rewards, whereby 5 LSK will be sent directly to each elected delegate for every block they forge. We can now announce that this block will be reached before the end of 2016,” said Max Kordek, CEO and Co-Founder of Lisk.  

Now it is  1288875 block   

Yeah! This is really a great news, finally the community forging will start and all the delegates can start to secure the mainnet and funds some lisk projects .

[Clonekiller]

I hope we will be over 40k soon i missed a buy in @ 20k i was on holiday
But i have already a big piece of the pie  
In mean time lisk team keep up the great work

[Diplo]

I hope we will be over 40k soon i missed a buy in @ 20k i was on holiday
But i have already a big piece of the pie  
In mean time lisk team keep up the great work

We probably will be