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

[uploadgod]

How long has it taken for you guys to move LISK to poloniex? I've been waiting over four hours now...nothing on polo's end showing anything

same here, even using docker,

0 confirmations

i don't know if i have to do something to sync the wallet.

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?

[1713303361]

1713303361

[1713303361]

1713303361

[1713303361]

1713303361

[tobsnn]

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!

Thanks for the update. Bright light always attracts big moths.

Not just focusing on big price predictions before launch insteat of talking about ddos security on launch and we would had hit a wonderful start. Now that we are aware of the envys, we know what we are dealing with. We a entering/disrupting a real real big business, so there will be challenges like this, which, all the way down, will be handled great by community and lisk itself. Like you said

We will fight for Lisk and our vision, the vision that everyone has unlimited access to all kinds of applications from any device they want.

[LiskHQ]

Stuck trying to move $LISK?

Use this WORKING wallet mirror

TIPS appreciated - LISK 14007737956546258989L or BTC 1A5zBffD75H2kFo4F147xTg6FKvkfZ6Znx

Both Mac and Docker did not work for me so i stood this up for the community on a linux server. I'll keep it up for 24hrs hopefully DDOS will be over by then. Takes about ~40min for a tx to show up on Poloniex. Use at your own risk, no support provided, and all that jazz.

danosphere is a well trusted member of the forum and also a respected member of this forum.

dunno how trusted these nodes are , i mean the creator danosphere is trusted but can someone possibly snoop in on it? not 100% certain

also please whenever someone quotes another user, click the post to be lead to their original post, someone could easily edit the post when quoting someone else and try to trick, so for safety always follow the quote to the original post

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.

[Vega]

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.

[LiskHQ]

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.

[wizzardTim]

6th worldwide in coinmarketcap.com

And it's only the beginning  

[Reez]

Still waiting for confirmations.

Do i need to do something with docker to sync the wallet?

[uploadgod]

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.

Now I see it! How much time it takes? Thanks

[blockexplore.in]

Please vote for
blockexplore.in   3421883776008210770L

For delegate.

Our team will be building some dapps for games that utilize lisk.

Thank you.

[LiskHQ]

Still waiting for confirmations.

Do i need to do something with docker to sync the wallet?

Please read this:

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.


https://blog.lisk.io/lisk-launch-post-mortem-what-went-right-what-went-wrong-65fdb1fc8dde#.wf8kng1t9

[LiskHQ]

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.

Now I see it! How much time it takes? Thanks

1 confirmation is 10 seconds. 303 confirmations about 51 minutes.

[bigs21024]

simple i dont need all the crazy answers i just want to get my coins and a working wallet

[jhamis]

Guys, I'm having a problem with the web login since yesterday. Doesn't matter which one I use (login.lisk.io, login01.lisk.io or login02.lisk.io), the same thing happens: I send my LISKS to Poloniex, then it keeps coming back to my balance, and then going on the transaction again... it keeps happening and I don't get any confirmations.

If I log out, the transaction is gone and the LISKS are back in my balance. Can anyone help me, please?

I suspect it is either Ddos attacks or too many requests per node and they are not going thru , have far up the list have you tried?

the more people trying to request actions on a node the busier the nodes and what seems to be the less liklihood of the transaction going thru currently , either by an over load of requests or ddos, technically the same thing, althou one is legitimate requests and one is 10's of thousands of fake requests .

how many different nodes have you tried? the most used ones will likely be the less likely to work as they are the busiest

I've only tried those 3. I wasn't sure if the rest of the list was valid, since the Lisk Team didn't tweet it. Guess it was unofficial, like the rest of the nodes thrown up here in the thread.

I used a 3rd party node, but from a trusted member of the forum, i don't know how safe it is all i can tell you for sure it is worked for me over 12 hours ago

Stuck trying to move $LISK?

Use this WORKING wallet mirror: http://107.170.93.237:8000

TIPS appreciated - LISK 14007737956546258989L or BTC 1A5zBffD75H2kFo4F147xTg6FKvkfZ6Znx

Both Mac and Docker did not work for me so i stood this up for the community on a linux server. I'll keep it up for 24hrs hopefully DDOS will be over by then. Takes about ~40min for a tx to show up on Poloniex. Use at your own risk, no support provided, and all that jazz.

danosphere is a well trusted member of the forum and also a respected member of this forum.

dunno how trusted these nodes are , i mean the creator danosphere is trusted but can someone possibly snoop in on it? not 100% certain

also please whenever someone quotes another user, click the post to be lead to their original post, someone could easily edit the post when quoting someone else and try to trick, so for safety always follow the quote to the original post

Thanks for your help, man. Appreciate it. I don't trust this 100% but I understand your point. I'll wait for the official wallet to work properly.

[DarkTanner]

 #22222 post 

GO LISK

[X1235]

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.

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

[Vega]

One more thing, that I find interesting.

Most of the potential delegates have their nodes up already. Most of them have web UI enabled, at least some of them with SSL installed.
I myself had three nodes up 20 minutes after launched (and still do), with domain, SSL and everything.
But for one we didn't want to share the addresses that much, don't wanting to be DDoSed, also you can't really know what and who you an trust yet. So we had tons for serves, and web wallets you just didn't know about it or been able to trust them.

By the way this is how and why some were able to send coins without problem while everyone else was struggling. We spent the last two months learning about Lisk, we knew what to do. I think this is more than fair. The better informed you are the best position you are in.

[Hollowman338]

Just remember for how long eth was around 120-200k satoshis.

That's in the front of my mind right now. The question is, how long will Lisk sideline?

The Ethereum team actually made a very smart move by structuring its team as a full-fledged startup. They've been able to reach out to startups interested in adding blockchain functionality to their gizmos on a relationary basis: startup to startup (so to speak.) They clicking with real startups like Augur and The DAO is the main reason behind ETH's post-sidelining pump.

At this point, the real risk - and the real opportunity - sinks in. Right now, Lisk is something like a decentralized marketplace. All the advanced features are nice, but nothin' makes a platform go vroooooom like a "SUPER BEST SELLER!!" emerging from its ecosystem. Folks like nothin' better than to hitch their wagons to a star.

This point is where Lisk's lifecycle gets really interesting...

First off we have to shake out the ICO puddle jumpers.  Once those retards get their meager profits and run off to lose it on shitcoins, we can really take off.

[ed101]

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.

[etoque]

I seriously don't understand this coin,what is suppose to be the client ? The docker ?

[rezilient]

Oh man, i've got a problem.. i cant send any lisk from any of the login.lisk.