Topic: [ANN][LSK] Lisk | Blockchain Application Platform for JavaScript Developers - page 618. (Read 3074310 times)
November 07, 2016, 03:37:39 PM
Hats off to the team for relentlessly delivering despite all the whining in the last couple of weeks. Good times!
November 07, 2016, 03:28:16 PM
This is good, I switched from ICN (garbage scam) back to Lisk right on time. I think we're hitting a 100k floor. Lisk is finally putting things together.
You do realize that ICN is the 4th largest (soon to be 5th largest) holder of LSK?
What's good for LSK is good for ICN is good for ARK
I'm holding all 3 of these winners
November 07, 2016, 03:24:03 PM
My average is 40k and i don't care !! i don't trade its on a wallet
November 07, 2016, 03:22:26 PM
I bought at the floor. I bought at the floor. 
Im a going to win on this trade. Win I will!
Who else bought the floor and is ready for the pump now like I am....
No pumps please. Im a going to win on this trade. Win I will!Who else bought the floor and is ready for the pump now like I am....
Would be nice to see the price stabalise again between 40k and 50k, feels like a nice range for LSK to me
November 07, 2016, 03:21:14 PM
I bought at the floor. I bought at the floor. Im a going to win on this trade. Win I will!
Who else bought the floor and is ready for the pump now like I am....
Im a going to win on this trade. Win I will!Who else bought the floor and is ready for the pump now like I am....
I've had buy orders of increasing quantity in all the way down from 39k, think the lowest I bought at was 21k, the floor was just above 20000, so I got pretty close. My 20k didn't get filled though
November 07, 2016, 03:19:19 PM
This is good, I switched from ICN (garbage scam) back to Lisk right on time. I think we're hitting a 100k floor. Lisk is finally putting things together.
November 07, 2016, 03:17:48 PM
I bought at the floor. I bought at the floor. Im a going to win on this trade. Win I will!
Who else bought the floor and is ready for the pump now like I am....
No pumps please. Im a going to win on this trade. Win I will!Who else bought the floor and is ready for the pump now like I am....
November 07, 2016, 03:10:01 PM
I bought at the floor. I bought at the floor. Im a going to win on this trade. Win I will!
Who else bought the floor and is ready for the pump now like I am....
Im a going to win on this trade. Win I will!Who else bought the floor and is ready for the pump now like I am....
November 07, 2016, 02:42:45 PM
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
But i have already a big piece of the pie
In mean time lisk team keep up the great work
We probably will be
November 07, 2016, 02:36:21 PM
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
But i have already a big piece of the pie
In mean time lisk team keep up the great work
November 07, 2016, 02:22:55 PM
“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
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
. November 07, 2016, 01:25:57 PM
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.
Also surely a delegate could vote themselves into the 101 using their Lisk balance.
November 07, 2016, 12:55:34 PM
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
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
. November 07, 2016, 12:40:49 PM
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
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
November 07, 2016, 12:38:05 PM
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.
November 07, 2016, 12:31:20 PM
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.
November 07, 2016, 12:14:55 PM
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!
November 07, 2016, 11:53:37 AM
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.
November 07, 2016, 11:52:33 AM
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.....
November 07, 2016, 11:44:55 AM
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?
Jump to: