http://www.euroforum.de/blockchain/blockchain-crowdfunding-dezentralisierung-list-max-kordek/

Ich werde am 19.09.2016 als Referent in Frankfurt beim EUROFORUM mit dabei sein und einen Vortrag über das Thema "Blockchains außerhalb des Finanzwesens; der nächste Schritt für das Internet?" halten.

Yes. The bonuses will be applied before launch.



AFAIK there are three ways to do it.

1. Oracle

You have an oracle (outside, disconnected with the dapp) which is giving you a random number. This could either be something centralized which uses random() or something decentralized in which a bigger number of users state a number from which a random number is generated.

2. User input

If you have a dapp with 2 users which are "competing" against each others, then each of them could state one random number. The final random number could then be generated out of this.

(e.g. User A: 5, User B: 7 -> 5+7=12 -> 12%10=2 -> 2 is the random number) (I don't know if this is mathematical secure, or if the distribution is "unfair". It's just an example)

3. Block IDs

You could also use block IDs of the future.

At time 0s you need a random number. To get this random number it takes 1 minute (6 block IDs). At time 60s you can then continue with the dapp.


These variations are obviously not good enough for poker. Poker is extremely hard to do, you could check out Pokereum how they are doing it. For dice or slot machines these are legit methods in my opinion.


Later: Buy a dapp with LISK

Now (and later): Internal dapp functions cost a fee (e.g. send a message for 1 LISK). All sidechain forgers will get 100%-x% of these fees, the dapp owner gets x%.

No. All commits from the 19th and 20th April are the necessary changes for dapps with the DB switch.

https://github.com/MaxKK/guestbookDapp/commits/master


However, a few weeks ago Oliver fixed a bug in the Dapp SDK already, so at that point of time the dapps were not compatible anymore.

Send me a PM after you have done so.


Right now there is no collaboration between Lisk and other crypto-currency projects. Status on developers is still the same.

That is the first day reward. It will be distributed later on. (200,000 LISK out of our own private pockets to the first day investors)

^ push for visibility.



We are still preparing them. Because client translations are also in this category, they will take a while longer.



It is possible, but would make things more complicated. We will do it the same as last time. Let more people slowly into the top 101.

101 votes limit should be integrated in 0.2.0. Basically, it should also be integrated in 0.1.4 already but with a limit of 104 votes. Let's write on the Lisk Chat about that.

BIP39 will be enforced yes. With the English word list.



I don't have any details. Not sure what he is talking about.



All important announcements are in the OP and our blog. Best to check out our blog once a day than this thread.



I will probably release more information in 1-2 weeks. These bounties are tailored for developers.

This week. Back end changes are finished.



Nothing to be ashamed of! I think many are envious.

This is possible. But we don't recommend it. The mainchain needs to be as secure as possible, i.e. fast VPS/server with DDoS protection. You can run one (or more) sidechains on your Raspi.

What do you want to see in the OP? I keep it up-to-date all the time.

I will try my best!


Hehe, thanks. I will try my best to get back to it. At one point it was just too much to answer all these requests here on the forum. That alone was a 24h job.

However, if I see serious posts I will answer them. Best if you guys PM me with the post, so I absolutely don't miss it. There is so much spam here, I can easily miss a post from time to time.

No. The charter is nearly ready, need a few updates and explain it to Oliver. Then we may adjust it again after his feedback. Then we can do the next steps.

MalReynolds may get the joke without Google.

I don't study anymore. Oliver also isn't enrolled.

However, in Germany right now the university summer term just started and all exams are only at the end of it. That means around August/September. (In the winter term they are all in February/March)

1. We said estimations like "End of March. End of April". Now we have a date, because we are certain we meet it. It's exactly what you are asking for.

2. Which money? Everything until now is paid out of our own pockets. Before the ICO started and we knew how successful Lisk will be, we already spent about $8000. Now we come closer to $20000. We don't have access to any funding collected. There is still only Oliver, Joel and I in the team.

Joel: Doing everything associated with the community. Answering questions, preparing academy guides, sending the newsletters, publishing community updates, handling the bounties (I think over 10000 stakes) and so on.

Oliver: Is developing and optimising Lisk. Just in the last week til today he successfully migrated the codebase to a different database engine, and improved block processing efficiency ten fold (after improved syncing speed twenty fold before). Besides Lisk core development, he also updates (with every release) the explorer, faucet, lisk-cli, lisk sdk, binaries, docker etc. He also regularly updates the Lisk chat and is currently stress testing 0.2.0 while preparing the release of it.

Max: I fight with you guys. :p No honestly, I'm talking with a lot of people which benefit will only become visible in many weeks or months. But this is extremely important. Besides this I try to be as open with everything as possible. Preparing important documents for launch on the vision and further development plans. Checking the legal documents provided by our lawyer for the legal Lisk entity. Answering emails, interviews, and questions. Improving the Lisk front end. Taking care of financials and the numbers.

3. We recently hired a PR company which worked with many crypto-currency startups before. More news soon. Besides that with the release now on the horizon we will start the marketing machine again. I think the past showed we know what needs to be done in that regard.

May 24th is the first explicit launch date we gave yet. Our estimations were delayed, that's why they were estimations.



Yep. We knew of the concurrency problem all along, but the stress test really opened our eyes that SQLite is really much worse than we anticipated and needs to be switched out sooner than later. Regarding why Postgres, you should write Oliver a PM on our chat or here on BTT. 

No, he is not. If anyone is doing trades, obviously just with escrow.


I also think this is the case. Lisk is a substantial threat to many crypto-currencies on the market. It's not a threat to all the legit projects out there like BitShares, Factom or Ethereum. They profit from Lisk, as we profit from them. By bringing more people and progress into the space.

However, it's a threat to many smaller projects which are all just re-inventing the wheel and bring nothing new to the table. I think with the next bubble the legit projects will suck a lot of money out of the smaller ones.

At the end of the day all these controversies and sockpuppets are a complete farce, and everyone can see it. Especially after we release Lisk 0.2.0 this week.

Everyone who wants serious discussions come to our own forum or chat.

Nothing more than another security precaution. Many other projects used this word as well. IOTA, Ethereum. They all use it.

The forging rewards (inflation) are not "the only important new technical feature". Oliver worked on countless optimisations and other things which are 1000x more important and more time intensive. As Vega pointed out, everyone who wants to break Crypti at this point of time, can do so.

I said I will provide it at launch. What I can do is to make a forum post and add all the things we change there. And once we have the launch version I will publish the blog post as intended. Will do so once 0.2.0 is released this week.



You are right. 99% is yet to come. We have many years full of new features and dapps ahead.

The "12 word key" generated during the ICO IS your first passphrase. The second passphrase is optional and can be configured later in the client against a small network fee. The words in the "12 word key" are called mnemonics. The checksum makes sure that the specific format (12 words) are used. The generated passphrases during the ICO already follow this principle, which is explained in the BIP39 (Bitcoin Improvement Proposal #39).

So you don't need to worry about anything. All is OK. If you ask yourself why we do this. I saw MANY passphrases cracked at Nxt, because people chose easily passphrases. The BIP39 passphrases are extremely secure and uncrackable in the next centuries.



We thought that the Crypti code base would be more robust. We already implemented a lot of improvements and Lisk is not just a Crypti fork anymore. It's a completely new "beast" now.



Correct.



We successfully tested 3 full rounds with 50tx per block, i.e. 16200tx per hour. We are certain that later on there is much more upside potential. We are just taking the more reliable/secure route right now and set the limit to 25tx per block. The new version will be 0.2.0 because it's quite a big update.

Regarding the "buffer size" which is called payload in Lisk, I'm not 100% certain. Better ask Oliver later on the Lisk Chat or forum. However, a regular transaction requires 117 bytes (without 2nd passphrase). The payload maximum size is currently 1MB. That means (1024*1024)/117=8962 tx. This can obviously be increased. As I said, better ask Oliver for this.



You know it's marketing. Same as BitShares 100000 tps and in the end they can handle 1000 tps. Our numbers look small in that regard right now, but (1) much volume will happen on our sidechains only and (2) we will gradually increase our supported tps.