Bitcoin Forum

The bottom line is that they have made claims about support from various people that were not true.

Could you please elaborate on that? Support from whom?

If you want a safer investment, get some more Bitcoin. If tou are willing to accept high risk/potential high return scenario, jump on board with something like Waves.

You know damn well what I'm talking about. You have posted all over the thread by charles H.

But to others wondering what the hell I'm talking about, go read the other thread.

So was there a claim of kushti support?

Did it turn out to be true?

Another post from me, now on "production readiness".

It is hard to develop a database engine. Jan Kotek is a brilliant dev undoubtly but there's no stable MapDB release around after few years of active development,

Cryptography isn't just hard, its a mess. It is really hard to implement a primitive properly(!) (e.g. a signature scheme). And even a perfect implementation cant' save against improper usage or bad randomness. Things are much harder when we're talking about design and implementation of cryptographic protocols.

A cryptocurrency can dev go nuts. It is a crazy mix of many hard-to-develop things. And if millions of users put billions collectively at stake, software behind that must be polished like a diamond. Unfortunately, amongst thousands of coins(few IPOs to be declared daily on this forum) there are only 1.5 seriously validated systems(so Bitcoin, after few years of issues fixing, see https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures, and partly Ethereum).

So Scorex was declared to be not ready for a production use. Since 1.1.0 modular design is there, so a consensus as well as transactional modules are to be injected into core. Since 1.2.0 only core is to be called Scorex, and our first testnet application running on Permacoin consensus protocol is being called Lagonaki.

Let's take a closer look on readiness of modules:

1. Core: no any protection against any DDoS atm. Peer blacklisting is just done(in 1.2.3). Networking layer is quite raw. Other things in the core are seem to be pretty OK.

2. Nxt-like consensus module: unlike Nxt, "effective balance" == balance and that is trivially insecure. There are many small tweaks in Nxt not copied into the module(I am pretty unsure all of them are adding up to the protocol security though).

3. Qora-like consensus module: again "effective balance" == balance. Aside of that, algo is copied pretty precisely.

4. Permacoin consensus module(https://github.com/ScorexProject/Permacoin-consensus): there are some open question in the protocol design itself (see my paper http://arxiv.org/abs/1603.07926 ). Our implementation isn't tested on really huge datasets.

5. Simplest transactional module. Simplest tokens transfers (like Nxt payments) and nothing more. Protection against double-inclusion is quite stupid(account nonces like in Ethereum are needed).

So yes, all the components must not be used as provided in a popular cryptocurrency. And I'll eventually fix only core issues. I'm going to implement next few modules(more innovative this time) and a new testnet application with working name Ergaki (https://scorex-dev.groups.io/g/main/message/3?p=,,,20,0,0,0:Created,0,,20,1,0,1996315 ).


But Waves doesn't need anything except of core probably. They will build own transactional and consensus modules. Then it is Waves business to prove those modules are shine like a diamond.



P.S. On a team's photo, I was offline for those days, so do not really know what happened. I need to have another call with Sasha to clarify.

kushti is here (writing from a some place in Russia, yes).

First, some historical points. Scorex was started in Nov, 2014 as kinda funny project. To that moment, I spent few months working for Nxt. As you may know, Nxt prevents forking with closing code not released into production yet and also by somewhat terrible licensing(since 1.5?). Anyway, it has a lot of forks, and some of them with very interesting ideas (e.g. BURST).

To have thing open to the extreme I've published Scorex under CC0(Public Domain) license, so everyone can do literally anything with the code.

Since last autumn development of Scorex is subsidized by IOHK, and since Feb I'm a Research Fellow and Scorex project director in IOHK Research.
-------

Well, Scorex(as well as papers publicly published) could be used in any project. That surely does not mean collaboration with IOHK. However, we would like to get issues on core functionality to be reported to resolve and also (and especially) pull requests.  

Me & Sasha, Charles & Sasha, and three of us had some conversations after Sasha's decision to build Waves on top of Scorex. No any collaboration has been established to the moment as a result. And that is surely up to Charles.

I do not endorse neither oppose Waves ICO. I do not have much technical details, and I'm not competent in other topics.

Yeah! Scorex is not production ready. Alex(kushti)'s job is to work on Scorex (through IOHK). As far as I grasp this, Waves is using Scorex (open-source) for their own purpose -- they like the code and the approach. They will have to make it production ready indeed. Sasha and Alex know each other, thus his friend is consulting. Doesn't mean that he has to endorse the/an ICO. He's working for IOHK after all, this is not his main project apparently, and an official collaboration has not been established. Naturally this also means that he has to comply with Charles Hoskinsons' approach.

Lotta noise about... what? ; D

It has came to my attention that project with the most fud have risen the most like Bitcoin, Ethereum, Dash, Waves now etc.

So bring it back to the Op, this ICO seems rushed.

What if it turns out Charles is right? Kushti is an acquaintance of Sasha that much we know. However representing Kushti as a consultant/advisor was/is misleading. It presumes that Kushti is involved in the decision making process and the coding process. Whereas if you read what Kushti wrote. It is up to Waves people to figure out how to make the platform work. And acording to Kushti the platform IS NOT READY to work, and needs lots in order to vet it.

The Waves thread represented their project as Kushti was working on it. In reality Kushti is an acquaintance of Sasha, and they had a conversation or two about Scorex. That does not equal advising or consulting.

Charles is right to distance his organization from Waves. There could be serious legal issues regarding Waves ICO.