Topic: [ANN][LSK] Lisk | Blockchain Application Platform for JavaScript Developers - page 1859. (Read 3074324 times)
April 06, 2016, 09:56:22 AM
April 06, 2016, 09:54:43 AM
April 06, 2016, 09:53:09 AM
April 06, 2016, 09:51:22 AM
April 06, 2016, 09:50:23 AM
April 06, 2016, 09:49:07 AM
April 06, 2016, 09:48:47 AM
So how long do we have in order to confirm the passphrase? Is there a set time please?
Do it A.S.A.P that's one reason why there's going to be a delay in the launch. People aren't generating there keys AND/OR verifying them. 
April 06, 2016, 09:41:59 AM
So how long do we have in order to confirm the passphrase? Is there a set time please?
April 06, 2016, 09:40:36 AM
April 06, 2016, 09:36:05 AM
How to GENERATE your LISK ICO PASSPHRASE(S):
https://academy.lisk.io/how-to-generate-your-lisk-ico-passphrase-62536fce5edc#.6fy6ab13n
How to VERIFY your ICO PASSPHRASE(S):
https://academy.lisk.io/lisk-guide-to-verifying-your-ico-generated-keys-c11a5df1089f#.86dafspv2
April 06, 2016, 08:59:59 AM
Once you completed the exchange a window popped with the address and passphrase. It gives you the option to download the credentials to a text file and afterwards you close the dialog box by "accepting" or basically saying that you've recorded the pass phrase.
THIS is the problem, right here. The window should not have closed (i.e, "trusted you") after you clicked "accept". The window should have kept going, stopped displaying your pass phrase, and said "Prove to me you've got it, buddy. Type it in right now while I'm not showing it to you, or we're going to a password reset screen."
If the GUI had been set up like THIS, none of us would be having this conversation right now.
Huh this never happened to me... It just shut.. WTF is that all about? I saved the keys. What do I do now then?
The answer is obviously, VERIFY YOUR DAMN KEYS.
Stop rolling the dice on your money and take care of your shit. Really, wtf people.
sure... that's quite usual, blame it on the users...
Yes, It is their fault. If they would have taken care of their shit 3 weeks ago we would be on track for the release. I guess that's not surprising from a guy with the word Moron in his username.
This comment just fucking blew my mind. I have now lost all my faith in humanity.
Obviously there's a lot of confusion among the users which is not a good sign of course.
April 06, 2016, 08:57:10 AM
The launch date is not set yet so I don't know where you got April 18...
Hmm.. Hows it going, I've been on a short break from developing but I'm back now!
Let's go Lisk!
April 18!
Let's go Lisk!
April 18!
April 06, 2016, 08:24:12 AM
When I want to enable forging for my test Node it says Acces Denied.
Does anybody have a clue on how I can fix this?
Thx,
Does anybody have a clue on how I can fix this?
Thx,
1. make sure you're on your node ip and not the lisk.io login
2. make sure your passphrase has the "" around the passphrase like ["passphrase"] and not [Passphrase] in the config file
3. restart the node possibly if you were able to forge before
mine was doing that as well. It worked, Thanks alot.
cool, yeah those seem to be the solution to most of the forging issues that I've seen. More nodes the merrier.
April 06, 2016, 08:21:43 AM
When I want to enable forging for my test Node it says Acces Denied.
Does anybody have a clue on how I can fix this?
Thx,
Does anybody have a clue on how I can fix this?
Thx,
1. make sure you're on your node ip and not the lisk.io login
2. make sure your passphrase has the "" around the passphrase like ["passphrase"] and not [Passphrase] in the config file
3. restart the node possibly if you were able to forge before
mine was doing that as well. It worked, Thanks alot.
April 06, 2016, 08:11:01 AM
When I want to enable forging for my test Node it says Acces Denied.
Does anybody have a clue on how I can fix this?
Thx,
Does anybody have a clue on how I can fix this?
Thx,
1. make sure you're on your node ip and not the lisk.io login
2. make sure your passphrase has the "" around the passphrase like ["passphrase"] and not [Passphrase] in the config file
3. restart the node possibly if you were able to forge before
Thanks alot!
Ill try it out asap.
Cheers.
April 06, 2016, 08:07:06 AM
When I want to enable forging for my test Node it says Acces Denied.
Does anybody have a clue on how I can fix this?
Thx,
Does anybody have a clue on how I can fix this?
Thx,
1. make sure you're on your node ip and not the lisk.io login
2. make sure your passphrase has the "" around the passphrase like ["passphrase"] and not [Passphrase] in the config file
3. restart the node possibly if you were able to forge before
April 06, 2016, 08:06:05 AM
Once you completed the exchange a window popped with the address and passphrase. It gives you the option to download the credentials to a text file and afterwards you close the dialog box by "accepting" or basically saying that you've recorded the pass phrase.
THIS is the problem, right here. The window should not have closed (i.e, "trusted you") after you clicked "accept". The window should have kept going, stopped displaying your pass phrase, and said "Prove to me you've got it, buddy. Type it in right now while I'm not showing it to you, or we're going to a password reset screen."
If the GUI had been set up like THIS, none of us would be having this conversation right now.
Huh this never happened to me... It just shut.. WTF is that all about? I saved the keys. What do I do now then?
The answer is obviously, VERIFY YOUR DAMN KEYS.
Stop rolling the dice on your money and take care of your shit. Really, wtf people.
sure... that's quite usual, blame it on the users...
Yes, It is their fault. If they would have taken care of their shit 3 weeks ago we would be on track for the release.
This comment just fucking blew my mind. I have now lost all my faith in humanity.
"Would have" and "could have"... It is what it is...
The situation is: we need more people to validate their keys. Let's put our energy on that instead of complaining for the next 3 weeks.
I don't think it's going to help. You can see that most of the people who didn't validate their keys are skipping it on purpose. Some dudes are actively fighting against people trying to explain why they should validate.
like you said, it is what it is.
Well, whatever
Someday Lisk will launch, with or without those people validating their keys.
I can only advise to do so, and if not: don't complain that you lost your ICO funds because you didn't save your passphrase(s) correctly (while you thought you did).
that's why I gave up.
Anyone else with me on making page 420 all Cannabis gifs?
April 06, 2016, 08:05:00 AM
Once you completed the exchange a window popped with the address and passphrase. It gives you the option to download the credentials to a text file and afterwards you close the dialog box by "accepting" or basically saying that you've recorded the pass phrase.
THIS is the problem, right here. The window should not have closed (i.e, "trusted you") after you clicked "accept". The window should have kept going, stopped displaying your pass phrase, and said "Prove to me you've got it, buddy. Type it in right now while I'm not showing it to you, or we're going to a password reset screen."
If the GUI had been set up like THIS, none of us would be having this conversation right now.
Huh this never happened to me... It just shut.. WTF is that all about? I saved the keys. What do I do now then?
The answer is obviously, VERIFY YOUR DAMN KEYS.
Stop rolling the dice on your money and take care of your shit. Really, wtf people.
sure... that's quite usual, blame it on the users...
Yes, It is their fault. If they would have taken care of their shit 3 weeks ago we would be on track for the release.
This comment just fucking blew my mind. I have now lost all my faith in humanity.
"Would have" and "could have"... It is what it is...
The situation is: we need more people to validate their keys. Let's put our energy on that instead of complaining for the next 3 weeks.
I don't think it's going to help. You can see that most of the people who didn't validate their keys are skipping it on purpose. Some dudes are actively fighting against people trying to explain why they should validate.
like you said, it is what it is.
Well, whatever
Someday Lisk will launch, with or without those people validating their keys.
I can only advise to do so, and if not: don't complain that you lost your ICO funds because you didn't save your passphrase(s) correctly (while you thought you did).
that's why I gave up.
Anyone else with me on making page 420 all Cannabis gifs?
April 06, 2016, 08:03:27 AM
Once you completed the exchange a window popped with the address and passphrase. It gives you the option to download the credentials to a text file and afterwards you close the dialog box by "accepting" or basically saying that you've recorded the pass phrase.
THIS is the problem, right here. The window should not have closed (i.e, "trusted you") after you clicked "accept". The window should have kept going, stopped displaying your pass phrase, and said "Prove to me you've got it, buddy. Type it in right now while I'm not showing it to you, or we're going to a password reset screen."
If the GUI had been set up like THIS, none of us would be having this conversation right now.
Huh this never happened to me... It just shut.. WTF is that all about? I saved the keys. What do I do now then?
The answer is obviously, VERIFY YOUR DAMN KEYS.
Stop rolling the dice on your money and take care of your shit. Really, wtf people.
sure... that's quite usual, blame it on the users...
Yes, It is their fault. If they would have taken care of their shit 3 weeks ago we would be on track for the release.
This comment just fucking blew my mind. I have now lost all my faith in humanity.
"Would have" and "could have"... It is what it is...
The situation is: we need more people to validate their keys. Let's put our energy on that instead of complaining for the next 3 weeks.
I don't think it's going to help. You can see that most of the people who didn't validate their keys are skipping it on purpose. Some dudes are actively fighting against people trying to explain why they should validate.
like you said, it is what it is.
Well, whatever
Someday Lisk will launch, with or without those people validating their keys.
I can only advise to do so, and if not: don't complain that you lost your ICO funds because you didn't save your passphrase(s) correctly (while you thought you did).
April 06, 2016, 08:01:14 AM
Stop rolling the dice on your money and take care of your shit. Really, wtf people.
Just because someone didn't use the verification process, it doesn't mean that they are rolling the dice. Maybe they are competent adults, handling money.
When they generated the keys, they tested it on crypti network if they lead to the correct account id, then saved the passphrases into keepass (that has being backup up automaticaly twice a day, two different locations), saved the txt files to a Truecrypt volume. (also backuped).
So when verification process come along, they didn't bother.
Or maybe that's just me.
Jump to: