Thanks Poly#Crypto for the extensive breakdown. Much appreciated.

In the end, this is all a question of who is willing to do the hard work needed to get a job done. I would say despite our imperfections, Lisk is, and will continue to be the leading light in this regard.

Since the beginning of this year, the code base has been constantly and iteratively improved, to the point where we are now approaching the required stability in order to enable community forging.

To give a brief overview:

The numerous modules and logic that form the Lisk core have been (or are being) gradually refactored, or rewritten.

The various fork causes 1, 2 and 3, which have been holding back community forging are very close to being largely mitigated.

The peer to peer transport layer has been drastically improved, and I would argue in the forthcoming 0.5.0/0.6.0 releases, vastly more efficient than before.

The newly implemented "broadhash" implementation should guarantee much better block and unconfirmed transaction propagation throughout the network.

The test suite which guarantees stability, and prevents regressions between releases has been rewritten and gradually expanded.

This is all part and parcel of software development. In the end, we end up with a more efficient and stable product.

Getting to this point has required a lot of hard work and perseverance.

This hard work is not for the weak of heart, or mind.

Thank you.

Yes, all issues assigned to 0.3.2 milestone are complete.

Today, I am preparing testnet binaries for the community to test. We will announce as soon as packages are ready.

Start a new exchange.

Thank you ttookk

Blockr is currently behind the rest of the network by a number of blocks: http://btc.blockr.io/

We also are using them as our API service provider, so deposits won't show on the ICO site until they fix their nodes.

I am monitoring the situation, so will update when they sort their shit out (or we switch providers).

Sorry for the inconvenience.

Sorry but this is not true, nor so easy as you would like to think.

I therefore invite you to come to https://lisk.chat/, where I am happy to outline the changes we have made, plus the shear amount of hours and dedication required to get where we are today. GitHub commits are our friend in this regard

The BTC raised will be used for the development and marketing of Lisk, and are not personal fortunes.

Lisk is also not merely a clone as you suggest, but rather a finishing of the job, with certain areas of it completely reimplemented to a higher standard of workmanship.

Thank you.

Yes you can. We will also add a validator to the ICO site to check against our public key record.

There you go: https://cryptichain.lisk.io/tx/4478706938792790370

Crypti was led by a different team which we were a part of, but certainly not in control of.

Max and I are providing new leadership, a better execution of ideas, and an overall greater sense of transparency and openness towards the community.

There are areas of the source code which need to be rethought, some features are missing, dapps need to be developed, therefore the scope for change is quite enormous.

You can follow our work on GitHub, there you will see for yourself the changes we are making.

Thank you.

I'm sure Boris will speak for himself here, but in essence he is working on a new project unrelated to Crypti AFAIK. However, he shall be advising us on future directions and is in regular contact with us.

LISK (quite rightly so), is supporting the Crypti network with delegates and a block explorer throughout the course of the ICO.

The funding and tremendous support we are receiving, will help ensure the technology evolves into something far greater than ever before.

Thank you.

Proof of what exactly? That we accept constructive criticism?

Anyway, sorry we can't please every living soul, but we had to start somewhere.

As previously stated, we will likely rebrand completely, but this will come later.

As far as our stats go, it means 1 user who has completed at least 1 exchange.

We have our own forum: https://forum.lisk.io/, early days, but already we are having some good positive discussions. Feel free to participate.

There is also our chat: https://lisk.chat/home

There is no need to feel repulsed

Deposits are confirmed after 3 confirmations.

^ To the sensitive souls who pointed out the discrepancy in the Top Accounts page of the explorer.

The reason for this is that two (out of five) of our crypti nodes had to be restarted, therefore you were seeing an older version of the blockchain as it reloaded.

I disabled the nodes within the cluster while they finished loading. Now all should be good.

To prevent future confusion, I will likely adjust the block explorer to automatically ignore nodes which are reloading.

If you have any doubts, then I invite you to install a Crypti node: https://github.com/karmacoma/crypti-docs/blob/master/BinaryInstall.md and see for yourself. The source code for the blockchain explorer is also open source: https://github.com/karmacoma/cryptichain#crypti-blockchain-explorer

Each sidechain is discrete, therefore not coupled with the main network.

A total of 101 master nodes can be selected by the dapp's owner, as in public keys are added to the dapp, allowing them to forge blocks on the sidechain.

In the future, this is something we will obviously address. What we have now is a starting point, therefore we will move further away from the model Crypti established as time progresses.

For example, we could implement the same voting mechanism used within the parent network, or maybe the ability to "bid" for a slot on a particular sidechain, we are open to ideas.

The choice of version number is simply an indicator of our desire for a fresh start / new approach.

Although Lisk is a fork of Crypti, and right now the differences are few, this won't be the case forever.

Your confidence will likely increase in the number, when you actually see us deliver what we set out to achieve

BTC Bonuses are allocated based on the BTC transaction time, not the time an exchange was started.

No it's not hacked. We are experiencing difficulties connecting to the ShapeShift API.

Working on it now.

Regarding the current VM, there are more pressing issues that need to be addressed before we turn our attention here.

Having said that, I've already fixed a critical bug affecting the Lisk VM, which was present in the Crypti source code, therefore bug fixes and further stabilisation will be our first top priority.

Later on we will make further improvements, but right now "stablisation" is our main objective.