Quote from: GreXX on May 25, 2016, 04:20:59 PM

Quote from: Transpotime21Bus on May 25, 2016, 04:19:14 PM

Quote from: GreXX on May 25, 2016, 04:14:00 PM

Quote from: Transpotime21Bus on May 25, 2016, 04:05:22 PM

Quote from: GreXX on May 25, 2016, 03:48:19 PM

Again, from my perspective, the network has been running great aside from one small hiccup this morning that Isabella already fixed. We have seen huge volume on the network and it's still running and pumping out blocks. The ONLY problem people have run into is the main wallets being down or not properly synced. The issue here is that once they are out of sync, it can take a while on a reload to sync back up and if you are seeing huge connection requests, it's just slowing those nodes down.

Multiple solutions and community run nodes have been posted here and as long as you are using an HTTPS node, that means the connection is using SSL and the connection is encrypted prior to sending your nodes information. Does it mean you are 100% safe, probably not, but it is considered by the industry to be standard encryption practices and generally safe.

You can use the network monitor here: http://explorer.lisknode.io/networkMonitor to see active nodes on the network (even if they aren't in the 101 it's OK). You can try accessing port 8000 on those nodes and see if they have SSL enabled, and if they do, they should be safe to login to for limited use while you wait for the official nodes to be repaired and get through whatever is happening.

We also have several trusted community members who have offered up their servers for access, here is a current list of some available wallets copy/pasted from Lisk Chat:

Official Run by Lisk Team

https://login.lisk.io
https://login01.lisk.io
https://login02.lisk.io
https://login03.lisk.io
https://login04.lisk.io
https://login05.lisk.io
https://login06.lisk.io
https://login07.lisk.io
https://login08.lisk.io

Community Delegate Run Servers

https://lisknode.grumlin.com
https://main.liskafrica.com/

Keep in mind some of these are not at the correct block height or are stalled, so check the blockchain within the wallet to see if it is moving and if it is at the current block height. You can get the current block height from the top section of http://lisknode.io/ . If a node isn't synced up to the current block or is forked, your transactions either won't show, won't go through, will never get to the exchange, etc. The node has to be synced to the correct block height in order to have the transactions work smoothly.

The best explorer to use right now is here: http://lisknode.io/

You can also see additional delegate focused tools here: https://lisktools.io/

Are you a member of the team, how do we know you are genuine and not a scammer? Please can someone confirm

I am one of the original 5 members of Crypti and I am in no way officially affiliated with the Lisk team. I am however a supportive community member and have been around this community and the Crypti community for a long time. I totally get the nervousness and understand if you don't trust people here, it's a good practice to uphold, but I'm here to help.

The community delegates listed are all running SSL on their servers which is about as secure as we can get right now. It's the same setup the official wallets are using. I'm not saying it's 100%, there are always weird loopholes and zero days no one knows about, but they are more trustworthy than a random crap shoot and are part of the delegate group I am personally voting for to run the entire network.

Thanks GreXX which site can I use now for the non technical people to access my lisk as https://login.lisk.io/ when i click the send botton is not working

I would say start with Grumlins as he has been around the community a long time and many have had success with his node.

https://lisknode.grumlin.com/

The official wallets appear to be hit or miss right now.

thank you so much!!! yes https://lisknode.grumlin.com/ is working for those who are still trying...now all together and positive we make lisk to go up where it belong!!!