Author

Topic: [ANN][LSK] Lisk | Blockchain Application Platform for JavaScript Developers - page 1185. (Read 3074324 times)

legendary
Activity: 1666
Merit: 1020
expect(brain).toHaveBeenUsed()
Sorry guys. The installation routine is way to complicated. Ok as a developer it is no problem, but you targeted DAUs as well with the ICO.
They have a lot of work to do. A lot. Making a more user friendly local wallet is one of them.
The main problem is that even with this month long delay it simply wasn't enough time to do some things that otherwise would've been done by launch.
It was unexpected how much improvement Crypti needed that was essential to do before Lisk launch, so development effort was redirected by this from other thinks like making user friendly solutions.

Those of us who followed the testnet and dealt with running, testing, updating, etc the delegate nodes, it wasn't a suprise, but the opposite. We considere it a very successful launch, because the network held up, the nodes are synced, Lisk handled a great amount of transactions at launch and since then.

I'm understand why ppl are angry. They expected a finished product (for some reason), that works flawlessly, yet they didn't get it, from their perspective.

This could have been avoided or at least mitigated if a precise time to launch (with timer and everything) wasn't given.
Ironically it also didn't help that both big altocoin exchange was ready and even pre-announced adding Lisk.


I know, that it was a lot of work. I even offered help as well...
legendary
Activity: 1988
Merit: 1000
transaction error using dock client


Nothing workkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk

24 hours of pain trying to get my shit

What a waste of time

If you're having problems with the current web client (https://login.lisk.io/), we have setup additional web clients so you can login to Lisk
https://login03.lisk.io

https://login04.lisk.io

https://login05.lisk.io

https://login06.lisk.io

https://login08.lisk.io


Please verify the blockchain is synced before sending any LSK.

Kind regards,


try using any of those..

the login04 worked for me awhile back.

None of them work Im really tired of this.
hero member
Activity: 518
Merit: 501
Lisk launch post-mortem: What went right, what went wrong

Yesterday, at exactly 8pm UTC, we published Lisk v0.3.0 and announced the launch of Lisk. What a launch that was! In this post-mortem we bring light to the problems we faced, explain why our web login isn’t/wasn’t accessible, and clear up misunderstandings.



First of all, I’d like to apologise for the rough launch and the harm that the DDoS attack caused. Since the launch, we have been working tirelessly to ensure that all our systems are working perfectly again. We simply didn’t anticipate this overwhelming demand and trading chicanery.

The only problem we still face at this moment are our web logins. The reason is the same as yesterday: huge amount of traffic and ongoing DDoS attacks. However, everything else is working very well. Users can install Lisk on various operation systems like Windows, Mac OS, and Linux. Local client installations are functional and the Lisk network is alive and healthy.

The current client is aimed at technical users, but it’s relatively easy to install it with our guides. The best option is to simply use the Docker installation if you are on Windows or Mac. After we have guaranteed the network’s stability and optimised a few important Lisk modules (e.g., peer communication); we will look into options to provide a one-click Lisk client.


Read our complete post-mortem now!

excuse mr master "True"(or CTO or whatever you are) but you are liar... all windows users was put in the limbo from start and at final was fucked up thanks to you. you collect so much money and at final you say ddos attack? Omg all LSK start was pure failed one. much money from windows users and didn't predict docked version together with linux one? You are a joker with pink glasses - face the true. Sorry for saying this but its true...

i'm pretty sure nobody forced you to use windows.
hero member
Activity: 671
Merit: 505
Then the delegates and the rest of this community should be aware that https is not secure enough, if at all, and should not encourage its usage.
This is a decentralized network, that anyone can run a Node on.
You simply can't enforce anything like this, the best the community can do is offer advise.
And believe me, there were many discussions, guides, live help, etc about security and other issues. But still...

Then why not just a simple wallet based on a JS platform like Electron? Obviously most of the pretentious FUD idiots don't get Linux, Docker, etc. simple ways. Let's give them the simplest solution, just setup.exe / dmg / whatever-one-click-installer.
hero member
Activity: 574
Merit: 500
transaction error using dock client


Nothing workkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk

24 hours of pain trying to get my shit

What a waste of time

If you're having problems with the current web client (https://login.lisk.io/), we have setup additional web clients so you can login to Lisk
https://login03.lisk.io

https://login04.lisk.io

https://login05.lisk.io

https://login06.lisk.io

https://login08.lisk.io


Please verify the blockchain is synced before sending any LSK.

Kind regards,


try using any of those..

the login04 worked for me awhile back.
full member
Activity: 381
Merit: 101
i tryed docker aswell i send transaction from http://192.168.99.100:8000/

But there is still no confirmations

why you didn't just upload the windows wallet on google drive or something like this? i seriously don't get it
legendary
Activity: 1988
Merit: 1000
LOl max,why fucked windows user knowing it represent 90% of your investor/user ?
hero member
Activity: 739
Merit: 500
About the docker:
To be honest I coudn't make it work and I've been running three separate Lisk delegate nodes in the last two months, on five different server setups. Smiley
newbie
Activity: 53
Merit: 0
I have used this lisknode.grumlin.com And now my trnasaction have confirmations, now my question is How much confs are neccessary to see Lisk in Polo?

You should be able to see them immediately on the deposit page. It takes 303 confirmations (3 rounds) to be accepted.

It takes about 70 confirms before your deposit will show as pending in polo..and then 303 to actually confirm.


Good to know. Danke! Smiley


It didn't take me anywhere near 70 confirms to have it start showing at Polo. It started showing at 3 for me last night. For what it's worth.


Glad to hear it. I was one of the first sending my lisk to polo, so could be at first they wanted more confirms, glad to see everyone is able to take a lil profit before they start making lisk work better.
legendary
Activity: 1988
Merit: 1000
transaction error using dock client


Nothing workkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk

24 hours of pain trying to get my shit

What a waste of time
full member
Activity: 381
Merit: 101
Frequently Asked Questions

    My transactions don’t get any confirmations.

Please install the Lisk client locally on your computer, let it completely sync, and try it again. If the problem occurred locally, please restart the client, let it completely sync, and try it again.



HOW? I'm on windows, please someone have to tell me how, i'm getting mad seriously, i spend 15 hours now to try to make it works omfg
hero member
Activity: 739
Merit: 500
Then the delegates and the rest of this community should be aware that https is not secure enough, if at all, and should not encourage its usage.
This is a decentralized network, that anyone can run a Node on.
You simply can't enforce anything like this, the best the community can do is offer advise.
And believe me, there were many discussions, guides, live help, etc about security and other issues. But still...
sr. member
Activity: 358
Merit: 251
When will genesis blocks disappear?
legendary
Activity: 1988
Merit: 1000
Using Dock now not more working than .io link.



Just ugh


This coin is a pain in the ass to make it work


i used this web wallet https://bitcointalksearch.org/topic/annlsk-lisk-blockchain-application-platform-for-javascript-developers-1346646

worked for me.

Lol im not gonna use link from outside official for sure.

Big problem to lisk team if we need to trust another random party to get our coin lol.
sr. member
Activity: 437
Merit: 250
simple i dont need all the crazy answers i just want to get my coins and a working wallet

Got any linux skills?
legendary
Activity: 1708
Merit: 1000
Reality is stranger than fiction
Using Dock now not more working than .io link.



Just ugh


This coin is a pain in the ass to make it work


i used this web wallet https://bitcointalksearch.org/topic/annlsk-lisk-blockchain-application-platform-for-javascript-developers-1346646

worked for me.
hero member
Activity: 532
Merit: 500
I have used this lisknode.grumlin.com And now my trnasaction have confirmations, now my question is How much confs are neccessary to see Lisk in Polo?

You should be able to see them immediately on the deposit page. It takes 303 confirmations (3 rounds) to be accepted.

It takes about 70 confirms before your deposit will show as pending in polo..and then 303 to actually confirm.


Good to know. Danke! Smiley


It didn't take me anywhere near 70 confirms to have it start showing at Polo. It started showing at 3 for me last night. For what it's worth.
legendary
Activity: 1988
Merit: 1000
Using Dock now not more working than .io link.



Just ugh


This coin is a pain in the ass to make it work
hero member
Activity: 671
Merit: 505
This node is vulnerable for man-in-the middle attacks. We suggest to have at least SSL installed. Additionally, no matter how trusted an individual is. Everyone can still hack his account on his server provider and change the files. The Lisk team won't endorse 3rd party nodes ever. Smiley

Free certificates for https https://letsencrypt.org/

Most delegates know about this, and was encouraged to use it, since almost day one.
There is even a guide how to do it on a delegate node.

Then the delegates and the rest of this community should be aware that https is not secure enough, if at all, and should not encourage its usage.
Jump to: