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.
|
|
|
Lisk launch post-mortem: What went right, what went wrongYesterday, 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. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fcdn-images-1.medium.com%2Fmax%2F800%2F1%2AX-uYxrg2PMYks-bWX0Qeww.jpeg&t=663&c=GlJPbSidfklehg) 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!
|
|
|
Where Max, Joel ?
Answering questions all over the place. Am at my emails right now, then BTT PMs, then Twitter, then support center. I'm also working on an official statement.
|
|
|
It seems like funds from the advisor fund have moved and probably sold. Intentional or account compromised?
My guess would be that they had agreements with some of them to give them a portion of the adviser ICO funds in exchange for their assistance leading up to the launch. This is common practice for startups. They probably sent the agreed funds to whoever helped them. You should be able to see where the funds went in the block explorer and determine if they went to the Polo wallet or not. Yes. We have a few advisors which are not announced yet. They are big personalities in the blockchain industry and we will announce them at the best possible time (marketing-wise). This is obviously not at the moment. We needed to send the coins to them before any trading activity happened, in order to not get them into tax problems. The amounts were declared and sealed months ago. We will issue a blog post about the current situation this evening. There, I will go into detail about that again.
|
|
|
Also, when we are talking about the prices and dump, how much LSK was sold on Polo? Around 500k?
Well, you have close to 5 000 000 LSK on the sell side, so that's there. Plus, I have the suspicion, that this is polos wallet: http://explorer.lisknode.io/address/18278674964748191682LCan anybody confirm that by following a transaction he_she made? If it is, at this point, 20% of Lisk are at polo. Yes that's polo wallet Good to know, thanks. That's quite reassuring, actually. If you listen to the screaming in here, you would think that the overall lisk at exchanges was closer to 5% and the really big dump was yet to come. Could still dump, once every lemming is able to access his_her lisk, but it's going to be smaller. Phew. VOLUME (LSK) 149,399,083.55039775 LSK transferred within 20 hours from 17706 transactions in 3326 / 4983 blocks Everyone who wanted to move their LSK already moved them.
|
|
|
please can someone tell me what was the last announcement from management about what is happening?
We are preparing a detailed report for this evening (UTC). The whole blockchain seems to be stuck for over 6 hours now, so the whole LISK infrastructure is down.
No, it's not. It's working just fine. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FKphsI4m.png&t=663&c=znEanLfEbugzxw) The Lisk network is running. It seems like the only pause was a few hours ago for like 20 minutes. It automatically recovered as intended. It is working good again since then. One problem currently is the 0 confirmation problem. We are investigating the issue. It is either a UI glitch or a problem due to the heavy load of individual nodes. Best to restart your node and check again. Or access your account on another node. The LSK are NOT lost!
|
|
|
How com the dev team cant sort out a working online wallet let alone a desktop 1 yet a community member can knock up a working 1 fine!!?? Can anyone from the team comment on this? is it safe to use?
We setup a cluster consisting of several nodes with SSL encryption. This takes a while to configure. Additionally, our official logins are being heavily accessed and DDoS'ed. Next to preparing nodes we also fixed the binary installation method which didn't work because downloads.lisk.io also was being DDOS'ed. It's working now. We also worked on the Docker version which is now available for Windows, Linux and Mac OS. So now we should have all three methods working. More backup cluster will come.
|
|
|
LiskHQ canyou please confrm? It's not secured with SSL. So I won't recommend it. You can install Lisk locally in like 10 minutes with 3 commands which you simply copy&paste. You should do this.
|
|
|
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. Man I dont have Linux and you keep recmmending to install the client locally Do you know how brazen and impolite that actually is? I'm seriously about to smash my computer You can install Lisk on Windows, Linux, and Mac. Use this: https://lisk.io/documentation?i=lisk-docs/DockerInstall
|
|
|
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.
|
|
|
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.
|
|
|
Running well in my VPS, although I had to tweak the installLisk.sh script to bypass a couple issues. Probably related to the downloads server being hammered.
Yes, it can't pull the version because of the DDOS. Glad that it's working for you.
|
|
|
We checked our server logs. The web login and Lisk chat are getting massively DDOS'ed. They both are offline or unresponsive.
Oliver is currently preparing the docker version!
Isabella is mitigating the connections on our web login. Currently there are 50,000!
|
|
|
|