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

[CryptoMrM]

I've sold all my LISK.

I was going to hold for the future but after this pathetic launch by the LISK team I'm selling it all.

I have no faith in the team anymore. I'm beginning to see why Crypti wasn't a success.

LOL, Ethereum holders are DDOS'ing it, what do you expect lisk to do? They are being attacked.

They should have had contingency plans in place.

You could have handed out different trusted nodes to allow people to access their LISK.

[1715547346]

1715547346

[BitPotus]

with docker i get this error:

Error while pulling image: Get https://index.docker.io/v1/repositories/lisk/mainnet/images: dial tcp: lookup index.docker.io on 10.0.2.3:53: no such host.

any advice?

YES. JUST GIVE UP AND GIVE THEM BATTY BOIS TIME TO SORT THEIR CLUSTER-FUCK OUT. THEY JUST SHOT THEIR PROJECT IN THE FOOT.

[ntrader]

Working wallet http://40.68.214.86:8000 - just put it into your url... (and no it's not a corrupted wallet or something, is one of main node from lisk team) - check binary files if you don't believe me

Confirm, it work's. Received 3 transactions on Poloniex account from web wallet.

[cienki7]

You can use http://40.68.214.86:8000/ to access your wallet. Its secure, is one of the official nodes.

LiskHQ canyou please confrm?

[Brewins]

what ?? i don't blaming anybody, i just show you alternative way to use wallet, to prevent fuding around here.

I won't touch any other wallet than login.lisk.io

if you or admins really expect that I use an inofficial wallet, you are insane and I consider this a fraud

We don't expect this and don't recommend it. We recommend to install the client locally.

I installed it locally about 100 times on a Mac and on Ubuntu - (finally got the Docker to work several hours after launch). So in reference to your statement about installing client locally, I will say this for the third time in a nice way:

IT DOES NOT FUCKING WORK
I GET THE FOLLOWING ERROR:
Cannot GET/

[Jcga]

Damn! Missed posting on page 1000 by a long shot.

i did:)

I do too

[Nefritox]

You can use http://40.68.214.86:8000/ to access your wallet. Its secure, is one of the official nodes.

THANK YOU!!! thats what i try to explain to those idiots for like last 3 hours...

[Jordan23]

The panic is epic. Just another day/coin to me. Seen it over and over and over and over.

[str4wm4n]

NEED HELP WITH TRANSACTION ID 5960699272035633494

[Bigcabrito]

What a sad failure of a launch. Be a man Lisk team and take it on the chin. Agree it wasnt as expected and apologise. Doesn't give confidence to investors this is going anywhere if you react in such a way.

The official Lisk web client is being worked on, it takes time to stop such an attack.

The client is running great at the moment, that's the positive side.

what do you mean attack?

didn't you expect to be swamped at launch???

what did you expect just 10 people to use the site?

Do you really think that 50000 users were trying to access the web login? I don't think so.

YOU HAD TIME TO PREPARE!!!

NO EXCUSES!!

We are not making any excuses. We're giving you data on what's been occurring in the background and why login.lisk.io is not accessible at the moment.

Listen Blud, don't get me started.

You muppets fucked this up royally.

the majority of people don't use linux.

if some scam coin has a working windows wallet, there's no bloody excuse why LISK doesn't have one at launch.

You said you were delaying the launch to ensure that everything worked like clockwork.

You Failed!!!

Take it on the chin and sort it out.

The web client (login.lisk.io) was the victim of a coordinate DDoS attack.

The client is working as intended, no hiccups so far with over 1000 blocks generated.

[tangleNinja]

Docker Image not working.

all i get is "Cannot GET /"

Seriously how do you even fuckup a docker image.

How come i cant find the Dockerfile for this?

Also you guys sure you dont want users to -v a mountpoint
so users dont have to redownload blockchain every time they update?

exact same error with default linux install.

[Reavon]

i set up a delegate : reavon up and running and synced you can calm down now guys the launch was a birth , but its a girl .

We shall call her Liska.

[badam]

Finally the docker image is working flawless, managed to sync, send and get tx confirmed with a blazing fast speed.
Not the best launch but at least within a few hours all of us got a possibility to use lisk.

For those who are against docker, you have to copy paste 3 commands and your client is up and running.

[prettybuds]

Do you really think that 50000 users were trying to access the web login? I don't think so.

What? 50000 is a very low number for a project that was extremely hyped all over the internet by your marketing team

Did you work only on the hype or did you also work on the infrastructure?

with every comment I read I am more and more beyond my strength

[LiskCryptoFan]

What a sad failure of a launch. Be a man Lisk team and take it on the chin. Agree it wasnt as expected and apologise. Doesn't give confidence to investors this is going anywhere if you react in such a way.

The official Lisk web client is being worked on, it takes time to stop such an attack.

The client is running great at the moment, that's the positive side.

what do you mean attack?

didn't you expect to be swamped at launch???

what did you expect just 10 people to use the site?

Do you really think that 50000 users were trying to access the web login? I don't think so.

How do you not plan for that? Did you think a major competitor such as Lsk was just going to glide into a launch?  How about the docker file? What's the excuse for not having that ready with correct instructions?  

[Wolf Rainer]

You can use http://40.68.214.86:8000/ to access your wallet. Its secure, is one of the official nodes.

LiskHQ canyou please confrm?

Download the linux binary at https://downloads.lisk.io/lisk/main/0.3.0/ then open the config.json with a notepad... Inside you will find:

    "peers": {
        "list": [
            {
                "ip": "40.68.214.86",
                "port": 8000
            },
            {
                "ip": "13.70.207.248",
                "port": 8000
            },
            {
                "ip": "13.89.42.130",
                "port": 8000
            },
            {
                "ip": "52.160.98.183",
                "port": 8000
            },

Those are all official nodes. Its safe to use them.
  

[Breasal]

I think I found an error in the documentation?

https://lisk.io/documentation?i=lisk-docs/DockerInstall

Fixed!

$ docker run -d --restart=always -p 0.0.0.0:8000:8000 lisk/mainnet
a65b03c0a6725411c21bbff8b2da922dbebfd206bcf1130722c7dd305ade2a2f
docker: Error response from daemon: driver failed programming external connectivity on endpoint hungry_albattani (29e877ff92a965ddabe2d21d10cabf64cd026512f616acdeafd2155420c6aa96): Bind for 0.0.0.0:8000 failed: port is already allocated.


How to fix this error: do I have to purchase a docker vps?

[bcmine]

with docker i get this error:

Error while pulling image: Get https://index.docker.io/v1/repositories/lisk/mainnet/images: dial tcp: lookup index.docker.io on 10.0.2.3:53: no such host.

any advice?

YES. JUST GIVE UP AND GIVE THEM BATTY BOIS TIME TO SORT THEIR CLUSTER-FUCK OUT. THEY JUST SHOT THEIR PROJECT IN THE FOOT.

what would be a problem to install 50 nodes with the f******* lisk.node on 500 different servers for 50 cents each, Max???
or asking community to do that???

[benthach]

lisk team shouldn't block customers access to their coins at this moment

[badam]

I think I found an error in the documentation?

https://lisk.io/documentation?i=lisk-docs/DockerInstall

Fixed!

$ docker run -d --restart=always -p 0.0.0.0:8000:8000 lisk/mainnet
a65b03c0a6725411c21bbff8b2da922dbebfd206bcf1130722c7dd305ade2a2f
docker: Error response from daemon: driver failed programming external connectivity on endpoint hungry_albattani (29e877ff92a965ddabe2d21d10cabf64cd026512f616acdeafd2155420c6aa96): Bind for 0.0.0.0:8000 failed: port is already allocated.


How to fix this error: do I have to purchase a docker vps?

Delete your container that is already present in docker