Topic: [ANN][LSK] Lisk | Blockchain Application Platform for JavaScript Developers - page 1263. (Read 3074324 times)
May 24, 2016, 07:07:37 PM
I can't take it anymore I don't know what to do I'm close to a breakdown. I'll just log off
May 24, 2016, 07:06:47 PM
just like expected we start at $0.20
Cause Lisk is a just a fork of Crypti.
The initial plan of Crypti was to make a second IPO, but Max and Oliver took the source, said goodbye to Crypti team and started ICO by themselfs instead of Crypti team.
And here is the result: thanks to premine and ICO money, Max and Oliver are USD millionaires
And these two Lambos is for you Kordek and Beddows:
You earn it.
May 24, 2016, 07:06:47 PM
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?
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???
Max's Lambo needs some new polishing stuff it costs money sry bro :/
May 24, 2016, 07:06:38 PM
NEED HELP WITH TRANSACTION ID 5960699272035633494
Just Log out and Log in again. Then you see all your original LSK amount is still there and send the transaction again 
May 24, 2016, 07:06:30 PM
lisk team shouldn't block customers access to their coins at this moment
Nothing is blocked at the moment, you can at anytime install the client and have access to your LSK.
May 24, 2016, 07:05:58 PM
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.
And how come you muppets did not anticipate a co-ordinated DDos attack?
I mean, we all know it's been fairly common recently.......
CONTINGENCY PLAN!!!!
May 24, 2016, 07:05:54 PM
hello bullshitters wer you gone
May 24, 2016, 07:05:48 PM
SEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEELLLLLLLLLLLLLLLLLLLLLLLLLLLL!
Still x2.5 ICO, sell now or cry later!
Still x2.5 ICO, sell now or cry later!
May 24, 2016, 07:05:44 PM
I think I found an error in the documentation?
https://lisk.io/documentation?i=lisk-docs/DockerInstall
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
May 24, 2016, 07:04:50 PM
lisk team shouldn't block customers access to their coins at this moment
May 24, 2016, 07:04:43 PM
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?
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???
May 24, 2016, 07:04:25 PM
I think I found an error in the documentation?
https://lisk.io/documentation?i=lisk-docs/DockerInstall
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?
May 24, 2016, 07:03:27 PM
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.
May 24, 2016, 07:02:14 PM
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?
May 24, 2016, 07:02:11 PM
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
May 24, 2016, 07:01:55 PM
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.
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.
May 24, 2016, 07:01:46 PM
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.
.We shall call her Liska.
May 24, 2016, 07:01:16 PM
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?
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.
May 24, 2016, 07:00:49 PM
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.
May 24, 2016, 07:00:44 PM
NEED HELP WITH TRANSACTION ID 5960699272035633494
Jump to: