max said
Regarding real-life meetings:
- Every month I'm at the local startup events in my city, even had a presentation about Bitcoin and Lisk there.
- Every month I attend the local Bitcoin meetup in my city, which I started with two friends.
- In 10 days I'm in Berlin attending a networking meeting at which we (the whole conference) will also talk with Edward Snowden via a video conference.
- Next month I'm in China attending and speaking at a Blockchain conference.
- In July I'm in Russia for private reasons, I will definitely meet up with a few guys in Moscow.
- In September I'm in Frankfurt speaking at a professional conference about Lisk and blockchains.
I'm sure this is enough. Wink
yolo nom nom list train wont stop
Topic: [ANN][LSK] Lisk | Blockchain Application Platform for JavaScript Developers - page 1200. (Read 3074324 times)
May 25, 2016, 11:22:55 AM
May 25, 2016, 11:21:37 AM
I set up lisk faucet and lisk wallet with SSL connection!
Faucet works fine! Enjoy!
You can see my topic here
my delegate name is grumlin address is 16979707772780220012L
Vote for me in mainnet! Thanks!
p.s. I write script for delegates help, can use it
ADD 50 LISK on FAUCET ELSE! ENJOY!
Faucet works fine! Enjoy!
You can see my topic here
my delegate name is grumlin address is 16979707772780220012L
Vote for me in mainnet! Thanks!
p.s. I write script for delegates help, can use it
ADD 50 LISK on FAUCET ELSE! ENJOY!
While I cant recommend non-official wallets.
I used grumiln's wallet with no issues, and moved my coins no problem.
May 25, 2016, 11:20:59 AM
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/
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.
May 25, 2016, 11:19:14 AM
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/
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
May 25, 2016, 11:19:03 AM
My dividend node needs your support.
My plan is to have a bonus:
50% for dividends to all voting to my node.
Another 50% for node server spending to maintain and support the development of DAPP.
My node name: #196 liskyun
Thank you very much for giving me the vote.
My plan is to have a bonus:
50% for dividends to all voting to my node.
Another 50% for node server spending to maintain and support the development of DAPP.
My node name: #196 liskyun
Thank you very much for giving me the vote.
May 25, 2016, 11:18:51 AM
What is dao?
May 25, 2016, 11:17:09 AM
May 25, 2016, 11:16:12 AM
Interesting depth chart. Sell orders real thin for the volume. The red goes up to 93000 sats and is only about 1000BTC up to there.
Now I'm just wondering how low will it go before I can buy some Lisk. Traders are still cashing out their profit from ICO.
Yeah, tough call. I bought back in a bit to be safe. Still got my panic/flash crash buy orders in place just in case, but 2.5 times ICO price seems a decent entry point too. To put in perspective the market's likelyhood of seeing higher prices, 1000 BTC would move ETH from .0275 to .0283. And that happens in seconds. Whether or not Lisk is comparable to ETH, just a fraction of the speculative action.... would be nice for anyone entering now.
the question is more who gonna put 1000 btc after that such desperate fail.
they only proven they're incapability to make successful coin
transaction are working just way too slow for my taste, but it's there
now if the same was true at the beginning would have been better...
If I hold how long before I make a profit. I invested 3BTC in lisk yesterday
think LONG and prosper.
May 25, 2016, 11:14:36 AM
May 25, 2016, 11:14:00 AM
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/
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.
May 25, 2016, 11:13:53 AM
Don't use it.. Keep ur safe on #Polo and #Trex...
what about BTER? any news?
May 25, 2016, 11:12:40 AM
what about BTER? any news?
May 25, 2016, 11:12:26 AM
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/
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
He is a member of a team. Just check his previous posts
Ok many thanks, so please which link should I use now to access my lisk via webwallet?
May 25, 2016, 11:07:33 AM
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/
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 can confirm the Lisk team nodes are correct, I a not saying dont use the other two, I am sure they are honest community members trying to help, i am just saying be cautious !!! For now its strongly advised to use the lisk provided nodes
May 25, 2016, 11:06:53 AM
thats make us clear now, why i'm failed installing binary on raspberry, but its success now, moonnn
muthafukka ddos attack, go go lisk nom nom , shining crytaLISK from fabula nova crystalis
muthafukka ddos attack, go go lisk nom nom , shining crytaLISK from fabula nova crystalis
Yep. If somebody wants to be critical, there is just one point in my opinion: They didn't anticipate such an attack. But all the other accusations are bullshit. Plus: Now it's back to normal and for the dramaqueens it's time to calm down. Price will reflect that.
May 25, 2016, 11:06:47 AM
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/
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
Attesting.. Grexx is a delegate - mainnet confirmed I believe? And the top lisk logins are hosted by the dev team.
May 25, 2016, 11:06:01 AM
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/
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
He is a member of a team. Just check his previous posts
May 25, 2016, 11:05:53 AM
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/
https://lisk.host/
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/
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/
https://lisk.host/
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/
Thats the ticket.. Thanks Grexx
May 25, 2016, 11:05:22 AM
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/
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
May 25, 2016, 11:04:00 AM
Lisk really pumping now 
Jump to: