Please note that we don't support early trading and if you get scammed we can't help you out later. Early trades are all at your own risk!
As the ICO was a huge success, would you use some of that money to support the market when its listed - (to protect from investors from the early dumpers/market manpulators?) No, we are using the money to actively developing the platform. Not to play the markets. |
|
|
|
|
Please note that we don't support early trading and if you get scammed we can't help you out later. Early trades are all at your own risk!
|
|
|
|
Gibt es Neuigkeiten, wenn man bei der Facebook-Kampagne mitgemacht hat? Bekomme ich noch Bescheid oder muß ich aktiv was tun?
Alles wie gehabt. Die Teilnehmer werden über die E-Mail-, die Social Media- bzw. über die Bitcointalk Accounts von Lisk kontaktiert. Wenn Du also erfasst wurdest, bekommst Du rechtzeitig bescheid. Ungefähr 'ne Woche nach launch.  Bedeutet das, daß Joel in Zukunft die Fragen in den Threads, Chats, Foren usw. beantworten wird?
Sieht man Max und Oliver dann weniger oft?
Community Pflege ist extrem Zeitaufwendig. Allgemein wird man uns seltener sehen, aber ich werde natürlich immer mal wieder vorbei schauen. |
|
|
|
Wish I knew the reason for the surge in interest in XCR - over 6000 sats and 64 BTC volume on Polo, also 2900 sats and 16.8 BTC volume on Bter. Crypti does offer the same features as Lisk without the inflation, so maybe one or more people want to continue on with it as an alternative platform given the huge interest in Lisk.
If that is the case he should contact me. |
|
|
|
I hope the problem is in those extra spaces, yesterday I had the same issue but when I tried to log in again the addres was correct so thought it was my mistake
After more than two years experience with brain wallets I can tell you it's always the same problems. Your passphrase gives the wrong address? -> typed or copied it wrong Copy pasted your password but doesn't work? -> extra space was copied Someone stole your coin? -> didn't random generate your passphase did you?The same three problems over and over and over again. We will provide a fix for this by only accepting passphrases which follow the BIP39 format. This way people can't use weak passphrases anymore. (Only in the UI of course, if people use the API calls we can't do anything) |
|
|
|
Ok! I tried my passphrases again (I have 7)
First 3 were ok but the other 4 showed me a different address.
Then I entered again and the addresses showed were right.
So... or I misstyped or im getting crazy. LOL
You misstyped. So all 7 addresses were the correct ones? Good. |
|
|
|
Guys I'm having a strange problem, I've made 4 exchanges during the ico, I've tried the 4 passphrase on the main site and I log in perfectly.
Today I was trying again my 4 passphrase, but after I set one of them I logged in, but the Liks address was different from the one I've in the TXT and in the ICO page.
2 out of 4 gave me access but the address was wrong, different. Of course the passphrase are right, and I've even a screenshot of them, so no changes have been made to the txt file, screenshot and txt have same information. Now after another try one of the 2 access gave me the right address. But one of them is still giving me a different address. I've already opened a support ticket, but anybody have the same issue?
Yes... when I enter my passphrase happen the same to me. Different address! :/ Splatters, I already answered your ticket! Please come back at me ASAP. Mrmoney2, for 100% you saved the wrong passphrase. Open a support ticket immediately and we will reset your passphrase. So you can generate a new one. |
|
|
|
A quick update regarding your attempts on logos.  Right now we don't have access to the ICO money. Legally (escrow terms) we can get access to it after the first Lisk block was forged. Due to tax reasons however, we will only have access to it once we registered the Lisk entity as a non-profit organisation. This is a process which still takes several weeks. Once we have access to the money we will hire a reputable and excellent design agency to do a complete rebranding (logo, website, client, mobile client, media kit, design guidelines) with an even better UX than now. So this is being taken care of! We will come up with a new logo and design. Thank you for your concerns! Feel free to create a thread on our forum and do brainstorming there. So that the design agency can go there later and maybe get a few ideas. Thanks!
|
|
|
|
How to Generate your Lisk ICO PassphraseEveryone who didn't generate the passphrase yet should take a good look at our new guides!- Video Guide
- Written Guide
- Image GuidePlease generate your passphrases as soon as possible! Some people may have made an error in copying their passphrases, they may skipped the first or last word or letter. Will there be a way or a tool to validate the saved passphrases before launch? The video describes a method everyone can use now. But Olivier is working on a validator. It will be released soon. |
|
|
|
How to Generate your Lisk ICO PassphraseEveryone who didn't generate the passphrase yet should take a good look at our new guides!- Video Guide
- Written Guide
- Image GuidePlease generate your passphrases as soon as possible!
|
|
|
|
Danke gibt es auch auf Deutsch mein Englisch ist nicht so gut
Was thandie schon meinte. Unseren Klienten gibt es auch auf Deutsch. |
|
|
|
The Lisk Team is Expanding - Introducing Joel Fernández as the Lisk Community Manager!Now that the crowd-fund is over we can concentrate on hiring a great team with valuable skills. The first one who will enrich the Lisk team is Joel Fernández. As of now he is the official Lisk Community Manager and will act as the bridge between the community and the Lisk core team. Read the full blog post about Joel's tasks at Lisk now!PS: Joel is "Bigcabrito" here on Bitcointalk.
|
|
|
|
The Lisk ICO has now ended with a total of 14,009 BTC and 80 million XCR exchanged!As of the 21st March 2016 the Lisk ICO has now officially ended and wow! It was a really intense ride these past 4 weeks! The crowd-fund has been an enormous experience for us, with a now burgeoning community, and very substantial amount of funding raised, we are very much looking forward to working on the ecosystem over the next years. Read our full blog post here!
|
|
|
|
Fees can be adjusted. It's pretty evident that fees had been determined in anticipation of a much lower initial market cap. I'm only guessing, but I'm pretty sure if the ICO would have rased 1000 bitcoin Max and Oliver would be very happy with the succesfull fundrasing round. As a matter of fact if you read through the Lisk page there is much content that is off-kilter in light of the amount raised and the initial market cap. Thinks need adjustment, initial plans need revisions and countless other stuff need rethinking for this new reality. Addressing the high fees are I'm sure somewhere on their to-do list, around #157. Spot on. |
|
|
|
Answered. In general, serious discussions should all happen on our own forum! Please move over there guys! |
|
|
|
Someone fixed it and now it is correct. We are place #19. Rocket.chat? Slack is industry standard. 21 uses it, slock.it uses it. why does LSK not use it? Some people belive in owning their data instead of relying on a third party. That's one reason. The other is that on Slack only the last 10,000 messages will be saved. If you have 1000 users you will always end up with empty rooms. In fact our chat already have nearly 900 users and over 20,000 messages. Now that you've brought up the subject, is there a Developer's Guide?
https://lisk.io/documentation?i=lisk-docs/READMEI'm a full stack developer and a early investor (2nd week). I like Lisk because of JavaScript as main language. I have just started looking at the dapp development, noticed some serious security concerns with dapp development.
My understanding with dapps is (correct me if I'm wrong), a dapp is hostable component that exposes an http external api and is capable of doing some transactions (withdrawals and deposits). Every dapp can be hosted within in some sidechain. Users can access dapp functionality with the help of exposed api by passing secret and transaction info. It means you have to pass your pass phrase to every dapp you want to do a transaction lets say a withdrawal (paying to dapp owners).
Apple, Microsoft, and google stores are centralized. Every app has to go rigorous review process before getting published in stores ( I published few apps in google and windows stores). The review process mainly includes scanning for malicious code that exposes user phone to external attackers.
Situation 1:
Lisk has no such review process but the code can be viewed by others. Lets say if dapp included with some malicious code that records pass phrases somewhere (not in the dapp), lisk-cli just creates a foundation base for dapp development and users extends it with their own api. How lisk prevents user from accessing dapp and removes from store if malicious code found.
Situation 2:
Lisk dapps and their sidechains can be hosted by third party entities. Lets say owner setup two VMS. One with actual sidechain with clean dapp code internally and installed a reverse proxy on another VM(that sits on external point and forwards request to internal VM that hosted dapp). The reverse proxy receives the request from user first and records pass phrase and then forwards same request to internal VM without modifying request headers.
Situation 3:
Man in the middle attacks.
If the dapp owner not hosting sidechain with SSL, How Lisk ensures user data not compromised.
Just wondering how lisk handles these situations and prevents owner from misusing pass phrases. Last year, I encountered similar issue with NXT and lost around 10K coins. I used a remote nxt web node to check my transactions frequently. I suspect they recorded my pass phrase and transferred my 10k to theirs account.
I think users shouldn't be forced to send pass phrases to dapp owners, its like sending your BTC private keys to others.
@ 1: We are in a decentralized environment. Any kind of censoring by the devs will hurt lisk. The only way is a reputational... removing malicious code will probably not be possible. But who knows, maybe the reputation system can offer that.
Ok, I agree but this doesn't mean system should be infected with all malicious dapps. Reputation wise its not good. Still the dapp has to communicate with mainnet to keep consistency. I think Lisk mainnet holds meta information about each dapp. This should be enough to record info about dapp. Now the question is how to warn the user about that particular malicious dapp .
I'm thinking few alternatives, will present them in coming posts. @ 2+3: you don't need to send your password to the server hopefully. You also don't have to do that in NXT. Just the Frontend needs it. I think Dapp UI asks for pass phrase, and pass same to server through api call or http post. its enough to capture pass phrase. Its not like Dapp UI (client face) directly talking to mainnet. it doesn't matter, Whether its UI or api all should go through http endpoints on the server. Please head to our forum, there were some discussions already and we are open to discuss it there. It just can't be answered in a good way in this thread. http://forum.lisk.io/viewforum.php?f=13If someone post it there, I will answer as soon as possible. Just very quick: Yes, there are some security issues right now. Especially involving the passphrase in dapps. Devs can either send the passphrases via an API though the network, or directly sign the transactions locally. The second option is more secure and our recommended way, but also slightly more complicated. Long-term we want that the user will send/receive LISK from the Lisk UI into/from a sidechain. We will concentrate on various security related issues in the beginning. As I wrote above, please join us on our forum. I think you would be a great asset to the discussions! |
|
|
|
@LiskHQ I have a question for u, i've sent btcs 40 min before the end of the ICO and up until now my funds haven't arrived to LISK ICO exchange nor back to my wallet. So where r my funds stuck? Thx
Please open a support ticket on http://support.lisk.io/. |
|
|
|
ico is finish but my coins keep on being less everytime i check .. why?  ? same as mine at first it was 177 then 135 and again 135 and again 133. i wonder what happens Oliver did a last complete re-scan therefore it might be that the numbers adjusted slightly. Please note that the bonuses are not counted in yet, so the number will change once again. It's just an estimate, not a promised number. Thank you. |
|
|
|
A few important things for now:General:- We currently plan to launch on the 11th April. This is not the exact date, just an estimate. - At launch we will provide a client to access your LISK. - All support enquiries please via our support center! - I will update the BTT OP this evening with all important information. ICO:- The given BTC amount on our website is an estimation. Some transactions were after the time limit, so they will be refunded. The collect amount is more like 14,009 BTC. - We will release the exact ICO numbers (total collected, satoshi price, number of participants, number of exchanges etc..) end of this week. It takes a few days to confirm every transaction by hand. - We will also provide a list with all exchange IDs, the generated LISK address and its balance next week. So you can see if you are included. - I will talk with Oliver and our advisers about what we do with Lin's XCR deposit. We don't want to make a crude statement. Lisk Trading:- Please don't buy any LISK in this forum. The owner can reset the passphrases by simply open a ticket on our support center and provide us with his email address and exchange ID. We check the data and if all is good, we will reset the passphrases. Passphrases/keys:- You have time to generate your passphrases until the 4th April! We will also provide a tool this week to validate if your saved passphrase is correct or not. - If you lost the passphrases please send us a ticket on http://support.lisk.io/. - We will provide a video and detailed instructions on how to generate your passphrases this week. - Everyone who generated a key and lost it, will also loose access to his LISK. - Everyone who didn't generate a key will be contacted 1-2 weeks after launch. He can then get his LISK via email. This method is not the most secure option, therefore please generate your passphrases ASAP! Also there will be a deadline after which the non-collected LISK will go into the bounty fund. Bounties:- We will provide exact bounty numbers next week. |
|
|
|
|
Show Posts
