Topic: [ANN][LSK] Lisk | Blockchain Application Platform for JavaScript Developers - page 2168. (Read 3074169 times)

Fourth week bounty summary

I just wrote down all Facebook likers (484 stakes), Twitter followers (911 stakes), Newsletter subscribers (1675 stakes), Signature participants (281 stakes) and translators (53 stakes).

Week #1 Values
Week #2 Values
Week #3 Values


IMPORTANT! This is the last week (2nd March - 9th March) to receive a bounty stake!

The number of participants grew extremely big, we didn't anticipated that. Therefore this will be the last week of the bounty campaign. After this week I won't count new stakes anymore! I will distribute the bounties amongst all those who participated after Lisk has launched.

Here you can view the signature stakes for all weeks. The other lists won't be released, because there exists a privacy conflict. I saw that recently some users only wrote into this thread that they participated in the signature campaign. You need to send me a PM! If you are not on this list, please send me a PM until the 4th March! After the 4th I will not add you to the 4th week list!

Thank you very much.

Nice LISK I joined the company's signature

Wow, lots of pages and what looks to be a smoothly running ICO.  Looking good Lisk!

I do agree with this. it should be percentage not constant. Constant will disrupt free economy as lisk goes up.

Noooo my Lisk is keep going down. Although I have been smart and bought a lot of xcr when it was 700 satoshi or something, I still feel bad my Lisk going away

Great job! So if lisk will cost 10 usd in the future, transaction fee will be 1 usd. You guys rock! "Now it's very easy", lawl

Sound advice I will try to heed.

MalReynolds your enthusiasm is palpable, but you might want to temper it a bit  .

In asymmetric cryptography (public-key cryptography) a pair of keys is used (public and private). Both keys are generated simultaneously.
With the "first transaction" you mentioned, the public key is not generated, but firstly stored in the blockchain.

I was a little surprised to see a public key along with a passcode and Lisk account number from my XCR deposit.  Is this public key the same as the one in discussions going like "please send me 1 XCR so I can get a public key" ?  Will we need to do a "first transaction" in our new Lisk accounts in a few weeks to generate a new public key, or is the one assigned at the ICO site a good public key forever?

As stated, a wallet wouldn't do you much good right now. Although I assume you know this is a fork of XCR, so codewise a wallet and all of those nice things exist, they don't need to be coded from scratch.

I do have a question though for the devs here... around when do we have to get our keys by? Is there a deadline, or can we just wait until the wallet is ready to go? I assume we can just get them whenever we want, but wanted to doublecheck.... I haven't gotten all of my keys/passphrases yet (and probably would be paranoid about losing them, so figure I'll just wait).

Lisk is currently in ICO phase. Wallet will be available with main net start.

What about reading the homepage https://lisk.io/ ?

Edit: You can also try out the web wallet (testnet!) https://login.lisk.io/

Without a wallet? Thats what im looking for.

@Max
 You can please ask the exchange again?

Otherwise I will wait a week...

Perhaps we should make a little "publicity" for bter.

Go to http://ico.lisk.io and use the exchange there.

Hey@all,

i want to change some btc to Lisk.

Where can i get a client for windows? That link https://downloads.lisk.io/lisk/main/lisk-0.1.1-Darwin-x86_64.zip on the page don't works.

Can someone help?

A great accomplishment!  And to celebrate, I'm gonna drag back up a post of mine from page 89 that nobody responded to at all.  

The subject is latency: https://bitcointalksearch.org/topic/m.14038854

I've been thinking about this some more.  The post above discusses my desire to say something specific in the whitepaper on the maximum ISP latency acceptable for running a Lisk mainchain node.  (I am worried we are going to have a lot of disappointed Active Delegates when they realize they can't run a Lisk mainchain node from home on their spare PC and they actually have to rent a server at Vultr for $5 per month).  I also ask for confirmation that sidechains can run at slower block times that the mainchain, and if that alone would allow the use of slower, high-latency ISPs.

These are important and hard questions that nobody really knows the answers for yet.  One of my first goals when Lisk goes live with 0.5.5  is to set up some cheap sidechain nodes and run some timing experiments to get some answers.  I want to give my future sports dapp customers great service!

However, I've been thinking about this some more and I have more questions.  So here goes.

First off, are we going to start Lisk on version 0.5.5 software and not 0.5.4?

Second, what is the specific reason we are going to launch Lisk with a 10 second blocktime?  Sure, that's the number Crypti worked hard to achieve.  Sure, it is technically cool and impressive.  Sure, it was originally intended to allow ultrafast merchant confirmations.   But seriously....why?  We are changing many things in Lisk that were originally done a different way in Crypti.  Why not its blockchain speed?

Lisk is not promoting itself as a "coin for commerce" the way Crypti started out, so we don't claim fast merchant confirmations as a major selling point for Lisk.  Also, most of the Lisk blocks are going to be empty - way above 90%, I'll bet  -  and piling empty blocks on at 10 second intervals produces nothing but blockchain bloat.  Sure, Lisk has an efficient blockchain structure compared to Bitcoin or Ethereum and so has less bloat per block.  And Lisk can handle large blockchain files just fine.  The Crypti chain is doing fine at over 2 million blocks in length after two years.  

But....if we launch with a Lisk block time of 20 seconds instead of 10 seconds, there would be no merchants saying we've caused them headaches by doubling the confirmation time.  We would also cut our bloat growth rate by 50%.   We would also have twice as long before bloat becomes an issue of concern... which it will, eventually, and we have to have the inevitable blockchain pruning discussion.   So why not go from 10 seconds to 20 seconds for Lisk blocktime?

And once we start saying a Lisk blocktime of greater than 10 seconds is OK - why not set the official Lisk blocktime as necessary to maximize high-latency home ISP participation by Active Delegates?  Maybe that's a blocktime of 15 seconds, maybe that's 30 seconds, maybe that's a full minute of 60 seconds.  Logically, a 60 second blocktime should be able to handle 6 times higher latency delays than a 10 second blocktime, right?

All I'm saying is that Lisk is an effort to start over and correct many of Crypti's deficiencies.  Possibly the technically impressive 10 second blocktime may be one of those deficiencies.  We have a few weeks before this Lisk train leaves the station and goes rolling full spead down the track.  We should talk about just how fast that Lisk train is going to go.

I agree. But after recent discussions with developers, we need to improve our docs first. 2-3 weeks after launch I think we have improved them quite a lot already, so we can start to promote within the JS community.

We will definitely directly target those groups. Also by going to Node.JS and JavaScript conferences.



We will start with the full client and probably in the end of April release the lite client. This gives us enough time to prepare everything.

I had hoped they filled it by now. I had that problem like a week or so ago.

You can chat with a rep to cancel the order if you want (use their chat and ask for English Lilly, unless you speak Chinese), although then it's basically just folks trading a coin that they may or may not be able to
withdraw at a later time.

There will be downloadable full and light clients in addition to the Web Wallet (https://login.lisk.io/)

See:
https://lisk.io/download