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

Very good summary and explanation of what happened!

Everybody should read it. And all who still would like to spread FUD... read it two or three or ten times. ;-)

Shut the fuck up fag. You are useless.

Thank you Max.

Very nice analysis

DDos attack was made from MAX itself! Open your eyes guys!
A dev that wasn't able to prevent addos attack at launch? ridicolous.

So are there any suspects for DDoS attack?  Who are those criminals??

https://lisknode.grumlin.com/

Smooth as hell!! Thanks a lot grumlin, finally could tranfer my funds. And now  i will sit back and watch the market, no way i'm selling  

Max,
You didn't solve main stuck here: weblogin, and you got 24 hours time.
If you rent 5 usd vps it's your fault. not ddos attack.

Did you already bought your lambo today with your 6 million usd?

use ./lisk.sh coldstart it worked for me =]

It could be a GGWP to ICO holders.  

I have several different accounts from different buys during ico. Is it safe to move them all to 1 of my addresses so I don't have to key into all the different accounts that are holding my lisk?

"DDoS attack caused"?

Your coin is fucked up!
You're already the new meme over internet.

Tell me again about multiple delayes to perform a SMOOTH LAUNCH on may 24 please.

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!

Lot of bugs here. It's normal, we are in testnet.

When mainet will be available, we will se a SMOOTH LAUNCH as dev said.

When lisk will official launch? 

i get this error while server use my system user for database, i create a password for Postgre and edit the config.json

Too much attension, lisk will go to the moon!

I was getting this error before being able to even download any of the files associated with LISK so there was no docker to restart.

Or just restart the Docker container:

docker stop $(docker ps -a | grep lisk | awk '{print $1}')
docker start $(docker ps -a | grep lisk | awk '{print $1}')

OW EM GEE. I GOT A CONFIRMED TRANSACTION FROM THE WEBWALLET..... after only trying 21 times.

Your transaction never reached the network, try logging into a different web wallet and send it again.

I had this error when I first set up the node.  I ended up restoring my VPS server from scratch and it solved the issues with the name stuff which was preventing me from also downloading the files.

this might also be the solution to the guy above