Quote from: anu on October 14, 2017, 08:43:54 PM

With the similarities of WAVES to Ripple, these two systems are fundamentally dissociating at a very basic point. Similarly, both systems make it possible to export fully reserved crypto-prices to brokerage houses. The point where they decompose, Ripple is not exactly decentralized, and this means that the system can be brought to the system at any time by a restriction. On the other hand, WAVES is a platform based on the decentralized PoSconsensus algorithm. To give an example of the concrete consequences of this deal, I do not know how it is now, but the last time I looked, you had to scan your identity photocopy system to become a member of Ripple. Although I personally think this is a breach of privacy in itself, it is actually a step that can be considered reasonable for many people. But what it expresses is great. For example, If Ripple is forced to make a photocopy of identity today, and then tomorrow will be able to impose other things too. This is contrary to the free nature of the crypto money ecosystem. On the other hand, such situations for WAVES can never be discussed; As is clearly stated in our Vision section, WAVES aims to have no restrictions on the block chain.

Ripple were very aiming to be a protocol of fiat/crypt bridge at initial stage, thus, they are both open to consumer user and companies. But at some point, they shifted their main stream customer to be a banking and they push out existing consumer users by terminating their own wallet/trading system. And let 3rd party to do KYC.

I think exchanges and local fiat currency banks will be the point of KYC requirements. Waves do not need KYC process for now. But if things moving forward and momentum changed, this is may good idea that Waves creating special secured APIs/EDI to those bankings. That may appreciated that those banks can obtain existing consumer users who currently using Waves Clients(I recall names is changing, correct?). Ripple can't make more consumer users if current partnership org charts... especially unuser friendly dead slow Gatehub.

So, I am expecting a lot to Waves in considering current user base of Waves client.