Quote from: Wulfcastle on October 23, 2014, 08:19:45 PM

Quote from: Passion_ltc on October 23, 2014, 07:59:34 PM

Quote from: Wulfcastle on October 23, 2014, 07:56:51 PM

Quote from: Litoshi on October 23, 2014, 07:13:44 PM

Quote from: rtrtcrypto on October 23, 2014, 06:33:01 PM

Read my reply months ago, before IPO and you will find me asking for more info on the algo and white paper - reason was to see what sort of technical solutions devs had in mind for the problems they wanted to solve, it became clear devs were not going to release an exact or specific outline of their algo and I bought in anyway. It now appears that there WAS NO defined algo at the time, only an idea of what the algo should accomplish.

They did have a working algo for the PoT. It worked just fine as long as there were not more than 50 nodes up. Once there were more than that, a scaling issue surfaced.

That resulted in most of the nodes not getting any forged blocks, and the nodes with the least latency were getting lots and lots of generated blocks. There were also forks and "forks of forks" as the longer latency nodes were not updated quickly enough. Many transactions showed as confirmed, but were never received, including 1200XCR I sent to my windows wallet/node from Cryptsy (which still has not arrived and not shown in the balance on Cryptsy).

They then reworked the wallet/node to correct any forking at every block, but it did not fix the scaling issue. Several fixes were tested, but were unsatisfactory. Now we have hired a programmer who is very experienced in altcoin programing to write the algo, incorporating the PoT, PoI, PoP, and PoS in the algo.

As a temporary fix, and to get the network up and running, we are now using a random method of picking forgers, just like NODE.

Who have you hired? Secondly why do you need to hire a programmer to code the algorithm in the first place? Is it because the devs themselves can't code it? If so, how do we know that the devs even have the capability to code Custom Blockchain Support and other features planned down the line?

The hired person isn't coding. He is helping our devs with the algorithm design. This is a very critical part and needs to be done 100% correct, that's why several experts need to have their eyes on this.

Had this been open-sourced you could have had a whole bunch of experts look at the code. I understand that the developers don't want clones popping up, but had Crypti been open-sourced in the first place critical issues such as the PoT algo bugs could have been picked up and addressed much earlier. Crypti is kept closed-sourced for the time being as a counter-measure for the spread of its clones, however in my opinion, not open-sourcing Crypti has put the whole project a couple months behind.

You could have countless experts, including Come-from-Beyond (which he requested to), analyse the code had it been open-sourced. If you look at NXT's history, which is what Crypti is most often compared to, you'll see that NXT started to make major leaps in progress once it was open-sourced. Judging from the "Bug Bounty Thread" that was opened with the purpose of offering bounties for bugs that were found in the NXT code-base, there must've been over 30 bugs that were fixed within weeks.

I haven't posted much about this aspect of Crypti before, as there hasn't been the need to, but with these critical problems, I'd say open-sourcing the Crypti code-base (or only the affected parts of it) would go a long way to helping Crypti move forward.

Sorry, but that's not true. Most people don't work without getting paid. Only a handful of guys would take a look at the code, because Crypti is written in Javascript in a C/C++ dominated cryptocurrency space, even less than a handful of guys would have looked at the code.

In NXT's case the development didn't took major leaps in progress once it was open-sourced. Come-from-Beyond is working on the code from the beginning until a few months ago. Jean-Luc is working on it consistently since before it was open-source as well IMO. All other devs came in much later and are still urgently needed.