Re: Crypti | XCR | Ͼ | 3 PoS algorithms | Ed25519

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.

Come on Wulf, no one can do everything. There are times that there is a need to call in outside experts who specialize in a certain area. IT is no different than medicine or law Your doctor and lawyer refers to experts all the time.

I am sure, that given enough time our team could come up with a satisfactory solution. But, since we are always thinking of the community, a business decision was made to use some of the IPO funds to hire a specialist. The time saved will benefit all.

Your previous posts were all about "hurry up". Now we "hurry up", and you not happy?

Yes, I realize my previous posts like many others here, were criticizing the slow progress being made, but my concern now is in the Crypti devs ability, or lack thereof, to deliver the rest of the features.

The part that confuses me is that you are hiring an outside expert to analyze an algorithm that has never been implemented anywhere else before, therefore the only real "experts" should be the developers who actually developed the algorithm. I don't know the specifics of the situation so I may be wrong, but you shouldn't be hiring an expert to write the whole algorithm for you (if that is the case).

The outside expert should only be hired to work on specific isolated issues, i.e. latency issues between nodes causing forks, not to re-write the whole algorithm.